Report this

What is the reason for this report?

IPv6 route advertisements are not received on the private interface

Posted on January 5, 2023

I’m trying a very simple setup where two nodes in my VPC have IPv6 enabled and a working radvd which assigns ULAs to eth1 (e.g. fdaa::/64 and advertises them. Both have the following /etc/radvd.conf:

interface eth1
{
        AdvSendAdvert on;
        MinRtrAdvInterval 30;
        MaxRtrAdvInterval 100;
        AdvDefaultLifetime 0;
        prefix fdaa::/64 {
        };
};

I can confirm that advertisements are send to ff02::1 but they are not received on the other machine. So, pinging one node from another using the assigned ULAs does not work. What is the problem?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there,

As far as I know, DigitalOcean VPC private networking is IPv4 only. The VPC isn’t a shared L2 segment, so IPv6 multicast like RA/ND to ff02::1 on the private interface won’t be delivered. That’s why your ULAs on eth1 don’t get advertised or reachable.

Seems to be listed as a limitation here: https://docs.digitalocean.com/products/networking/ipv6/details/limits/

Instead, you could use public IPv6 on the primary interface and route over that, stick to IPv4 on the VPC.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.