SixXS::Sunset 2017-06-06

Subnet does not route?
[nl] Shadow Hawkins on Monday, 07 February 2011 17:00:43
Ik have a tunnel and a subnet. I followed the instruction for setting up the machine where the tunnel ends as router for the subnet. The local NIC on that machine gets an autoconfigureated IPv6 address in the range of the subnet and so does the NIC of another IPv6 enabled machine on my LAN. But those addresses are not pingable from outside and the second machine does not have IPv6 access to the net. So it apears that the forwarding and routing does not work. I notice that the operation cost me 14 ISK. Ths puzzles me. I also see that adding an NS record will cost me 1 ISK and that would bring the cost to a multiple of 5 again. Do I need to add an NS record? Or am I missing something else? Here are some details: OS: Win XP SP3 Tunnel type: AYIYA Results from ipconfig: Ethernetadapter LAN-Verbindung: Verbindungsspezifisches DNS-Suffix: vlist.eu Beschreibung. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physikalische Adresse . . . . . . : 00-15-60-52-21-3D DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja IP-Adresse. . . . . . . . . . . . : 192.168.1.108 Subnetzmaske. . . . . . . . . . . : 255.255.255.0 IP-Adresse. . . . . . . . . . . . : 2001:7b8:154f:0:74f8:961a:799d:a81e IP-Adresse. . . . . . . . . . . . : 2001:7b8:154f:0:215:60ff:fe52:213d IP-Adresse. . . . . . . . . . . . : fe80::215:60ff:fe52:213d%4 Standardgateway . . . . . . . . . : 192.168.1.1 DHCP-Server . . . . . . . . . . . : 192.168.1.1 DNS-Server. . . . . . . . . . . . : 212.54.40.25 212.54.35.25 fec0:0:0:ffff::1%2 fec0:0:0:ffff::2%2 fec0:0:0:ffff::3%2 Lease erhalten. . . . . . . . . . : maandag 7 februari 2011 16:41:20 Lease luft ab. . . . . . . . . . : maandag 7 februari 2011 18:41:20 Ethernetadapter aiccu: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V8 Physikalische Adresse . . . . . . : 00-FF-C2-3D-78-B7 DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja IP-Adresse (Autokonfig.). . . . . : 169.254.139.32 Subnetzmaske. . . . . . . . . . . : 255.255.0.0 IP-Adresse. . . . . . . . . . . . : 2001:7b8:2ff:3a9::2 IP-Adresse. . . . . . . . . . . . : fe80::2ff:c2ff:fe3d:78b7%5 Standardgateway . . . . . . . . . : 2001:7b8:2ff:3a9::1 DNS-Server. . . . . . . . . . . . : 2001:838:1:1:210:dcff:fe20:7c7c 2001:7b8:3:1e:290:27ff:fe0c:5c5e 2001:770:18:8::4 show routes: netsh interface ipv6>show routes Der aktive Status wird abgefragt... Verff. Typ Met Prfix Idx Gateway/Schnittstelle ------- -------- ---- ------------------------ --- --------------------- no Autokonf 10 2001::/32 6 Teredo Tunneling Pseudo- Interface no Manuell 0 2001:7b8:2ff:3a9::/64 5 aiccu yes Manuell 0 ::/0 5 2001:7b8:2ff:3a9::1 yes Manuell 0 2001:7b8:154f::/64 4 LAN-Verbindung netsh interface ipv6> What is missing?
Subnet does not route?
[ch] Jeroen Massar SixXS Staff on Monday, 07 February 2011 18:30:50
Due to something in the tun/tap driver and Windows a subnet is not properly routed over the tun/tap device.
Subnet does not route?
[nl] Shadow Hawkins on Monday, 07 February 2011 19:49:15
Is there a solution? I am presently using version 801 of the tun/tap driver. Would it help to switch to version 901 and use the console version of aiccu?
Subnet does not route?
[nl] Shadow Hawkins on Tuesday, 08 February 2011 11:12:10
If it does not work and there is no solution, please update the FAQ to reflect that. It would save others the effort of trying in vain. If it never worked, I wonder how the procedure for setting up a subnet under Windows and AYIYA, made it into the FAQ in the first place...
Subnet does not route?
[ch] Jeroen Massar SixXS Staff on Tuesday, 08 February 2011 12:46:49
AICCU : Future Updates / Wishlist / Known bugs and issues states: "Windows AYIYA implementation doesn't route correctly, requires mac-based fixup." The FAQ details are correct, with a proto-41 tunnel (optionally with heartbeat and thus AICCU) this works like a charm. The combination of Subnet+AYIYA on Windows does not work though as stated above. Sorry, but we can't repeat everything on every page unless you want us to put all the content on a single page (and that while there are people who are scared of this website as there is too much text on it...)
Subnet does not route?
[nl] Shadow Hawkins on Tuesday, 08 February 2011 16:22:20
Ok, thanks for pointing me in the right direction. Is there any chance this will be fixed before the 8th of June IPv6 day, or should I go for plan B?
Subnet does not route?
[gb] Shadow Hawkins on Monday, 07 March 2011 03:07:34
Sorry to "steal" this thread, but I have almost the same problem. Only difference is, I no longer use AICCU for the tunnel. Currently, my tunnel is created from my WRT54GS router, and it also adds the subnet. The normal IPv6 Endpoint is reachable (pingable) from outside. Internal LAN hosts (Win7) get a Autoconfigured IPv6. I can access IPv6 sites, but if I try to ping the same from outside my LAN I get no reply. Not sure if there are more steps required then just get the tunnel on the router and the IPv6 on the client configured.
Subnet does not route?
[nl] Shadow Hawkins on Monday, 07 March 2011 22:06:47
Ah, this is interesting. After almost five years of faithful service for FON, my WRT54GL has been flashed with OpenWrt with te Ipv6 additions. (Tnx to Zsub) I have the same problem. When I issue a ping6 from the command line of OpenWrt the tunnel opens and the endpoint is pingable from outside for a few minutes. When there is no further activity it stops being pingable from outside. I suppose a cron job running on OpenWrt that pings the other tunnel endpoint periodically will solve the problem, but I consider this a kludge and I would prefer the "proper" solution.
Subnet does not route?
[ch] Jeroen Massar SixXS Staff on Tuesday, 08 March 2011 17:26:14
When there is no further activity it stops being pingable from outside.
See the connection tracker FAQ item which handles this problem.
Subnet does not route?
[ch] Jeroen Massar SixXS Staff on Tuesday, 08 March 2011 17:25:20
Do you use tun/tap? As the above statement only refers to tun/tap. Protocol-41 based tunnels are not affected by that. Thus then you have another issue; and the only way to figure out what that might be is to provide proper details, see the contact page for the list.

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

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