2.2.1: No IPv6 assigned to LAN anymore

maverick_slo

You described my case very well ;)

kejianshi

OK - I see.

azzido

Now I use my custom config file```
interface em0_vlan88 {
send ia-na 0; # request stateful address
send ia-pd 0; # request prefix delegation
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_wan_script.sh"; # we'd like some nameservers please
};
id-assoc na 0 { };
id-assoc pd 0 {
prefix ::/48 infinity;
};
I would like to use the advanced config section but I don’t know exactly how to fill up these fields. The first part works, but where should I put```
id-assoc na 0 { };
id-assoc pd 0 {
	prefix ::/48 infinity;
```for getting the right result?

Configure advanced settings exactly how they appear in the image I posted, then add '::/48' in the 'Prefix ipv6-prefix' field and 'infinity' in 'pltime' field.

azzido

@maverick_slo:

Yeah that is not good :)
But my provider gives me one /64 static connecting segment (pppoe) and a static /56 that I divided into 256 /64 networks and I HAVE TO USE STATIC on my VLANs :)
Trac interface is at no use to me…

br,
m

maverick, why do you have to use static on your VLANs? I use DHCP6+PD with VLAN configured as track interface and everything works fine.

maverick_slo

Because I need: XXXX:XXXX:XXXX:XXXX::X to be static and always the same.
I have 5 subnets that I chose and of course they need to be static…

azzido

So essentially you are doing it because you want to have a short interface identifier (rightmost 64-bits) in your IPv6 address instead of having them be auto-configured, which would be the case if you used track interface. Did I understand that correctly?

maverick_slo

My provider gives me static /56 which means 256 /64 subnets.
I cant use track interface for this config to work in my 5 subnets of /64… Also small ip size is cool to have but its not intended or needed in my case...

azzido

Did you try following configuration? In your case you can have up to 256 track interfaces, so I still don't understand what exactly is not working for you.

WAN Configuration
IPv6 Configuration Type: DHCP6
DHCPv6 Prefix Delegation size: 56
VLAN1 Configuration
IPv6 Configuration Type: Track Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 1
VLAN2 Configuration
IPv6 Configuration Type: Track Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 2
VLAN3 Configuration
IPv6 Configuration Type: Track Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 3
VLAN4 Configuration
IPv6 Configuration Type: Track Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 4
VLAN5 Configuration
IPv6 Configuration Type: Track Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 5

maverick_slo

Oh man….
Sorry but you will have to learn to read what I posted.
It is all working for me with advanced options or custom conf file.

For the last time I DON`T WANT TO USE TRACK INTERFACE OPTION! :)

kejianshi

Unless I'm confused, your setup will break eventually.

maverick_slo

My setup?
Why?

hda

@kejianshi:

Unless I'm confused, your setup will break eventually.

Conclusion is the "Track Interface" is promoted to the default LAN config. Plus automated issuance of LAN IP using SLAAC.
The don't bother out-of-the-box solution for beginner. ;)

All other LAN config goes by using WAN "Advanced". Fine with me.

maverick_slo

Couldn't agree more.
My ipv6 setup works like this 3 years, last 2 years on pfsense…
Autoconfig of lan seems bad idea for me and my both networks, home and work...

hda

@maverick_slo:

…
Autoconfig of lan seems bad idea for me and my both networks, home and work...

IF or WHEN my native (quasi-)static number of IPv6 prefix, by DHCP(PD), is changed (by ISP) I want to have my LAN dropped !. Security. No secret unnoticed changes from the far side allowed. :)

kejianshi

IMHO its a bastardized solution and getting a tunnel would be better for what you guys are doing, but its cool. Sounds like you are well aware it is not ideal.

hda

@kejianshi:

IMHO its a bastardized solution…

Yes, Track Interface is wizard-like, the easy way out. But, if one does IPv6, they should know the manual workings, in analogy with (experience of) multiple IPv4-no-NAT. So for me the full (overly) automation with Track Interface is a security flaw or allowing meddling with your site by ISP.

kejianshi

The things you talked about are not the problem for the average user as I see it.

Yes its good to understand the inner workings and all, but the problem as I see it is that you are assigning static IPs on the LAN from a /48 or /56 or /64 or whatever that is assigned dynamically by dhcp and could break in a day or a year. Who knows?

Thats the part I'd never do, but if its working for you and you don't mind the possible breakage, then thats cool.

For me, its a show stopper if my internet breaks because my pfsense is far far away.

hda

@kejianshi:

The things you talked about are not the problem for the average user as I see it.
…

There is no such as an average user 8)

But. ISP WAN/LAN prefix changes AND the LAN SLAAC on boxes are without question a privacy security risk issue. pfSense should promote security. This comes with understanding what one is doing. Otherwise one may just get a consumer-router-FW. (duh) :)

kejianshi

I agree - Thats why I'd advise you to get a reliable /48 from HE. Its actually static.

hda

@kejianshi:

…get a reliable /48 from HE....

Dependent on IPv4, that's funny.
I want local paid accountability, not SIXXS or not HE, and parallel functionality level like multiple-IPv4.