Recent Posts

Please see attached 2 screen shots which show:
(1) Data received from port 30288 of RPi / rbfeeder
(2) Perfectly normal display on ANRB software

LATER ADDITION:
If you are still convinced that rbfeeder is supplyin garbage on port 30288, then it means during installation of rbfeeder, some corruption occured. In this case purge rbfeeder and then install a fresh copy.

IMPORTANT:
Before issuing following commands, open file /etc/rbfeeder.ini and copy key from there, paste key on notepad, and save notepad. You will need this key when a new copy of rbfeeder is installed.

Code: [Select]

sudo apt purge rbfeeder  

sudo apt autoremove  

sudo apt autoclean  

sudo apt update   

sudo apt install rbfeeder   

sudo systemctl restart rbfeeder  

sudo systemctl status rbfeeder

AirNav Radar Discussion / Re: RadarBox ANRB 6.02.003 - no flights shown

« Last post by BicNav on November 17, 2025, 02:49:30 PM »

Screenshot of the remote XRange2 flights shown on my local ANRB

AirNav Radar Discussion / Re: RadarBox ANRB 6.02.003 - no flights shown

« Last post by BicNav on November 17, 2025, 02:41:09 PM »

I have found that the output from RBFeeder on port 32088 is malformed as I originally suspected.

I have a RadarBox Xrange2 running at a remote location which is feeding into the RadarBox Network. I checked using ANRB 6.02.003 installed on a PC at the remote location correctly processed and showed the flights from the XRange2, by using it's LAN IP and port 32088. I was able to forward port 32088 through the remote router internet gateway, and could telnet to port 32088 on the remote network from this location.

I found that the telnet dump from my local RBFeeder running on the local RasPi compared to the XRange2 dump were similar but not quite the same. I do know that the feed from port 32088 is definitely not BEAST format as Alan (@Runway 31) has suggested.

The final confirmation was to point my local ANRB to the remote XRange2 forwarded port - however this didn't work as the IP address associated with the source must be on the same private Class C subnet as the PC the ANRB is hosted on. Clearly a remote address does not qualify. I overcame the issue by using a local Windows port proxy. In that way I could point the ANRB to the local loopback host 127.0.0.1 port 32088 instead of the remote IP. This was the Powershell command:-

netsh interface portproxy add v4tov4 listenport=32088 connectaddress=<remote IP address> connectport=32088 listenaddress=127.0.0.1

So I'm still left with the original issue that the RBFeeder on my local RasPi is ouputting garbage on port 32088.

Pages: 1 ... 4 5 [6] 7 8 ... 10