One seems t be the mastering parent process, try ps faux

SNMP with VRRP work

# snmpwalk -v2c -c public 10.0.0.1  VRRP-MIB:vrrpOperations
VRRP-MIB::vrrpNodeVersion.0 = INTEGER: 2
VRRP-MIB::vrrpNotificationCntl.0 = INTEGER: disabled(2)
VRRP-MIB::vrrpOperVrId.3.10 = INTEGER: 10
VRRP-MIB::vrrpOperVirtualMacAddr.3.10 = STRING: 52:54:0:1d:4:4e
VRRP-MIB::vrrpOperState.3.10 = INTEGER: backup(2)
VRRP-MIB::vrrpOperAdminState.3.10 = INTEGER: up(1)
VRRP-MIB::vrrpOperPriority.3.10 = INTEGER: 50
VRRP-MIB::vrrpOperIpAddrCount.3.10 = INTEGER: 1
VRRP-MIB::vrrpOperMasterIpAddr.3.10 = IpAddress: 10.0.0.2
VRRP-MIB::vrrpOperPrimaryIpAddr.3.10 = IpAddress: 10.0.0.1
VRRP-MIB::vrrpOperAuthType.3.10 = INTEGER: noAuthentication(1)
VRRP-MIB::vrrpOperAdvertisementInterval.3.10 = INTEGER: 1 seconds
VRRP-MIB::vrrpOperPreemptMode.3.10 = INTEGER: true(1)
VRRP-MIB::vrrpOperVirtualRouterUpTime.3.10 = Timeticks: (2) 0:00:00.02
VRRP-MIB::vrrpOperProtocol.3.10 = INTEGER: ip(1)
VRRP-MIB::vrrpOperRowStatus.3.10 = INTEGER: active(1)
VRRP-MIB::vrrpAssoIpAddr.3.10.10.0.0.254 = IpAddress: 10.0.0.254
VRRP-MIB::vrrpAssoIpAddrRowStatus.3.10.10.0.0.254 = INTEGER: active(1)

This feature request can be closed.
T1981 - Allow 'set src' to reference either IPv4 or IPv6
T1983 - Expose route-map when BGP routes are programmed in to FIB

@max1e6 Did you have a chance to test? Otherwise I assume the issue isn't present anymore.

Let me know if you come across any issues.

https://github.com/vyos/vyos-1x/commit/b11a301b130a01cba035a0cd5aa5b17c99eb1d44

By default we don't need delay, I think it must be configurable feature.

set service pppoe-server pado-delay delay 100 sessions 100
set service pppoe-server pado-delay delay 200 sessions 300
set service pppoe-server pado-delay delay 300 sessions 1000

and configuration for this

@Dmitry What default delays do you suggest?

@syncer After all considerations, because of the authentication modules squid brings in, I would rather stay with squid for now. Let me know what you think.

If it possible, please explain me in private message how I can reach this behaviour. In my LAB this does not reproduced.

This patch tested successful on VyOS 1.2.4 VM with 25 network interfaces.
Also works as expected on VyOS 1.3-rolling-202001230217
Thx @runar !

@TriJetScud Would please make it works on vyos latest version ?

This also could be the same issue as described in T577

This issue is possibly fixed in current by ticket T1970, could you retry with the newest current rolling release?

When using logrotate we can take full owership about the resources that will be used for number of files and its size - so i think this will be the best approach.

Please test and feedback in latest rolling.

Howadays there is the generic vyos.ifconfig Python class which deals with IPV6 dhcp client stuff.

I haven't tested the vyos-1x changes that @gadams made with 1.3 rolling (current). But it seems before we can do that we'll need to create the interface-definitions so they show up on the CLI and can be configured. Since I believe that's what changed in between minor versions.

I've attached a simple patch to expose FRRouting's built-in capability of being able to apply a route-map to routes that are submitted to the FIB from BGP to VyOS.

Why we not fix just logrotate config for it?

I've attached a simple patch to allow 'set src' to be either IPv4 or IPv6 addresses.

Turns out that 'destination-interface any' works, and I just hadn't read the help.

• trafficserver (buster native - 19.7 MB of additional disk space will be used)
• looks like squidguard can't be integrated (removing it entirely?)

fixed in https://downloads.vyos.io/rolling/current/amd64/vyos-1.3-rolling-202001211723-amd64.iso.

If this is always enabled "hardcoded" and SNMPd is not running the following will happen:

https://phabricator.vyos.net/T1977

I've created a PR in the vyos/vyos-1x repy for the config verification fix: https://github.com/vyos/vyos-1x/pull/208

I've created a PR in the vyos/vyos-documentation repo for the documentation fix: https://github.com/vyos/vyos-documentation/pull/190

This was only a problem in rolling and is fixed

Many thanks again, I much prefer having interface specific settings in a single place instead of arbitrary script locations.

PR for this fix: https://github.com/vyos/vyatta-cfg/pull/20

@bbs2web you can try use sysctl params from set

This is working nicely, many thanks!

I've attached a simple patch to expose FRRouting's built-in capability of being able to set a prefix's local administrative distance to VyOS.

I've attached a simple patch to expose FRRouting's built-in capability of being able to match on prefix's BGP local preference to VyOS.

I like the idea, but unfortunately I do not understand why there needs to be a cancel node? If maintenance mode is not activated shouldnt this be enough?

FRR build triggered, please try next rolli g

No, work would be needed to add the necessary logic to VyOS scripts.
This wasn't possible before the version of isc-dhcpd VyOS uses was
updated to one that supported PD length. But now it is at least
possible, before it wasn't possible at all.

With the above change, some 2 years later, are we able to finally use a DHCP PD for IPv6? ie does it actually work?

Ack, I have already after step 5 an issue. The uids shouldn't be an issue, since the users should be all in the same group and the group has r/w permissions.

I hacked through how to reproduce.