Quote from: meyergru on January 29, 2026, 09:54:46 AMWhat is the question?
If that MTU works for you, you could probably distribute it network-wide with DHCP option 26 and there is also an RA option to send it, but as I said, IDK if those work for most clients.
Quote from: Patrick M. Hausen on January 29, 2026, 10:05:39 PMThese are the rules for the "Restricted" group:
1 2 3 4
[ SFP ] [RJ-45] [RJ-45] [RJ-45] [RJ-45]
4 LAN WAN DMZ |
|______________Shared______________|
igb0 igb1 igb2 igb3 igb0 (again)Quote from: tgurr on January 29, 2026, 11:50:48 PMSo after updating to 26.1 today I uninstalled the os-isc-dhcp plugin, so far so good, things still appear to work as intended.There were some reports of the option "Track Interface (legacy)" not properly disabling I believe in another topic so maybe the fix for that bug didn't work out completely as it should have ?!
However when trying to change the "IPv6 Configuration Type" in either my home or guest vlan/interface from "Track Interface (legacy)" to the new "Identity association" and try to save the changes I get an error message:QuoteThe following input errors were detected:
The DHCPv6 Server is active on this interface and it can be used only with a static IPv6 configuration. Please disable the DHCPv6 Server service on this interface first, then change the interface configuration.
which makes me wonder what the actual problem is since "Track Interface (legacy)" works without any issue, is it because I use "Dnsmasq DNS & DHCP"? I can't seem to find an option to do what I'm instructed by "disable the DHCPv6 Server service on this interface first" like in only use Dnsmasq DNS & DHCP for IPv4, like there was for ISC-DHCP and probably also is for Kea with its two separate Kea DHCPv4 & Kea DHCPv6 services to enable/disable.
QuoteOn another more or less unrelated note, some parts of the release notes are harder to read/understand for me than they maybe could be, for example:I was wondering the same and totally agree with you :)QuoteOne thing that the upstream software cannot cover is prefix delegation so that is no longer offered by default. Use another DHCPv6 server in this case.
"the upstream software": which one? supposedly Dnsmasq? Why not call it by it's name?
"Use another DHCPv6 server in this case": when Dnsmasq doesn't work in this case and Kea is the new alternative to the now deprecated ISC-DHCP, why not just write "Use Kea DHCPv6" in this case? Or doesn't Kea work here as well, or are there too many other alternatives to mention them?
And another thing I was kind of scared is because the talk is all about DHCP and IPv6, I was afraid that removing the ISC plugin would also remove the option for the WAN interface to select "DHCPv6" in its "IPv6 Configuration Type" option, so a small mention that it doesn't touch that part and/or that they're completely unrelated and this option will stay would've probably been reassuring as well.