An alpha version can be found here: https://github.com/c-po/vyos-1x/tree/pppoe-rewrite

After looking into this, the problem seems bigger than originally thought. If the syslog config is being removed from the config the syslog.py script is called and syslog stopped. However if the system is rebooted the init system starts syslog and the config is not calling the script since there is no 'system syslog' node in the config. systemctl disable rsyslog doesn't work some type of depend unit is starting it during reboot.

tested successfully

@ekim seems this issue with kernel and your device. If I build custom stable kernel for VyOS installed on same device without CONFIG_PINCTRL_CHERRYVIE all works properly.
Can you show cat /pro/interrupt output for confirm this?
You can also change /boot/grub/grub.cfg add noapic and reboot device.

menuentry "VyOS 1.2.3 linux (Serial console)" {
	linux /boot/1.2.3/vmlinuz boot=live noapic quiet rootdelay=5 vyos-union=/boot/1.2.3 console=tty0 console=ttyS0,9600
	initrd /boot/1.2.3/initrd.img
}

Can you confirm that with grub modification after reboot all works correct?

aone migrator for all interfaces is sufficient (see mew bridge interface and migrator 0-to-1 in interfaces)

Yes, I think set service ra interface ... or something like that might be the best option. That would eliminate the template generator script all together and I was thinking to remove interface by interface from the generator, as the rewrite progresses.
Since it needs a migrator script for each interface then as well, even if the option are the same.

How is it planned to implement this in the new style configuration? As own service bound to interfaces (denest) or as part of an interface?

Next rolling will have it included.

done

need to merge it into crux

@Merijn I will build and run a sanity check, and then we can merge into rolling for testing; I'll confirm when done. Thanks again for the offer to test.

@jestabro i am not able to build the vyos-1x package because of dependencies on other packages.
Can we include them in rolling so i can test tomorrow?

@jestabro i have encountered the first situation in my networks where i really need RFC-Complaint VRRP
(Some devices do not learn the MAC-address on the VRRP gateway, it works for some time and then stops).

The merged fix addressed the problem as it occurs in configuration mode, however, the same issue can occur during the running of migration scripts. A solution to cover all cases has been tested, and is pending.

Notice: When we run restar vrrp on MASTER, files with VRRP interfaces states stored in /run/vyos/vrrp/ don't deleted. Next time scripts not running, because already have some state.
We need review this task with T1350

This appears to be fixed in 1.2.4 EPA1.

This is still broken for me on the most recent 1.3 rolling releases:

how can this be invalid and closed? The error is still there on a Crux build of this week...

Resolved in T1786 (for 1.3 too). Please reopen T1786 in case of further troubles.

Reproducible via:

I tested https://phabricator.vyos.net/T1787 for @c-po with the following results. He asked me to write down this here in the parent task.

Depending on your configuration, in SNMPv3 you can limit the scope, in SNMPv2 we export all.

Ok so that would mean the BGP4 info is exposed to the SNMP server and someone has to check it on a client.

VyOS 1.2.3 has agentx enabled:

@cpo the SNMP server has to support the MIB to export the OID. And afterwards the client has to have an up2data MIB to map it again. If the server does not export it the client can update the MIB but the OID won’t be there.

Hmm the way I have understood SNMP this is not a VyOS issue. VyOS only deliveres the MIB tree to the SNMP poller. The MIBs database must be up2date on the client side to map the OIDs to their specific values.

@zsdc Can you take a look at that?
Ref
https://phabricator.vyos.net/T1721
https://github.com/FRRouting/frr/pull/4602/commits

Looks like no one really wants it except for 2 people, going to cancel it.

Hello, I created LAB with sync-group configuration. In this LAB I use VyOS 1.2.2 on all routers for reason like in your ticket

PR168 https://github.com/vyos/vyos-1x/pull/168