# Bind (separate) Transport and HTTP to two different IP addreses

**URL:** <https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630>\
**Category:** Elasticsearch\
**Created:** [October 18, 2011, 3:47pm UTC](https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630 "2011-10-18T15:47:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shlomke](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@Shlomke](https://discuss.elastic.co/u/Shlomke)\
**Post date:** [October 18, 2011, 3:47pm UTC](https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630/1 "2011-10-18T15:47:20Z")

</div>

Hi,

I'm trying ES 2-node cluster on a GoGrid cloud environment. For high-  
availability, I'm going to use GoGrid's load-balancer.

On each node I have two network interfaces - one Public and one  
Private. Using the Private interface is free, but using the Public  
costs per 1GB transferred. And here's the problem: The load balancer  
will only communicate with the Public network interface. I will have  
to bind ES to the Public interface, and that means that I'm going to  
pay for each query my web servers send to the ES servers. But that's  
not all. I also will have to pay for the Transport module traffic,  
since it binds too to the Public interface.

So, the question is can I separate HTTP and Transport modules to two  
different IP addresses.

Thanks,

Shlomke`

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [October 18, 2011, 4:21pm UTC](https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630/2 "2011-10-18T16:21:53Z")

</div>

Sure, set the transport.host setting to the private IP address, and set  
http.host setting to the public IP.

On Tue, Oct 18, 2011 at 5:47 PM, Shlomke` [shlomi.shlush@gmail.com](mailto:shlomi.shlush@gmail.com) wrote:

> Hi,
> 
> I'm trying ES 2-node cluster on a GoGrid cloud environment. For high-  
> availability, I'm going to use GoGrid's load-balancer.
> 
> On each node I have two network interfaces - one Public and one  
> Private. Using the Private interface is free, but using the Public  
> costs per 1GB transferred. And here's the problem: The load balancer  
> will only communicate with the Public network interface. I will have  
> to bind ES to the Public interface, and that means that I'm going to  
> pay for each query my web servers send to the ES servers. But that's  
> not all. I also will have to pay for the Transport module traffic,  
> since it binds too to the Public interface.
> 
> So, the question is can I separate HTTP and Transport modules to two  
> different IP addresses.
> 
> Thanks,
> 
> Shlomke`

---

<div class="post-metadata">

**Author:** ![Shlomke](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@Shlomke](https://discuss.elastic.co/u/Shlomke)\
**Post date:** [October 18, 2011, 4:36pm UTC](https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630/3 "2011-10-18T16:36:35Z")

</div>

Thanks Shay, I will give it a try.

On Oct 18, 6:21 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> Sure, set the transport.host setting to the private IP address, and set  
> http.host setting to the public IP.
> 
> On Tue, Oct 18, 2011 at 5:47 PM, Shlomke` [shlomi.shl...@gmail.com](mailto:shlomi.shl...@gmail.com) wrote:
> 
> > Hi,
> 
> > I'm trying ES 2-node cluster on a GoGrid cloud environment. For high-  
> > availability, I'm going to use GoGrid's load-balancer.
> 
> > On each node I have two network interfaces - one Public and one  
> > Private. Using the Private interface is free, but using the Public  
> > costs per 1GB transferred. And here's the problem: The load balancer  
> > will only communicate with the Public network interface. I will have  
> > to bind ES to the Public interface, and that means that I'm going to  
> > pay for each query my web servers send to the ES servers. But that's  
> > not all. I also will have to pay for the Transport module traffic,  
> > since it binds too to the Public interface.
> 
> > So, the question is can I separate HTTP and Transport modules to two  
> > different IP addresses.
> 
> > Thanks,
> 
> > Shlomke`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:51am UTC](https://discuss.elastic.co/t/bind-separate-transport-and-http-to-two-different-ip-addreses/5630/4 "2017-07-06T03:51:35Z")

</div>

Closed on July 6, 2017, 3:51am UTC


