WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?
-
We have WAN (ISP) static lease line with IPv6, but in our internal network LAN We having IPv4 it is possible to NAT or configure for internet in PFSense?
-
No, there's more to the differences between IPv4 and IPv6 than just addresses. There is something called 464XLAT, used on cell phones that will do that, but I don't know that it's available for pfSense. Does the ISP not provide any IPv4, even if only carrier grade NAT?
-
@JKnott
Thanks for your update,
For 1:1 NAT for IPV6, the ISP providing n numbers of IPs. But for IPv4 ISP is charging very high price for singe IP. -
Why are you using NAT on IPv6? NAT is a hack to get around the IPv4 address shortage. You should have a huge number of addresses on IPv6.
-
@JKnott ,
Yes ipv6 is the huge number that was given by ISP, But don't know how to use with the pfsense. Can you kindly help on it. -
@moorthyragav said in WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?:
But for IPv4 ISP is charging very high price for singe IP.
So your saying they are not assigning your device wan any ipv4 address? Not even a carrier grade nat IP, ie rfc1918?
-
@johnpoz
They are providing /30 ipv4 address with gateway and /126 ipv6 address with gateway.
But they given LAN Pool with /64 with out gateway.we don't know how to use it.
Now we are plan to change our LAN segment to ipv6. -
@moorthyragav said in WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?:
But they given LAN Pool with /64 with out gateway.we don't know how to use it.
Ask your ISP what they support. Many use DHCPv6-PD, which provides the prefix, which pfSense then assigns to an interface. However, a single /64 isn't much, though certainly usable. My ISP provides a /56, which is 256 /64s, which I can use as I wish.
BTW, a /126 is unusual. My pfSense is assigned a /128, which identifies it only and is not used for routing. If they're providing a point to point connection, they should be using a /127, which is what is recommended in the RFC.
-
@moorthyragav said in WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?:
They are providing /30 ipv4 address
And why do you think you need more than that? Are you wanting to host services behind this IP(s)? Your outbound connections will be natted to the wans IPv4 address..
-
yes, we are using 30 public IPs 1:1 nat for our clients with old ISP.
Now the new ISP provider not giving IPS in v4, so we are facing issue. -
@moorthyragav said in WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?:
yes, we are using 30 public IPs 1:1 nat for our clients with old ISP.
Now the new ISP provider not giving IPS in v4, so we are facing issue.That is quite different from what you said initially, when I thought you weren't getting an IPv4 address at all.
"But for IPv4 ISP is charging very high price for singe IP."
IPv6 will provide plenty of addresses. As for IPv4, you either have to pay or find someway to share addresses. If you're only hosting web sites, it's possible to put all the servers behind NAT and then use the original URL to select which server to go to. However, I have no experience with that.
Also, your original idea would have done nothing for those with only IPv4 trying to reach those servers.
-
@moorthyragav said in WAN IPv6 and LAN IPv4 is Possible to configure in PFSense 2.44 ?:
yes, we are using 30 public IPs 1:1 nat for our clients with old ISP.
So let me get this right - you have clients that currently have a public IPv4 address for their own use.. And now your plan is to move them only to ipv6..
Pretty sure many of them will just leave, if you do that. While ipv6 is the future and all.. If these clients are currently hosting services to their customers/clients via IPv4 and you take that away from them - they prob going to be pretty freaking pissed ;)
The whole internet is not all ipv6 capable - and they could loose many of their customers/clients if they can no longer provide their services via IPv4... Did you ok it with all your clients the removal of IPv4?
