bbb and all components binds to wrong ip/interface

[ethrgeist]

Hi,

i'm currently testing the new BBB release for a migration of our production systems.

One of the things i found is that the services are getting bound to the wrong interface and i find it hard to set the correct interface.

I have multiple interfaces with multiple public/semi-public IP addresses on this server, one of them is a public IP bound to my loop back adapter, which the install script then uses as my public IP. But since a lot of our servers have multiple public IP addresses with multiple rdns names setup, we need to that to specific IP addresses.

How to overwrite that during install?

For the time being i am overwriting

• /usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml
• /opt/freeswitch/etc/freeswitch/vars.xml
• /opt/freeswitch/etc/freeswitch/sip_profiles/external.xml
• /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties
• /usr/share/bbb-apps-akka/conf/application.conf

(Did i miss any?)

But i'd prefer to be able to hand-over the IP which should be used, instead of relying on auto detection. Maybe as optional parameter?

e: to clarify: all services are effected, not just kurento.

[michi-80337]

The install script looks for the interface used by the default route and has some heuristics to detect some NAT setups. The real work happens in the function get_IP, which is called once without a -s switch and twice with a -s given. It should be an easy task to add an additional switch to manually set the IP address, because get_IP already checks if it was called before.

As a workaround it should work to set two environment variables when starting the install script:

root@server:~# IP=xxx.xxx.xxx.xxx INTERNAL_IP=yyy.yyy.yyy.yyy install.sh

But please be aware that the workaround will work on the current version of the script. There are good chances that it will fail on older or newer versions, as the workaround explores a side effect, hidden in the depth of the code. ...

CU, Michi