IPv6 with Sonic ONT

[gatsbylee]

I am just curious.
If starting to use IPv6, I can't visit websites that don't support IPv6?

And, BTW, what are the steps to enable IPv6 on UDM SE?

Thank you
Gatsby

[virtualmike]

I can't answer the second question, but for the first, when IPv6 is enabled, your equipment should have both IPv4 and IPv6 connectivity. When it does an address lookup, it will get the appropriate address (IPv6 or IPv4) and connect accordingly.

Your connection is not IPv4 or IPv6, it's IPv4 or IPv4+IPv6.

[gatsbylee]

I can't answer the second question, but for the first, when IPv6 is enabled, your equipment should have both IPv4 and IPv6 connectivity. When it does an address lookup, it will get the appropriate address (IPv6 or IPv4) and connect accordingly.

Your connection is not IPv4 or IPv6, it's IPv4 or IPv4+IPv6.

ah... I see.
Thank you for your comment

[henro2k]

I do not seem to get an answer to DHCPv6 here in the Sunset in San Francisco (pfsense, 1G Fusion). I'm looking forward to native ipv6 and glad to see progress from Sonic on it. I would love to know when to expect it to work here. Even a rough schedule of rollout plans would be useful.

Echo this. I'm in the Sunset as well and it does not seem to be possible to pull a v6 address at my location.

[daniel15]

I can't answer the second question, but for the first, when IPv6 is enabled, your equipment should have both IPv4 and IPv6 connectivity. When it does an address lookup, it will get the appropriate address (IPv6 or IPv4) and connect accordingly.

Your connection is not IPv4 or IPv6, it's IPv4 or IPv4+IPv6.

Note that it's very common for mobile carriers like T-Mobile have an IPv6-only network. Even on an IPv6-only connection, there's technologies like 464XLAT and DNS64 that let you access legacy IPv4-only servers from an IPv6-only connection.

[virtualmike]

mobile carriers like T-Mobile

Good to know. For the purposes of this discussion, however, the fact is that a Sonic connection that is IPv6-enabled will use both addressing protocols.

[tigertech]

Since I've been complaining about this for years, I thought I'd say "thanks": as of yesterday, I now have native IPv6, with a /56 prefix, in Berkeley. Finally I can say goodbye to tunnels.

Thank you Sonic!

[stephenamar85]

For posterity, it took me more than time than I liked but I got sonic IPv6 to work in Mikrotik RouterOS 7 - excluding firewall config (I use the default).

Code: Select all

/ipv6 settings
set accept-router-advertisements=yes disable-ipv6=no forward=yes
/ipv6 address
add address=::1/64 advertise=yes disabled=no eui-64=no from-pool=sonic \
    interface=bridge no-dad=no
/ipv6 dhcp-client
add interface=sfp-sfpplus1 pool-name=sonic pool-prefix-length=56 request=\
    prefix use-peer-dns=no
/ipv6 nd
set [ find default=yes ] dns=2001:4860:4860::8888,2001:4860:4860::8844 \
    hop-limit=64 interface=sfp-sfpplus1 managed-address-configuration=yes \
    mtu=1500 other-configuration=yes ra-interval=20s-1m ra-preference=high \
    reachable-time=5m
/ipv6 nd prefix default
set preferred-lifetime=4h valid-lifetime=4h

Some notes:

• The first problem I had was the default ND configuration was not great and prevented dhcp-client prefix from working
• No need to request an address in dhcp-client, prefix is enough
• I spent a week trying to figure out why LAN->WAN was not working and it dawned on me that I disabled IPv6 Forward in my eagerness to enable RA.

Good luck to everyone!

[mutelight]

I am just curious.
If starting to use IPv6, I can't visit websites that don't support IPv6?

And, BTW, what are the steps to enable IPv6 on UDM SE?

Thank you
Gatsby

As mentioned already you can visit IPv4 sites with it enabled.

On Ubiquiti, in the network app you want to go to Settings --> Internet --> Select your WAN connection --> scroll down to the bottom and enable "DHCPv6" and set the Prefix Delegation Size to 56.