IPV6 Static IPV6 address

axsense2

I thought I just open a document of many instructions how to setup IPV6 with static IP. But... wasn't that easy.
My ISP has gave me 2a00:900:10:10::/64 network
GW is 2a00:900:10:10::1/64

So I have put 2a00:900:10:10::2/64 to WAN interface. So far so good. I can ping outside world. IPV6 works in general.

I thought of changing LAN IPV6 interface to "Tracking", but no choices allowed. I can see several solutions including bridging, dhcp6 etc, but I would like to set this up the correct way. Not the way it happens to work somehow after tries and errors.
So my question is: how to set LAN side?

Ax.

viktor_g

from https://docs.netgate.com/pfsense/en/latest/book/interfaces/ipv6-wan-types.html:
"The Track Interface choice works in concert with another IPv6 interface using DHCPv6 Prefix Delegation. When a delegation is received from the ISP, this option designates which interface will be assigned the IPv6 addresses delegated by the ISP and in cases where a larger delegation is obtained, which prefix inside the delegation is used."

JKnott

@axsense2 said in IPV6 Static IPV6 address:

My ISP has gave me 2a00:900:10:10::/64 network
GW is 2a00:900:10:10::1/64

Your ISP's gateway is within your network? That will never work. Are you sure the info you posted is correct?

johnpoz

@JKnott said in IPV6 Static IPV6 address:

Your ISP's gateway is within your network?

Huh? Normally yes the gateway would be on the network your in..

I think the users problem is while the ISP gave him a /64, which other /64s are routed to that.. You need more than 1 network to route.. I take it they think your devices are directly attached vs behind a router.

axsense2

Hi. Thanks for the answer. Yes that is the information I got from ISP. Values are changed of course, but anyway.

I could not understand how I can route /64 network both sides, but the answer is that it is not possible of course.

Ax.

johnpoz

If they gave you 1 /64 then no you can not route another ipv6.. Did they not also give you a /56 or /60 to use behind that?

JKnott

@johnpoz said in IPV6 Static IPV6 address:

Huh? Normally yes the gateway would be on the network your in..

Then it appears they are just giving him a /64 range to work in. As you mention, in another note, he can't route to a local network beyond that point. This also means he needs a bridging firewall, instead of routing, as normally used.

With my ISP, my /56 is entirely my own and I use a link local address to route to the Internet. My firewall is assigned an address that is not within my /56. That address is also a /128, so it plays no part in routing.

axsense2

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.

axsense2

@JKnott said in IPV6 Static IPV6 address:

With my ISP, my /56 is entirely my own and I use a link local address to route to the Internet. My firewall is assigned an address that is not within my /56. That address is also a /128, so it plays no part in routing.

Could you give an practical example of this. Can I do that with my /64 network as well?

Ax.

JKnott

@axsense2 said in IPV6 Static IPV6 address:

Could you give an practical example of this. Can I do that with my /64 network as well?

I can describe my setup. My ISP uses DHCPv6-PD to distribute addresses and prefixes. PfSense gets an address, but it's a /128, which means it's not used to carry traffic, but can be used as a target address for VPNs, servers, etc.. This address is not within my /56. The prefix is passed to pfSense, to set the range of addresses I can use on my network. Since I have a /56, I can have up to 256 /64 networks. Local networks are always /64. My ISP's gateway address is fe80::217:10ff:fe9a:a199.

It sounds like your ISP is just giving you a /64 to work with, just like my LAN uses one of my /64s. If so, you can't route it to your local LAN.

BTW, I could configure pfSense to request anything from a single /64 to the full /56. If I selected only a single /64, I'd still have a route out of my network, that doesn't use an address within my /64.

I don't understand why some ISPs are so cheap with addresses. Even with my cell phone, tethered devices connect to a full /64 and the phone's WAN address is not within that /64.

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

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.