@SquirePug Can you check 1.2.7 release?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 22 2021
In T3640#96771, @Viacheslav wrote: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>]...] ]...
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:~$
Confirmed that's what is happening:
vyos@cr01a-vyos# TEST='variable' [edit] vyos@cr01a-vyos# set system login user vyos authentication plaintext-password HqNzXaK27k19$TEST [edit] vyos@cr01a-vyos# comp [edit system login user vyos authentication] +plaintext-password HqNzXaK27k19variable
@fernando Are you sure you're testing this on 1.3?
vyos@cr01a-vyos# run show ver
@SrividyaA Fixed in PR https://github.com/vyos/vyos-1x/pull/894
Jun 21 2021
I 've been checking this behavior with a different password , also I used the same password as you . But I couldn't reproduce the issue , both cases i add $ in the word and change the hash, let me show :
In fresh/new setup, the output of the command "show vpn ike sa" is throwing an exception error:
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>]...] ]...
In T3640#96759, @Viacheslav wrote:Is it helps in your case?
set interfaces wireguard wg0 disable commit del interfaces wireguard wg0 disable commitThere 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?
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 20 2021
Now that all major instances of curl have been replaced with the in-house script, we can begin to backport these changes to v1.3 in small pieces ahead of the first stable version.
Now I see the problem. paramiko.client.SSHClient().close() calls paramiko.transport.Transport().close() which implicitly calls socket.close() regardless of whether the socket was internally created or externally provided. This is a bit counterintuitive but I'll simply remove the socket closing logic then.