I too have battled with this before and gave up, accepting only ipv4 in pfsense. OpnSense ipv6 worked, but I preferred not to shift to OpnSense as I rely on some stuff in pfsense.

Seeing this thread, I dutifully followed V's post at Orange DHCP conformité protocolaire 2023 - lire depuis le début du sujet

In the end, I had the same result as I always do. No luck.

Could you look at my attached screenshots below and see if there is any mistake?

ia-pd 0, raw-option 6 00:0b:00:11:00:17:00:18, raw-option 15 00:2b:46:53:56:44:53:4c:5f:6c:69:76:65:62:6f:78:2e:49:6e:74:65:72:6e:65:74:2e:73:6f:66:74:61:74:68:6f:6d:65:2e:4c:69:76:65:62:6f:78:35,  raw-option 16 00:00:04:0e:00:05:73:61:67:65:6d, raw-option 11 $1, raw-option 1 00:03:00:01:E4:$2
dhcp-class-identifier "sagem", user-class "+FSVDSL_livebox.Internet.softathome.Livebox5", option-90 $1, dhcp-client-identifier 01:E4:$2

The Mac address of my live box starts with E4 for reference.

Thank you!

In the end I got IPv6 and I detailed the procedure (and all the things I wondered about when I read the forum) in « Orange DHCP conformité protocolaire 2023 - lire depuis le début du sujet » pinned post (90th page – the last right now).

It’s in french but as my pfsense is in english I mention all the options by their english names so you should be able to figure it out.

I see in your wan that you did not tick DHCP6 VLAN Priority, thus not doing the COS stuff, this might be it since I think it is mandatory.

I am afraid I cannot provide much more help, I’m a monkey with a hammer and patience.
I have no deep understanding of what I am doing yet. Just cross checking information I find and trying stuff. Knowledge develops along the path but remains below the average level around here.

Thanks, I went ahead and ticked that box unplugged all the cables from the ONT for a few minutes and restarted pfsense and reconnected the ONT. Unfortunately no change.

Your post with your settings carefully laid is definitely appreciated, I wonder though if I might be missing something else, that I could spot in screenshots? When you have time would it be possible to make a comprehensive collection of screenshots?

I know Keyser was also interested in this, I wonder if he has had a chance to try?

Cheers

that's one of the main reason I migrated to opnsense (along with netgate update policies on the free version), having been a user since ~v1.2.1. I ended up facing the exact same conclusion I didn't want to replace binaries after each upgrade. (and most of the upgrades didn't work out out of the box. I remember pain when upgrading to v2.5 and 2.6  ).

Hello Sloopbun,

My apologies for the late answer, i am afraid I cannot provide screenshots since I ditched pfsense.
I have a wireless card at hand that – of course – has no BSD driver so I am looking for a Linux solution now.

For your first question, as far as I know yes. Sosh is the low-cost Orange. Main difference is the absence of any shop to ask for help. You have a chat and that’s about it for customer service.
Then, I think they have a slightly different offering in terms of bandwidth. Sosh is lower.

For the second question, as far as I understood yes absolutely, the ONT is the device talking to them on their side and they need to know it to actually whitelist it : hence calling them and giving them the serial number and vendor id. I have no idea how you actually got it working ? Then I don’t think sfp modules users do that so there must be another path, but I didn’t looked in depth.

I was using pfsense 2.7 Community Edition and yes modified DHCPc binaries.