BIND_ON_ALL_INTERFACES property on Edge setup not working on recent releases

[#1]

Hi Team,

I received a customer query about the design change if anything of "BIND_ON_ALL_INTERFACES" property for Private Cloud.

It doesn't seem to work on 4.16.x or later releases.

Even though we configure setup config file with “BIND_ON_ALL_INTERFACES=n”, it looks still binding to all the interfaces including HOSTIP.

# netstat -an | grep 9001
tcp 0 0 192.168.99.100:9001 0.0.0.0:* LISTEN
tcp 0 0 153.153.52.85:9001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN
tcp 0 0 10.1.179.74:9001 0.0.0.0:* LISTEN
tcp 0 0 10.1.179.138:9001 0.0.0.0:* LISTEN
tcp 0 0 10.1.179.10:9001 0.0.0.0:* LISTEN

while it was on 4.15.x as I confirmed:

# netstat -an | grep 9001
tcp 0 0 192.168.99.100:9001 0.0.0.0:* LISTEN

where 192.168.99.100 is HOSTIP.

Their requirement is to separate the interface between external communication and internal communication.

Could someone please let them know how it can be configured on 4.17.x or 4.18.x?

Regards,
Toshi

[#2 · Accepted solution]

I confirmed that the property 'BIND_ON_ALL_INTERFACES' is no more supported on 4.16.x or later releases.

On these version of Private Cloud, binding to and listening on a specific interfaces is supported on the Virtual Host level only. So, we need to configure Virtual Host property "Interface" as explained at:

https://docs.apigee.com/api-platform/fundamentals/virtual-host-property-reference

for example,

"interfaces" : [ "eth1","eth2" ],