Adding additional PR to add bonding.py to op-mode-standardized.json: https://github.com/vyos/vyos-1x/pull/3408
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Sat, May 4
Wed, May 1
Tue, Apr 23
In T6258#184716, @Viacheslav wrote:Most likely needs to change priority to 319 for the sysctl
vyos@r4:~$ /usr/libexec/vyos/priority.py | match "ethernet|sysctl" 300 interfaces_virtual-ethernet.py ['interfaces', 'virtual-ethernet'] 318 interfaces_ethernet.py ['interfaces', 'ethernet'] 318 system_sysctl.py ['system', 'sysctl'] 321 interfaces_pseudo-ethernet.py ['interfaces', 'pseudo-ethernet'] vyos@r4:~$
Apr 12 2024
Mar 30 2024
Since descriptions can be very long I assume there will be a linewrap at the end?
Mar 25 2024
@jestabro Thanks, a solution definitely seems close.
In T5991#181120, @Viacheslav wrote:It is not an actual ethernet interface, but you name it as an ethernet interface.
You can check the output sudo ip link show type wireguard or sudo ip link show type tun
I tested https://github.com/vyos/vyos-1x/pull/3173 today, and it definitely helps the original use-case of this task. Configuration calling interfaces that come up post-boot, like those installed from a container, persist. The one problem is the interface level config is still deleted on-boot from some check that is performed.
Mar 18 2024
@Viacheslav I'm not super familiar with git, so hopefully I did everything correctly. Here is the PR:
https://github.com/vyos/vyos-1x/pull/3145
Mar 15 2024
Should add the ability to view the default action log would be nice as well.
Mar 14 2024
Mar 5 2024
Perfect, that's what I was trying to better understand. Thanks for the clarification!
Mar 4 2024
Gotcha! The thing I keep struggling to understand is why is the full section of the config removed? This will 100% cause outages. If there's part of the config that is invalid, only that part should not be applied. You shouldn't remove 19 valid lines of config due to a single invalid line. Particularly with almost all of the instances I've seen of this, the invalid line is just cosmetically invalid, and doesn't cause any issues with the operation of the system.
@jestabro, do you guys consider the process of deleting the entire config section for a single offending line working as intended? Or do you consider it a design flaw/bug that will get fixed? I'm trying to understand if that is an intentional design choice and will permanently be part of VyOS going forward, or if it's just part of growing pains as VyOS moves from 1.3 to 1.4.
I wanted to add this post from the forums to this thread. It appears to be the same behavior where the failure of a single line deletes the logical section:
https://forum.vyos.io/t/upgrade-from-1-3-6-to-1-4-0-epa1-looses-complete-dhcp-configuration/13935
Feb 29 2024
Gotcha, thanks!
In T5991#178350, @jestabro wrote:I raised this issue for discussion last week, and am testing more 'lenient' verification in cases such as above; I'll add results and plans here, as available.
Feb 14 2024
@jestabro I appreciate you looking into this. It does seem to be a timing issue. I checked on a few of my systems....it almost always does it in a VM on my slow server, but I have a faster mini-pc where it doesn't appear to happen as often, though it does still happen on some reboots. Now that I have done more testing, it does happen on 1.4-rc1 as well. It does not however happen in 1.3.5.
Jan 29 2024
Firstly, note that this is a failure in boot configuration, and is not related to migration: the log output of vyos-router is misleading, reporting the steps following initialization. On success:
Starting VyOS router: migrate configure
on failure:
Starting VyOS router: migrate configure failed !Adding vyos-config-debug to the boot options on first boot after installation will provide more information on the config error, if it is possible to try that; cf.:
https://docs.vyos.io/en/sagitta/contributing/debugging.html#kernel