Forum - Using my tunnel host as a router for network :: SixXS

Using my tunnel host as a router for network

Shadow Hawkins on Thursday, 07 June 2012 21:51:56

Hi all, I have a problem getting my tunnel host working as router for the rest of my network. I'm probably overlooking something really simple; any tips or pointers would be much appreciated! I have an Ubuntu Server 12.04 host successfully running Aiccu and RADVd. From this host, I can connect to the rest of the IPv6 internet (dancing turtles ahoy!), but the rest of my hosts on my network can't seem to route through it. My network interfaces look like :

eth0 Link encap:Ethernet HWaddr 48:5b:39:0b:80:44 inet addr:192.168.0.105 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: 2a01:348:6:5ee::3/64 Scope:Global inet6 addr: fe80::4a5b:39ff:fe0b:8044/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6046 errors:0 dropped:0 overruns:0 frame:0 TX packets:5033 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1511396 (1.5 MB) TX bytes:942255 (942.2 KB) Interrupt:42 Base address:0xa000 sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::48:6:5ee:2/64 Scope:Link inet6 addr: 2a01:348:6:5ee::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:1040 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:31164 (31.1 KB) TX bytes:110232 (110.2 KB)

So I have eth0 as the "internal" network, and sixxs as the "external". Both have IP addresses manually allocated from my prefix in addition to the link-local addresses. Radvd.conf looks like :

interface eth0 { AdvSendAdvert on; AdvLinkMTU 1280; MaxRtrAdvInterval 300; prefix 2a01:348:6:5ee::/64 { AdvOnLink on; AdvAutonomous on; }; };

And from my Mac Mini, I now have an address of 2a01:348:6:5ee:3e07:54ff:fe51:b796 assigned. So far , so good. I can also ping6 the address of the ubuntu eth0 from my Mac mini :

# ping6 -c2 2a01:348:6:5ee::3 PING6(56=40+8+8 bytes) 2a01:348:6:5ee:3e07:54ff:fe51:b796 --> 2a01:348:6:5ee::3 16 bytes from 2a01:348:6:5ee::3, icmp_seq=0 hlim=64 time=2.470 ms 16 bytes from 2a01:348:6:5ee::3, icmp_seq=1 hlim=64 time=2.666 ms

But, if I try to ping the address of my sixxs interface (2a01:348:6:5ee::2), the ping just hangs. Looking at tcpdump on my Ubuntu box, I see this :

20:44:36.130430 IP6 2a01:348:6:5ee:3e07:54ff:fe51:b796 > ff02::1:ff00:2: ICMP6, neighbor solicitation, who has 2a01:348:6:5ee::2, length 32

And a reply never gets sent. I have net.ipv6.conf.all.forwarding=1 set, so I'm unsure why this is happening. If I try from my Mac to ping any Ipv6 host such as ipv6.google.com or my Sixxs PoP address that fails too, but I thought I'd start right at the basics... Does anyone have any idea what I'm doing wrong ? Thanks, -Mark

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Thursday, 07 June 2012 22:19:49

eth0 Link encap:Ethernet HWaddr 48:5b:39:0b:80:44

inet6 addr: 2a01:348:6:5ee::3/64 Scope:Global

sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

inet6 addr: 2a01:348:6:5ee::2/64 Scope:Global

You have configured the tunnel prefix on eth0. That won't work. You need to use the subnet prefix, in your case 2a01:348:6:85ee::3/64 Thus in radvd.conf: prefix 2a01:348:6:85ee::/64 and all should work like a charm (after having removed the wrong prefix).

Using my tunnel host as a router for network

Shadow Hawkins on Thursday, 07 June 2012 22:46:04

Thank you! I knew it was something stupid I'd done wrong :) -Mark

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Thursday, 07 June 2012 22:50:31

Nothing stupid, just a common misconception, now you know it and won't do it wrong again ;)

Using my tunnel host as a router for network

Shadow Hawkins on Tuesday, 27 November 2012 06:30:16

Hallo Jeroen and all, I too wish to connect my LAN network through the Tunnel. After following this thread and others on this subject I think I may have discovered my problem. My tunnel terminates on a Raspberry Pi router, and I have a server running nicely over the Tunnel. However my Network host PC refuses to talk to the Raspberry Pi router. Please inspect my eth0 and sixxs entries on the Raspberry Pi router. eth0 inet addr: 192.168.1.8 Bcast192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fed4:706c/64 Scope:Link sixxs inet6 addr: fe80::4428:200:59:2 Scope:Link inet6 addr: 2001:4428:200:59::2 Scope:Global I believe I am missing a Scope:Global entry here under eth0 ?? What should it be ?? inet6 addr: 2001:4428:200:159::2 ?? Thanks Gordon

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Tuesday, 27 November 2012 07:53:28

I believe I am missing a Scope:Global entry here under eth0 ??

Indeed

What should it be ??

An address out of a subnet.

inet6 addr: 2001:4428:200:159::2 ??

No, that is not an address/prefix assigned to you. Check your user home where you will find a section called 'subnets' where you will have a list of subnets for your tunnels. In this case for you that is thus 2001:4428:200:8059::/64. See also FAQ: How do I give connectivity to other hosts on my subnet?

Using my tunnel host as a router for network

Shadow Hawkins on Wednesday, 28 November 2012 09:38:32

Hi Jeroen, Many thanks, yes that was my problem. Working ok now. Gordon

Using my tunnel host as a router for network

Shadow Hawkins on Thursday, 21 February 2013 08:20:30

Thanks for this. I've been trying to figure that out for a while myself too. Now have full ipv6 connectivity on all of my lan. Next step might be to set up ip6tables so I don't have more connectivity than I can really handle ;)

Using my tunnel host as a router for network

Shadow Hawkins on Thursday, 04 April 2013 02:49:17

i already has installed radvd and aiccu on my ubuntu and enable net.ipv6.conf.all.forwarding = 1. i already setting up the radvd.conf with my subnet prefix which is 2401:e800:100:8098::/64. when i test it in my win7, i already get an ipv6 address like 2401:e800:100:8098:xxxx:xxxx:xxxx:xxxx/64. i'm able to ping my ubuntu (2401:e800:100:8098::1/64), my sixxs tunnel interface 2401:e800:100:98::2/64 and so do my ipv6 prefix from sixxs which is 2401:e800:100:98::1/64 from win7. but i still wonder why i can't ping the ipv6 sites from win7 ??? the result is destination host unreachable. any help will be very much appreciated, this is for my thesis. i'm sorry if i have some terrible english.

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Thursday, 04 April 2013 07:38:02

i'm able to ping my ubuntu (2401:e800:100:8098::1/64), my sixxs tunnel interface 2401:e800:100:98::2/64 and so do my ipv6 prefix from sixxs which is 2401:e800:100:98::1/64 from win7. but i still wonder why i can't ping the ipv6 sites from win7 ??? the result is destination host unreachable.

Which router is returning that error? A traceroute6 to the destination address will already give some insight in which nodes are properly routing. You might also want to show the networking configuration of both the ubuntu (ip -6 addr show; ip -6 ro show) and the windows box (ipconfig /all).

Using my tunnel host as a router for network

Shadow Hawkins on Friday, 05 April 2013 06:16:53

Which router is returning that error?

Win7, but it's not a router anyway. It's a client. I want my ubuntu tunnel turn as a router so that it can share the ipv6 connection with my client (win7). I connected the tunnel via wlan and eth0 is my interface card that connect between router and client. Ubuntu router has enable to access ipv6 sites.

You might also want to show the networking configuration of both the ubuntu (ip -6 addr show; ip -6 ro show) and the windows box (ipconfig /all).

In my ubuntu machine

mer@mer-1015PW:~$ sudo ip -6 addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 2401:e800:100:8098::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::f66d:4ff:fe17:c515/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::e2b9:a5ff:fe66:9c49/64 scope link valid_lft forever preferred_lft forever 5: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500 inet6 2401:e800:100:98::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::e800:100:98:2/64 scope link valid_lft forever preferred_lft forever

mer@mer-1015PW:~$ sudo ip -6 ro sho 2001:470:35:a21::2 dev eth0 proto static metric 1024 2401:e800:100:98::/64 dev sixxs proto kernel metric 256 2401:e800:100:8098::/64 dev eth0 proto kernel metric 256 fe80::/64 dev sixxs proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev wlan0 proto kernel metric 256 default via 2401:e800:100:98::1 dev sixxs metric 1024 default via 2001:470:35:a21::2 dev eth0 proto static metric 1024

In my Win7

Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2401:e800:100:8098:f0fb:d562:f361:9632 Temporary IPv6 Address. . . . . . : 2401:e800:100:8098:b8c5:4f96:5590:2304 Link-local IPv6 Address . . . . . : fe80::f0fb:d562:f361:9632%11 IPv4 Address. . . . . . . . . . . : 192.168.1.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1

these are the results when i try to ping

C:\Windows\System32>ping 2401:e800:100:98::2 Pinging 2401:e800:100:98::2 with 32 bytes of data: Reply from 2401:e800:100:98::2: time=1ms Reply from 2401:e800:100:98::2: time<1ms Reply from 2401:e800:100:98::2: time<1ms Reply from 2401:e800:100:98::2: time<1ms Ping statistics for 2401:e800:100:98::2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms C:\Windows\System32>ping 2401:e800:100:98::1 Pinging 2401:e800:100:98::1 with 32 bytes of data: Reply from 2401:e800:100:98::1: time=215ms Reply from 2401:e800:100:98::1: time=212ms Reply from 2401:e800:100:98::1: time=238ms Reply from 2401:e800:100:98::1: time=285ms Ping statistics for 2401:e800:100:98::1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 212ms, Maximum = 285ms, Average = 237ms C:\Windows\System32>ping 2401:e800:100:8098::1 Pinging 2401:e800:100:8098::1 with 32 bytes of data: Reply from 2401:e800:100:8098::1: time=1ms Reply from 2401:e800:100:8098::1: time<1ms Reply from 2401:e800:100:8098::1: time<1ms Reply from 2401:e800:100:8098::1: time<1ms Ping statistics for 2401:e800:100:8098::1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms C:\Windows\System32>ping ipv6.google.com Ping request could not find host ipv6.google.com. Please check the name and try again. C:\Windows\System32>ping www.kame.net Ping request could not find host www.kame.net. Please check the name and try again.

Sorry, if i'm confusing you.

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Friday, 05 April 2013 08:23:36

Merlie Anita wrote:

Win7, but it's not a router anyway. It's a client.

(Every node is a router in a sense, as they have a local routing table) It likely means that you do not have a proper default route though on that host.

mer@mer-1015PW:~$ sudo ip -6 ro sho

2001:470:35:a21::2 dev eth0 proto static metric 1024

Seems you have something old lingering there.

default via 2401:e800:100:98::1 dev sixxs metric 1024

default via 2001:470:35:a21::2 dev eth0 proto static metric 1024

And those two default routes are not going to help you either. You will want to remove the latter one.

It seems you did not get a default route there (as there is no IPv6 Gateway), which is a bit strange. Can you cut & paste the full output of 'netstat -rn'? That should clarify this quite a bit.

Pinging 2401:e800:100:98::1 with 32 bytes of data:

Reply from 2401:e800:100:98::1: time=215ms

That definitely shows that you can route to the other side though which is counter to what you see above.

C:\Windows\System32>ping ipv6.google.com

Ping request could not find host ipv6.google.com. Please check the name and try again.

That looks like a DNS server problem. But try 'ping -6 ipv6.google.com' instead, that forces IPv6. If that also does not work, type 'nslookup' in a command prompt and then type 'ipv6.google.com' that should return the IPv6 address. If it does not it might be that your DNS server is dropping AAAA queries or is otherwise misconfigured.

Using my tunnel host as a router for network

Shadow Hawkins on Friday, 05 April 2013 12:34:10

Seems you have something old lingering there.

And those two default routes are not going to help you either. You will want to remove the latter one.

Seems like I have remove the latter one and it becomes like this:

mer@mer-1015PW:~$ ip -6 ro sho 2401:e800:100:98::/64 dev sixxs proto kernel metric 256 2401:e800:100:8098::/64 dev eth0 proto kernel metric 256 fe80::/64 dev sixxs proto kernel metric 256 fe80::/64 dev wlan0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 default via 2401:e800:100:98::1 dev sixxs metric 1024

and then i restart radvd service (am i doing right???).

It seems you did not get a default route there (as there is no IPv6 Gateway), which is a bit strange.

I thought it's given automatically since ubuntu using radvd to advertising the route.

That looks like a DNS server problem.

Actually I'm a little bit confused with dns concept in ipv6 with AAAA things :-) and I'm pretty sure that this is the main problem. But I dont know, maybe you have different thought after seeing this result:

C:\Windows\System32>netstat -rn =========================================================================== Interface List 23...06 24 2b 5e 64 24 ......Microsoft Virtual WiFi Miniport Adapter 12...00 24 2b 5e 64 24 ......Atheros AR5007EG Wireless Network Adapter 11...00 1e ec de ef 47 ......Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NI .20) 21...08 00 27 00 80 69 ......VirtualBox Host-Only Ethernet Adapter 1...........................Software Loopback Interface 1 33...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #6 39...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 30...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #3 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 22...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5 32...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #5 29...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #2 31...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #4 37...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #10 35...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #8 34...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #7 36...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #9 38...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.2 276 192.168.1.2 255.255.255.255 On-link 192.168.1.2 276 192.168.1.255 255.255.255.255 On-link 192.168.1.2 276 192.168.56.0 255.255.255.0 On-link 192.168.56.1 276 192.168.56.1 255.255.255.255 On-link 192.168.56.1 276 192.168.56.255 255.255.255.255 On-link 192.168.56.1 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.56.1 276 224.0.0.0 240.0.0.0 On-link 192.168.1.2 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.56.1 276 255.255.255.255 255.255.255.255 On-link 192.168.1.2 276 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.1.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 11 276 ::/0 fe80::f66d:4ff:fe17:c515 1 306 ::1/128 On-link 11 28 2401:e800:100:8098::/64 On-link 11 276 2401:e800:100:8098:444c:9598:1d32:9210/128 On-link 11 276 2401:e800:100:8098:f0fb:d562:f361:9632/128 On-link 21 276 fe80::/64 On-link 11 276 fe80::/64 On-link 21 276 fe80::ece9:75e4:cb8d:a28f/128 On-link 11 276 fe80::f0fb:d562:f361:9632/128 On-link 1 306 ff00::/8 On-link 21 276 ff00::/8 On-link 11 276 ff00::/8 On-link =========================================================================== Persistent Routes: None

C:\Windows\System32>ping google.com Ping request could not find host google.com. Please check the name and try again.

C:\Windows\System32>ping -6 ipv6.google.com Ping request could not find host ipv6.google.com. Please check the name and try again.

C:\Windows\System32>nslookup DNS request timed out. timeout was 2 seconds. Default Server: UnKnown Address: 8.8.8.8

ipv6.google.com

Server: UnKnown Address: 8.8.8.8 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out

what should i do then???

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Friday, 05 April 2013 13:32:07

and then i restart radvd service (am i doing right???).

No need to restart radvd, unless you are using the "prefix ::" method, but then it should also detect that change hopefully.

I thought it's given automatically since ubuntu using radvd to advertising the route.

It should but it seems it did not.

Actually I'm a little bit confused with dns concept in ipv6 with AAAA things :-)

One can ask for both A and AAAA records over IPv4 and IPv6 DNS transport.

32...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #5 29...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #2 31...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #4 37...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #10 35...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #8 34...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #7 36...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #9

Those look very strange. You might want to try a 'netsh int ipv6 reset' or the windows 7 equivalent, or better still, disable 6to4 altogether.

C:\Windows\System32>nslookup DNS request timed out. timeout was 2 seconds. Default Server: UnKnown Address: 8.8.8.8 ipv6.google.com Server: UnKnown Address: 8.8.8.8 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out

Looks to me that your DNS server is misconfigured completely. Instead of trying to use the Google Public DNS at 8.8.8.8 try using a local DNS recursor.

Using my tunnel host as a router for network

Shadow Hawkins on Monday, 08 April 2013 09:36:54

i made a connection between 2 laptop with ubuntu installed and it works (each laptop with ubuntu). So i conclude the problem is in my win7 with all these microsoft 6to4 adapter. i give up to fix it in windows since 'netsh int ipv6 reset' didn't work (-,-'). i have another question, is it possible for me to build this network scheme?? -----|tunnel|-------|ubuntu|-------|mikrotik|-----|client|-------- the story is still the old one. these are ifconfig in ubuntu: mer@mer-laptop:~$ ifconfig | grep addr eth0 Link encap:Ethernet HWaddr 08:00:27:54:27:3e inet addr:202.11.17.1 Bcast:202.11.17.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe54:273e/64 Scope:Link eth1 Link encap:Ethernet HWaddr 08:00:27:e1:de:79 inet addr:192.168.86.1 Bcast:192.168.86.255 Mask:255.255.255.0 inet6 addr: 2401:e800:100:8098::1/64 Scope:Global inet6 addr: fe80::a00:27ff:fee1:de79/64 Scope:Link inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2401:e800:100:98::2/64 Scope:Global inet6 addr: fe80::e800:100:98:2/64 Scope:Link I only have one subnet (2401:e800:100:8098::/64) in my sixxs account. I've been testing these configuration in other ubuntu machine and it did worked. I can access ipv6 sites so did the sixxs tunnel.

Using my tunnel host as a router for network

Jeroen Massar SixXS Staff

on Monday, 08 April 2013 14:13:38

Merlie Anita wrote:

-----|tunnel|-------|ubuntu|-------|mikrotik|-----|client|-------- [..] I only have one subnet (2401:e800:100:8098::/64) in my sixxs account.

You would have to request a subnet, and then you can delegate /64's out of that to other hosts.

Using my tunnel host as a router for network

Shadow Hawkins on Tuesday, 09 April 2013 12:57:18

Thanks a ton, Jeroen. It helps me a lot. I will ask another subnet to make my ipv6 network.

Please note Posting is only allowed when you are logged in.