Homebridge listens on tcp6 only

Hi,

I have two HomeBridge instances running. The problematic one is on Debian:

root@supermicro:/etc# netstat -an | grep 51828 | grep LISTEN
tcp6       0      0 :::51828                :::*                    LISTEN     

It listens on IPv6 only, but is advertised with IPv4 and IPv6:

root@supermicro:/etc# avahi-browse --verbose _hap._tcp | grep Supermicro
Server version: avahi 0.6.31; Host name: Supermicro.local
E Ifce Prot Name                                          Type                 Domain
+   eth1 IPv6 Homebridge Supermicro                         _hap._tcp            local
+   eth1 IPv4 Homebridge Supermicro                         _hap._tcp            local
+   eth0 IPv6 Homebridge Supermicro                         _hap._tcp            local
+   eth0 IPv4 Homebridge Supermicro                         _hap._tcp            local

Another instance on a Mac works fine:

➜  ~ netstat -an | grep 51826  
tcp46      0      0  *.51826                *.*                    LISTEN     

This one listens on both, IPv4 and IPv6 and is advertised as such.

How can I force hombridge to use both, IPv4 and IPv6 or advertise IPv6 only?

[fuzzy01]

This the result of the way nodejs creates the server socket, see here: (homebridge / hap-nodejs creates the server socket without specifying a hostname)

https://github.com/nodejs/node/issues/9390 and here https://github.com/nodejs/node/commit/12cf3594235e6c4c6838ae7588b5e73ad9775dfa

It looks like the behaviour of nodejs on Ubuntu/Debian has changed, it opens only a tcp6 socket.

It is easy to test it, if you start a simple server:

node -e "net.createServer(c=>console.log).listen(5555)"

netstat -a | grep 5555
tcp6       0      0 [::]:5555               [::]:*                  LISTEN    

The solution is to modify hap-nodejs to create a tcp4 server socket or both.

A quick fix is to modify eventedhttp.js in /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util, in line 60:

this._tcpServer.listen(targetPort);

to this

this._tcpServer.listen(targetPort, '0.0.0.0');

[Sailing74]

It just worked for me as well - thanks!

Any plans to include this into homebridge in some way?