@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

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

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

https://phabricator.vyos.net/T1977

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.

@kroy Can you please test with the latest rolling? I can't reproduce the issue.

@max1e6 Did you have a chance to test?

https://github.com/vyos/vyos-1x/commit/742da889afa4375d5b6cb98dada7f2d3ec2f0326
@Xesxen http://dev.packages.vyos.net/repositories/current/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb addresses that issue for the rolling release.

@jestabro yup, go ahead please and let me know when I can close it or if you can you can close as well.

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

Has been fixed already.

Hang on, I see the error in syslog (only syslog), so at least I can reproduce it now.

@Merijn I tested with the latest rolling and can't reproduce the issue. From your error message yesterday it looks like your snmpd.conf has an issue. Can you copy that content as well?

@jjakob https://downloads.vyos.io/rolling/current/amd64/vyos-1.3-rolling-202001081700-amd64.iso and later should address that issue.

https://github.com/vyos/vyos-1x/commit/3863e5dc24a622090f52c13f8aa04e5c9f00341a should fix it.
(http://dev.packages.vyos.net/repositories/current/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb if you want to manually install and test or wait for tomorrows iso).

systemctl renamed it to syslog, so it won't be restarted correctly and the conf script won't generate the files correctly. It is correctly named within init.d.

looks like service syslog did disappear from the default config.

@Merijn Can you please share the snmp part from your config?

I only have a workaround right now, it appears that grub.cfg can't be found. To boot at least the installed system do the following within the grub shell:

configfile /EFI/VyOS/grub.cfg

Sure thing, let me know the result.

@Merijn https://github.com/vyos/vyos-1x/commit/78df0c46865b3af89d6bc327b4c1d08cc4450aff or tomorrows rolling, as you seem to compile it yourself is should now work out of the box when you install the new vyos-1x package.
(http://dev.packages.vyos.net/repositories/current/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb)

Debian default snmp user is called Debian-snmp while the script tries to get the uid of the user snmp. Looks like that is the entire issue.

Hi @max1e6 , can you please share the relevant openvpn config, so I can try to reproduce the issue? Thx.

@kroy thx for testing, glad it is working for you since I'm not really satified with it.

Yup, https://phabricator.vyos.net/T1831 is pending. FRR RAs will fix the issue entirely or going with set service ipv6-ra interface... would fix that too regardless what daemin is being used at the backend which would also make it interchangeable.

That's what it does but using the init script.

Let's see if it does the job, it's more a hack than a fix. The real problem is that you will have reloads for each interface which has router-advert configured during boot.
Systemd doesn't like the quick restarts during boot and limits that.

I'm going to change the node.def to reload if radvd is running already, not sure if it fixes that since the issue appears to be systemd related.
Also if you just disable a vif, radvd won't be restarted and has an invalid interface it tries to announce on, that's why I want to move it out of the interfaces and set it as it's own service.

Hmm, I can't reproduce the issue, looks good when I test it with your config and reboot few times.

@jjakob It's not really relevant if you SIGHUP or SIGKILL as RAs have no status, they are just send. I was looking into rewriting it anyway and port it into frr as frr sends RAs reliably as well. (https://phabricator.vyos.net/T1831) So the above is just a quick fix to get it working again with buster using the original logic.

@kroy I think I found the issue, the script just called start every time when radvd was already running, please test with either tomorrows iso or: http://dev.packages.vyos.net/repositories/current/pool/main/v/vyatta-ipv6-rtradv/vyatta-ipv6-rtradv_0.38+vyos2+current1_all.deb

It sends it after a while, I was waiting around 5 minutes and captured 1 RA msg.
But it sends only on vlan 22, which is quite unusual since all vlans are setup and readable by radvd, at least when I check /proc/<pid> it has it setup.
After the restart it sends on all interfaces (Just sent a SIGHUP, so no systemd involved). Reboot fixes it then as well.

All right, I can reproduce it now, thanks for the detailed report. I see what I can find out.

Weird, afaik there was nothing to migrate yet.

That can't be the issue, what do you see if you do a grep radvd /var/log/messages?

I used your config and just changed to eth1, commit works and after reboot radvd runs and sends RAs as well. radvd has a very low priority, I think 999 or so to ensure all interfaces are up and running plus the fact that radvd runs with a flag which allows the config running on an offline interface. (IgnoreIfMissing on;) Could anything else x-fire?