AW: Packet looping back to...

[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.

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-bounces at tinc-vpn.org [mailto:tinc-bounces at tinc-vpn.org] Im
Auftrag von Guus Sliepen
Gesendet: Sonntag, 9. Januar 2005 22:36
An: tinc at tinc-vpn.org
Betreff: Re: Packet looping back to...


On Sun, Jan 09, 2005 at 07:52:46PM +0100, Oliver Belikan wrote:

> "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:

The 224.0.0.22 thing is Windows trying doing some kind of autodetection
stuff. Just ignore it. As for the packets looping back:

> 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 <guus at sliepen.eu.org>