Quote from: marvelolivia on Today at 01:48:31 PMThe VPP support definitely sounds interesting, especially for a Linux-based firewall. I'm curious to see how this project develops.VyOS has VPP support.
Quote from: marvelolivia on Today at 01:48:31 PMHas the source code/repository been made public yet?Not yet.
Quote from: mooh on Today at 01:23:18 PMQuote from: funtowne on Today at 06:38:51 AMOut of morbid curiosity I set up DNSMASQ with SLAAC as the mode with the IP range of my ULA ffd0::1000 to ffd0::2000 (ULA truncated).I'm fairly certain that it won't make a difference but a ULA is currently defined in the range of fd00::/8
Quote from: funtowne on Today at 06:38:51 AMOut of morbid curiosity I set up DNSMASQ with SLAAC as the mode with the IP range of my ULA ffd0::1000 to ffd0::2000 (ULA truncated).I'm fairly certain that it won't make a difference but a ULA is currently defined in the range of fd00::/8
Update your secondary unit and wait until it is online again
On your primary unit go to Interfaces ‣ Virtual IPs ‣ Status and click Enter Persistent CARP Maintenance Mode
You secondary unit is now MASTER, check if all services like DHCP, VPN, NAT are working correctly
If you ensured the update was fine, update your primary unit and hit Leave Persistent CARP Maintenance Mode
Quote from: meyergru on Today at 09:02:53 AMWhile you can syntactically do that and maybe the different RAs even get send out, I would not have expected it to work, because RAs are broadcasts, so they reach all clients. The mode flag determines if the clients should ask for DHCP offers. So, the clients will probably not request DHCP addresses once they see an RA that explicitely forbids them to.
I doubt that they would do that depending on specific ranges.
Quote from: Monviech (Cedrik) on July 30, 2026, 11:52:54 AMMaybe dnsmasq can do it. You can configure different RA pools on the same interface with different flags from what I can see.
But I never tested that.