pfSense 2.7.2CE not working when trying to assign multiple interfaces

[BigTulsa]

Re: Multiple IPv6 Prefix Delegation over AT&T Residential Gateway for pfSense 2.4.5

Trying to ascertain if this still works for this version of pfSense (2.7.2CE). I followed the referenced topic, but once I rebooted, I got what appaeared to be a public ipv6 on the WAN interface but the IPv6 tools couldn't read my public IP, and the lans didn't get a ipv6. If I disable the script, and set back to my old config where I set the delegation prefix to /64 instead of /60, then I get a public ipv6 for the WAN and my first interface gets an ipv6 as well (I have two interfaces set up, one for wired connections and one for my Unifi AP.

This was the config I used:

interface em0 {
        # Enable ia-na if you want WAN to be given a prefix delegation
	send ia-na 0; 
	send ia-pd 0;
	send ia-pd 1;
	send ia-pd 2;
	send ia-pd 3;
	send ia-pd 4;
	send ia-pd 5;
        send ia-pd 6;
	send ia-pd 7;
	request domain-name-servers;
	request domain-name;
	script "/var/etc/dhcp6c_wan_script.sh";
};
# Enable ia-na if you want WAN to be given a prefix delegation
# id-assoc na 0 { };
id-assoc pd 0 {
	prefix-interface em1 {
		sla-id 0;
		sla-len 0;
	};
};
id-assoc pd 1 { 
	prefix-interface em2 {
		sla-id 0;
		sla-len 0;
	};
};
id-assoc pd 2 { };
id-assoc pd 3 { };
id-assoc pd 4 { };
id-assoc pd 5 { };
id-assoc pd 6 { };
id-assoc pd 7 { };

I'm wondering if allowing the ia-na 0 is causing the problem here or if I should comment that out from the script. I will likely try it here shortly, but I wanted to jump in here to see if anyone has tried this?

My device is the BGW-320-500 firmware 6.30.6

[Gertjan]

@BigTulsa said in pfSense 2.7.2CE not working when trying to assign multiple interfaces:

I'm wondering if allowing the ia-na 0 is causing the problem here or if I should comment that out from the script. I will likely try it here shortly, but I wanted to jump in here to see if anyone has tried this?

Only one way to be sure :
packet capture the DHCPv6 traffic (dhcp6c and other) and see what 'you' send out and what your ISP box or DHCP4v6 send back as a result.

Be ware :of the reality : IPv4, after 5 decades or so, has reached the 'stable' situation and works pretty well.
IPv6 is another thing. There are the official IPv6 RFC's, and the joke of the century : every ISP interprets them 'differently'. So what works for me - doesn't work for you.
When dealing with IPv6, mention who is your ISP - what equipment you use on the other side of the pfSense WAN port.

Example, my ISP has a pretty good IPv6 support.
I get a IPv6 for my pfSense WAN, and a prefix for my LAN.
Here it comes : just one prefix, even if my pfSense wants more. So I can equip just one LAN with IPv6.
I use the pro version of the ISP Internet access of course. But my ISP (Orange, France) isn't aware of the fact that a company can use more the one LAN ..... (no joke )

My WAN DHCP6 settings :

If I change the /64 for 'something else' everything breaks.

edit : and my ISP box tells me :

so it tells me that it has a /56 or 256 x /64 avaible ....

@BigTulsa said in pfSense 2.7.2CE not working when trying to assign multiple interfaces:

version of pfSense (2.7.2CE).

Hummm.
Your using bleeding edge technology = IPv6 prefixes for your pfSense LANs : what about using the bleeding edge solution : upgrade to 2.8.0 beta right away.
It works ...