It looks like was the same bug T1866
Try ssh keyscan
https://docs.vyos.io/en/latest/cli.html#remote-archive
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 16 2021
@Scoopta Can you share commands on how to reproduce it?
It will be easier for developers to reproduce this bug.
Jul 15 2021
I can't reproduce it.
Re-open the task if you get this issue again.
@jingyun Can you describe more details?
PR for 1.3 https://github.com/vyos/vyos-1x/pull/925
PR for 1.4 https://github.com/vyos/vyos-1x/pull/926
Jul 13 2021
More details https://github.com/vyos/vyatta-webproxy/pull/17
Jul 12 2021
Jul 10 2021
Jul 9 2021
It is a feature request.
So we don't have a "large-comm-list" for set in our CLI. It is incorrect to compare "large-community" with "large-comm-list"
The option "delete" is preset only for the "lists"
I can't reproduce it in 1.3-rc5
set interfaces wireguard wg0 address '10.1.0.3/24' set interfaces wireguard wg0 address 'cafe:c01d:c01a::2/64' set interfaces wireguard wg0 description 'VPN-to-wg-PEER01-192.0.2.1' set interfaces wireguard wg0 ipv6 ospfv3 cost '24' set interfaces wireguard wg0 ipv6 ospfv3 dead-interval '40' set interfaces wireguard wg0 ipv6 ospfv3 hello-interval '10' set interfaces wireguard wg0 ipv6 ospfv3 instance-id '0' set interfaces wireguard wg0 ipv6 ospfv3 priority '1' set interfaces wireguard wg0 ipv6 ospfv3 retransmit-interval '5' set interfaces wireguard wg0 ipv6 ospfv3 transmit-delay '1' set interfaces wireguard wg0 peer PEER01 address '192.0.2.1' set interfaces wireguard wg0 peer PEER01 allowed-ips '0.0.0.0/0' set interfaces wireguard wg0 peer PEER01 allowed-ips '10.0.3.0/24' set interfaces wireguard wg0 peer PEER01 allowed-ips '::/0' set interfaces wireguard wg0 peer PEER01 port '12345' set interfaces wireguard wg0 peer PEER01 pubkey 'Cpqy8=' set interfaces wireguard wg0 port '54321' set protocols ospf area 0 network '10.1.0.0/24' set protocols ospf passive-interface 'default' set protocols ospf passive-interface-exclude 'wg0' set protocols ospfv3 area 0 interface 'wg0'
In the latest rolling release all works fine without any changes
vyos@r1-roll:~$ show version
Jul 8 2021
It seems there were changes in squid , but not in our code.
It is not used /var/log/frr anymore T2061
Jul 5 2021
@tjh If you have a test lab, can you check conntrack-sync in the latest 1.3?
Jul 4 2021
Jul 2 2021
Fixed for 1.3 in commit https://github.com/vyos/vyos-1x/commit/21527ef4551613fe9b7eed9e4b2ce33ad46fe540
Fixed for 1.3 in commit https://github.com/vyos/vyos-1x/commit/21527ef4551613fe9b7eed9e4b2ce33ad46fe540 and T3535
Jun 29 2021
Is it worked in 1.3/1.2?
Jun 28 2021
For 1.2.7 it adds unexpected multicast group per "save"
Configs for reproduce:
To reproduce (VyOS 1.3-beta-202106271614):
Doesn't work, VyOS 1.4-rolling-202106271939
Jun 27 2021
Jun 26 2021
Jun 25 2021
Jun 24 2021
@Dmitry Is it an actual task? Code was rewritten.
Already fixed with "no_tag_node_value_mangle=True"
https://github.com/vyos/vyos-1x/blob/705eddbc7a2caf09c37ecafb27418a764217975a/python/vyos/config.py#L218
Eigrp in the FRR doesn't work correctly.
The routes still live even if neighbors in a shutdown state.
@Cheeze_It can you re-check it?
There is a link to the existing code for configuration mode, not pr.
So we can to add the op-mode function to re-add/reset with a similar logic. Only thoughts
Jun 23 2021
Not sure about double quotes, but for example for cloud-init configs, it is necessary to use single quotes.
Ideally, the configuration should look like in show configuration commands
I think it will be enough to remove the peer and add again.
@hagbard what do you think?
https://github.com/vyos/vyos-1x/blob/d48dddab0509e562209adfb115b0e691b8e47f54/python/vyos/ifconfig/wireguard.py#L197
PR https://github.com/vyos/vyos-1x/pull/897
Fix path for swanctl.conf file
@Harliff Try 1.2.7/1.3 it was fixed with commit https://github.com/vyos/vyos-build/pull/138/files#diff-c7d29a506307d9cf8d86c3cd3f65ca4e4058ea442cacdf9a89d2485b56c7417aR67
T2061
Jun 22 2021
@SquirePug Can you check 1.2.7 release?
I don't see the reason to delete the "disable" option, as it uses for adjust-mss and adjust-mss6.
And you need temporarily disable it.
Try to set single quotes.
Different format
vyos@r1-roll:~$ show vpn ipsec sa Connection State Uptime Bytes In/Out Packets In/Out Remote address Remote ID Proposal ------------------------ ------- -------- -------------- ---------------- ---------------- ----------- ---------- peer_192-0-2-2_tunnel_1 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_10 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_11 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_12 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_13 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_14 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_15 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_16 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_17 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_18 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_19 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_2 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_20 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_3 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_4 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_5 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_6 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_7 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_8 down N/A N/A N/A N/A N/A N/A peer_192-0-2-2_tunnel_9 down N/A N/A N/A N/A N/A N/A vyos@r1-roll:~$
Jun 21 2021
We don't use any configuration file for it, so I think we can't use wg-quick
We use "wg set"
$ sudo wg set --help Usage: wg set <interface> [listen-port <port>] [fwmark <mark>] [private-key <file path>] [peer <base64 public key> [remove] [preshared-key <file path>] [endpoint <ip>:<port>] [persistent-keepalive <interval seconds>] [allowed-ips <ip1>/<cidr1>[,<ip2>/<cidr2>]...] ]...
Is it helps in your case?
set interfaces wireguard wg0 disable commit del interfaces wireguard wg0 disable commit
There is no any native command for reset wireguard interface in Linux (as I know). Also, we don't use any daemons which we can restart to "re-establish" session.
Is one host behind nat?
Jun 18 2021
Works fine VyOS 1.4-rolling-202106180929
vyos@r1-roll# set interfaces ethernet eth1 offload lro [edit] vyos@r1-roll# commit [edit] vyos@r1-roll# sudo ethtool -k eth1 | match large-receive-offload large-receive-offload: on [edit] vyos@r1-roll#