It seems issues with migrations
[ OK ] Reached target cloud-init.target - Cloud-init target. [ 28.675603] vyos-router[1767]: Waiting for NICs to settle down: settled in 0sec.. [ 31.572854] vyos-router[1767]: Mounting VyOS Config...done. [ 42.670126] vyos-router[1767]: Starting VyOS router: migrate configure failed! [ 43.268753] vyos-config[1773]: Configuration error
Hopefully this can be resolved for VyOS 2.0 in the future...
Hopefully this can be resolved for VyOS 2.0 in the future...
New PR for dynamic address groups: https://github.com/vyos/vyos-1x/pull/2756
Mounting a ram disk on top should be pretty easy.
The question is, how much ram should be allocated for this, and how to make sure it doesn't run out of space.
I am no expert in logrotate, but it sounds like it should be able to do it.
set system options logtoram
Complete config
Admin@vyos:~$ show dhcp server leases
I've further determined that it also occurs if no container is attached to the network because the interface is only created when a container is attached.
Happy new year!
Can you provide your DHCP server config?
T4516 adds this functionality.
Workaround for clouds introduced in:
https://github.com/vyos/vyos-cloud-init/pull/68
https://github.com/vyos/vyos-cloud-init/pull/69
This might fix this problem
https://github.com/vyos/vyos-1x/pull/2752
Add please the simple examples with set of commands to reproduce
set xxxx x.x.xx
Still issue persists when u create a new install its fine but upgrading breaks dhcp server ,tried in latest rolling releases 😢 why no solution??? YET...........
@dmbaturin @c-po can you see this and tell me if it's still current
OK, local-route actually worked!
Thanks!
The same issue could be with any dynamic interface like PPP that could be don't exists during the boot process/ISP issues
Which version?
Just a heads up that the above script can potentially destroy the config on boot, because if the system is fast enough, the hook will run before the boot config has finished loading. This will result either in an error when commiting because the config is locked (good outcome), or the config not being loaded at all (bad outcome). I've changed it a bit to actually wait for the boot config to load and now it runs safer, but it's still a bit janky in my opinion, I'm still hoping we can get something that works in-system for this case