Thanks for reopening and reporting.

Sorry, I must reopen this task. Absolutely the same situation with multiple "lower" interfaces:

OPTIONS="-6 -l ::%eth1.100-l ::%eth1.102 -u 2001:db8:0:feed::2%eth2.88 -u 2001:db8:0:feed::3%eth2.88 "
                         ^^
                         here

This will be a nice feature, exactly what I needed. Is it hard to implement? I could help testing the ovf deployment to vSphere.

The packages were out of sync with reality, it should work as expected now.

@zsdc Can you please test your use case? thx.

Ok, so I found it. host_name.py is being called when dhcp had been configured and the system rebooted. vyatta-cfg-system didn't call host_name.py when an interface is configured via dhcp, so when you configure dhcp for the first time and don't reboot /etc/resolv.conf stayed empty.
I need to test it in crux, but i think there is the same issue, therefore you would need 2 commit in crux, host_name.py and the one from the address node in vyatta-cfg-system.

There is still an issue with it, when the system is rebooted all is working as expected, but when you configure dhcp on the fly, hostname.py is still doing something weird and leaves resolv.conf broken.

cherry-picked (https://github.com/vyos/vyos-1x/commit/361a4419e0042369fae7eddf67f06a658372db93)

cherry-picked. (https://github.com/vyos/vyos-1x/commit/d0d044918ae10b2a5db1a4f218adef4187ca7e22)

Fixed in: http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-quagga/vyatta-cfg-quagga_0.19.1+vyos2+current9_all.deb or next rolling release.

Issue verified, new bug ticket or shall we use this one to resolve the issue. Looks like it's been broken for a while.

set protocols static route 10.100.100.0/24 next-hop 10.1.1.1 next-hop-interface eth1

@syncer @zsdc tested the rolling from tonight, works as far as i can tell, however it looks like 'delete protocols static ip' doesn't work. Not sure if it was always broken or not, I have a look into it asap.

VyOS runs on 4.19.28 for a week now. Update can be used for both crux and current.

AS Curretn and Crux kernels and modules are build the same way, it's on @dmbaturin to use the packages. From the source side everything is there.

There's nothing special to do for crux, just build the packages for the next release.

There is no specific crux branch here. @dmbaturin only needs to build the appropriate packages and we're good.

Yep. Can confirm issue is fixed with the latest hot fix.

With 1.2.0-H4 this issue seems to be fixed on my router.

@hagbard need this in the crux

@hagbard if that in the crux, you can close this, marked it as finished for 1.3

@c-po should be in crux too

@c-po need to backport it into the crux branch

@c-po is also in crux?

@hagbard need to confirm it in the crux too

@hagbard need this merged into the crux branch

Need to backport this to 1.2.1

need to backport it into the crux branch