Forum - NAT on Windows 2003, XP clients :: SixXS - IPv6 Deployment & Tunnel Broker

NAT on Windows 2003, XP clients

Shadow Hawkins on Friday, 19 November 2004 17:01:04

i found on the forum and FAQ these commands to setup the tunnel and the routing for the clients (On the Windows 2003 computer everything works fine) FAQ / forum:

netsh interface ipv6 add v6v4tunnel SixXS [YourIPv4] [POPIPv4] netsh interface ipv6 add address SixXS [YourIPv6] netsh interface ipv6 add route [POPIPv6]/[IPv6Prefix] SixXS publish=yes netsh interface ipv6 add route 0::/0 SixXS publish=yes netsh interface ipv6 add route [SubNetPrefix]/64 [LANIFID] publish=yes netsh interface ipv6 set interface SixXS forwarding=enabled netsh interface ipv6 set interface [LANIFID] forwarding=enabled advertise=enabled

I Entered thise:

netsh interface ipv6 add v6v4tunnel SixXS 213.10.40.113 193.109.122.244 netsh interface ipv6 add address SixXS 2001:7b8:2ff:fd::2 netsh interface ipv6 add route 2001:7b8:2ff:fd::2/64 SixXS publish=yes netsh interface ipv6 add route 0::/0 SixXS publish=yes netsh interface ipv6 add route 2001:7b8:2ff::/64 "local area connection" publish=yes netsh interface ipv6 set interface "local area connection" forwarding=enabled advertise=enabled

trace ouput on XP client:

Tracing route to noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:7b8:2ff:0:eca2:c784:e23d:d506 over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:7b8:2ff:0:201:3ff:febe:d492 2 * * * Request timed out. 3 * * * Request timed out.

netsh .... show routes:

Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- ---- ------------------------ --- --------------------- no Autoconf 8 2001:7b8:2ff::/64 4 Local Area Connection no Autoconf 16 2001:7b8:2ff:fd::/64 4 fe80::201:3ff:febe:d492 no Autoconf 16 ::/0 4 fe80::201:3ff:febe:d492

Someone that nows the problem? O-)

NAT on Windows 2003, XP clients

Carmen Sandiego on Sunday, 12 December 2004 11:45:34

Try entering the ip-adress of your pc instead of your router. So not: netsh interface ipv6 add v6v4tunnel SixXS 213.10.40.113 193.109.122.244 But for example: netsh interface ipv6 add v6v4tunnel SixXS 192.168.1.100 193.109.122.244 This works for me, so i hope this helps for you also. Grtz, Frank

NAT on Windows 2003, XP clients

Shadow Hawkins on Sunday, 12 December 2004 21:59:29

You have to request a subnet for your clients. As far as i can see you just used a part of the POP IPv6 address.

NAT on Windows 2003, XP clients

Jeroen Massar SixXS Staff

on Monday, 13 December 2004 12:02:47

IPv6 does not care about NAT anymore. The tunnel has to punch through the NAT and that works. What you are doing 'wrong' is the fact that you are using the wrong prefix... You where assigned 2001:7b8:384::/48 as a subnet, thus you should use: netsh interface ipv6 add v6v4tunnel SixXS 213.10.40.113 193.109.122.244 netsh interface ipv6 add address SixXS 2001:7b8:2ff:fd::2 netsh interface ipv6 add route 2001:7b8:2ff:fd::2/64 SixXS publish=yes netsh interface ipv6 add route 0::/0 SixXS publish=yes netsh interface ipv6 add route 2001:7b8:384::/64 "local area connection" publish=yes netsh interface ipv6 set interface "local area connection" forwarding=enabled advertise=enabled This will work (with luck ;) )

NAT on Windows 2003, XP clients

Shadow Hawkins on Thursday, 16 December 2004 17:03:11

Thank you all, yes i have been reading about te ipv6 protocol. and because off the ipsec it's not possible to NAT a ipv6 connection :-) But i have requested my subnet and everything is working properly Maurice.

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