PR for Saggita: https://github.com/vyos/vyos-1x/pull/2388
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 20 2023
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2386
Is vni100 the vxlan interface or the bridge interface?
Just in case: using anything except current image scripts for installation is not possible without a full chroot into the installation candidate. Python versions and modules may be different and new scripts in many cases will not work in the old environment.
Oct 19 2023
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2383
PR for 1.5 current https://github.com/vyos/vyos-1x/pull/2378
File gets generated but could be not extracted nor transferred as it tries to resolve it as hostname
Oct 18 2023
Implementation; this may be slightly revised before PR, to provide extra data ...
https://github.com/vyos/vyos-1x/compare/current...jestabro:commit-schedule
Furher to this, manually setting "mru 1500" gives me my 1500 MTU back again.
The new MRU config in 1.3.4 seems to have caused my MTU to be lower.
Oct 17 2023
Out of the blue it looks like some compile thats gone wrong?
What is the exact path within the chroot directory?
This will be fixed by merge of PR:
https://github.com/vyos/vyos-1x/pull/2371
Good point @Viacheslav apologies I was distracted at the time.
I can make it work by starting manually ( # ip vrf exec RCS3 zabbix_agent2 -c /run/zabbix/zabbix-agent2.conf )so I guess updating the systemd units file (/lib/systemd/system/zabbix-agent2.service) should make this work.
In T5657#162236, @bbabich wrote:Yep looks fine @Viacheslav
I've been using it like this for a while now but figure it may be useful as part of making 'VRFs' complete...$ sudo ip vrf exec RCS3 mtr 192.168.222.11
Yep looks fine @Viacheslav
I've been using it like this for a while now but figure it may be useful as part of making 'VRFs' complete...
Oct 16 2023
@fsbof This change was accepted so it should end up in the 1.5 rolling soon. I suspect backporting to 1.4 wouldn't be an issue but that is a question for a more senior dev. But as for 1.3, I am unsure as I have never ran that version and don't know if there are any changes between those releases that would make it a pain to backport.
Oct 14 2023
I was also affected by this issue. I could only update to 1.5-rolling-202309280022. Updates to more recent versions had the effect that after login I coudn't manage VyOS as I only had a standard linux bash.
Did you test it in vrf? Is it really works as expected?
@JeffWDH I am happy to download, build and test when you're ready if you point me to the right version(s)/location(s). I'm also very new to this but I managed to Build Equuleus in a docker container which has been working ok. Appreciate your efforts.
I've updated this to default to no ASCII art as I think it's cleaner, but added an option to show it if you want to see it:
Wow - you guys work quickly! 👍
I think it should be included, its often used during generation in Debian among other distros.
I wonder if we need the ASCII art though or not the plain fingerprints only (first line of the command)
Oct 13 2023
$ show ssh fingerprints SSH server public key fingerprints:
I had a similar issue going from 1.5-rolling-202309250022 to 1.5-rolling-202310090023.
