Discussion:
Packet looping back to...
Oliver Belikan
2005-01-10 01:44:34 UTC
Permalink
Hi,

I use tinc1.0.3 with a WinXP SP2 box to connect to a linux-server. After
startup of tincd the connection from XP-box (Oliver) is established but
i receive a routing error:

"Cannot route packet from Oliver (MYSELF): unknown IPv4 destination
address 224.0.0.22" and
"Packet looping back to Oliver (MYSELF)!"

I?ve no idea where the address 224.0.0.22 comes from. My hosts file is:

/hosts/Oliver
Subnet = 192.168.4.0/24
-----BEGIN RSA PUBLIC KEY.................

In TAP-Device i use
IP: 192.168.4.1
Mask: 255.255.255.0


I tried to change "Subnet = 192.168.4.0/32" in hosts/Oliver, but
received no other result.

Any ideas what is wrong ?
Thank you.
Guus Sliepen
2005-01-10 04:35:36 UTC
Permalink
Post by Oliver Belikan
"Cannot route packet from Oliver (MYSELF): unknown IPv4 destination
address 224.0.0.22" and
"Packet looping back to Oliver (MYSELF)!"
The 224.0.0.22 thing is Windows trying doing some kind of autodetection
Post by Oliver Belikan
In TAP-Device i use
IP: 192.168.4.1
Mask: 255.255.255.0
I tried to change "Subnet = 192.168.4.0/32" in hosts/Oliver, but
received no other result.
You should change it to Subnet = 192.168.4.1/32.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <***@sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20050109/f4a9230b/attachment.pgp
Oliver Belikan
2005-01-10 06:22:55 UTC
Permalink
Ok thank you.
I changed /host/Oliver to 192.168.4.1/32 and as a result the "Packet
looping back..." seems to be gone, but the entry "Cannot route packet
from Oliver (MYSELF): unknown IPv4 destination address 192.168.4.255" is
still to see in the logfile.

No ping, no ssh is possible from the Win XP box. Needs Win XP some
special running (remote)-services ?

Again my Files:
\hosts\Oliver
Subnet = 192.168.4.1/32
Address = 192.168.4.1
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----


\hosts\Server
Subnet = 192.168.10.0/24
Address = 217.24.201.66
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----

IP TapWin32-Adapter: 192.168.4.1
Subnetmask: 255.255.255.0



Win XP SP2 Firwall is temporary switched off.


Logfile:
1105313169 tinc.vpn[2616]: Read packet of 110 bytes from Windows tap
device
1105313169 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313169 tinc.vpn[2616]: Writing packet of 138 bytes to Windows tap
device
1105313170 tinc.vpn[2616]: Read packet of 110 bytes from Windows tap
device
1105313170 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313170 tinc.vpn[2616]: Writing packet of 138 bytes to Windows tap
device
1105313171 tinc.vpn[2616]: Read packet of 110 bytes from Windows tap
device
1105313171 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313171 tinc.vpn[2616]: Writing packet of 138 bytes to Windows tap
device
1105313171 tinc.vpn[2616]: Read packet of 110 bytes from Windows tap
device
1105313171 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313171 tinc.vpn[2616]: Writing packet of 138 bytes to Windows tap
device
1105313172 tinc.vpn[2616]: Read packet of 678 bytes from Windows tap
device
1105313172 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313172 tinc.vpn[2616]: Writing packet of 590 bytes to Windows tap
device
1105313172 tinc.vpn[2616]: Read packet of 246 bytes from Windows tap
device
1105313172 tinc.vpn[2616]: Cannot route packet from Oliver (MYSELF):
unknown IPv4 destination address 192.168.4.255
1105313172 tinc.vpn[2616]: Writing packet of 274 bytes to Windows tap
device


-----Urspr?ngliche Nachricht-----
Von: tinc-***@tinc-vpn.org [mailto:tinc-***@tinc-vpn.org] Im
Auftrag von Guus Sliepen
Gesendet: Sonntag, 9. Januar 2005 22:36
An: ***@tinc-vpn.org
Betreff: Re: Packet looping back to...
Post by Oliver Belikan
"Cannot route packet from Oliver (MYSELF): unknown IPv4 destination
address 224.0.0.22" and "Packet looping back to Oliver (MYSELF)!"
I?ve no idea where the address 224.0.0.22 comes from. My hosts file
The 224.0.0.22 thing is Windows trying doing some kind of autodetection
Post by Oliver Belikan
In TAP-Device i use
IP: 192.168.4.1
Mask: 255.255.255.0
I tried to change "Subnet = 192.168.4.0/32" in hosts/Oliver, but
received no other result.
You should change it to Subnet = 192.168.4.1/32.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <***@sliepen.eu.org>
Guus Sliepen
2005-01-10 06:49:42 UTC
Permalink
Post by Oliver Belikan
Ok thank you.
I changed /host/Oliver to 192.168.4.1/32 and as a result the "Packet
looping back..." seems to be gone, but the entry "Cannot route packet
from Oliver (MYSELF): unknown IPv4 destination address 192.168.4.255" is
still to see in the logfile.
192.168.4.255 is caused, again, by Windows trying to autodetect
whatever.
Post by Oliver Belikan
No ping, no ssh is possible from the Win XP box. Needs Win XP some
special running (remote)-services ?
\hosts\Oliver
Subnet = 192.168.4.1/32
Address = 192.168.4.1
Remove that Address line or change it to the public IP address of
Oliver.
Post by Oliver Belikan
\hosts\Server
Subnet = 192.168.10.0/24
IP TapWin32-Adapter: 192.168.4.1
Subnetmask: 255.255.255.0
You should change the subnet mask to 255.255.0.0.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <***@sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20050110/3fe2819e/attachment.pgp
Continue reading on narkive:
Loading...