Setup NAT64 in pfSense
-
@johnpoz said in Setup NAT64 in pfSense:
They are running out of IPv4 rfc1918 space because they choose to do so.. Plain and simple!
Sure some devices might need to talk to each other.. Not ALL of them!! And if need be they can nat, etc. etc.. Sorry but they are touting their move to ipv6 like they are doing something innovative.. And they are using it as marketing.. they don't NEED to move to it..
Which is GREAT... But don't tell me you "have to" because your out of rfc1918 space.
And to be honest here is the big problem with the eventual migration... Is once you move part of the network to IPv6.. That frees up lots of IPv4 that can be used now..
For example could their management vlans on Ipv6, they could put their storage vlans on IPv6, they could put xyz on IPv6, etc etc.. This frees up LOTS of address space to use where its needed, etc.
They don't need to move to IPv6, they could continue working around the shortcomings of legacy ip for years to come. Just like you could keep repairing and modifying a rusty 1980s car. Microsoft have clearly decided that it's more cost effective, easier and more secure to move to IPv6.
Yes not everything needs to talk to each other, but inevitably some things will.
With an IPv6 network where everything is addressable, you add the necessary allow rules and job done.With legacy ip, you might have overlapping address space so you need nat or even double nat, which then means you need to waste address space with the translated addresses too. Their offices in redmond and finland might both use 192.168.1.x, so 192.168.1.10 (finland) cant talk to 192.168.1.10 (redmond) as the stack will route the traffic locally. Instead you need to create a virtual network 192.168.2.10 (virtual) which 192.168.1.10(redmond) talks to, which then translates the traffic before forwarding it to 192.168.1.10(finland), so both sides are actually talking to 192.168.2.10.
Then you have inconsistent addresses, depending on where you're locate you might need to connect to 192.168.1.10 or 192.168.2.10, so you need to setup split dns etc too.
Then you consider logging/security, as the traffic will have different src/dst addresses depending where on the network it is, you have to correlate multiple log sources. If your sat in the SOC and you see suspicious traffic from 192.168.1.10 did it originate in finland or redmond? You now have extra work to find out... If you see traffic from an ipv6 address it's unique and you know it correlates to a single device.The idea that the number of employees correlates to address usage also makes no sense... Assuming every employee has at least a desktop and a mobile device, some employees are going to have a lot more - for instance software developers will have clusters of machines performing builds, machines for testing etc. Microsoft also support their products for several years after release so they are going to have build/test networks for each major version going back several years.
Then you have address wastage due to the nat kludges above...
Not to mention the wastage of addresses each time you create a legacy ip subnet - network address, broadcast address, minimum of 1 address for the router possibly 3 if you use vrrp/hsrp/etc.
Then every time you create a subnet, you make it bigger than strictly necessary to allow room for expansion - because otherwise having to readdress everything is extremely painful.Github isn't the last company microsoft are going to acquire either, sooner or later they are going to acquire more and it will be the same integration headaches all over again.
So yes, Microsoft could kick the can down the road and continue struggling with legacy ip for a few more years, spending a lot of money dealing with the headaches and security implications before having to implement IPv6 at some point in the future anyway.
Or they can implement ipv6 now, then its done and doesn't need to be done again. They gain a network which is simpler, easier to manage, easier to monitor, more secure and easier to expand in future. They made the smart move. -
@bert64 said in Setup NAT64 in pfSense:
They don't need to move to IPv6, they could continue working around the shortcomings of legacy ip for years to come. Just like you could keep repairing and modifying a rusty 1980s car. Microsoft have clearly decided that it's more cost effective, easier and more secure to move to IPv6.
Yes not everything needs to talk to each other, but inevitably some things will.
With an IPv6 network where everything is addressable, you add the necessary allow rules and job done.
With legacy ip, you might have overlapping address space so you need nat or even double nat, which then means you need to waste address space with the translated addresses too.Yep, IPv4 hasn't been adequate since the day it became necessary to use NAT. Now, we have hacks upon hacks to get around the address shortage. Of course, this is before we get to the fact that many people are behind carrier grade NAT, which means they have no means of accessing their home network with a VPN etc..
IPv6 is where the world is moving and refusing to move with it is head in the sand stupidity. The longer people refuse to move, the longer some people will be behind CG NAT.
-
Just tried this and it works great. Here is what I did:
- Download FreeBSD 11.3 (or whatever version your pfSense is based on), copy /boot/kernel/ipfw_nat64.ko to your pfsense install.
- Load the IPFW module: 'kldload ipfw_nat64'
- Enable IPFW: 'sysrc firewall_enable=YES' and 'service ipfw start'
- Enter the nat64lsn rules you want, like in OP.
- Make sure you are allowing the traffic in both PF and IPFW firewalls.
How do we go about getting this integrated?
-
@dabombnl said in Setup NAT64 in pfSense:
Just tried this and it works great. Here is what I did:
- Download FreeBSD 11.3 (or whatever version your pfSense is based on), copy /boot/kernel/ipfw_nat64.ko to your pfsense install.
- Load the IPFW module: 'kldload ipfw_nat64'
- Enable IPFW: 'sysrc firewall_enable=YES' and 'service ipfw start'
- Enter the nat64lsn rules you want, like in OP.
- Make sure you are allowing the traffic in both PF and IPFW firewalls.
How do we go about getting this integrated?
There is very old feature request, but the developers haven't seemed to be working on it.
https://redmine.pfsense.org/issues/2358
Maybe you could add this comment to the end of the feature request and see if it will bump it.
I do know that the unbound resolver has added a feature to turn on the DNS64 support in 2.5 roadmap.
-
Just went ahead and implemented this.
https://github.com/pfsense/pfsense/pull/4405
Have never tried to integrate code into pfSense before. Will see how it goes.
-
Thanks for this. I am hoping your work will make it into pfsense.
I would love to contribute, but coding and such is just not my forte, so even for submitting what you have you have my thanks whatever the outcome.
-
Just FYI: the issue https://redmine.pfsense.org/issues/2358 got that pull request #4405 so it should go into review now.
-
@jegr said in Setup NAT64 in pfSense:
Just FYI: the issue https://redmine.pfsense.org/issues/2358 got that pull request #4405 so it should go into review now.
Unfortunately this didn't make it.
We will have to start all over.
-
I was researching this and this is the best I could find.
https://www.arnavion.dev/blog/2020-04-18-i-switched-my-home-network-to-ipv6/ -
-
@SpoZen well, I'm going to Lazarus this thread
We'll have NAT64 in 25.01. I may even decide to put it in CE 2.8.
This is an effect of the work we've been doing on pf of late.
To use it, you simply give pf a rule like:
pass in on $LAN inet6 from any to 64:ff9b::/96 af-to inet from ($WAN:0)Of course, this will be buried well inside the pfSense UI, you'll just have to enable with minor config.
Unbound already supports DNS64
-
@jwt Definetly looking forward to it and be glad to test it out in first snapshots/betas that will have it. We can easily hook up an v6 only network in the lab (there should already be one) and give it a spin :)
