Using interface=ib0 interferes with serving bokeh

(After asking around with my sysadmins, I think this is not just related to my network configuration. But I could be wrong.)

I am using infiniband (--interface=ib0 for dask-scheduler and dask-worker) on a small linux cluster. The only change I needed was to refer to the host by its IP rather than domain name, as identified by at scheduler startup. After that, I can see all processes start well and seem to run tasks, etc..

However, after this change I cannot find the bokeh web server. The scheduler reports an IP address and port for the bokeh server. The IP address is the same as that of the scheduler and the port is 1 higher, as usual. But using my usual ssh tunneling to that address:port does not expose the bokeh server.

My sysadmins noted that the infiniband is configured to handle TCP/IP traffic, but that is only intended to communicate with other devices on infiniband. Outside traffic is not supported. Their suggestion is to explcitly tell the web server the device to listen to. Is this supported by an existing scheduler option?