topic Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U in IPv6 Trial

Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragona — Wed, 30 Oct 2013 20:01:49 GMT

Hi all,
Trying to set up 6in4 on my DSL-N55U for the most part i think the router is set up. I seem to be able to ping from router to any ipv6 address ive foudn thus far:

Quote
traceroute to 2620:0:ccc::2 (2620:0:ccc::2), 30 hops max, 16 byte packets
1 Dragona-1.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:e78::1) 24.050 ms 22.803 ms 24.910 ms
2 gige-g4-8.core1.lon1.he.net (2001:470:0:67::1) 28.177 ms 19.368 ms 29.480 ms
3 10gigabitethernet1-1.core1.ams1.he.net (2001:470:0:3f::2) 31.984 ms 43.671 ms 26.088 ms
4 2001:7f8:1::a503:6692:1 (2001:7f8:1::a503:6692:1) 26.546 ms 26.281 ms 27.022 ms
5 2620:0:ccc::2 (2620:0:ccc::2) 26.302 ms 26.348 ms 46.473 ms

However ive noticed that my local client doesn't seem to do the same i get general failure every time i try to ping ipv6 when chcking my tunnel adapter all i see is media disconnected:

Quote
Tunnel adapter IP6Tunnel:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

i set up the tunnel following the instructions on the site which ended up being the following:

Quote
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 192.168.1.229 216..xx.xx.xx
netsh interface ipv6 add address IP6Tunnel 2001:xxx:xxxx:xxx::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:xxx:xxxx:xxx::1

192.168.1.229 being my dhcp address in v4
I'm wondering if anyone can point out where i may have gone wrong im suspecting its either router advertisement (when i enable this my router always disconnects from the internet but stays connected to the exchange and is unable to reconnect unless i reboot. and occasionally it will crash the web GUI) the other possible cause is i've mucked up setting up the tunnel adapter.
I also noticed the following in system log:

Quote


Jan  1 00:01:37 syslog: module nf_conntrack_ipv6 not found in modules.dep

Any suggestion would be appreciated
-D

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

hazzamon — Wed, 30 Oct 2013 20:57:45 GMT

Are you configuring your tunnel in the router settings as well as configuring a tunnel on your PC? If your router lets you configure IPv6, you should NOT manually configure the same tunnel in your PC, as this will cause a conflict.
Do you have a menu in your router settings like the attached image?

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragona — Wed, 30 Oct 2013 21:43:16 GMT

Yes, I do its all set up in there ive removed the lines from netsh to try and stop any conflicts but get the following:
I now seem to be able to ping some ipv6 addresses which resolve to v4 addresses others just time out..


C:\Users\Dragona>tracert ::ffff:d043:dcdc
Tracing route to resolver2.opendns.com [::ffff:208.67.220.220]
over a maximum of 30 hops:
  1  Transmit error: code 1214.
Trace complete.

C:\Users\Dragona>ping ::ffff:d043:dcdc
Pinging 208.67.220.220 with 32 bytes of data:
Reply from 208.67.220.220: bytes=32 time=110ms TTL=51
Reply from 208.67.220.220: bytes=32 time=108ms TTL=51
Reply from 208.67.220.220: bytes=32 time=19ms TTL=51
Reply from 208.67.220.220: bytes=32 time=67ms TTL=51

Sorry, I'm fairly new

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

hazzamon — Wed, 30 Oct 2013 21:54:03 GMT

For a start, get rid of that third DNS server - it looks mighty invalid!
Ensure you've reset Window's TCP-IP stack to defaults to remove any traces that may be left. This link will show you how. Make sure to restart afterwards of course.
Assuming you are using Hurricane Electric, here's a link that will help you ensure you have entered all the settings correctly. Pay particular attention to the DDNS settings if you have a dynamic IPv4 address. Note that when typing in IPv6 addresses into the router configuration, you should not type in the '/64' at the end.

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragona — Wed, 30 Oct 2013 22:23:29 GMT

Done the above, replaced the third address with the secondary google one however i did get those addresses from a plusnet thread about dns servers that one being an open dns one.
reset the stack, seemed to work but no log produced and the thread you linked is was i originally used to configure my N55U
I can see in my ipv6 leases on the router that my NAS drive picked up an ipv6 address with no issues but 2 laptops both running different blends of win7 have not.
Edit: ping now gets the following message:
PING: transmit failed. General failure.
dick:quote

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

hazzamon — Wed, 30 Oct 2013 22:40:19 GMT

Try the following commands:

ping www.google.com
ping 8.8.8.8
ping 2001:4860:4860::8888
nslookup www.google.com 8.8.8.8
nslookup www.google.com 2001:4860:4860::8888

They may give an indication as to which stage the problem lies.
Also try http://test-ipv6.com/ and see what it says.
In addition, go to your tunnel settings at www.tunnel-broker.net and check that 'Client IPv4' is accurate (Should be the IPv4 address allocated to you by Plusnet).
I assume that you have power-cycled the router too?

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragona — Wed, 30 Oct 2013 22:48:56 GMT

Got the following responses:


Pinging www.google.com [173.194.67.105] with 32 bytes of data:
Reply from 173.194.67.105: bytes=32 time=21ms TTL=47
Reply from 173.194.67.105: bytes=32 time=21ms TTL=48
Reply from 173.194.67.105: bytes=32 time=20ms TTL=48
Reply from 173.194.67.105: bytes=32 time=20ms TTL=48
--------------------------------------------
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=21ms TTL=48
Reply from 8.8.8.8: bytes=32 time=22ms TTL=48
Reply from 8.8.8.8: bytes=32 time=83ms TTL=48
Reply from 8.8.8.8: bytes=32 time=22ms TTL=48
--------------------------------------------
Pinging 2001:4860:4860::8888 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
--------------------------------------------
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
Non-authoritative answer:
Name:    www.google.com
Addresses:  2a00:1450:4009:808::1010
          173.194.41.179
          173.194.41.177
          173.194.41.180
          173.194.41.176
          173.194.41.178
-------------------------------------------
Server:  UnKnown
Address:  2001:4860:4860::8888
*** UnKnown can't find www.google.com: No response from server

Router has indeed been power cycled, Ipv4 address is correct its also static i know it off the top of my head.
http://test-ipv6.com/ states that im not ready for ipv6 " No IPv6 address detected [more info]"
also noticed my Galaxy S3 is picking up an ipv6 address and scores 9/10 on the test-ipv6 website.

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

hazzamon — Wed, 30 Oct 2013 22:56:07 GMT

Your PC isn't picking up an IPv6 address correctly then.
Does IPConfig show your PC as having the expected IPv6 address? (ie your Hurricane Electric routed /64 followed by some more digits)

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragona — Wed, 30 Oct 2013 22:57:30 GMT

nope still showing an fe80:
Edit: Strange, got it working now had to move away from dell drivers for my Advanced N 6230 and go to the latest intel drivers to get ipv6 to work. tried a few different dell versions and had no luck.
Thanks for the help
-D

Re: Setting up 6in4 (tunnelbroker.net) on Asus DSL-N55U

dragon2611 — Sat, 09 Nov 2013 21:38:14 GMT

Don't forget to enable the firewall in the router if it has one, and if it doesn't then make sure any devices with an IPv6 address do, since the IPv6 addresses your router is handing out will be globally routable.