PR: https://github.com/vyos/vyos-1x/pull/894

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 
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?

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?

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.

Yes, though the error has changed:

trae@cr01b-vyos# commit
Using source address fd52:d62e:8011:fffe:192:168:253:3
Archiving config...
  sftp://stor01z-rh8.int.trae32566.org:/int/cr01b-vyos Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 299, in upload
    upload_sftp(local_path, url.hostname, url.path, username, password, port, source, progressbar)
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 178, in upload_sftp
    transfer_sftp('upload', *args, **kwargs)
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 174, in transfer_sftp
    sock.shutdown(socket.SHUT_RDWR)
OSError: [Errno 9] Bad file descriptor

PR: https://github.com/vyos/vyos-1x/pull/888

PR: https://github.com/vyos/vyos-1x/pull/887

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#

Added PR:

@SrividyaA Fixed in PR: https://github.com/vyos/vyos-1x/pull/884

PR https://github.com/vyos/vyos-1x/pull/883

Tested with basic ipsec configuration and it does not seem to work when 3des encryption is configured. It works with default (aes128) and aes192.
Version

PR's for both crux and equuleus

copy file still depends on vyatta-image-tools.pl. I think it merits a rewrite, maybe a simple file transfer script that uses a couple of basic routines for file:// and running:// and remote.py for everything else.

@trae32566 Does this problem still persist in the newest rolling release?

Submitted this PR: https://github.com/vyos/vyatta-op/pull/46

the possible completion output is fixed in the latest release: 1.4-rolling-202106151212

PR https://github.com/vyos/vyos-build/pull/172

At least on simple tests, this modification seems to work.
I have tested on version 1.3, first configuring dhcp server for both addresses: for the one that was defined first, and one for the las IP address defined (of course, one instance of dhcp-server running at a time).
If this needs more testes, let me know what I can do for you.

Can you try any 1.3 rolling version before 2020-10-30 commit c8b7e5c ?

Uploaded the config as generated.

Swanctl migration PR: https://github.com/vyos/vyos-1x/pull/881