# Rancher LB port range **URL:** \ **Category:** Rancher 1.x\ **Created:** [February 23, 2018, 7:28am UTC](https://forums.suse.com/t/rancher-lb-port-range/9606 "2018-02-23T07:28:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Elton\_Renda](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Elton\_Renda](https://forums.suse.com/u/Elton_Renda)\ **Post date:** [February 23, 2018, 7:28am UTC](https://forums.suse.com/t/rancher-lb-port-range/9606/1 "2018-02-23T07:28:22Z")
Is there anyway to set a port range in Rancher LB for public TCP service rule? The goal is to setup LB to handle connections for passive FTP backends, the data connections require a range of ports to be opened in the LB. We are wanting to set the pasv\_range to at least 1000 ports, which right now means putting all the service rules in manually? not to mention the LB rules list will be massive. Is there anyway to achieve this? We are currently using Rancher v1.6.10. ---
**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\ **Post date:** [February 23, 2018, 7:56am UTC](https://forums.suse.com/t/rancher-lb-port-range/9606/2 "2018-02-23T07:56:58Z")
Port ranges are not supported by cattle managed networking or kubernetes, and are very inefficient in Docker/swarm. You can do --net=host and then the server container can listen on whatever it wants… But not with a load balancer container. ---
**Author:** ![Elton\_Renda](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Elton\_Renda](https://forums.suse.com/u/Elton_Renda)\ **Post date:** [February 26, 2018, 9:37am UTC](https://forums.suse.com/t/rancher-lb-port-range/9606/3 "2018-02-26T09:37:47Z")
Thanks for reply Vincent, have got it working by setting --net=host for data connections and using ELB for round robin on command port 😉