Issues with LAN clients getting IPv6 address

Good morning,

I’m hoping someone can help me out. I’m very new to VyOS and am eager to get this set up, however IPv6 in general is a little confusing to me (I know enough about it to have used it in pfSense), but I can’t seem to get things to work properly in VyOS.

My current network set up is:
eth0 - WAN - Has a /128 from ISP
eth3 - LAN - Has a /64 from ISP

However, when clients connect to the network they aren’t pushed an IPv6 address.

My ISP uses DHCPv6 to assign an address.

show interfaces
ethernet eth0 {
     address dhcp
     address dhcpv6
     description OUTSIDE
     dhcpv6-options {
         pd 1 {
             interface eth3 {
                 address 1
                 sla-id 0
             }
             length 64
         }
     }
     firewall {
         in {
             name OUTSIDE-IN
         }
         local {
             name OUTSIDE-LOCAL
         }
     }
     hw-id 00:0c:29:5a:41:25
     ipv6 {
         address {
             autoconf
         }
     }
 }
 ethernet eth1 {
     address 192.168.0.2/22
     hw-id 00:0c:29:5a:41:2f
     ipv6 {
         address {
             autoconf
         }
     }
     mac 00:0c:29:5a:41:2a
 }
 ethernet eth2 {
     hw-id 00:0c:29:5a:41:39
 }
 ethernet eth3 {
     address 10.20.0.1/22
     description VLAN40
     hw-id 00:0c:29:5a:41:43
     ipv6 {
         address {
             autoconf
         }
     }
     vif 40 {
     }
 }
 loopback lo {
 }

Hoping someone can help!

Hello @Jon, can you add accept firewall rules for all ICMP types?

Check this very nice guide how to enable ipv6 prefix delegation in 1.3-RC

http://soucy.org/vyos/DHCPv6-PD_on_VyOS.pdf

You seem to be completely missing the RA announnemt on the LAN.

If your iSP is not using prefix delegation you will have to modify the setup a bit to enable RA announcements for a fixed lan prefix rather than the delegated ::/64 one in the guide.

2 Likes

Dmitry,

Still a little rough around the edges with VyOS and still haven’t figured out how to do firewall rules, so I wasn’t able to try that, however @Ulrik’s link solved my problem!

Much appreciated you two!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.