Metadata socket and net2str() error
Fredrik Björk
Fredrik.Bjork.List at varbergenergi.se
Mon Jul 8 08:11:50 CEST 2002
Hi!
It seems you should read the documentation again. Even if I don't agree
100% with the IP addressing policy of tap0 in there, it works and is simple
enough to set up. If you want to use the same IP addresses for both the
server and the client, you cannot route packets between them, but you have
to bridge (like a switch) or repeat the traffic (like a hub, not
recommended). In your setup you don't explicitly state that you want
bridging, and tinc then defaults to routing. You also have the same subnet
(192.160.0/24) on both eth1 interfaces, and routing is hard to do then...
/Fredrik
At 23:40 2002-07-07 +0200, you wrote:
>Oops, silly me.
>My name is Arno van der Kolk, by the way. ;)
>
>
>I have been reading some more through the mail archive and have enabled
>debug level 5. It seems both hosts are ping-ponging quite nicely.
>
>However, I have also found out the following:
>
>Client:~$ ping 10.0.0.1
>PING 10.0.0.1 (10.0.0.1): 56 data bytes
>
>--- 10.0.0.1 ping statistics ---
>3 packets transmitted, 0 packets received, 100% packet loss
>
>
>Generates the following in the log:
>
>Jul 7 23:21:53 Client tinc.iwan[273]: Read packet of 249 bytes from Linux
>ethertap device
>Jul 7 23:21:53 Client tinc.iwan[273]: Sending packet of 249 bytes to Client
>(MYSELF)
>Jul 7 23:21:53 Client tinc.iwan[273]: Packet is looping back to us!
>
>This goes for both hosts.
>
>----------------------------------------------
>
>More information
>
>The routing table for the Server looks like this:
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use
>Iface
>192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
>217.x.x.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
>10.0.0.0 10.0.0.3 255.255.0.0 UG 0 0 0 tap0
>10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tap0
>0.0.0.0 217.120.198.1 0.0.0.0 UG 0 0 0 eth0
>
>The routing table for the Client looks like this:
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use
>Iface
>192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
>10.0.0.0 10.0.0.1 255.255.0.0 UG 0 0 0 tap0
>10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tap0
>10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tap0
>0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
>
>The duplicate entries for the tap0 device are because of some experimenting,
>normally there's only one (!! without a gateway !!).
>
>Here's also the output of ifconfig...
>
>ifconfig on the Server:
>
>eth0 Link encap:Ethernet HWaddr 00:00:C5:0D:F1:A9
> inet addr:217.x.x.22 Bcast:217.x.x.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:15412 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4380 errors:0 dropped:0 overruns:0 carrier:0
> collisions:103 txqueuelen:100
> RX bytes:2506803 (2.3 MiB) TX bytes:3599805 (3.4 MiB)
> Interrupt:10 Base address:0xfc80
>
>eth1 Link encap:Ethernet HWaddr 00:20:18:39:2B:2F
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8683 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9515 errors:0 dropped:0 overruns:0 carrier:0
> collisions:6 txqueuelen:100
> RX bytes:4069422 (3.8 MiB) TX bytes:2289202 (2.1 MiB)
> Interrupt:9 Base address:0xff40
>
>lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:120 errors:0 dropped:0 overruns:0 frame:0
> TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:12880 (12.5 KiB) TX bytes:12880 (12.5 KiB)
>
>tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:500 (500.0 b)
> Interrupt:5
>
>ifconfig on the Client:
>
>eth0 Link encap:Ethernet HWaddr 00:AA:00:35:7F:51
> inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2253 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4892 errors:0 dropped:0 overruns:0 carrier:0
> collisions:3 txqueuelen:100
> RX bytes:210815 (205.8 KiB) TX bytes:269997 (263.6 KiB)
> Interrupt:10 Base address:0x300
>
>lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)
>
>tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
> inet addr:10.0.0.3 Bcast:10.255.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:14278 (13.9 KiB)
> Interrupt:5
>
>
>
>Again, any help would be appreciated because I still don't know what the
>problem is; everything looks alright to me. Thanks.
>
>Arno
>Tinc: Discussion list about the tinc VPN daemon
>Archive: http://mail.nl.linux.org/lists/
>Tinc site: http://tinc.nl.linux.org/
Tinc: Discussion list about the tinc VPN daemon
Archive: http://mail.nl.linux.org/lists/
Tinc site: http://tinc.nl.linux.org/
More information about the Tinc
mailing list