Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot add multiple Interfaces to IPSec VPN encryption domain. #2120

Closed
bobbythomas opened this issue Jan 21, 2018 · 14 comments
Closed

Cannot add multiple Interfaces to IPSec VPN encryption domain. #2120

bobbythomas opened this issue Jan 21, 2018 · 14 comments
Labels
support Community support

Comments

@bobbythomas
Copy link

There is no option to add multiple networks to the IPSec VPN encryption domain. The only option is to add interface network in phase 2 configuration, but even if we add multiple phase 2 paramaeters to include multiple interface networks, it wont show up under the active tunnel and cannot access those networks over the tunnel (only the first phase 2 config is accepted). Please provide a method to use subnets instead of interface network in VPN encryption domain.

Thank you,
Regards,
Bobby Thomas

@mimugmail
Copy link
Member

This is not possible with the software behind (strongswan). You can only have one network as source and destination for every SA, but you can as many SA's as you want. There is no real encryption domain like wiht other vendors (Cisco ASA), but you wont get into any trouble creating multiple SA's

@bobbythomas
Copy link
Author

I tried creating multiple phase 2 entries for multiple interface networks but it didn't work.

@mimugmail
Copy link
Member

Can you give me an example? Perhaps I'm too stupid to get it .. I can set interface subnets or edit networks manually in a P2 so I dont see any problem ..

@bobbythomas
Copy link
Author

yes, even I can set interface subnets or add network if I add new phase 2 rule but when a VPN is established I am not seeing that network in the SPD (Security Policy Database).

@mimugmail
Copy link
Member

Perhaps because the other side is misconfigured and that's the reason the VPN isn't fully established?
For me it works great, you should check the logs for failed SAs

@fichtner
Copy link
Member

what type of device is on the other end?

@fichtner
Copy link
Member

also, you haven't mentioned which ike version....

@bobbythomas
Copy link
Author

Sorry, this is for Ikev1 roadwarrior remote access connection. I am connecting from my Android mobile.

@fichtner fichtner added the support Community support label Jun 23, 2018
@jsirianni
Copy link

I too am having the same issue. No trouble getting my first phase 2 to work, but the second will not work at all.

The goal is to have my remote site route to my primary site which has multiple networks (and routes to other remote networks)

The issue is seen with both ike v1 and v2. I am on the latest release.

@mimugmail
Copy link
Member

Do you have trouble adding it or doesnt it just come up?

@fichtner
Copy link
Member

With IKEv2, you can set "Tunnel Isolation" in your phase 1. But if the issue is also on IKEv1, that would indicate it's another issue that is almost impossible to debug without logs from both sides.

I have a FortiGate device that would always take none but the last phase 2 and the "Tunnel Isolation" mode is what made this work.

@jsirianni
Copy link

Ill have to try Tunnel Isolation. The issue is that my first phase 2 will work, with the subnet of my choice (it happens to be 10.1.10.0/24, but 0.0.0.0/0 does the trick as well).

The second phase 2 never works. the otherside of the tunnel has a route to 10.70.1.0/24, but I cant hit those IPs from my remote site.

@mimugmail to answer your question, I can add the second phase 2 just fine. It just does not come up / route traffic.

@mimugmail
Copy link
Member

This is likely impossible to fix when not knowing logs of both sides and also config of the other side.

@jsirianni
Copy link

Sure, ill get them when I can. Should be soon.

@fichtner fichtner closed this as completed Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

4 participants