I can't be sure about OPNsense WAN side GUA at the moment. While I was working on this problem last night, I started experiencing some bizarre behavior from the OPNsense firewall. It displayed weird pop-ups that said "Dangerous error" and then became non-responsive. Its boot process is now abnormal. Protectli support says they've never seen that behavior before and recommends reinstalling OPNsense. If I still have problems, they will replace the SSD. Anyway, I am currently using my previous firewall (Supermicro E200-9B/pfSense). I have the same issues here (this makes me think that I am missing something basic), though my pfSense WAN interface has the following IPv6 addresses:
The ONT is more than just a simple network terminal. Race provides a Calix u6xw/4227w ONT/"Residential Gateway" at the customer endpoints of its fiber network. I only use it as an ONT, since I normally use a Protectli Vault V1410/OPNsense as a router/firewall feeding two Ubiquiti WiFi access points and some GbE wired connections.
From the Calix GUI I can ping and traceroute, just like I can from the OPNsense GUI. From the OPNsense GUI I can ping and traceroute with IPv6 to arbitrary host FQDNs, as well as IPv6 addresses.
Code Select
IPv6 Link Local fe80::ec4:7aff:fe7f:80f4%igb0
IPv6 Address 2607:9b00:620d:7b00:ec4:7aff:fe7f:80f4
I have only seen Link Local addresses on the LAN side (both in OPNsense and pfSense), is this expected behavior?The ONT is more than just a simple network terminal. Race provides a Calix u6xw/4227w ONT/"Residential Gateway" at the customer endpoints of its fiber network. I only use it as an ONT, since I normally use a Protectli Vault V1410/OPNsense as a router/firewall feeding two Ubiquiti WiFi access points and some GbE wired connections.
From the Calix GUI I can ping and traceroute, just like I can from the OPNsense GUI. From the OPNsense GUI I can ping and traceroute with IPv6 to arbitrary host FQDNs, as well as IPv6 addresses.