I added a new neighbor belonging to the sub-AS 65031 to the existing bgp configuration:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 30 2021
Aug 11 2021
Aug 7 2021
I see these error in the openvpn log:
I don't think so the configuration is working, the interface is down. It is not assigning the ipv6 addresses to the tunnel interfaces.
Aug 4 2021
set interfaces openvpn vtun10 encryption cipher 'aes256' set interfaces openvpn vtun10 hash 'sha512' set interfaces openvpn vtun10 local-host '10.2.0.15' set interfaces openvpn vtun10 local-port '1194' set interfaces openvpn vtun10 mode 'server' set interfaces openvpn vtun10 persistent-tunnel set interfaces openvpn vtun10 protocol 'udp' set interfaces openvpn vtun10 server client client1 ip '2001:470:1f14:af1::2' set interfaces openvpn vtun10 server client client1 subnet '2001:470:1f14:af1::/64' set interfaces openvpn vtun10 server push-route '2001:db8:0:abc::/64' set interfaces openvpn vtun10 server subnet '10.140.0.0/20' set interfaces openvpn vtun10 server topology 'subnet' set interfaces openvpn vtun10 tls ca-cert-file '/config/auth/ea1/ca.crt' set interfaces openvpn vtun10 tls cert-file '/config/auth/ea1/central.crt' set interfaces openvpn vtun10 tls dh-file '/config/auth/ea1/dh.pem' set interfaces openvpn vtun10 tls key-file '/config/auth/ea1/central.key'
Jul 29 2021
As requested, checked in 1.3.0-rc and it shows the destination translations with basic configuration.
Jul 13 2021
Parent task: https://phabricator.vyos.net/T2816
Jul 12 2021
@sdev It still shows the ikev2 as the default version in the output.
I agree with your point that strongswan has changed the default version. A quote from their documentation: "Since 5.0.0 both protocols are handled by Charon and connections marked with ike will use IKEv2 when initiating, but accept any protocol version when responding."
Jul 6 2021
@sdev , Thank you. I will test and confirm, once the new rolling version is released.
Jun 28 2021
Parent Task: https://phabricator.vyos.net/T2816
I have tried one more scenario:
Jun 21 2021
In fresh/new setup, the output of the command "show vpn ike sa" is throwing an exception error:
Jun 17 2021
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
Jun 16 2021
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
Jun 14 2021
May 30 2021
thank you for the suggestion, I will work on this.
When the following command "set system syslog file <filename> facility <keyword> level <keyword>" is applied, then the files are stored in the /var/log/user directory. These files can be deleted using the command "delete log file <text>"
May 26 2021
May 25 2021
Providing an entire path of the file i.e. /opt/vyatta/etc/key-pair.template instead of "@sysconfdir@/key-pair.template", makes the command executable.
IPSec VPN in X509 mode needs ca cert file, also server/client cert has to be signed by the CA for identification.
So, maybe rewriting this script will be helpful.
Any suggestions are welcome.
May 20 2021
It seems other commands like save, copy which depend on scp and tftp are also broken.
May 18 2021
May 17 2021
Even I also faced this error while upgrading the server from 1.2.7 to the latest rolling release.
May 5 2021
Apr 20 2021
It seems to show the output correctly when single tunnel is present not with multiple tunnels.
Ref Task: https://phabricator.vyos.net/T3473
Apr 19 2021
I tested in 1.2.7 ver and the issue did not reproduce:
Apr 17 2021
Version: VyOS 1.4-rolling-202104151445
Apr 11 2021
Submitted following PR:
Mar 31 2021
Parent task: https://phabricator.vyos.net/T3356
Mar 30 2021
The workaround for save command does not seem to work, have you tried for commit-archive option ?
Mar 29 2021
This command is used to generate the ssh fingerprint of your host when vyos cannot verify the legitimacy of the remote server
Mar 27 2021
Mar 23 2021
Fixed in the latest version:1.4-rolling-202103230217
Mar 22 2021
Post the migration of the script from /opt/vyatta/bin/vyos-strip-config.pl to /usr/libexec/vyos/strip-private.py, the strip-private seems to be not working when the ipv6 address is configured to an interface.
Mar 8 2021
Mar 5 2021
Submitted this PR to fix the issue:
Mar 4 2021
Feb 20 2021
Hi, I have tried these set of configuration and the openvpn connection was up and working fine.
Feb 17 2021
This issue has been fixed in this commit: https://github.com/vyos/vyos-1x/commit/0fb5cc02c6c16ef410c1b1f746c1fbfbc40a0da0