User Details
- User Since
- Oct 2 2019, 6:00 PM (232 w, 5 d)
Yesterday
It looks like the local broken build.
At least it is not reproducible.
You can try to set it on some test VM to be sure if is it an issue with the node or the image itself.
Can you try the same link as in my example and provide the full output?
Could you show show version?
Never had this bug with 1.4.0-epa.
vyos@r1-right:~$ show ver Version: VyOS 1.4.0-epa1 Release train: sagitta
@matthewr Thanks for confirming!
Closing it as resolved now. Feel free to reopen or create a new one if this bug remains again.
Fri, Mar 15
@m.serdienis Add set of configuration commands to reproduce.
Most likely won't fix
https://chrony-project.org/doc/3.4/chrony.conf.html
I don't think it is expected to get speed to the node itself.
A router is generally used for forwarding traffic. It is better to use iperf to check the speed between 2 hosts.
@Apachez the original issue was related nft
If use nftables natively as:
Thu, Mar 14
PR https://github.com/vyos/vyos-1x/pull/3132
set service config-sync mode 'load' set service config-sync secondary address '192.0.2.1' set service config-sync secondary key 'xxx' set service config-sync section firewall set service config-sync section interfaces pseudo-ethernet set service config-sync section interfaces virtual-ethernet set service config-sync section nat set service config-sync section nat66 set service config-sync section protocols static set service config-sync section pki set service config-sync section vrf
Change some section:
vyos@r4# set nat source rule 100 outbound-interface name 'eth0' [edit] vyos@r4# set nat source rule 100 source address '10.0.0.0/24' [edit] vyos@r4# set nat source rule 100 translation address 'masquerade' [edit] vyos@r4# commit INFO:vyos_config_sync:Config synchronization: Mode=load, Secondary=192.0.2.1 [edit] vyos@r4#
Tue, Mar 12
Close the task due to the reporter not responding.
Reopen if you still have this bug.
Seems fixed, checked on VyOS 1.5-rolling-202403110024
vyos@r4# rollback Possible completions: <N> Rollback to revision N (currently requires reboot)
The similar task T5956
For 1.3 you have to add a separate PR
Do we need it for 1.3?
If yes, a separate PR should exist, as a backport is impossible.
Mon, Mar 11
Sat, Mar 9
Thu, Mar 7
There is no 1.3.7 version ;)
Wed, Mar 6
There is the task for the bug with "backslashes" T5996
The 1.3.x behaviour,
- VTI interfaces without IPsec is not created
# 1.3 set interfaces vti vti10 address '10.0.0.1/30' commit
Create the PR without smoketest. This case is not tested.
Tue, Mar 5
kea_parse_leases was deleted in https://github.com/vyos/vyos-1x/commit/c44d24eae276f77c700e961a22c0cd5582416dff
Probably the correct function is kea_get_leases
For 1.5 fix works as expected
vyos@r4:~$ cat /run/opennhrp/opennhrp.conf # Created by VyOS - manual changes will be overwritten
Mon, Mar 4
Should be fixed in the next rolling release.
Can you recheck it after 20240304 ?