a bug causing MTU to be set by DHCP rather than .conf has been resolved and should be available in wicked 0.6.16
Does anybody know what kind of timeframe shold be expected ?
This may be a minor problem for most users but in my case ( a server acting as router among others ) the bug actually cases errors in internet apps on the LAN behind.
A workaround in the meantime might be to set your server with a static address (hence not using DHCP).
Depending on how DHCP is setup,
If the DHCP lease is very long, you might configure your static address to be the same as the the address handed out by DHCP
If you understand how the IPv4 subnet mask works, you can determine whether the DHCP address range monopolizes the entire address space or not. If it doesn’t, then you can determine what IP addresses in the address space are unused and available, then set your server to one of those addresses (Would recommend coordinating with your ISP so they know what you are doing).