Viktors Žilinskis wrote: > Hello, again! > > I was following that example indeed. Thanks a lot for your time, I got it > work at home :) > Excellent. :-) Glad we could help. > Hard to understand these things when you've never managed more that 3 PCs. > Tomorrow I'll check it at office, > I hope the result will be no different. While this is not of primary concern > at the moment may I ask your comment on these "logs": > > ########### > # @SERVER # > ########### > > # ping -v 10.20.40.2 > PING 10.20.40.2 (10.20.40.2): 56 data bytes > 64 bytes from 10.20.40.2: icmp_seq=0 ttl=128 time=96.480 ms > 64 bytes from 10.20.40.2: icmp_seq=1 ttl=128 time=83.773 ms > 36 bytes from 188.Red-83-50-137.dynamicIP.rima-tde.net (83.50.137.188): > Destination Port Unreachable > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 9300 ea5a 0 0000 30 11 9320 XX.XXX.XXX.XXX 83.50.137.188 > UDP: from port 2885, to port 17353 (decimal) > > 36 bytes from 225.Red-88-19-105.staticIP.rima-tde.net (88.19.105.225): > Destination Port Unreachable > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 9300 ea7f 0 0000 30 11 adf5 XX.XXX.XXX.XXX 88.19.105.225 > UDP: from port 2885, to port 22204 (decimal) > > 36 bytes from 236.Red-81-38-15.dynamicIP.rima-tde.net (81.38.15.236): > Destination Port Unreachable > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 6100 eabc 0 0000 30 11 0ecd XX.XXX.XXX.XXX 81.38.15.236 > UDP: from port 2885, to port 21285 (decimal) > > 64 bytes from 10.20.40.2: icmp_seq=2 ttl=128 time=50.530 ms > 36 bytes from 171.Red-83-42-32.dynamicIP.rima-tde.net (83.42.32.171): > Destination Port Unreachable > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 9300 ea43 0 0000 30 11 fc50 XX.XXX.XXX.XXX 83.42.32.171 > UDP: from port 2885, to port 22682 (decimal) > > 36 bytes from 134.Red-83-36-72.dynamicIP.rima-tde.net (83.36.72.134): > Destination Port Unreachable > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 9300 eb18 0 0000 30 11 d3a6 XX.XXX.XXX.XXX 83.36.72.134 > UDP: from port 2885, to port 16431 (decimal) > > ####### > # EOF # > ####### > > What's that 188.Red-83-50-137.dynamicIP.rima-tde.net and others? Is it > something I just don’t understand or is it some crap that shouldn't be there? > Something strange is happening with your routing? What's the output of your routing table?
> ########### > # @CLIENT # > ########### > > Received packet of 74 bytes from lenovo_server (XX.XXX.XXX.XXX port 655) > Writing packet of 74 bytes to Windows tap device > Read packet of 175 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 239.255.255.250 > Writing packet of 203 bytes to Windows tap device > Read packet of 230 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > Writing packet of 258 bytes to Windows tap device > Read packet of 74 bytes from Windows tap device > Sending packet of 74 bytes to lenovo_server (XX.XXX.XXX.XXX port 655) > Sending PACKET to lenovo_server (XX.XXX.XXX.XXX port 655): 17 74 > Sending 6 bytes of metadata to lenovo_server (XX.XXX.XXX.XXX port 655) > Sending 74 bytes of metadata to lenovo_server (XX.XXX.XXX.XXX port 655) > Flushing 80 bytes to lenovo_server (XX.XXX.XXX.XXX port 655) > Got PACKET from lenovo_server (XX.XXX.XXX.XXX port 655): 17 74 > Received packet of 74 bytes from lenovo_server (XX.XXX.XXX.XXX port 655) > Writing packet of 74 bytes to Windows tap device > Read packet of 110 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > Writing packet of 138 bytes to Windows tap device > Read packet of 110 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > Writing packet of 138 bytes to Windows tap device > Read packet of 110 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > Writing packet of 138 bytes to Windows tap device > Read packet of 175 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 239.255.255.250 > Writing packet of 203 bytes to Windows tap device > Read packet of 110 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > Writing packet of 138 bytes to Windows tap device > Read packet of 110 bytes from Windows tap device > Cannot route packet from lenovo_client (MYSELF): unknown IPv4 destination > address 10.20.40.255 > > ####### > # EOF # > ####### > It's just windows doing a network broadcast NETBIOS thing. You're running tinc in the default "router" mode - It doesn't support broadcast addresses. Nothing to worry about. > So here is fragment from level 5 debug as Mike had suggested, and I have two > questions. First - is this "unknown IPv4 destination address 10.20.40.255" > message ok, or it point out a problem. And the second one - why in the earth > does it care about some 239.255.255.250 addresses? > > I feel like I should RTFM again, but this time I will think why it does work, > not fails to do so :D > Good Luck, Mike > Best Regards, > Viktors Žilinskis > > _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
