Related task https://phabricator.vyos.net/T3546

PR for 1.3 https://github.com/vyos/vyos-1x/pull/1094

Ok. I just found out, that I had an error, when porting my changes to github.

I checked it on these versions of VYOS. (VyOS 1.3.0-epa3, VyOS 1.3-beta-202112010443 , VyOS 1.4-rolling-202112021432)

I hope I can find some time tomorrow to also test with crux. My current build job only builds the 1.3.x branch, but should be easy to adjust.

It is working only for TCP right now

set system syslog host 192.168.122.1 facility all protocol 'tcp'
set system syslog host 192.168.122.1 format octet-counted
set system syslog host 192.168.122.1 port '1514'

Config:

vyos@r4-epa2# cat /etc/rsyslog.d/vyos-rsyslog.conf 
## generated by syslog.py ##
## file based logging
$outchannel global,/var/log/messages,262144,/usr/sbin/logrotate /etc/logrotate.d/vyos-rsyslog
*.info;local7.debug :omfile:$global
## console logging
## remote logging
*.err @@(o)192.168.122.1:1514;RSYSLOG_SyslogProtocol23Format
[edit]
vyos@r4-epa2#

@fetzerms Thanks, Could you test the crux build?

I think I found the issue. Please see https://github.com/vyos/vyos-build/pull/207/

Update: If I run

https://github.com/vyos/vyatta-config-mgmt/blob/current/scripts/vyatta-commit-push.pl#L71-L82 seems to be the root cause for this.

Does this problem persist with the latest rolling version?

The way sockets are handled in the last version should've fixed this once and for all.

Less scary error messages are produced now.

@sever To me it seems it's not even present in the iso and according to the dpkg logs it seems to install vyos-xe-version.

@fetzerms Is xe-guest-utilities is present in iso image?
I'll look at it soon.

It's just a warning message, as ppp+ it is a regex, exactly interface with such name not exist.
But rule applied

@sever I think you implemented that feature. Am I using it wrong?

I get the following below, even though ppp0 exists:

Sadly my firewall rules got wiped on upgrade and I'm a little nervous know about going backwards. I will try one going forward in a week or so.

I opened an issue https://github.com/FRRouting/frr/issues/10160

@FileGo It does not require such configuration in the server section.
As user interfaces creates dynamically "ppp0 ppp5 ppp23" etc
Your zone should look like:

@anthr76 Try vyos-1.4-rolling-202112010318-amd64.iso

After disable/enable interface ethX the routes reappear

vyos@r11-roll:~$ sudo ip link set dev eth0 down
vyos@r11-roll:~$ sudo ip link set dev eth0 up

Problem seems to be when 2 ip addresses on same network is defined on interface, like this: