dump1090 mutability --net-bo-port 30005, no TCP Beast output

FlightAware ADS-B Flight Tracking
1

Hi,

I changed from the Flightaware dump1090 to the mutability dump1090 on two of my four raspberry’s and now I no longer being able to feed one dump1090 with TCP Beast output from an other raspberry with the new dump1090-mutability.

I thought I could replace the dump1090 flightaware version of dump1090 for the mutability version? Or am I wrong?

My four raspberry’s run piaware and dump1090. I have four different antenna’s.
This is my setup:

**host ted1090-1 (IP 192.168.11.44 ) **

  • piaware 2.1-1 (mlat disabled)
  • dump1090 (1.2-2 flightaware version)
  • should also listen to the dump1090 on ted1090-2 (IP 192.168.11.34) & ted1090-3 (192.168.11.32) using netcat:
    nc -d 192.168.11.34 30005 | nc 127.0.0.1 30004 &
    nc -d 192.168.11.32 30005 | nc 127.0.0.1 30004 &
    This host no longer connects over port 30005 to ted1090-3 (IP 192.168.11.32 ) since the dump1090 upgrade on host ted1090-3 to mutability.
    Netstat show this:

pi@ted1090-1 ~ $ sudo netstat --program --protocol=inet --tcp --wide --all
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:http-alt              *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:30001                 *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:30002                 *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:30003                 *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:30004                 *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:30005                 *:*                     LISTEN      1962/dump1090   
tcp        0      0 *:ssh                   *:*                     LISTEN      2184/sshd       
tcp       94      0 localhost:30004         localhost:58627         ESTABLISHED 1962/dump1090   
tcp        0      0 192.168.11.44:40360     192.168.11.34:30005     ESTABLISHED 2346/nc         
tcp      748      0 localhost:48133         localhost:30005         ESTABLISHED 2226/faup1090   
tcp        0      0 192.168.11.44:32822     eyes.flightaware.com:1200 ESTABLISHED 2150/piaware    
tcp        0   1131 localhost:30005         localhost:48133         ESTABLISHED 1962/dump1090   
tcp        0    117 localhost:58627         localhost:30004         ESTABLISHED 2347/nc

**host ted1090-2 (IP 192.168.11.34) **

  • piaware 2.1-1 (mlat enabled)
  • dump1090 (1.2-2 flightaware version)
    Netstat looks good. Connections to ted1090-1 (IP 192.168.11.44) and ted1090-4 (IP 192.168.11.8) over port 30005:

pi@ted1090-2 ~ $ sudo netstat --program --protocol=inet --tcp --wide --all
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:http-alt              *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:30001                 *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:30002                 *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:30003                 *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:30004                 *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:30005                 *:*                     LISTEN      1878/dump1090   
tcp        0      0 *:ssh                   *:*                     LISTEN      2138/sshd       
tcp        0      0 192.168.11.34:50793     earrs.hou.flightaware.com:1200 ESTABLISHED 2113/piaware    
tcp        0      0 localhost:30005         localhost:37289         ESTABLISHED 1878/dump1090   
tcp        0      0 192.168.11.34:30005     192.168.11.44:40360     ESTABLISHED 1878/dump1090   
tcp        0      0 localhost:54461         localhost:30004         ESTABLISHED 3009/fa-mlat-client
tcp        0      0 192.168.11.34:30005     ted1090-4.bachstraat20:42710 ESTABLISHED 1878/dump1090   
tcp        0      0 localhost:37289         localhost:30005         ESTABLISHED 3009/fa-mlat-client
tcp      134      0 localhost:37284         localhost:30005         ESTABLISHED 2182/faup1090

**host ted1090-3 (IP 192.168.11.32) **

  • piaware 2.1-1 (mlat enabled)
  • dump1090 (1.14 mutability version)
  • This host no longer connects to ted1090-1 (IP 192.168.11.44) and ted1090-4 (IP 192.168.11.8) over port 30005 since the upgrade to dump1090 mutability!
    Netstat:

pi@ted1090-3 ~ $ sudo netstat --program --protocol=inet --tcp --wide --all
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:http                  *:*                     LISTEN      2166/lighttpd   
tcp        0      0 localhost:10001         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 localhost:30001         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 localhost:30002         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 localhost:30003         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 localhost:30004         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 localhost:30005         *:*                     LISTEN      1830/dump1090-mutab
tcp        0      0 *:ssh                   *:*                     LISTEN      2126/sshd       
tcp        0      0 ted1090-3:46073         eyes.flightaware.com:1200 ESTABLISHED 1997/piaware    
tcp        0      0 localhost:30004         localhost:59109         ESTABLISHED 1830/dump1090-mutab
tcp        0      0 localhost:53668         localhost:30005         ESTABLISHED 2208/fa-mlat-client
tcp        0   1011 localhost:30005         localhost:53667         ESTABLISHED 1830/dump1090-mutab
tcp        0      0 localhost:30005         localhost:53668         ESTABLISHED 1830/dump1090-mutab
tcp     1011      0 localhost:53667         localhost:30005         ESTABLISHED 2206/faup1090   
tcp        0      0 localhost:59109         localhost:30004         ESTABLISHED 2208/fa-mlat-client

**host ted1090-4 (IP 192.168.11.8) **

  • piaware 2.1-1 (mlat disabled)
  • dump1090 (1.14 mutability version)
  • should also listen to the dump1090 on ted1090-2 & ted1090-3 using netcat:
    nc -d 192.168.11.34 30005 | nc 127.0.0.1 30004 &
    nc -d 192.168.11.32 30005 | nc 127.0.0.1 30004 &
    This host no longer connects over port 30005 to host ted1090-3 (IP 192.168.11.32) since the dump1090 upgrade on host ted1090-3 to mutability.
    However, it still connects to ted1090-2 with the dump1090 flightaware version over port 30005!
    Netstat shows this:

pi@ted1090-4 ~ $ sudo netstat --program --protocol=inet --tcp --wide --all
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:http                  *:*                     LISTEN      2504/lighttpd   
tcp        0      0 localhost:10001         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 localhost:30001         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 *:8754                  *:*                     LISTEN      2048/fr24feed   
tcp        0      0 localhost:30002         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 localhost:30003         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 localhost:30004         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 localhost:30005         *:*                     LISTEN      1853/dump1090-mutab
tcp        0      0 *:ssh                   *:*                     LISTEN      2282/sshd       
tcp        0     81 localhost:56352         localhost:30004         ESTABLISHED 2538/nc         
tcp        0      0 ted1090-4.bachstraat20:42705 192.168.11.34:30005     ESTABLISHED 2457/nc         
tcp        0      0 ted1090-4.bachstraat20:42832 eyes.flightaware.com:1200 ESTABLISHED 2018/piaware    
tcp        0      0 localhost:39257         localhost:30002         ESTABLISHED 2048/fr24feed   
tcp       49      0 localhost:30004         localhost:56348         ESTABLISHED 1853/dump1090-mutab
tcp        0   1034 localhost:30005         localhost:46223         ESTABLISHED 1853/dump1090-mutab
tcp        0      0 localhost:30002         localhost:39257         ESTABLISHED 1853/dump1090-mutab
tcp     2036      0 localhost:46223         localhost:30005         ESTABLISHED 2337/faup1090

I question is why can hosts ted1090-1 and ted1090-4 no longer connect to ted1090-3 over port 30005 after I upgraded this host tot dump1090-mutability?

The dump1090’s are running on all four hosts. This shows that dump1090-mutability is running on host ted1090-3:


pi@ted1090-3 ~ $ ps -ef | grep dump
dump1090  1830     1 31 08:06 ?        00:35:16 /usr/bin/dump1090-mutability --net --ppm 0 --oversample --fix --phase-enhance --max-range 300 --net-http-port 0 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30004 --net-bo-port 30005 --net-sbs-port 30003 --net-fatsv-port 10001 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --net-bind-address 127.0.0.1 --stats-every 3600 --write-json /rundump1090-mutability --write-json-every 1 --json-location-accuracy 1 --quiet
pi        2488  2214  0 09:59 pts/0    00:00:00 grep --color=auto dump

The option –net-bo-port 30005 (default) should give TCP Beast output on port 30005.

And piaware runs as well on all four raspberry’s. Even on host ted1090-3 it is sending messages to flightaware every 5 minutes!

When I stop dump1090-mutability on host ted1090-3 and I start the dump1090 flightaware version, it works as it should.

Why isn’t it working with the dump1090-mutability? What is wrong? How can I fix this?

2

The default configuration passes --net-bind-address 127.0.0.1 which binds listening sockets to localhost only. If you want to open it up for remote access, clear the bind address in the configuration.

3

damn, you beat me a few seconds there Oliver :slight_smile:, was about to post the same

4

Thanks a lot. I appreciate your prompt response very much!

Ted