- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 27 2021
I can confirm that the issue of accepting configurations that yield errors is present in the latest LTS (1.2.6) and latest rolling release (1.4-202101240218). However, I couldn't replicate the issue of the configuration parser breaking at startup. Do we want to prevent the user from committing erroneous input at the risk of annoying false positives?
Found a minor bug: if DHCPv6 PD is configured without requesting an IPv6 address, the configured DUID is not sent.
I think we can make it a systemd service that is started on commit-confirm and stopped on confirm.
No one complained in a long time. ;)
If it re-appears, feel free to reopen. We also need to find a platform that knowingly does IKEv1 lifetime negotiation for testing this.
Last I checked it was able to log in the post-rewrite code. If the problem re-appears, feel free to reopen of course.
Backported to equuleus https://github.com/vyos/vyos-1x/commit/fb5a64a0a517291efe62185d053b437b62ef2921
THis issue also exists in the WWAN interface, can you please also provide a fix here and a SMoketest checkick this exact situation, that when switching from online -> disabled the interface is gone and no ppp peer configs exist?
Looks good on 1.4-rolling-202101270854:
vyos@vyos:~$ configure [edit] vyos@vyos# set interfaces ethernet eth0 address dhcpv6 [edit] vyos@vyos# set interfaces ethernet eth0 dhcpv6-options duid 00:02:00:00:0d:e9:30:30:31:45:34:36:2d:58:58:58:58:58:58:58:58:58:58:58:58:58:58 [edit] vyos@vyos# commit [edit] vyos@vyos# exit Warning: configuration changes have not been saved. exit vyos@vyos:~$ show version
Tested on VyOS 1.4-rolling-202101261956. Works fine
I can say that after testing here's what I found.
Jan 26 2021
This remains open; need to rejoin discussion.
This smoketest structure is currently revised as it makes no sense to refill the list on every run, should be a class method instead.
Tested on 1.4-rolling-202101240218, works as expected.
The official upstream address is https://gitlab.com/gsliepen/tinc , no Debian package generation rule file
The problem with preference, it should be different
The bug with FRR described here,
ref https://github.com/FRRouting/frr/issues/7583
ref https://github.com/FRRouting/frr/issues/7522
A possible reason, in the FRR hostname, declares 2 times.
Jan 25 2021
weird, I am woth the same ISP and do not have this problem.