IPv6

[vincepoy]

Wow, never realized there was a 6"to"4 and a 6"in"4 since I thought there was only 6"to"4 and 6"rd". I still need to learn how to read the addresses since it seems more complicated than ipv4.

You are probably correct that it's not a sonic.net assisned IP as it seems like I am directly connected to Hurricane Electric or something according to my traceroutes.

I tried going to the member tools and it only shows a Transport and a Network with nothing else but I don't see anywhere to input that information. I also don't see the assigned IPv4 border relay.

I also have a ASUS RT-AC68U and a LinkSys EA6900 which is still new in the shrinkwrap box. The other option to get all the ipv6 options is to use DD-WRT with the Netgear R7000. The only thing with non-OEM firmwares is it doesn't support CTF/Hardware Acceleration as those are paid licensed drivers from Broadcom which is not in any of the third party firmware.

Netgear's IPv6 choices for connection type are:
Auto Detect
6to4 tunnel
Pass Through
Fixed
DHCP
PPPoE
Auto Config

Am I correct that unlike ipv4 where the gateway is the other end, ipv6 tunnels work similar to VPN where you can pretty much use anything on the global internet because your traceroute seems to indicate I am right behind Hurricane Electric.

[nsmill49]

Wow, never realized there was a 6"to"4 and a 6"in"4 since I thought there was only 6"to"4 and 6"rd". I still need to learn how to read the addresses since it seems more complicated than ipv4.

Definitely different, not necessarily more complicated. Sign up a Hurricane Electric "Tunnelbroker" account. It is free, and comes with more detailed descriptions than you will find in the Sonic.net IPv6 lab.

https://tunnelbroker.net/

You are probably correct that it's not a sonic.net assisned IP as it seems like I am directly connected to Hurricane Electric or something according to my traceroutes.

Might even be Hurricane Electric. Both the IPv4 border relay ([192.88.99.1]) and the assigned IPv6 block (2002::/16) are reserved by IANA, and can be used by any organization which wants to run a "6to4" relay.

I tried going to the member tools and it only shows a Transport and a Network with nothing else but I don't see anywhere to input that information. I also don't see the assigned IPv4 border relay.

You are given the transport in the form of a ::/127; two contiguous IPv6 IP addresses, and you are given a block of IPv6 IP addresses as ::/60. If you click on the "View Example Configuration" button, you will be given the border relay as the, "sonic-side v4 address", and your own IPv4 address as the, "customer-side v4 address". You will also be shown which of the two IPv6 transport IP addresses is on the Sonic.net side, and which is on your side.

I also have a ASUS RT-AC68U and a LinkSys EA6900 which is still new in the shrinkwrap box. The other option to get all the ipv6 options is to use DD-WRT with the Netgear R7000. The only thing with non-OEM firmwares is it doesn't support CTF/Hardware Acceleration as those are paid licensed drivers from Broadcom which is not in any of the third party firmware.

Netgear's IPv6 choices for connection type are:
Auto Detect
6to4 tunnel
Pass Through
Fixed
DHCP
PPPoE
Auto Config

Am I correct that unlike ipv4 where the gateway is the other end, ipv6 tunnels work similar to VPN where you can pretty much use anything on the global internet because your traceroute seems to indicate I am right behind Hurricane Electric.

Yes, IPv6 tunnels are similar to VPNs, in that IPv6 packets are encapsulating within IPv4 packets at the customer side, and unencapsulated at the ISP side.

If you could get the Sonic.net "6in4" tunnel working, you would trace on Sonic.net IPv6 transit. But I can't because the stupid RT-AC66U limits the IPv6 transport prefix length to values between 3 and 64; the Sonic.net IPv6 transport pair is not aligned to a ::/64 block boundary, so the router tunnel is borked. OTOH, the Hurricane Electric IPv6 transport pair is aligned to a ::/64 boundary, so the router builds the tunnel, even though the transport pair is, technically, a ::/127.

I have seen a screen shot of a D-Link DIR-655RevB IPv6 "6in4" configuration page. Unlike the RT-AC66U, the DIR-655b has a separate field for each IPv6 transport IP address. So a person can set up for Sonic.net fairly easily.
If I could figure out how to access the RT-AC66U CLI, I could probably issue a Linux command for the IPv6 transport ::/127.

[vincepoy]

Definitely different, not necessarily more complicated. Sign up a Hurricane Electric "Tunnelbroker" account. It is free, and comes with more detailed descriptions than you will find in the Sonic.net IPv6 lab.

https://tunnelbroker.net/

I actually meant learning how to read and translate the addresses since it's different than reading 4 numbers which each is 8 bit. Thanks for the info on the Hurricane Electric "Tunnelbroker" account, I just signed up for one and hopefully I'll learn more about IPv6.

Might even be Hurricane Electric. Both the IPv4 border relay ([192.88.99.1]) and the assigned IPv6 block (2002::/16) are reserved by IANA, and can be used by any organization which wants to run a "6to4" relay.

Makes sense.

You are given the transport in the form of a ::/127; two contiguous IPv6 IP addresses, and you are given a block of IPv6 IP addresses as ::/60. If you click on the "View Example Configuration" button, you will be given the border relay as the, "sonic-side v4 address", and your own IPv4 address as the, "customer-side v4 address". You will also be shown which of the two IPv6 transport IP addresses is on the Sonic.net side, and which is on your side.

Thanks for the pointer, I kept thinking the example configuration actually contained a sample config that is unrelated to my settings except to use it as a reference. I did try putting in the sonic-side v4 address for the router ip but the traceroutes just times out without going anywhere yesterday.

Yes, IPv6 tunnels are similar to VPNs, in that IPv6 packets are encapsulating within IPv4 packets at the customer side, and unencapsulated at the ISP side.

If you could get the Sonic.net "6in4" tunnel working, you would trace on Sonic.net IPv6 transit. But I can't because the stupid RT-AC66U limits the IPv6 transport prefix length to values between 3 and 64; the Sonic.net IPv6 transport pair is not aligned to a ::/64 block boundary, so the router tunnel is borked. OTOH, the Hurricane Electric IPv6 transport pair is aligned to a ::/64 boundary, so the router builds the tunnel, even though the transport pair is, technically, a ::/127.

I have seen a screen shot of a D-Link DIR-655RevB IPv6 "6in4" configuration page. Unlike the RT-AC66U, the DIR-655b has a separate field for each IPv6 transport IP address. So a person can set up for Sonic.net fairly easily.
If I could figure out how to access the RT-AC66U CLI, I could probably issue a Linux command for the IPv6 transport ::/127.

I'll try to help you get access to the RT-AC66U/R CLI, I can't on my current version of the Netgear R7000 beta firmware because the telnet enabler tool no longer works in this version but anyways, here is what you need to do:

This is nice too:

You can enable telnet on the ASUS. "Enable Telnet" on http://192.168.1.1/Advanced_System_Content.asp

then telnet to 192.168.1.1 and login with the same username/password you use to access the web interface, I think you can even ssh to the ASUS.


After you login, ifconfig will show a interface named 6rd which is the 6rd config.