PR https://github.com/vyos/vyos-1x/pull/3193
Extend config-sync for sections qos and system
vyos@r4# set service config-sync section system Possible completions: conntrack Connection Tracking flow-accounting Flow accounting option System Options sflow sFlow static-host-mapping Map host names to addresses sysctl Configure kernel parameters at runtime
It is not an actual ethernet interface, but you name it as an ethernet interface.
You can check the output sudo ip link show type wireguard or sudo ip link show type tun
@tjh already backported
Tags show the code base at the step where the tag was added.
But binary can be changed since this time. For the same reason, you will not be able to build 1.1.8 or 1.2.1, etc. exactly with those binary that were on the step of tagging.
Close it as wonfix.
At least tech-support-archive.tgz MUST not copied between updates
PR https://github.com/vyos/vyos-1x/pull/3155
set service config-sync secondary address 192.0.2.1 set service config-sync secondary timeout 3600
PR https://github.com/vyos/vyos-1x/pull/3150
vyos@r4:~$ show conntrack table ipv4 Id Original src Original dst Reply src Reply dst Protocol State Timeout Mark Zone ---------- ----------------- ------------------- ------------------- -------------------- ---------- ----------- --------- ------ ------ 2589405901 192.0.2.14:37122 34.206.168.146:123 34.206.168.146:123 192.168.122.14:37122 udp 99 0 931438034 192.168.122.14:22 192.168.122.1:56010 192.168.122.1:56010 192.168.122.14:22 tcp ESTABLISHED 431999 0 4269448361 192.0.2.14:43882 34.117.118.44:80 34.117.118.44:80 192.168.122.14:43882 tcp TIME_WAIT 116 0 821718377 192.0.2.14:36208 1.1.1.1:53 1.1.1.1:53 192.168.122.14:36208 udp n/a 0 vyos@r4:~$ vyos@r4:~$
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.
@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:
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#
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