AndreaTosi  Freshman Member

no problem! thanks for letting me know it works on other devices!

Hi, all went back to normal relinking and reconfiguring by scratch that device.

thank you, mMontana, for replying... I'll leave it as it is now, with a public IP on my wan interface. Since i'm on a SDWAN device, i have no power on what parameters goes where in l2tp configuration. Next sdwan firewall I'll have to remotely connect i'll double check and update this post... Bye!

... since I was in a hurry, as usual, I unlinked that device from the problematic site, then relinked it and recreate from scratch its configuration... Just curious if there was a better option.

:s Resolved my issue by buying an 8IP subnet from my ISP and assigned directly to the WAN1 port. Anyone has ever successfully created a natted l2tp ?

Found a workaround: if I modify a port, then go back in editing and disable it, the Save button pops up. I can then re-enable the same port and see my configuration where i'd like to see it !!

Another update: I've managed to make a VPN working ... Set up a branch VPN50 to connect to the hub's older Zywall110! To do this, I configured the hub's zywall 110 as a "service / non sdwan gateway"; disabled the "hub" option on the new firewall i had setup under profile/autovpn and enabled branch to non-sdwan, adding the…

Just to update my post... Yesterday I double checked branch's router and Zywall100Plus configuration; checked once more my hub's vpn300 nebula configuration, profile and services but didn't get a working connection. Since that flag reads Branch to non-sd Hub, tomorrow I'll try leaving our hub's old firewall (Zywall 110)…

Checking my configuration, noticed this: I said i left disabled the "branch to non-sdwan hubs" but this way i couldn't see our "other" firewall listed under our hub's VPN300 configuration page. Enabled that option, can see the remote listed. This evening I'll have another round with them and update this post.