Fixed
vyos@r1# set interfaces ethernet eth2 description foo [edit] vyos@r1# set interfaces ethernet eth2 mtu 1200 [edit] vyos@r1# commit [ interfaces ethernet eth2 ] link-local IPv6 address will be configured on interface "eth2", the required minimum MTU is 1280!
Close it, as it is not bug/feature
@zsdc Can we close it?
Fq_codel was added for 1.4/1.5 in T5489
Not planning to do it for 1.3 now
Not sure if Jool supports it.
As I understand, it is better to have a separate address for translations, otherwise, you should define ports for 64 translations. If you set 1-65535 for the "main" address, you will lose connections and can't use those ports for the system (they will be available only for translations)
Jool uses its own bib table instead of conntrack to manage nat mappings.
So you should add a separate pool only for translations.
Is it possible to add a feature of setting the translation pool address to follow an interface IP address similar to nat44's source masquerade for those with dynamic public IPv4 addresses?
@w4 could you provide some links or retest? Which patches?
The bug is not clear.
Should be fixed in T5817
Could you re-check?
Done for 1.4/1.5 https://github.com/vyos/vyos-1x/tree/current/python/vyos/utils
It won't be implemented for 1.3 as we risk breaking something.
I finally got a chance to dive into this some more.
PR for 1.5: https://github.com/vyos/vyos-build/pull/476
Also while at it, the smoketests regarding UPnP should probably be updated by this task aswell since they claim everything is OK:
configuration for dhcp reservation with just mac address doesn't give configuration exception, but cause an error to kea directly as ERROR [kea-dhcp4.dhcp4/49022.140176366361024] DHCP4_PARSER_FAIL failed to create or run parser for configuration element shared-networks: specified reservation for DUID: hwtype=1 xx:xx:xx:xx:xx:xx must include at least one resource, i.e. hostname, IPv4 address, IPv6 address/prefix, options (/run/kea/kea-dhcp4.conf:59:5)
Thanks for that heads-up @Viacheslav - My bigger concern with this task was the failure-mode of the configuration problem being so unexpected and hard to troubleshoot.
@Viacheslav I upgraded to the latest rolling release and this seems to work perfectly.
So, I tested the version 1.5-rolling-202312191154
Firstly, this bug should be fixed T5837
@zsdc Can we close it?
It won't fix due the old backend
Fixed in 1.4/1.5
We agree not to use raw options anymore.
If some options are required, it should be a separate PR per configured option.
Most of the changes are not supported by reload accel-cmd/systemctl unit.
Accel-ppp cannot apply some features/changes without the daemon restarting. In other words, there are only several features that could be applied by reload.