

Set vpn l2tp remote-access ipsec-settings authentication pre-shared-secret Set vpn l2tp remote-access ipsec-settings authentication mode pre-shared-secret Set vpn l2tp remote-access dns-servers server-1 '1.1.1.1' Set vpn l2tp remote-access client-ip-pool stop 192.168.255.254 Set vpn l2tp remote-access client-ip-pool start 192.168.255.1

Set vpn l2tp remote-access outside-address 'x.x.x.x' Set vpn ipsec ipsec-interfaces interface 'dum0' Set vpn ipsec nat-networks allowed-network 0.0.0.0/0 Set nat destination rule 20 translation address 'x.x.x.x' Configure L2TP and IPSec:

Set nat destination rule 20 inbound-interface 'eth0' Set interfaces dummy dum0 address 'x.x.x.x/32' Create DNAT rules: Set public IP addresses on the dummy interface: In this case we can use a simple solution with a dummy interface and DNAT rules on VyOS routers. Working with this group was a real pleasure.Īll instances on AWS are located behind 1-to-1 NAT and this affectly IPSec negatively. The experience was equally impressive and I again had a simple and reliable workaround. (Hell, can I give them 10 stars?).Ĥ days later I opened a second ticket about an unrelated VTI issue that had also been plaguing us for many months. 5 Stars for service, knowledge, and going above and beyond. What a HUGE load off my back to have that issue resolved with a reliable fix. Fast forward a few days and the root cause was identified, I had a simple workaround in place and working in production(and had learned a lot from other Support Engineers that had contributed). Its was great to see a response from an Engineer in just a couple hours. I gave it a relatively low priority so I would know what to expect with future tickets. Just hours after our Support PO went thru, I opened a ticket. My boss, Daya Rajaratnam, decided we needed to get Commercial Support and open proper tickets and also to show our support of the VyOS Team. We were struggling due to a single “show-stopper” issue, month after month, and not able to proceed with the rest of the refresh project. My boss just recently purchased a VyOS Subscription, or license, because we were experiencing a couple bizarre issues during our VyOS refresh of 30+ routers. I believe it was Taras that even updated the VyOS/VMware doc to clarify a few things that I needed help understanding. Taras, Yuriy, Jose, (and I hope I didn’t miss anyone) are quick to contribute and answer any questions I have. I think Dmitriy has owned our last 2 ticket, and the rest of the Support Team have all helped out.

I have nothing but good things to say about the VyOS Support Engineers.
