# Ipsec service into rancher **URL:** \ **Category:** Rancher 1.x\ **Created:** [September 11, 2015, 2:04am UTC](https://forums.suse.com/t/ipsec-service-into-rancher/441 "2015-09-11T02:04:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kolesnikovIV](https://avatars.discourse-cdn.com/v4/letter/k/a3d4f5/32.png) [@kolesnikovIV](https://forums.suse.com/u/kolesnikovIV)\ **Post date:** [September 11, 2015, 2:04am UTC](https://forums.suse.com/t/ipsec-service-into-rancher/441/1 "2015-09-11T02:04:26Z")
Hi, we build public ipsec service and use rancher for scale our service now, and we have trouble with port conflict. we cannot use alternate ports (for example 501/udp,4501/udp) because service is public, and if we do that we must edit service list for each client. it is not possible. can i ask you for editing your ipsec service for alternate ports use? PS. i’m sure what it right move for rancher service and it help to use rancher for build ipsec services in future ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [September 25, 2015, 3:18am UTC](https://forums.suse.com/t/ipsec-service-into-rancher/441/2 "2015-09-25T03:18:33Z")
Currently this is impossible to do in Rancher, but we will most likely be reviewing our ipsec stack in the future and can consider providing the ability to edit our ipsec service or alternate ports. I’ve created a feature request in Github to track this. [https://github.com/rancher/rancher/issues/2139](https://github.com/rancher/rancher/issues/2139) ---
**Author:** ![hwinkel](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hwinkel/32/951_2.png) [@hwinkel](https://forums.suse.com/u/hwinkel)\ **Post date:** [March 4, 2016, 11:27am UTC](https://forums.suse.com/t/ipsec-service-into-rancher/441/3 "2016-03-04T11:27:45Z")
we are faced with a similar problem where we need access to rancher hosted service via a a "external"IPsec VPN. The VPN should be provided as a a service (similar seen in OPenStack) so somebody can send requests to an IP of a rancher managed network