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

Interestingly enough, I just found this error as well, but showed lines 173, 130, and 66.

This has been verified to be a driver issue as the Intel's out-of-tree module for ixgbe does indeed work when I compilied my own version of the ISO with the Intel's out-of-tree-module installed.

Implementation; this may be slightly revised before PR, to provide extra data ...
https://github.com/vyos/vyos-1x/compare/current...jestabro:commit-schedule

vyos logs

Oct 18 14:16:41 sshd[24197]: pam_succeed_if(sshd:auth): requirement "service = sudo" not met by user "olofl"
Oct 18 14:16:41 sshd[24197]: pam_succeed_if(sshd:account): requirement "service = sudo" not met by user "olofl"
Oct 18 14:16:41 sshd[24197]: Accepted password for olofl from 10.6.10.89 port 47110 ssh2
Oct 18 14:16:41 sshd[24197]: pam_succeed_if(sshd:session): requirement "service = sudo" not met by user "olofl"
Oct 18 14:16:41 sshd[24197]: pam_unix(sshd:session): session opened for user olofl(uid=1001) by (uid=0)
Oct 18 14:16:41 systemd[1]: Created slice user-1001.slice - User Slice of UID 1001.
Oct 18 14:16:41 systemd[1]: Starting [email protected] - User Runtime Directory /run/user/1001...
Oct 18 14:16:41 systemd-logind[1259]: New session 129 of user olofl.
Oct 18 14:16:41 systemd[1]: Finished [email protected] - User Runtime Directory /run/user/1001.
Oct 18 14:16:41 systemd[1]: Starting [email protected] - User Manager for UID 1001...
Oct 18 14:16:41 (systemd)[24203]: pam_succeed_if(systemd-user:account): requirement "service = sudo" not met by user "olofl"
Oct 18 14:16:41 (systemd)[24203]: pam_succeed_if(systemd-user:session): requirement "service = sudo" not met by user "olofl"
Oct 18 14:16:41 (systemd)[24203]: pam_unix(systemd-user:session): session opened for user olofl(uid=1001) by (uid=0)
Oct 18 14:16:41 rsyslogd[11051]:  message repeated 69 times: [-- MARK --]
Oct 18 14:16:41 rsyslogd[11051]: child process (pid 24200) exited with status 1 [v8.2302.0]
Oct 18 14:16:41 systemd[24203]: Queued start job for default target default.target.
Oct 18 14:16:41 systemd[24203]: Reached target paths.target - Paths.
Oct 18 14:16:41 systemd[24203]: Reached target sockets.target - Sockets.
Oct 18 14:16:41 systemd[24203]: Reached target timers.target - Timers.
Oct 18 14:16:41 systemd[24203]: Reached target basic.target - Basic System.
Oct 18 14:16:41 systemd[24203]: Reached target default.target - Main User Target.
Oct 18 14:16:41 systemd[24203]: Startup finished in 64ms.
Oct 18 14:16:41 systemd[1]: Started [email protected] - User Manager for UID 1001.
Oct 18 14:16:41 systemd[1]: Started session-129.scope - Session 129 of User olofl.
Oct 18 14:16:41 systemd[1]: opt-vyatta-config-tmp-new_config_24226.mount: Deactivated successfully.
Oct 18 14:16:41 sshd[24197]: pam_env(sshd:session): deprecated reading of user environment enabled

testing another radius user

Oct 18 14:19:32 sshd[24610]: pam_succeed_if(sshd:auth): requirement "service = sudo" not met by user "oxidized"
Oct 18 14:19:32 sshd[24610]: pam_succeed_if(sshd:account): requirement "service = sudo" not met by user "oxidized"
Oct 18 14:19:32 sshd[24610]: Accepted password for oxidized from 10.6.10.89 port 58054 ssh2
Oct 18 14:19:32 sshd[24610]: pam_succeed_if(sshd:session): requirement "service = sudo" not met by user "oxidized"
Oct 18 14:19:32 sshd[24610]: pam_unix(sshd:session): session opened for user oxidized(uid=1001) by (uid=0)
Oct 18 14:19:32 systemd-logind[1259]: New session 132 of user olofl.
Oct 18 14:19:32 systemd[1]: Started session-132.scope - Session 132 of User olofl.
Oct 18 14:19:32 systemd[1]: opt-vyatta-config-tmp-new_config_24614.mount: Deactivated successfully.
Oct 18 14:19:32 sshd[24610]: pam_env(sshd:session): deprecated reading of user environment enabled

What if you install the same version again but as a new boot name?

My radius user was not called admin, but local user called admin was configured before I tried.
I removed local admin user, and tried once again, and I get the same reults.

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.

RNDIS is once more on the "removal" list of the Linux Kernel.
https://www.phoronix.com/news/Linux-Disabling-RNDIS-Drivers

PR for current: https://github.com/vyos/vyos-1x/pull/2373

It seems related https://vyos.dev/T5663

PR:
https://github.com/vyos/vyos-1x/pull/2371

Fixed in
1.4/1.5: https://github.com/vyos/vyos-cloud-init/commit/5d3e4e79746772d80a6289f352e3606382f73eaa
1.3: https://github.com/vyos/vyos-cloud-init/commit/f627bf85746c5785836086538879e1101b6c4af3

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...

@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.

In this case we can use the next solution:

PR https://github.com/vyos/vyos-1x/pull/2366

Still fails:

Looks like this issue may actually be resolved now.

cf. T5027: the commit for this task necessarily removed the fix there, leading to failing of the same two tests. A fix is to specify a specific encryption cipher within test_openvpn_options and test_openvpn_site2site_interfaces_tun to avoid openvpn defaulting to bf.

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.

Fixed in https://github.com/vyos/vyos-1x/pull/2342

I wonder if we need the ASCII art though or not the plain fingerprints only (first line of the command)

Implementation complete

Implementation complete