This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

L2TP and Site to Site same remote Gateway IP, wrong?

So we have a HQ to which we have a Site-to-site ipsec tunnel from our branch office. It also serves as a L2TP host.

Some of our customers has locked access to our HQ ip so in order to connect to them we can connect via VPN to our HQ and then connect to the customer.

This works fine when we connect from home, hotel etc as long as we're not in one of our branch office.

Since we have the same subnet i've created a guest net to which we can connect (wifi) and i thought that that would solve the problem. But it didn't.

So my question is. If i'm connecting from a branch office, even though i'm on a different vlan, but still with the same public IP as the already configured site-to-site tunnel, is that causing the problem for me?

In that case i thought that if i move the l2tp vpn listening ip to .33 instead of .32 it should solve the issue. Am i thinking right?

Kind regards,

Sebastian



This thread was automatically locked due to age.
Parents Reply Children
No Data