SixXS::Sunset 2017-06-06

Subnet host fails to reach the ::1 Pop
[be] Shadow Hawkins on Sunday, 25 January 2009 11:37:01
Hi, first message here, I tried to configure a subnet, all the ICMP requests from my subnet host are working but not for the ::1 Tunnel. I think i'm missing a route somewhere else, but after reading a lot of posts I didn't find a solution. The Ubuntu 8.10 is the router and I connected a WinXP on eth0 , local 2001 pings are working perfectly between the two hosts The Windows XP subnet is capable to ping the local ::2 of the tunnel but not the ::1 PoP All the iptables and ip6tables are on ACCEPT I think the problem is from the Wireless, my Ubuntu router is connected in Wireless (computers are upstairs) I can't connect them to a wired network. The Windows XP that recieve the subnet ip's is directly wired connected to the eth0 of Ubuntu. He has also a Wireless connection, do I have to desactivate it ? Thank you for reading my text and trying to help me to fix this :-) My configuration : ------------------- #################### Ubuntu 8.10 Router # #################### ####################################### SIXXS Tunnel : 2001:6f8:202:352::1/64 # SIXXS Subnet : 2001:6f8:1439::/48 # ####################################### ########## IFCONFIG # ########## root@NotebookFx2:/home/fxm# ifconfig ath0 Link encap:Ethernet HWaddr 00:c0:a8:b0:d8:ea inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:a8ff:feb0:d8ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5087 errors:0 dropped:0 overruns:0 frame:0 TX packets:3554 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1736443 (1.7 MB) TX bytes:333492 (333.4 KB) eth0 Link encap:Ethernet HWaddr 00:40:d0:8b:01:cf inet6 addr: 2001:6f8:1439:0:240:d0ff:fe8b:1cf/64 Scope:Global inet6 addr: fe80::240:d0ff:fe8b:1cf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:181 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:32609 (32.6 KB) TX bytes:4188 (4.1 KB) Interrupt:23 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:584 (584.0 B) TX bytes:584 (584.0 B) sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2001:6f8:202:352::2/64 Scope:Global inet6 addr: fe80::4f8:202:352:2/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:553 errors:0 dropped:0 overruns:0 frame:0 TX packets:306 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:697539 (697.5 KB) TX bytes:23359 (23.3 KB) wifi0 Link encap:UNSPEC HWaddr 00-C0-A8-B0-D8-EA-30-30-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:51413 errors:0 dropped:0 overruns:0 frame:4087 TX packets:4230 errors:4 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:5740167 (5.7 MB) TX bytes:444025 (444.0 KB) Interrupt:19 ################ /etc/radvd.conf# ################ interface eth0 { AdvSendAdvert on; prefix 2001:6f8:1439::/64 { AdvOnLink on; AdvAutonomous on; }; }; ######### Forward # ######### root@NotebookFx2:/home/fxm# sysctl -a 2>/dev/null |grep forwarding|grep ipv6 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.lo.forwarding = 1 net.ipv6.conf.eth0.forwarding = 1 net.ipv6.conf.wifi0.forwarding = 1 net.ipv6.conf.ath0.forwarding = 1 net.ipv6.conf.sit0.forwarding = 1 net.ipv6.conf.pan0.forwarding = 1 net.ipv6.conf.sixxs.forwarding = 1 root@NotebookFx2:/home/fxm# ######## routes # ######## root@NotebookFx2:/home/fxm# ip -6 ro 2001:6f8:202:352::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 2001:6f8:1439::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2000::/3 via 2001:6f8:202:352::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev ath0 proto kernel metric 256 mtu 1300 advmss 1240 hoplimit 4294967295 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:6f8:202:352::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 ################### ping6 google : ok # ################### root@NotebookFx2:/home/fxm# ping6 ipv6.google.com PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes 64 bytes from 2001:4860:0:1001::68: icmp_seq=1 ttl=53 time=33.7 ms ############### Windows XP SP3# ############### ########## IPconfig # ########## C:\Documents and Settings\Fx>ipconfig Configuration IP de Windows Carte Ethernet Connexion au réseau local: Suffixe DNS propre à la connexion : Autoconfiguration d'adresse IP. . : 169.254.102.68 Masque de sous-réseau . . . . . . : 255.255.0.0 Adresse IP. . . . . . . . . . . . : 2001:6f8:1439:0:b8d2:9955:32b8:9d6d Adresse IP. . . . . . . . . . . . : 2001:6f8:1439:0:240:d0ff:fe67:840e Adresse IP. . . . . . . . . . . . : fe80::240:d0ff:fe67:840e%4 Passerelle par défaut . . . . . . : Carte Ethernet Connexion réseau sans fil: Suffixe DNS propre à la connexion : Adresse IP. . . . . . . . . . . . : 192.168.2.222 Masque de sous-réseau . . . . . . : 255.255.255.0 Adresse IP. . . . . . . . . . . . : fe80::2c0:49ff:fedb:4db7%5 Passerelle par défaut . . . . . . : 192.168.2.1 Carte Ethernet aiccu: Statut du média . . . . . . . . . : Média déconnecté Carte Tunnel Teredo Tunneling Pseudo-Interface : Suffixe DNS propre à la connexion : Adresse IP. . . . . . . . . . . . : fe80::ffff:ffff:fffd%7 Passerelle par défaut . . . . . . : Carte Tunnel Automatic Tunneling Pseudo-Interface : Suffixe DNS propre à la connexion : Adresse IP. . . . . . . . . . . . : fe80::5efe:169.254.102.68%2 Passerelle par défaut . . . . . . : Carte Tunnel Automatic Tunneling Pseudo-Interface : Suffixe DNS propre à la connexion : Adresse IP. . . . . . . . . . . . : fe80::5efe:192.168.2.222%2 Passerelle par défaut . . . . . . : ###################### ping6 to eth0 Ubuntu # ###################### C:\Documents and Settings\Fx>ping6 2001:6f8:1439:0:240:d0ff:fe8b:1cf Envoi d'une requête 'Ping' 2001:6f8:1439:0:240:d0ff:fe8b:1cf à partir de 2001:6f8:1439:0:b8d2:9955:32b8:9d6d avec 32 octets de données : Réponse de 2001:6f8:1439:0:240:d0ff:fe8b:1cf : octets = 32 temps=1 ms Réponse de 2001:6f8:1439:0:240:d0ff:fe8b:1cf : octets = 32 temps<1ms Réponse de 2001:6f8:1439:0:240:d0ff:fe8b:1cf : octets = 32 temps<1ms Réponse de 2001:6f8:1439:0:240:d0ff:fe8b:1cf : octets = 32 temps<1ms Statistiques de Ping pour 2001:6f8:1439:0:240:d0ff:fe8b:1cf : Paquets : envoyés = 4, reçus = 4, perdus = 0 (0% de perte), Durée approximative des boucles en millisecondes : Minimum = 0ms, maximum = 1ms, moyenne = 0ms ########################### ping6 to sixxs ::2 Ubuntu # ########################### C:\Documents and Settings\Fx>ping6 2001:6f8:202:352::2 Envoi d'une requête 'Ping' 2001:6f8:202:352::2 à partir de 2001:6f8:202:352::2 avec 32 octets de données : Réponse de 2001:6f8:202:352::2 : octets = 32 temps<1ms Réponse de 2001:6f8:202:352::2 : octets = 32 temps<1ms Réponse de 2001:6f8:202:352::2 : octets = 32 temps<1ms Réponse de 2001:6f8:202:352::2 : octets = 32 temps<1ms Statistiques de Ping pour 2001:6f8:202:352::2 : Paquets : envoyés = 4, reçus = 4, perdus = 0 (0% de perte), Durée approximative des boucles en millisecondes : Minimum = 0ms, maximum = 0ms, moyenne = 0ms ########################### ping6 to sixxs ::1 Ubuntu # ########################### C:\Documents and Settings\Fx>ping6 2001:6f8:202:352::1 Envoi d'une requête 'Ping' 2001:6f8:202:352::1 à partir de 2001:6f8:202:352::2 avec 32 octets de données : Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Statistiques de Ping pour 2001:6f8:202:352::1 : Paquets : envoyés = 4, reçus = 0, perdus = 4 (100% de perte), ################# ping6 to google # ################# C:\Documents and Settings\Fx>ping6 ipv6.google.com Envoi d'une requête 'Ping' ipv6.l.google.com [2001:4860:0:1001::68] à partir de 2001:6f8:202:352::2 avec 32 octets de données : Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Réponse de 2001:6f8:202:352::2 : Adresse de destination inaccessible. Statistiques de Ping pour 2001:4860:0:1001::68 : Paquets : envoyés = 4, reçus = 0, perdus = 4 (100% de perte),
Subnet host fails to reach the ::1 Pop
[ch] Jeroen Massar SixXS Staff on Monday, 26 January 2009 00:30:57
(Try adding: 'ip -6 ro add 2000::/3 via 2001:6f8:202:352::1' on your gateway. Some Linux kernels are broken and need that) But what I am really wondering about is how your network 'works' as it seems you have IPv6 on eth0 and IPv6 (wired) on none on ath0 (wireless), but IPv4 on ath0 and none on eth0. So how is that supposed to work? Do you bridge them or something? Can you better explain your network layout and what is connected exactly how? 'ip nei sho' outputs are helpful here too ;)
Subnet host fails to reach the ::1 Pop
[be] Shadow Hawkins on Monday, 26 January 2009 19:13:56
Hi, thanks for the reply, I add the 'ip -6 ro add 2000::/3 via 2001:6f8:202:352::1' route on my gateway it didn't help. For the interfaces, I don't know why I have two interfaces for ath0 and wifi0, I suppose Ubuntu did it himself with the installation, I bridged nothing manually :) I can explain the rest : Ubuntu : --------- ath0 : is directly connected with IPv4 to my router (Router IPv4 : 192.168.2.1) wifi0 : recieves the datas, I don't know why this interface exists and I don't know how it is supposed to work with ath0. Do I need a global IPv6 on these interfaces ? It is working without :-) eth0 is direclty IPv6 wired connected to a Windows XP host , they don't have any IPv4 configuration eth0 is the IPv6 subnet routed with radvd, it's working The sixxs tunnel is wireless connected with ath0 or wifi0 or both ?:-) WinXp : ---------- Also direclty IPv4 connected in wireless to my router and local wired connected with Ubuntu Do I have to shut down the wireless ? ######### ip -6 ro# ######### root@NotebookFx2:/home/fxm# ip -6 ro 2001:6f8:202:352::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 2001:6f8:1439::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2000::/3 via 2001:6f8:202:352::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev ath0 proto kernel metric 256 mtu 1300 advmss 1240 hoplimit 4294967295 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:6f8:202:352::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 ########### ip nei sho# ########### root@NotebookFx2:/home/fxm# ip nei sho 192.168.2.1 dev ath0 lladdr 00:12:bf:1b:26:fb REACHABLE
Subnet host fails to reach the ::1 Pop
[ch] Jeroen Massar SixXS Staff on Wednesday, 28 January 2009 12:44:26
wifi0 == control interface used by tools, I actually don't have an idea why they expose it to userspace though and why they don't just use /proc or something. ath0 == the actual interface Windows XP *requires* IPv4 because it does DNS only over IPv4.
Windows XP
Also direclty IPv4 connected in wireless to my router and local wired connected with Ubuntu
Why don't you just use 1 medium, that is either wired or wireless? For the rest, see the "Reporting Problems / Checklist" on the contact page, as a lot of details are missing.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker