IPV6 and firewall rules - My newb is showing
-
@jknott Im still back trying to follow directions from a few posts ago.
You told me a couple of times to follow the directions on "Using Unique Local Addresses"
Im still trying to figure out this step. -
@jknott
Is this my GUA?
-
@cr8tor said in IPV6 and firewall rules - My newb is showing:
You told me a couple of times to follow the directions on "Using Unique Local Addresses"
On that page, I said "There are two parts to enabling ULA. First, a prefix has to be created on the Router Advertisements page.". The other part is about assigning an address to the pfsense LAN interface. Funny thing though, ULA will work without that address assigned. You just won't be able to communicate with pfsense, though you can route through it, as link local addresses are used for routing. However, when you create a VIP, you can just copy your existing GUA LAN address for that interface and replace the prefix portion with the ULA prefix you created, to create the full 128 bit address. The address will then have the ULA prefix, but the original GUA suffix. However, there is no need for the ULA and GUA suffixes to match, it's just a convenience. You could have just as easily used ::1 or some other number for the suffix. In fact, pfsense does that with the link local address. The link local address for pfsense, which is used for a lot of stuff, on my LAN is fe80::1:1. Fe80 indicates a link local address, and the remainder can be anything, though often based on the MAC. In this example, ::1:1 is used.
Yes, that is the GUA, as it starts with 2.
Here's a Wikipedia article which covers the different address types.
-
-
@jknott said in IPV6 and firewall rules - My newb is showing:
The subnet in RA is done.
Its set to fd18:1B87:B34B:0:: as i used in my example.However, when you create a VIP, you can just copy your existing GUA LAN address for that interface and replace the prefix portion with the ULA prefix you created, to create the full 128 bit address. The address will then have the ULA prefix, but the original GUA suffix.
How do i do this?
Step by step.
Copy from where, paste to where? Replace what with from where?
You speak as if speaking to someone that knows what they are doing. I do not. Hence, "My newb is showing" in the title.I am sure you are frustrated trying to help me with my lack of understanding.
Many thanks though for continuing to work with me. -
@cr8tor said in IPV6 and firewall rules - My newb is showing:
How do i do this?
Step by step.
Copy from where, paste to where? Replace what with from where?
You speak as if speaking to someone that knows what they are doing. I do not. Hence, "My newb is showing" in the title.On the Dashboard, all the interfaces are shown with their GUA. You can copy the LAN GUA from there. Then paste the entire address into the box where you create the VIP. Next, replace the prefix with the one you created.
I have been running IPv6 on my home network for over 11 years and have done a lot of reading about it. I also got my Cisco CCNA. I first started learning about IP in 1995, working with Ethernet in the late '80s and LANs in 1978.
-
@jknott
Here is whats on my dashboard.
My LAN GUA is below correct?
2602:b8:6364:a00::1I take that and paste the entire address into the box where I create the VIP.
Next, replace the prefix with one I created.So this: 2602:b8:6364:a00::1
Becomes this: fd18:1B87:B34B:0::1 which is what put in the VIP? -
Yes, that's correct. That page is interesting. They provide only the prefix, not a usable address on the WAN. Also, there isn't an IPv6 address for the wireless. What size prefix are they giving you? It looks like it might be a single /64, which means you might not have one for the wireless. As I mentioned, I get a /56 from my ISP, which provides 256 /64s. I have one each for my LAN, guest WiFi, test LAN, connection to a Cisco router and OpenVPN and have plenty left over.
Perhaps there's someone here who knows CenturyLink better.
-
@jknott said in IPV6 and firewall rules - My newb is showing:
Yes, that's correct.
Why did we copy the GUA LAN just to replace everything by the 1 at the end??
That page is interesting. They provide only the prefix, not a usable address on the WAN. Also, there isn't an IPv6 address for the wireless.
What page? I dont know what you are talking about?
What size prefix are they giving you? It looks like it might be a single /64, which means you might not have one for the wireless. As I mentioned, I get a /56 from my ISP, which provides 256 /64s. I have one each for my LAN, guest WiFi, test LAN, connection to a Cisco router and OpenVPN and have plenty left over.
How would i look this up?
Perhaps there's someone here who knows CenturyLink better.
I just need to know what address to type into the virtual IP box.
I dont understand why you dont just answer that without all the extraneous information and side talk. You have me so confused just trying to figure out your own example with a bunch of other random info thrown in.. ughIve given you all my info, just tell type out what 29 characters i should be putting in the VIP address box. Ive been trying to figure out this one thing for 5 or 6 posts now and you keep going off on whatever.
Just give me the address please. What do i put in the box. Once its working i can backtrace it and play with it and learn how it works. But until it works, its broken and i dont learn how to make it work. -
@cr8tor said in IPV6 and firewall rules - My newb is showing:
Why did we copy the GUA LAN just to replace everything by the 1 at the end??
I didn't know it would be ::1 at the end. Take a look at mine and you'll see what my address was.
What page? I dont know what you are talking about?
That page you provided that showed your WAN, LAN and Wireless addresses.How would i look this up?
I don't know with CenturyLink. Perhaps you could call support.
I just need to know what address to type into the virtual IP box.
It's the address you created with the ULA prefix and the ::1 at the end. As for all that other info, I'm just trying to help you understand how things work.
-
I may have forgotten to provide the ULA address for pfsense on my LAN. Here it is:
fd48:1a37:2160:0:4262:31ff:fe12:b66c
As you can see, it doesn't end in ::1.
-
@cr8tor said in IPV6 and firewall rules - My newb is showing:
So i guess my underlying question might be "How do i properly set up IPv6 with dynamic address's to use firewall rules?"
It is somewhat easy to do with DHCP6, but if your ISP is not providing this, then forget it and stick with a HE-tunnel.
-
@cr8tor First thing is to save your DHCP DUID in the configuration (System > Advanced, Firewall & NAT)
You need to be sure you are giving the provider the same DUID every time so you get the same prefix delegation every time.
If you do this and they continue to give you a different prefix, they are broken.
IPv6 should be static for the all of these reasons. ISPs chose to implement dynamic addressing instead.
-
@derelict said in IPV6 and firewall rules - My newb is showing:
First thing is to save your DHCP DUID in the configuration (System > Advanced,
Interesting. Can I use this option to randomly change the host part of the IPv6 address on WAN? I do some NATing with it and would like to have something like privacy extensions for it or maybe this? The prefix is dynamic and I have to reboot pfSense daily via cron anyway.
-
Why would anyone want to run NAT on IPv6? NAT is a hack that was used to get around the IPv4 address shortage and it breaks things in the process.
If you want stable addresses for local DNS and your ISP won't supply them, then use Unique Local Addresses, as discussed above.
-
Changing it to DUID-LLT did nothing for me, even after a reboot.
@jknott I use it on one interface to give only one special host IPv6 connectivity to the internet, everything else on this interface has no NAT rule and because of that no IPv6 internet. I got dynamic prefixes and with this, it is one simple solution to my "problem".
I also use it to do DDNS on pfSense and not have to do it on the hosts. I wish the DHCPv6 Server could to DDNS by itself, this would be the best spot, but pfSense is not ready yet I guess.
I myself like dynamic IPs and prefixes because of privacy reasons, as long as DDNS is working.
