Configure LAN for IPv6 with SLAAC on WAN

dhcpipv6pfsense

My ISP assigns me an IPv4 address via DHCP and an IPv6 subnet through SLAAC.

I set up my pfSense box to use NAT and DHCPv4 for my LAN network which works fine. However, on the IPv6 side, my LAN computers only configure themselves with the standard link-local fe80.. address and don't get any global IPv6 address from the /64 pool my ISP assigned me.

I am fairly new to IPv6, so I tried a few options in pfSense like setting the LAN interface to SLAAC as well or setting it to a static IPv6 in the fc00.. range and enabling DHCPv6. Both of which didn't work for me. Also none of the options in the router advertisement tab helped either.

I'd be happy if someone with experience in setting up pfSense for my scenario could give me a hint to how I need to configure it.

Best Answer

The pfSense box should be seeing the ICMPv6 Router Advisory packets coming from your ISP's router over IPv6 multicast to ff02::1. If your pfSense should act as an IPv6 bridge, then it should pass these packets on to your local network, as the Router Advisory packets are essential for IPv6 and SLAAC.

If you are setting up your pfSense as an IPv6 router instead, then you should configure pfSense to send its own IPv6 Router Advisory messages to your LAN side.

The ICMPv6 Router Advisory messages are mandatory for IPv6 to work: they also carry information on whether or not DHCPv6 should be used in the network segment, and if so, whether it should be used for IPv6 address allocation or just for additional configuration information. The Router Advisory messages can even carry information on IPv6 DNS servers that the clients should use.

Related Solutions

IPv6 LAN to IPv4 with PFsense

6to4 needs to know your extern IPv4 address that it should use. This will determine your IPv6 prefix by embedding the IPv4 address in your IPv6 prefix (basically your IPv6 subnet has the information necessary for other IPv6 hosts to find their way back to your IPv4 address via another 6to4 router.

Your ISP must support 6to4, or you must use a public 6to4 router.

_{PFsense is based on FreeBSD, I don't know PFsense's interface all that well, but I have an Intro to 6to4 for the FreeBSD CLI on my blog.}

How to configure radvd, dhcpd6, routing and /64 subnet based on delegated prefix by DHCPv6-PD server

I don't know the answer to your question, but I just want to warn you about using the DHCP server address as your default router. If that works it is by chance... In IPv6 the default route is communicated by RA's and not by DHCP.

You will need to enable forwarding, accepting RA's and sending out RS's. A problem here is that the kernel included in Centos6 does not allow you to do that. When forwarding is enabled then accepting RA's and sending RS's is disabled. There should be a CentosPlus kernel with the relevant patches though. See the mailing list thread / message at http://lists.centos.org/pipermail/centos/2011-April/thread.html#109756

The relevant sysctl.conf settings are:

net.ipv6.conf.all.forwarding=1
net.ipv6.conf.eth0.accept_ra=2
net.ipv6.conf.eth0.accept_ra_defrtr=1
net.ipv6.conf.eth0.router_solicitations=1

Best Answer

Related Solutions

IPv6 LAN to IPv4 with PFsense

How to configure radvd, dhcpd6, routing and /64 subnet based on delegated prefix by DHCPv6-PD server

Related Topic