- User Since
- Dec 6 2017, 2:21 PM (92 w, 6 d)
Dec 3 2018
I forgot to fetch commits for the latest build-ami version when submitted report.
Now I confirms that problem exists in the latest version with the last commit:
In the latest rolling update build for AWS AMI there is no quagga package, because it was replaced by FRR. Should be the same for regular build.
Nov 30 2018
I confirm this issue at VyOS 1.2.0-rolling+201811290337
Is it working at start and fails after some time, or not connection not establishing at all?
This is great an very important feature for AWS since they introduced very cheap and advanced t3 instances.
Nov 24 2018
If engineid in user node only provides hashing for auth key I would remove it too.
Since we usually not assign engine id automatically it is created for every new hardware installation automatically, so hash of auth key became not transferable. In this case we have to keep plain text password for snmpv3 in our config store, because of automation of provisioning. But I would to keep hash instead of plain text credential.
Aug 29 2018
I am interesting to install and test image in Alibaba cloud.
We are using "Double static NAT" life hack in AWS, so IPsec protocols works actually without NAT
And it is working good.
Aug 10 2018
It seems to be working now
Aug 6 2018
Jul 12 2018
We did an upgrade of six running instance with complicated Ipsec configuration ( 10 to 50 peers) from VyOS 1.1.8 to 1.2.current. For 1 time from 6 we had a problem with Charon's install_routes = yes
Jul 9 2018
I was able to copy-paste configuration on latest VyOS 1.2.0 rolling update in my configuration
I also mentioned that my current configuration has not separate set v3 engineid 'id' command as in initial comment,
and it is working without problem.
This script can be removed as soon as we will implement better way for populating AS numbers in netflow configuration.
IKEv2 is not good in Strong Swan 4.5 at all. There is incompatibility with some other clients.
Jun 29 2018
I've update installation manual of Zabbix agent for VyOS 1.2
It is easier to maintain now because of using of standard Jessie repository.
Only VyOS scripts should be maintained.
Jun 26 2018
Jun 22 2018
We are runing VyOS 1.1.8 with AWS tunnels based on AWS provided config.
It's running for months !
Jun 21 2018
Dec 19 2017
I reproduce the same problem on VyOS 1.1.8 on different region - N.Verginia.
Dec 7 2017
After a lot of reinstallation and terminaton we broke Amazon VPS, so I did full test.
Dec 6 2017
I've did a lot of attempts, and removed old stuff. Anyway I can reproduce it one more time with the same result.
I am configuring 2 interfaces for the virtual router. May be it can be a problem?
I face this issue on the new VyOS 1.1.8 AMI in the Frakfurt region. It is working in Seoul region.