SixXS::Sunset 2017-06-06

default route in windows 2k (setup probs)
[nl] Shadow Hawkins on Thursday, 02 October 2003 15:26:10
Hi, I'm trying to get my tunnel up and running. but I cannot ping anyone or they can't ping me, I think it is because of the wrong default route. I used the following commands to setup my ipv6 tunnel: ===================================== ipv6 ifc 2 ipv6 ifc 2 forw ipv6 ifc 3 forw ipv6 ifc 4 forw ipv6 ifc 5 forw ipv6 ifc 6 forw adv ipv6 rtu ::/0 2/::213.204.193.2 pub ipv6 adu 5/2001:960:2:7d::2 ipv6 rtu 0::/0 2 <-- Is this right? ipv6 adu 2/2001:960:2:7d:2 ===================================== I cannot ping the POP endpoint (2001:960:2:7d::1) or other ipv6 addr. and they cannot ping me. I'm behind a NAT router but this configuration did work at xs26.net only with a other default route. I hope you can help me. thx in advance!
default route in windows 2k (setup probs)
[nl] Shadow Hawkins on Thursday, 02 October 2003 18:14:39
Why don't you use: (I think it is right) ipv6 rtu ::/0 2/::[PopIPv4TunnelEnd] ipv6 adu 2/[YourIPv6TunnelEnd]/127 ipv6 adu 2/[YourIPv6Subnet]/64 pub and if you are behind NAT you need to map Protocol 41 (not TCP 41 or UDP 41) to the internal Tunnel PC
default route in windows 2k (setup probs)
[ch] Jeroen Massar SixXS Staff on Thursday, 02 October 2003 18:33:13
See Windows Setup FAQ The second line above is wrong.. /127's are only on the IPng POP. Next to that try ethereal or any other networkmonitor and check which packets go in and out of your network to check the working of your NAT box.
default route in windows 2k (setup probs)
[nl] Shadow Hawkins on Thursday, 02 October 2003 19:09:55
thx allot. only removing the default route was enough to get it working! :) thx!

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

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