I have OpnSense running on a Proxmox VM with multiple networks. These are not VLANs from OpnSense perspective as Proxmox vnets are used to hide them from OpnSense. In OpnSense they are all separate networks.
I use DNSMasq for DHCP and tried both native as well as separate router advertisements and both have the same problem.
I have IPV6 enabled on three networks - these are ULA addresses used for internal communication.
DMZ (VNET VLAN - one VM on a wired network)
- statically assigned IP4 and IP6 addresses using DHCP and DHCP6. Slaac is used to generate addl. private outgoing IP6 addresses. (No issues)
Admin (VNET VLAN - fixed/known devices on wifi)
- statically assigned Ip4 and IP6 addresses using DHCP and DHCP6 (no Slaac) (no issues)
Home/LAN (all other devices using WiFi - this is not a VNET but untagged linux bridge created with a physical port on the machine)
All addresses on this network are dynamically assigned by DHCP for IPV4 which works.
In case of IP6, I tried many options (DHCP6, Slaac with Stateless DHCP for DNS address, both). In all cases, address assignment works few times after the changes are made in OpnSense and subsequently stops working.
When I check the log of DNSMasq there is RTR-Advert for the network address but no DHCP-Solicit from the clients after the first few times.
Any suggestions are appreciated.
I tried many times with all variations and I can't find a reason why it happens only on this network.
I switched Home and Admin such that now Admin uses the untagged network and Home uses tagged network.
Now the problem occured on Admin interface. It looks like this problem is specific to the untagged network.
Hope that generates some interest and suggestions.