IPv6 Router behind router
-
@jknott IPv4 never has been a problem. It's just IPv6
-
If you have a /56, configuring the interfaces and routing is exactly the same process. The only difference is the address length. So, get what you want going with IPv4 and duplicate with IPv6, allowing for differences such as SLAAC instead of configuring addresses. As I mentioned, you may want to have the prefix ID match up with the IPv4 subnet to keep things consistent. Another example where I do that is with my guest WiFi/VLAN, where I use prefix ID 3, 3 in the 3rd octet, on VLAN 3. As you work through this and get stuck, I or someone else can offer advice. One other area to watch is in filter rules. Some you can use the same rule for both IPv4 and IPv6. Others, you need separate rules for each. So, plan your networks, do what you need in IPv4 and replicate in IPv6. That should get you started.
Here are some examples. Your /56 is aaa:bbbb:cccc:1300:: to aaaa:bbbb:cccc:13ff:ffff:ffff:ffff:fffff (Not 1400 since you have 256 prefixes, not 257. Also, the :: represents all 0s.). You could match that up with 172.16.0.0 - 172.16.255.255. Then when you set up your networks, you could have 172.16.4.0 /24 and aaa:bbbb:cccc:1304:eeee::/64 on one interface. It's as simple as that when working with IPv4 & IPv6.
-
My tips for figuring out your IPv6 setup.
- Figure out how much is delegated to you by your ISP in my case a /48 (LAB) (ignore the other checked boxes as that only applies to my system)
make sure "start DHCP client in debug mode" is checked - go to status > system logs > DHCP
find this entry
Mar 24 12:04:02 dhcp6c 22277 update a prefix 2001:db8:1::/48 pltime=3600, vltime=3600 - I use this website to split my address and I don't fully understand how to do so myself
- Divide it into something bigger than /64 as a /64 only allows for one subnet, if that applies to you (if you want more that one IPv6 network behind the USG
- So something like this
than spin up a dhcpv6 server with two of those addresses in the "Prefix Delegation Range" section- make sure your router mode is properly set!
and this is unchecked
- leases should show up here:
Maybe @JKnott can assist if my tutorial had any errors?
- Figure out how much is delegated to you by your ISP in my case a /48 (LAB) (ignore the other checked boxes as that only applies to my system)
-
He has a /56, so no need for a calculator. The only variable is the last 8 bits of the prefix, which range from 0 to ff. Very simple. In fact far simpler than IPv4, where the divider can move according to subnet mask.
As I mentioned earlier, the best way to learn is to do. If he has problems, he can ask more questions.
-
@jknott Just saw that now, hadn't been keeping up with the thread.
-
@matthewgcampbell The problem is not really pfSense, like I said very early on, it's getting Unifi WAN and LAN to work.
The Unifi WAN gets the IP address and that address won't reach the internet and then the RA from pfSense isn't getting to the LAN.
The lan IPv6 setup on Unifi is asking the WAN to give the RA. This should be coming from pfsense..
The network topology is:
Modem to pfSense to USG (Unifi)
So, my real question is, why do I even need the pfSense DHCPV6 server? Why won't it issue IPv6 to the Unifi WAN?
-
@abuttino said in IPv6 Router behind router:
So, my real question is, why do I even need the pfSense DHCPV6 server?
You don't. SLAAC is normally used. Some packet captures may be useful in this area. However, as I have said, pfsense will not provide the prefix to the USG, unless you configure that some how. You can configure routing, as I have described or you can configure pfsense to provided DHCPv6-PD, which is something I haven't tried.
-
@matthewgcampbell Your thoughts about getting the Unifi WAN and LAN an IP? You say you've done it, I've been hoping to see how :)
-
In place of your USG, I used a Cisco router. I manually configured the routing so that the IPv6 prefix was routed to the Cisco. You have to do the same thing with the USG and I have been trying to show you how to do that. As I said, the easiest way is to do it on IPv4 and then replicate on IPv6.
-
Network??
What is the network if the USG Wan isn't giving me an IP address?Gateway??
What would be the gateway for this if it hasn't given me any IP addresses?I am trying to use RA mode only and it's not giving any IP addresses at all. That means I have nothing to fill out in a static route.
-
Wellll!!!
I rebooted pfSense and it started to give the USG WAN IP and subnet /64 plus internet access.
Pretty sure my that /56 address hasn't changed since the last time I fooled with this and that could mean my ticket to get off of tunnelbroker.
I guess the next step is to get the USG LAN set up with the static routes for pfSense and play around a little more.
Rebooting for every little thing when it comes to pfSense gets a little annoying,.
-
As I have said several times now, get it working with IPv4, as you said you know how to do that. Then do the same with IPv6, using IPv4 as your guide. Once again, you will have to manually configure routing IPv6 to the USG, unless you're prepared to enable DHCPv6-PD on the LAN side of pfsense or use something like OSPF. There is no other way to get IPv6 to that USG. Get your networks set up. Have you even selected the IPv6 prefix and IPv4 subnet to use on the USG? If so, manually configure both. Then go back to pfsense and configure IPv4 routing to the USG. Once you've done that, you can do the same on IPv6, using the IPv6 addresses, instead of IPv4. This is why I mentioned using the same prefix as as 3rd octet on IPv4. It makes it easy to keep track of what you're doing. Perhaps you should start with a sketch to show where you want what. Mark on that sketch what subnet & prefix you want on the LAN side of that USG. Then determine what addresses you have to route through to get there. I can't do that for you, as I don't know what your requirements are.
-
@jknott
As mentioned, I have IPv4 connected and properly routed for the USG WAN and LAN.pfSense uses the LAN v4 /16 address of 172.16.1.1 and the USG uses 172.16.1.2
USG LAN is a /24 at 10.2.0.1 and it is the DHCP server for the network.
As far as IPv6, pfSense has the RA server set up and is giving the USG WAN a /64 address.
This is as far as I've gotten and want to plan the network out for the rest of the USG LAN side first, such as what VLANs I'm going to give IPv6 to and not.
A major concern of mine at this point is that these addresses do not change. Such as addresses for the web services. I have a static IPv4 but Cox doesn't offer static IPv6.
-
So, configure IPv6 on the LAN side of the USG, just as you did with IPv4. Then configure routing for IPv6, just as you did for IPv4. Pfsense providing an IPv6 address for the WAN side of the USG will not provide addresses on the LAN side of it. You have to configure that using one of the methods I described above. You apparently routed for IPv4. You should be able to route a /64 to the USG using the same method.
-
@jknott will do. I'll check back to this thread for reference and questions should I have any.
The difference was all in the reboot of pfsense, it was not giving me IPv6 addresses until I did the reboot, and changing any ipv6 settings also requires more reboots.. Lots and lots of reboots..... Senseless to me. Other routers don't have the issue where it needs a reboot after changing a simple setting, just restarting the service/daemon should help (Apply settings).
-
That's not been my experience. The only thing I recall that required a reboot was a system update.
-
@jknott
Not to get on a tangent here but just last night I was fixing another pfSense for UPnP and it also required reboots for all things NAT. Resetting firewall states was not enough.Unless I'm doing work with HAProxy, I pretty much know it's going to have to be rebooted.
-
Well, it looks like I am plugging right along but I may have hit a road block..
First, the static routing needed to be done the USG to get to the internet.
::/0 next hop "pfsenseLANcard" ---- on USG, after that, internet.
I have all the static routes for the subnets for my VLANs in USG but it wasn't getting to the internet until I put that route in. 80% certain that this was wrong.
As mentioned earlier, I got a /64 from the pfSense LAN RA. Now, I would like to make sure these computers will be able to be routable from/to the internet. What is required for that?
I was looking at this tool:
http://www.gestioip.net/cgi-bin/subnet_calculator.cgiCurrent Static routes in pfsense:
2001:xxxx:xxxx:1300::/64 Gateway "USGsWAN64"
2001:xxxx:xxxx:1301::/64 Gateway "USGsWAN64"
2001:xxxx:xxxx:1302::/64 Gateway "USGsWAN64"
2001:xxxx:xxxx:1303::/64 Gateway "USGsWAN64"pfSense CANNOT ping (from LAN) USGsWAN64
Is this looping?
2001:xxxx:xxxx:1300::/64 Gateway "USGsWAN64" BECAUSE:
2001:xxxx:xxxx:1300:yyyy:zzzz:aaaa:bbbb is the USG WAN's address
What should I really be doing instead of what I am doing?
-
As I said, I haven't worked with the USG, so I can't provide specific help with it. However, what it appear's you're doing is just setting up the default route. With IPv6, that should be provided with the RA, likely a link local address. Do you not see that? BTW, for something like this, packet captures REALLY come in handy.
What does the USG show for the default route?
-
The WAN_DHCP6 coming from the modem is a link-local, I was editing my post when it got denied and saw you posted here..
I would guess, since I can't capture packets from 3000 miles away, I should try the LUA address to allow the internet to find the servers?
Such as:
::/0 next-hop fe80::b290:xxx:yyyy:7819Is I did exactly as you said with the pfSense static, but didn't know about the 1300 address subnet. Wouldn't that cause a loop as stated in the last post?
The USG's default route is the pfSense_v6_LAN
