anything
AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: rbfeeder non-standard dump1090?  (Read 634 times)

0 Members and 1 Guest are viewing this topic.

GlynH

  • Hero Member
  • *****
  • Posts: 589
rbfeeder non-standard dump1090?
« on: November 18, 2020, 07:26:58 PM »
I think I’ve mentioned here recently that I am over the moon with finally being able to have my own device sat on the network unattended, feeding both RB24 and FR24 and still be able to use the RadarBox software locally for the first time since I originally got into the hobby back in 2008!

In the two weeks since I setup the Raspberry Pi/FlightStick I notice I am now sat at the number 5 position in the UK ranking and number 83 Globally which is a result especially as I am tracking less than a quarter of the aircraft now than I was back in 2008!

Now I am looking to expand my horizons a little bit I seem to be hitting a brick wall with regard to using the OpenADSB app on my own phone to connect to my own data on my own device on my own network.

OpenADSB can use unfiltered data from ADSBExchange which should be good for military and other types of aircraft and it also has the option to connect to your local dump1090 to display your own contacts as this has always been my primary interest but here is where my problem begins.

Looking at the Pi it is not showing dump1090 as being installed so I am unable to determine what port I need to connect to it.

I suspect it is somehow integral and wrapped up in rbfeeder process being the software I installed from AirNav to feed the RadarBox network which incidentally takes up 20% of my CPU time.

Is this assumption correct and is there anything I might be able to do to rectify this so I can use the app I paid for to view my own data as going forward there might be further instances where I need an ‘industry standard’ type of connection to access my own data?

A question for Support I guess but as I’m still waiting for an answer to a question I asked over a week ago I thought I’d throw it out here first...

Thanks & kind regards,
-=Glyn=-
« Last Edit: November 18, 2020, 07:35:25 PM by GlynH »

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #1 on: November 18, 2020, 07:55:36 PM »
Run this command to list the available ports

NOTE: Increase the width of PuTTY window to see all columns

Code: [Select]
sudo netstat -anp | grep -w LISTEN   

« Last Edit: November 18, 2020, 07:57:53 PM by abcd567 »

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #2 on: November 18, 2020, 11:05:08 PM »
Thanks for the reply...this is what I see;

sudo netstat -anp | grep -w LISTEN

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      536/sshd
tcp        0      0 0.0.0.0:32088           0.0.0.0:*               LISTEN      464/rbfeeder
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      798/smbd
tcp        0      0 0.0.0.0:32004           0.0.0.0:*               LISTEN      464/rbfeeder
tcp        0      0 0.0.0.0:32008           0.0.0.0:*               LISTEN      464/rbfeeder
tcp        0      0 0.0.0.0:32457           0.0.0.0:*               LISTEN      464/rbfeeder
tcp        0      0 0.0.0.0:32458           0.0.0.0:*               LISTEN      464/rbfeeder
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      798/smbd
tcp        0      0 0.0.0.0:32459           0.0.0.0:*               LISTEN      464/rbfeeder
tcp6       0      0 :::8754                 :::*                    LISTEN      529/fr24feed
tcp6       0      0 :::22                   :::*                    LISTEN      536/sshd
tcp6       0      0 ::1:3350                :::*                    LISTEN      489/xrdp-sesman
tcp6       0      0 :::3389                 :::*                    LISTEN      521/xrdp
tcp6       0      0 :::445                  :::*                    LISTEN      798/smbd
tcp6       0      0 :::32004                :::*                    LISTEN      464/rbfeeder
tcp6       0      0 :::32008                :::*                    LISTEN      464/rbfeeder
tcp6       0      0 :::32457                :::*                    LISTEN      464/rbfeeder
tcp6       0      0 :::32458                :::*                    LISTEN      464/rbfeeder
tcp6       0      0 :::32459                :::*                    LISTEN      464/rbfeeder
tcp6       0      0 :::139                  :::*                    LISTEN      798/smbd

I did run a port scanner against the Pi the other day in an attempt to see what ports might be open and threw in some other ports I've seen in related software to no avail.

Thanks & kind regards,
-=Glyn=-


abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #3 on: November 19, 2020, 12:23:37 AM »
From your output of netstat command, I have copied lines pertaining to rbfeeder, and added a column at right describing each port. There are two ports (32008 & 32458) about which I dont know. Mostlikely these are ports for inputting/outoutting data in some special format. Try tem by typing in your browser these addresses

IP-of-Pi:32008

IP-of-Pi:32458

Extracted from netstad command's output:
NOTE:
Scroll right to see in full
Code: [Select]
tcp   0   0 0.0.0.0:32088   0.0.0.0:*   LISTEN  464/rbfeeder   Output for ANRB Windows 
tcp   0   0 0.0.0.0:32004   0.0.0.0:*   LISTEN  464/rbfeeder   Input-MLAT results feedback. 
tcp   0   0 0.0.0.0:32008   0.0.0.0:*   LISTEN  464/rbfeeder   ???????   
tcp   0   0 0.0.0.0:32457   0.0.0.0:*   LISTEN  464/rbfeeder   Output-Beast format. 
tcp   0   0 0.0.0.0:32458   0.0.0.0:*   LISTEN  464/rbfeeder   ??????   
tcp   0   0 0.0.0.0:32459   0.0.0.0:*   LISTEN  464/rbfeeder   Output-Basestation format. 
« Last Edit: November 19, 2020, 12:26:47 AM by abcd567 »

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #4 on: November 19, 2020, 01:00:36 AM »
Thanks for the info.

Yeah I tried all of the ports shown in my port scan in a web browser to no avail as it either sat there spinning or returned;

This page isn't working at the moment
xxx.xxx.xxx.xxx sent an invalid response.
ERR_INVALID_HTTP_RESPONSE

I believe that OpenADSB might be looking for port 80 or 8080 from dump1090 so a standard http port that might not be present in the version bundled with rbfeeder?

The port number can be configured from within OpenADSB but of course it has to exist in the first place!

Thanks & kind regards,
-=Glyn=-
« Last Edit: November 19, 2020, 01:21:59 AM by GlynH »

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #5 on: November 19, 2020, 02:35:12 AM »
Easy solution to have standard ports matching other software like OpenADSB and AdsbX :

Step-1: Install dump1090-mutability
Code: [Select]
sudo apt install dump1090-mutability 

sudo usermod -a -G plugdev dump1090 

sudo systemctl stop rbfeeder

sudo systemctl restart dump1090-mutability 

To set your latitude and longitude, give following command. Accept all other default settings by pressing Enter key.

When asked "address to bind", remove default value "127.0.0.1" to make it blank, then press Enter key.
Code: [Select]
sudo dpkg-reconfigure dump1090-mutability 


Step-2: Reconfigure rbfeeder to deactivate its integral dump1090
Code: [Select]
sudo nano /etc/rbfeeder.ini 

under [network], modify line:
network_mode=false
To
network_mode=true

Save (Ctrl+O) and close (Ctrl+x) the file.

restart rbfeeder
Code: [Select]
sudo systemctl restart rbfeeder 


Step-3: Reconfigure fr24feed to get data from dump1090-mutability
Code: [Select]
sudo nano /etc/fr24feed.ini   
Change line:
host="127.0.0.1:32457"
To
host="127.0.0.1:30005"

Save (Ctrl+O) and close (Ctrl+x) the file.

Restart fr24feed
Code: [Select]
sudo systemctl restart fr24feed   

« Last Edit: November 19, 2020, 06:28:52 PM by abcd567 »

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #6 on: November 19, 2020, 03:41:19 PM »

Now I am looking to expand my horizons a little bit I seem to be hitting a brick wall with regard to using the OpenADSB app on my own phone to connect to my own data on my own device on my own network.

OpenADSB can use unfiltered data from ADSBExchange which should be good for military and other types of aircraft and it also has the option to connect to your local dump1090 to display your own contacts as this has always been my primary interest but here is where my problem begins.

Looking at the Pi it is not showing dump1090 as being installed so I am unable to determine what port I need to connect to it.


You can not modify ports on RB feeder to match openADSB, as port numbers in RB feeder are hard coded. However you may be able to change settings of openADSB to match rbfeeder's ports, just as you have done in case of FR24 feeder.

Check settings of openADSB App to find what port number it is configured to by default. If that port number is 30005, it means it is set to receive Beast data from port 30005 of any standard dump1090.

If above is true, then in settings of openADSB app, change that port number from 30005 to 32457, as rbfeeder uses this port for Beast output instead of standard 30005
« Last Edit: November 19, 2020, 04:01:13 PM by abcd567 »

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #7 on: November 20, 2020, 08:29:16 AM »
Easy solution to have standard ports matching other software like OpenADSB and AdsbX :

Easy for you to say! :)

I'm definitely going to give that a go but if I could just check a few things please before I take the plunge;

I notice that after installing dump1090-mutability I issue the command to stop rbfeeder. Do I have to stop FR24 as well?

After configuring dump1090 and altering the configs for both rbfeeder and fr24feed will everything start up automatically after a reboot as it does at the moment?

Does dump1090 add itself to the repository source list so the usual sudo apt update / sudo apt full-upgrade will look in the correct place for future updates much like rbfeeder and fr24feed does?

Does this install any of the maps etc. that I see referred to? I don’t particularly want any bloatware etc. installed but curious whether anything else gets installed this way?

And finally will I still be able to feed the RadarBox Legacy program from port 32088?

Thanks once again for your full & detailed explanation and sharing your knowledge.

Kind regards,
-=Glyn=-
« Last Edit: November 20, 2020, 11:29:00 AM by GlynH »

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #8 on: November 20, 2020, 08:39:24 AM »
OpenADSB does not have a default port and can be set for any port number required as I understand it.

However reading the app synopsis it suggests port 80 which leads me to believe it is looking for a standard http port such as one that would drive a webpage or something?

I have already tried inputting every port number I can think of to no avail which suggests it does not understand Beast, RAW, Basestation or the usual datatype associated with feeders.

All moot now as I intend to follow the instructions in your previous post to install a standard dump1090 as every other feeder of this type offers.

Even now after all this time why do AirNav still insist on doing things differently from the standard approach which can make things difficult for the end user when looking to integrate with other applications?

What purpose does it serve in this day & age...<sigh>

Thanks & kind regards,
-=Glyn=-

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #9 on: November 20, 2020, 03:18:24 PM »
I have absolutely no idea about app openADSB.

Where the app "openADSB'" will be installed, on RPi or another machine (desktop/laptop/phone)?

The dump1090-mutability installation automatically installs a web server (lighttpd). The dump1090-mutability serves a map through this web server, and this map can be viewd on any computer/phone on the same local network in a web browser at following address:

IP-of-Pi/dump1090/gmap.html

From what you mentioned about openADSB app using port 80,I suspect that if both dump1090-mutability and openADSB are installed on same machine (i.e. RPi), it may result in a conflict.

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #10 on: November 20, 2020, 06:23:23 PM »
Thanks for the reply as always abcd,

OpenADSB is a paid iOS app that I have installed on both my iPhone & iPad.

http://openadsbapp.com/

I would think that's exactly how it works by connecting to the Pi over port 80 (or 8080 maybe) and takes its data from there so no conflict should be present as it will only be reading data from that port.

Thanks & kind regards,
-=Glyn=-

« Last Edit: November 20, 2020, 06:41:40 PM by GlynH »

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #11 on: November 20, 2020, 10:42:29 PM »

OpenADSB is a paid iOS app that I have installed on both my iPhone & iPad.

Great. Definitely there will be no conflict as dump1090-mutability and openADSB are installed on different machines.



http://openadsbapp.com/

I would think that's exactly how it works by connecting to the Pi over port 80 (or 8080 maybe) and takes its data from there so no conflict should be present as it will only be reading data from that port.

You have misunderstood it. Port 80 or 8080 is the port on your iPhone/iPad on which the openADSB will serve its table/map. It has absolutely nothing to do with RPi's port 80 or 8080.

As far as fetching data from RPi is concerned, the openADSB app on your iPhone/iPad can do it by pulling any one of the following data streams fron RPi:

- Beast format data from RPi's port 30005
- Basestation format data from RPi's port 30003
- json format data by pulling files fro RPi's data folder which stores these files.
- html map file directly from RPi into iPhone/iPsd's browser at following address:
IP-OF-PI/dump1090/
IP-OF-PI/dump1090-fa/

I am not aware what format data openADSB app pulls from RPi's dump1090 (mutab or mr or fa). Anyway it is not important for user, as this should be preconfigured in openADSB. The user will have to add only IP address of the Pi in the openADSB settings.



« Last Edit: November 20, 2020, 10:50:06 PM by abcd567 »

abcd567

  • Sr. Member
  • ****
  • Posts: 373
  • CYYZ - Toronto
Re: rbfeeder non-standard dump1090?
« Reply #12 on: November 21, 2020, 11:21:34 PM »
I notice that after installing dump1090-mutability I issue the command to stop rbfeeder. Do I have to stop FR24 as well?

No, you dont have to stop fr24feed.
The rbfeeder was using the Dongle, and dump1090-mutability after installation has failed as it did not find any free Dongle. The rbfeeder was stopped manually to free the Dongle, and after that the dump1090-mutability was restarted. Now there was a free Dongle available, and dump1090-mutability grabbed it and started working normally.

In the next step, rbfeeder's network_mode was changed from false to true, and after that rbfeeder was restarted. With changed setting, the rbfeeder wont look for Dongle (which is no more available, as it is being used by dump1090-mutability). It would connect to port 30005 to grab data from dump1090-mutability, and start working flawlessly.


After configuring dump1090 and altering the configs for both rbfeeder and fr24feed will everything start up automatically after a reboot as it does at the moment?

YES, sure.


Does dump1090 add itself to the repository source list so the usual sudo apt update / sudo apt full-upgrade will look in the correct place for future updates much like rbfeeder and fr24feed does?

YES, sure.
In fact the debian.org/raspberrypi.org have added the dump1090-mutability to Debian/Raspbian repository list when they released Debian/Raspbian Buster.


Does this install any of the maps etc. that I see referred to? I don’t particularly want any bloatware etc. installed but curious whether anything else gets installed this way?

The dump1090-mutability package comes with integral map, and the map is served by web server lighttpd. The lighttpd is installed automatically when dump1090-mutability is installed.


And finally will I still be able to feed the RadarBox Legacy program from port 32088?

YES, sure.




.
« Last Edit: November 21, 2020, 11:28:51 PM by abcd567 »

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #13 on: November 23, 2020, 03:35:46 PM »
I'm not sure that's the case though is it?

OpenADSB specifically asks for a port number to connect to in order to display aircraft on its map so I assume it polls /data/aircraft.json? Not sure if this is presented when installing rbfeeder to begin with?

The page in the app settings asks for a port number - see photo attached.

Here is what the author states;

----------snip----------
For your first question, yes OpenADSB can connect directly to your dump1090 server. Go to Settings (gear ⚙️ button) - Track Source - Edit - "+" to add a new source. You enter the host, port (if not port 80) and press Test Connection. To quickly switch trace sources, long-press the gear ⚙️ button.
----------snip----------

That's all well and good if you actually have dump1090 running but it looks to me like AirNav do something with dump1090 that is non-standard and ties you in preventing easy expansion outside the walled garden.

I've tried all of the ports that might be associated with radarbox/dump1090/fr24 including the two you give above 30003 & 30005 to no avail. OpenADSB will just not connect.

If I type dump1090 on the Pi it returns;

[email protected]:~ $ dump1090
-bash: dump1090: command not found

In fact it does not even show up in the list of running processes and just look at that CPU utilization of rbfeeder at 61.1% although in fairness through the web interface it usually sits @20%;

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  464 root      20   0  158576  16144   5612 S  61.1   0.4   2663:53 rbfeeder
  607 root      20   0   17776  11044   5652 S   7.6   0.3 177:40.76 mlat-client
  529 fr24      20   0  160708  15120   5716 S   7.3   0.4 270:51.49 fr24feed
  348 avahi     20   0    6408   3384   2556 S   0.3   0.1  17:17.16 avahi-daemon
  964 pi        20   0  160924  40712  22996 S   0.3   1.1  16:40.68 lxpanel
27577 pi        20   0   10408   3052   2532 R   0.3   0.1   0:00.08 top
    1 root      20   0   33740   8168   6492 S   0.0   0.2   0:08.09 systemd
    2 root      20   0       0      0      0 S   0.0   0.0   0:00.16 kthreadd
    3 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_gp
    4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_par_gp
    8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 mm_percpu_wq
    9 root      20   0       0      0      0 S   0.0   0.0   0:13.18 ksoftirqd/0
   10 root      20   0       0      0      0 I   0.0   0.0   5:05.91 rcu_sched
   11 root      rt   0       0      0      0 S   0.0   0.0   0:00.07 migration/0
   12 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/0
   13 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/1
   14 root      rt   0       0      0      0 S   0.0   0.0   0:00.06 migration/1
   15 root      20   0       0      0      0 S   0.0   0.0   0:05.38 ksoftirqd/1
   18 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/2
   19 root      rt   0       0      0      0 S   0.0   0.0   0:00.06 migration/2
   20 root      20   0       0      0      0 S   0.0   0.0   0:05.51 ksoftirqd/2
   23 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/3
   24 root      rt   0       0      0      0 S   0.0   0.0   0:00.06 migration/3
 
Even its time display looks to be the odd one out...<sigh>

Had I known then what I know now I would have followed one of your different tutorials and installed dump1090 and then took the decision whether or not to add rbfeeder to it rather than start off with rbfeeder and then end up banging my head on the wall in a futile attempt to use my data from my computer across my network in another application of my choice.

And although I believe it can be done I received this from PlaneFinder when I enquired about sharing my data with them;

----------snip----------
The points that you raise are very interesting - especially in relation to the non-standard AirNav software.
We would obvioulsy (sic) normally very much appreciate any data that you could share with us.
Unfortunately however we cannot accept your data using the current configuration.
The reason for this as that we have chose to only use standards based (or at least proven) software to be sure of data integrity.
----------snip----------

And in a second email when I pushed further and offered some suggestions as to how we might get things to work;

----------snip----------
The problem for us is that we only support the standalone version of dump1090 as this is a known entity to us.
----------snip----------

Plan B coming up methinks...

-=Glyn=-

GlynH

  • Hero Member
  • *****
  • Posts: 589
Re: rbfeeder non-standard dump1090?
« Reply #14 on: November 23, 2020, 03:41:31 PM »
Fantastic explanation abcd! Thanks very much for that...just what I needed.

You really are the fount of all knowledge when it comes to everything Pi.

Now I have options that I understand! Wish me luck...I'm going in!:)


On a semi-related issue I notice my Max range has dropped from 296->267Nm and with it my ranking has slipped down a few places.

With a properly installed & working dump1090 another advantage might be getting to play around to see what influence Gain might have on Max Range if any.

But that will be for another day (if at all) as I have already achieved my ultimate goal of a stand-alone, networked, reliable Virtual Radar so wouldn't ever want to compromise that.

Thanks again & kind regards,
-=Glyn=-