IPV6 Static IPV6 address

johnpoz

@JKnott said in IPV6 Static IPV6 address:

Incidentally, there are enough IPv6 addresses to give every single person on earth over 4000 /48s! No need to cheap out with them.

Yup.. and like the smallest block an ISP can get is a freaking /32 so even if all they had was that, they would still be able to hand out 65K /48s... So give the users freaking /56's for gosh sake.. They could have like 16M users all getting /56's If you want to be extra tight - make it /60s, what something over 268M they could hand out.. And that is just with a small /32, which again is like the min allocation arin will give you as an ISP..

I think comcast got what a /9?

edit: If you isp is going to be stupid with their ipv6, just head over to hurricane electric.. You can get a free /48 from them.. Which you can use on any isp you want, even if they don't support it.. I have the same /48 since like 2011.. And my current isp doesn't even support IPv6 - but doesn't matter since I have my /48 that I can just tunnel over any ipv4 network.

axsense2

I am going to get wider network than /64 next week. So that problem is going to be solved. But how to continue using best practice?

Lets suppose I get wider net. Lets say it is /56.
2a00:900:10:0001::/56 network
GW is 2a00:900:10:0001::1/64

I set WAN address of PFSense to GW is 2a00:900:10:0001::2.
So I should put something like 2a00:900:10:0101::1/64 to LAN nic address I suppose...

Is this all needed (I also have Firewall rule for routing from LAN to WAN_IPV6)? Should SLAAC take care of broadcasting 0101-network addresses to LAN devices or should I use DHCP6 as a best practice?

Ax.

johnpoz

You would never set a /56 on an interface... They would give you a transit network to use for your wan, or just link local - but that is kind of hard to route to. Or you would use say the first /64 in that /56 as your transit (wan) and then put the other /64s behind it.

Your need to get with your ISP on how to set it up..

JKnott

@johnpoz said in IPV6 Static IPV6 address:

I think comcast got what a /9?

That's a huge amount. Given that only 1/8th of the IPv6 addresses are GUA, that would be 1/64th of them. A few more of those and we'd be back in the same situation as IPv4, where a few organization had most of the addresses. IIRC, IBM had at least 2 /8s, which were in use in my office 20 years ago. The token ring LAN was 9., but we were moving to Ethernet on 8., IIRC. My own static address was 9.29.146.147. They had several /16 blocks too.

JKnott

@axsense2 said in IPV6 Static IPV6 address:

Lets suppose I get wider net. Lets say it is /56.

You'd split that into /64s. In PfSense you do that by selecting the IPv6 Prefix ID, when you configure an interface. You might also get a different gateway address.

Gateway addresses can be "fun" in IPv6. While you can use a routeable address, link local addresses are also often used. Regardless, they all resolve down to the MAC address & interface, to actually move the traffic. In a situation, such as mine, where a /128 address is assigned, traffic doesn't move through that address, but the ISP could use it to determine the MAC address that they have to talk to. Then again, they could use the DHCPv6-PD requests to determine the link local address and get the MAC through it.

JKnott

@johnpoz said in IPV6 Static IPV6 address:

but that is kind of hard to route to

All routing resolves down to interface and MAC address. The MAC isn't even needed on point to point links.

johnpoz

true - my point is I think it would be easier to just use a specific /64 as transit and give the users a /128 to set..

But yeah the isp could do it a bunch of different ways - which is why he needs to get with his isp for the specific instructions allowing him to use the /56 behind his router.

axsense2

@johnpoz said in IPV6 Static IPV6 address:

You would never set a /56 on an interface...

In where do you see I am using /56 on an interface? There are /64 on interfaces in the example.

Your need to get with your ISP on how to set it up..

My ISP does not provide PFSense support.

So my setup can be (we assume that I will have /56 network)
WAN:
IP: 2a00:900:10:0001::2 / 64
Upstream GW: WAN 2a00:900:10:0001::1

LAN:
IP: 2a00:900:10:0101::2 / 64
(there is no Prefix ID when LAN IPV6 configuration type is set to "Static IPv6")

Should this work without setting DHCP6 on LAN side?

johnpoz

@axsense2 said in IPV6 Static IPV6 address:

My ISP does not provide PFSense support.

Has ZERO do with what your using.. It has to do with how your suppose to set it up.. What is your transit, do you set static - then what are the details. Are you suppose to use slacc, are you suppose to use dhcpv6-pd, etc. etc.

JKnott

@axsense2 said in IPV6 Static IPV6 address:

My ISP does not provide PFSense support.

An ISP providing pfSense support would be the same as an ISP providing Cisco or D-Link support. The equipment is irrelevant. It's the protocols that matter.

axsense2

I am only asking what is best practice from PFSense perspective using example IPs. I am not asking ISP how to set up PFSense, I am asking it here. I am not asking ISP information from you, that is provided by ISP.

Lets put it this way.
As an example ISP provides a customer following network:
Network: 2a00:900:10:1000:: / 56
GW: 2a00:900:10:1000::1 / 64

What is suggested setup using static IP on WAN side?

Edit: Try&Error method started...
Edit2: I hope someone writes a tutorial how to setup static IP based configuration as good as they are WAN DHCP client ones...

NogBadTheBad

This post is deleted!

axsense2

Lets split this in easy questions. ISP provides /48 network a : b:c::

On WAN interface, static IP is being used. IP is a: b:c::1
What is length? /64 or /48?

johnpoz

it would NEVER be /48... You would never set a mask/prefix on a interface to anything other than /64 or /128.

If your isp is giving you a /48 it needs to be routed.. It would never be on any interface, if they are directly attaching you to a /48 they are doing it WRONG!!

axsense2

Ok. This is clear. So my setup is building up. Lets continue.
ISP network a: b:c:: /48
ISP GW a: b:c::1 /64
My WAN IP is now a: b:c::2 / 64

Then LAN side. I have subnets behind PFSense, but also individual devices.
Lets use the next /64 for LAN.
Static LAN IP: a: b:c:1::1 / 64

This must be correct, right?

johnpoz

Yes you can use any of the /64s out of the routed /48 on your lan.. But the 1st one might not be your transit.. They might give you something other than part of your /48 as your transit.

Or maybe they just use link-local.. Maybe they want you to use a /128 on your wan, maybe they want you to just let your wan get via slaac.. Have no idea - which is why get with them!

axsense2

johnpoz, please forget ISP already. I am building up IPV6 reference setup of configuring PFSense for myself as a learning curve. I asked for best practices. And best practices for PFSense only. Something I can use later with ISP connection. It was clear after two posts that the network they provided will not work. I will get a new next week.
But thank you for the confirmation and the clarification of transit detail.

So, lets move on into practice. There are quite many parameters needed to be correct in order everything to work.. I can assume. I tried following in PFSense.

Network setup:
PFSense LAN IPV6: 2001:1111:2222:3333::1 /64

DHCPv6 server enabled using following parameters:
Range start: 2001:1111:2222:3333::100
Range end: 2001:1111:2222:3333::1ff
Prefix Delegation Range start: 2001:1111:2222:3334::
Prefix Delegation Range end: 2001:1111:2222:333f::
Prefix delegation size: 64
Router mode: Managed

So my HW setup is:
PFSense [LAN] <--> [WAN] SubRouter1 [LAN] <--> PC [NIC]

PFSense LAN IP: 2001:1111:2222:3333::1/64 -> OK (set manually)
SubRouter1 WAN IP: 2001:1111:2222:3333::1c7/128 (DHCP seems to work OK)
PC IP: 2001:1111:2222:333e:6d12:8c45:1b7a:6388/128 (DHCP subnet provisioning seems to work since PC gets an address from 333e subnet OK)

Lets ping:
PC to SubRouter WAN: YES
PC to PFSense LAN: YES
Subrouter to PFSense LAN: YES
SubRouter to PC: YES
PFSense to SubRouter WAN: YES
PFSense to PC: YES

So this setup seems to work on IPV6 level. I don't know if that is best practice or even suggested setup, but maybe someone can comment on that (rather than asking me to contact ISP)... and sorry, I am not ungrateful or anything. Maybe there is language barrier and I can't express myself clear enough.

What surprises me a little bit is that I haven't configured anything like "Default gateway" in SubRouter nor PC. I can see that PC has default IPV6 gateway to SubRouter's fe80-address. So it works that way just fine. Because PFSense LAN IP is in the same subnet as SubRouter's WAN routing works between PC and PFSense. But I wonder what happens when I ping Internet from PC. That remains to be seen after I have working ISP IPV6 connection next week... (I would be surprised if Subrouter knows how to handle Internet traffic, but maybe IPV6/PFSense is smart enough for that too automatically...)

Ax.

axsense2

And yes, I wrote a little bit length message but I hope my learning notes helps someone else. I found quite many posts of how to set IPV6 on PFSense, but almost none related to Static IPs or using DHCP the way I need to. Also old seniors like me whom have done everything with IPV4 past 30 years there are quite many details done differently.

JKnott

@axsense2 said in IPV6 Static IPV6 address:

I asked for best practices.

How is that possible, when you don't know what the ISP is providing? The setup for DHCPv6-PD is quite different from assigned static addresses.

JKnott

@axsense2 said in IPV6 Static IPV6 address:

but almost none related to Static IPs or using DHCP the way I need to. Also old seniors like me whom have done everything with IPV4 past 30 years there are quite many details done

I'd suspect most people get IPv6 from an ISP that uses DHCPv6-PD. Again, until we know what you're dealing with, it's hard to offer advise.