AirNav Systems Forum

AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: Av8tor_from_Argentina on August 07, 2022, 11:09:44 PM

Title: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 07, 2022, 11:09:44 PM
Good morning. I had an issue since my last reboot/reinstall of all flight trackers software installed in my Rpi.

I have working and feeding Flightradar24, Flightaware and Planefinder. All of them work perfectly, the only one who refuses to work is RadarBox24

Suddenly a week ago, I´ve received an email stating that My account is back online again.. CHecked and was true.. ONLY FOR 3 days.. today my RadarBox24 is down... and is really annoying because it wasn´t working, and as started to work by herself, stopped by herself...

Anyone knows or "suffered" the same glitch, ghost, whatever you name it ??

Regards from Argentina
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 08, 2022, 12:18:38 PM
I cannot copy/paste because forum system rejected due to spam suspect...

attached is the systemctl status rbfeeder output

Maybe someone knows whats going on... I have 3 other providers working perfectly.

Regards

Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 08, 2022, 10:34:14 PM
please run following command and post its output.
(replace key by xxxxxxxxxxx when posting)

sudo cat /etc/rbfeeder.ini   

Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 09, 2022, 01:22:34 PM
Good morning. Here you have...

Marco@raspberry:~ $ sudo cat /etc/rbfeeder.ini
[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=xxxxxxxxxxx

sn=EXTRPI027210

lat=-3x.xxxxx

lon=-5x.xxxxx

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=false



Thanks
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 09, 2022, 09:21:38 PM
Your rbfeeder config settings are OK..
Maybe some other files of rbfeeder got broken/corrupted during install. Try purging current install, then update, then make a fresh install

Code: [Select]
sudo apt purge rbfeeder   

sudo apt update 

sudo apt install rbfeeder   



.
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 10, 2022, 11:14:50 PM
Thanks ABCD567, here you have the output from the installation...

It is attached because spam issue with the forum soft...

Something is not right at the end of the file...

Regards,

Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 11, 2022, 03:05:16 AM

(1) Which model your Pi is?
(2) Which OS image did you write to microSD card?

.
Code: [Select]
Preparing to unpack .../rbfeeder_1%3a1.0.8+deb11_armhf.deb ...
Unpacking rbfeeder (1:1.0.8+deb11) ...
Setting up rbfeeder (1:1.0.8+deb11) ...
Checking if service is running and restart, if needed...
Failed to restart rbfeeder.service: Unit rbfeeder.service failed to load properly: Device or resource busy.
See system logs and 'systemctl status rbfeeder.service' for details.
dpkg: error processing package rbfeeder (--configure):
 installed rbfeeder package post-installation script subprocess returned error exit status 1




Seems the package rbfeeder is broken

Try this


Code: [Select]
sudo apt --fix-broken install   

sudo reboot   


If above fails to fix the issue, try this command

Code: [Select]
sudo dpkg --configure -a   


.

Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 16, 2022, 07:25:04 PM
Model Raspberry Pi 3b+
OS : "Raspbian GNU/Linux 11 (bullseye)"


None of the procedures above could fix the issue. I have a doubt. When I execute sudo apt install rbfeeder    rbfeeder dont ask for initial parameters. Is there any way to ERASE DELETE VAPORIZE all RBFEEDER and make a clean installation ??

Regards
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 17, 2022, 12:02:47 AM
Just a simple question. I´ve realized that station key and Station name weren´t asociated, so I´ve edited the Station Name in the rbfeeder.ini file, to match it with the original station key.

Maybe there is another way to do that.

Waiting for answers...

Regards
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 17, 2022, 08:22:49 AM
OK Try this

(1) Give following commands
Code: [Select]
sudo systemctl stop rbfeeder 

sudo dpkg --purge rbfeeder   

sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"   

# NOTE: In command below, replace xxxxxxxxxxxxxxxxxx by your actual key

sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



(2) Press Ctrl+C to break-out


(3) Stop then restart rbfeeder
Code: [Select]
sudo systemctl stop rbfeeder 

sudo systemctl restart rbfeeder   



(4) Check status
Code: [Select]
sudo systemctl status rbfeeder   


If above fails, then locate the rbfeeder package by following command

Code: [Select]

sudo find / -name rbfeeder*.deb     

The above command will output location of rbfeeder package.  In my Pi it shows like this:
                       /var/cache/apt/archives/rbfeeder_1%3a1.0.8+deb11_armhf.deb

Please post output. This package will need to be deleted, then installation script run

Code: [Select]
sudo rm /var/cache/apt/archives/rbfeeder_1%3a1.0.8+deb11_armhf.deb   

sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"   
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 18, 2022, 11:34:26 AM
Just getting tired... 3 PROVIDERS WORKS PERFECT...

Attached info, because system keeps telling spam... don´t know how you guys copy/paste code/text in this forum and not getting that message...

How could you put those codes lines in green background ?

Regards
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 18, 2022, 04:45:43 PM
Just getting tired... 3 PROVIDERS WORKS PERFECT...

Attached info, because system keeps telling spam... don´t know how you guys copy/paste code/text in this forum and not getting that message...

How could you put those codes lines in green background ?

Regards

Code: [Select]
Marco@raspberry:~ $ sudo find / -name rbfeeder*.deb

/var/cache/apt/archives/rbfeeder_1%3a1.0.7_armhf.deb
/var/cache/apt/archives/rbfeeder_1%3a1.0.8+deb11_armhf.deb
find: ‘/run/user/1000/gvfs’: Permission denied

Oh, I think I found the culprit.
The first two lines of output show that you have two versions of rbfeeder (1.0.7 & 1.0.8) saved in apt cache. Either one or both versions are corrupt, OR presence of two versions is causing conflict.

Let us get rid of all old stuff first
Code: [Select]
sudo systemctl stop rbfeeder 

sudo apt purge rbfeeder   

sudo rm /var/cache/apt/archives/rbfeeder_1%3a1.0.7_armhf.deb 

sudo rm /var/cache/apt/archives/rbfeeder_1%3a1.0.8+deb11_armhf.deb 

sudo reboot 


After reboot, check that both versions are removed from apt cache by following command. If both are removed, the output of this command wont show them

Code: [Select]
sudo find / -name rbfeeder*.deb     


If apt cache is clear of rbfeeder, run the installation script

Code: [Select]
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"   

## NOTE: In command below, replace xxxxxxxxxxxxxxxxxx by your actual key
sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

## Output will show your key has been accepted
## Press Ctrl & C keys to break out

sudo systemctl restart rbfeeder   



Now check status 
Code: [Select]
sudo systemctl status rbfeeder   



.


Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 19, 2022, 02:57:22 PM
Good morning, after executind the command given below.....

Code: [Select]
sudo find / -name rbfeeder*.deb     


this is the output...

ATTACHED FILE because for some unknown reason to me system keeps telling CleanTalk: *** Forbidden. Please enable JavaScript. Contains contacts. *** enable javascript in 3 different browsers, and cannot copy/paste results here...

That message from sudo find / -name rbfeeder*.deb, means that something cannot be deleted?

revvin´up... damn...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 19, 2022, 04:00:50 PM

Code: [Select]
Marco@raspberry:~ $ sudo find / -name rbfeeder*.deb
find: ‘/run/user/1000/gvfs’: Permission denied


Great!
This is exactly the message I wanted to see.
It confirms that both versions of rbfeeder have been removed, as they are no more listed in the output. Never mind the line with "Permossion denied". It is always there.

As the apt cacbe has been cleaned now, go ahead to next step and run the installation script

Code: [Select]
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"   


When above command finishes installation, add your key by following command
(In command below, replace xxxxxxxxxxxxxxxxxx by your actual key)
Code: [Select]
sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Output of above command will show your key has been accepted

Press Ctrl & C keys to break out

Now restart rbfeeder
Code: [Select]
sudo systemctl restart rbfeeder   


Now check status 

Code: [Select]
sudo systemctl status rbfeeder   



Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 19, 2022, 11:41:44 PM
Will give up with this RADAR****BOX setup... unbelievable....

attached results from status command...

there are a couple of "failed to rename..."

What is annoying is that the other 3 feeders work like a charm...

Regards,
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 20, 2022, 01:24:22 AM
@Av8tor_from_Argentina:
Please REBOOT your Pi then check again


Please also see this thread
https://forum.radarbox24.com/index.php?topic=106461
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 20, 2022, 03:08:00 PM
Something is not right here,


[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=xxxxxxxx

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


As you can see there is no REFERENCE to Station Name or even LAT/LONG data...

Is there any way of reset and execute the setup in a way of ENTER all data again?, because everytime that I´ve executed the installer, never asked for position, altitude and email... And clearly remember that setup asked for that kind of information.

...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 20, 2022, 04:23:39 PM
Something is not right here,


[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=xxxxxxxx

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


As you can see there is no REFERENCE to Station Name or even LAT/LONG data...

Is there any way of reset and execute the setup in a way of ENTER all data again?, because everytime that I´ve executed the installer, never asked for position, altitude and email... And clearly remember that setup asked for that kind of information.

...

(1) Did you REBOOT your Pi? If yes, then did following error messsge disappear from status output?

Code: [Select]
failed to rename /dev/shm//rbfeeder_receiver.json.2coDHx to /dev/shm//rbfeeder_receiver.json: Operation >


(2) Did you add your key by following command or was it there automatically?
Code: [Select]
sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

(3) Once you have the key, and enter it by above command, the setup wont ask for email. It asks for email only when you dont enter a key and go to claims page to claim a new station.

(4) Location data (latitude, longitude, and altitude above sea level in meters) can be entered manually by you in the rbfeeder.ini file just above [network], and save the file. See below my file

(5) The station number "sn=EXTRPIxxxxxx" automatically gets entered when your key is accepted. You dont have to enter station number yourself. Are you sure the key you are using is correct and complete? Count that all 32 characters are there, no chrecters are left out in copy-pasting.



Quote

pi@raspberrypi:~ $ sudo nano /etc/rbfeeder.ini

[client]
network_mode=true
log_file=/var/log/rbfeeder.log
disable_log=1

key=xxxxxxxxxxxxxxxxxxxxxxx
sn=EXTRPI000008

lat=43.5xxxxx
lon=-79.6xxxxx
alt=1xx

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 20, 2022, 05:55:23 PM
Well seems that, Radarbox universe is against one more time...

Purge, removed, deleted every trace of rbfeeder...

Installed again, stopped, rebooted pi and status again...

Attached file with results


Is there any way to start with a new key? I left it worked for 30 minutes without a key and it has never created a new one. Also requested to radarbox support to check my current key with station name and is OK, KEY match with station....

Want to create a new account but how can I do that ??

I will become a Tibetan Buddhist monk...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 20, 2022, 09:23:01 PM
Well seems that, Radarbox universe is against one more time...

Purge, removed, deleted every trace of rbfeeder...

Installed again, stopped, rebooted pi and status again...

Attached file with results


From your attached file:
Code: [Select]
Aug 20 14:43:19 raspberry rbfeeder[529]: getaddrinfo: Temporary failure in name resolution
Aug 20 14:43:19 raspberry rbfeeder[529]: [2022-08-20 14:43:19]  Can't connect to AirNav Server.

OK I think following will solve the above noted issue of connectivity to AirNav Server:

Code: [Select]
sudo apt update

sudo apt install netbase   

sudo reboot 

After reboot check
(a) rbfeeder's status
(b) file rbfeeder.ini

Hope your multiple-disease iinstall (mutiple versions saved in apt-cache, broken/corrupted rbfeeder package, missing netbase package) will be solved finally.
.
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 21, 2022, 09:29:43 PM
Hello there.... performed AGAIN  STOP, PURGE, reinstall, netbase, restart...
Nothing...
So I will let Radarbox set a new key for me...
this is what rbfeeder.ini looks now...

[client]
network_mode=true
log_file=/var/log/rbfeeder.log

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


Also a search for a key...

Marco@raspberry:~ $ sudo rbfeeder --showkey

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini


Marco@raspberry:~ $ less /var/log/rbfeeder.log
[2022-08-21 18:34:17]  Data sent: 250 B
[2022-08-21 18:34:17]  Data received: 0 B
[2022-08-21 18:35:02]  Connection established.
[2022-08-21 18:35:02]  Empty sharing key. We will try to create a new one for you!
[2022-08-21 18:35:12]  Timeout waiting for new key. Will try again in 30 seconds.
[2022-08-21 18:35:19]  ******** Statistics updated every 60 seconds ********
[2022-08-21 18:35:19]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 11
[2022-08-21 18:35:19]  Data sent: 275 B
[2022-08-21 18:35:19]  Data received: 0 B
[2022-08-21 18:36:13]  Connection established.
[2022-08-21 18:36:13]  Empty sharing key. We will try to create a new one for you!
[2022-08-21 18:36:19]  ******** Statistics updated every 60 seconds ********
[2022-08-21 18:36:19]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 12
[2022-08-21 18:36:19]  Data sent: 300 B
[2022-08-21 18:36:19]  Data received: 0 B
[2022-08-21 18:36:24]  Timeout waiting for new key. Will try again in 30 seconds.
[2022-08-21 18:36:31]  Starting RBFeeder Version 1.0.8 (build 20220708190411)
[2022-08-21 18:36:31]  Using configuration file: /etc/rbfeeder.ini
[2022-08-21 18:36:31]  Network-mode enabled.
[2022-08-21 18:36:31]           Remote host to fetch data: 127.0.0.1
[2022-08-21 18:36:31]           Remote port: 30005
[2022-08-21 18:36:31]           Remote protocol: BEAST
[2022-08-21 18:36:31]  Using GNSS (when available)


Marco@raspberry:~ $ sudo systemctl status rbfeeder
● rbfeeder.service - RBFeeder Service
     Loaded: loaded (/lib/systemd/system/rbfeeder.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-08-21 18:23:07 -03; 15min ago
    Process: 1632 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=1/FAILURE)
    Process: 1633 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/run/rbfeeder (code=exited, status=0/SUCCESS)
    Process: 1634 ExecStartPre=/bin/touch /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 1635 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 1636 ExecStartPre=/bin/chown rbfeeder:rbfeeder /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
    Process: 1637 ExecStartPre=/bin/setfacl -m u:www-data:rwx /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
   Main PID: 1638 (rbfeeder)
      Tasks: 9 (limit: 1597)
        CPU: 4.360s
     CGroup: /system.slice/rbfeeder.service
             └─1638 /usr/bin/rbfeeder

Aug 21 18:37:25 raspberry rbfeeder[1638]: [2022-08-21 18:37:25]  Connection established.
Aug 21 18:37:25 raspberry rbfeeder[1638]: [2022-08-21 18:37:25]  Empty sharing key. We will try to create a new one for you!
Aug 21 18:37:35 raspberry rbfeeder[1638]: [2022-08-21 18:37:35]  Timeout waiting for new key. Will try again in 30 seconds.
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  ******** Statistics updated every 60 seconds ********
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 13
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Data sent: 325 B
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Data received: 0 B
Aug 21 18:38:36 raspberry rbfeeder[1638]: [2022-08-21 18:38:36]  Connection established.


No key, no coordinates, no station name... NOTHING...

That´s why I am asking if it is any command that can perform a setup like the FIRST TIME EVER... The kind of setup that a newby or someone who has never ever installed Radarbox24 software....

It´s a truly dissapointing experience....
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 22, 2022, 01:36:50 AM
@Av8tor_from_Argentina

Your software setup has become ok after purging and deleting old ones and installing new copy. Also after installing package netbase, you should not have any problem in connecting to AirNav Servers.

However as your latest logs show, rbfeeder is unable to obtain key from AirNav Server, and keeps on trying. This shows connection issue.

The possible reasons are Firewall settings in your router or local network. Has your router been recently changed by your internet service provider?

Another reason of failure to connect is to use IPv6 instead of IPv4. I have very little knowledge about Firewalls and IPv6. Better contact your internet service provider and tell them that your Pi is unable to connect to AirNav server through their Router. They may change settings of your router to allow connection.
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Dennis_K on August 22, 2022, 10:57:51 AM
Having a similar issue since yesterday, the connection is working fine for a while but will break eventually.
Log shows the following when the connection breaks:
Code: [Select]
******** Statistics updated every 60 seconds ********
Packets sent in the last 60 seconds: 0, Total packets sent since startup: 2
Data sent: 126 B
Data received: 0 B
Connection established.
Could not start connection. Timeout.

I did some troubleshooting and noticed the following the moment the timeout occurs:
TCP handshake with rpiserver-ng.rb24.com is successful. RBFeeder now sends a small package
Code: [Select]
Internet Protocol Version 4, Src: 172.17.0.5, Dst: rpiserver-ng.rb24.com (23.29.123.254)
Transmission Control Protocol, Src Port: 55528, Dst Port: 33755, Seq: 1, Ack: 1, Len: 2
Source Port: 55528
Destination Port: 33755
[Stream index: 13]
[Conversation completeness: Incomplete, DATA (15)]
[TCP Segment Len: 2]
Sequence Number: 1 (relative sequence number)
Sequence Number (raw): 1368053075
[Next Sequence Number: 3 (relative sequence number)]
Acknowledgment Number: 1 (relative ack number)
Acknowledgment number (raw): 442404819
1000 .... = Header Length: 32 bytes (8)
Flags: 0x018 (PSH, ACK)
Window: 502
[Calculated window size: 64256]
[Window size scaling factor: 128]
Checksum: 0xaa54 [unverified]
[Checksum Status: Unverified]
Urgent Pointer: 0
Options: (12 bytes), No-Operation (NOP), No-Operation (NOP), Timestamps
[Timestamps]
[SEQ/ACK analysis]
TCP payload (2 bytes)
Data (2 bytes)
Data: 7e23
[Length: 2]
and rpiserver-ng.rb24.com is closing the connection (fin+rst).
When the connection is working, rpiserver-ng.rb24.com is responding with ACK to the same package and is  keeping the connection alive.

Hard to tell if Av8tor_from_Argentina is having the exact same issue, but the symptoms are the same
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 22, 2022, 11:05:26 AM
Is there any remote possibility that dump 1090 (mutability or fa) is failing? how can I know which Dump1090 I have installed and running? Which one is recommended? Remember that I have FR24, Flightaware and PlaneFinder working PERFECT...

I would guess that I have Mutability, because I can see a map with Skyaware...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: abcd567 on August 22, 2022, 11:24:41 AM
Is there any remote possibility that dump 1090 (mutability or fa) is failing? how can I know which Dump1090 I have installed and running? Which one is recommended? Remember that I have FR24, Flightaware and PlaneFinder working PERFECT...

I would guess that I have Mutability, because I can see a map with Skyaware...


Output of following command will show which one is installed
Code: [Select]
apt-cache policy dump1090-mutability 

apt-cache policy dump1090-fa 



On my Pi with dump 1090-fa, I get:

pi@raspberrypi:~ $ apt-cache policy dump1090-fa
dump1090-fa:
  Installed: 7.2
  Candidate: 7.2
  Version table:
 *** 7.2 500
        500 https://raw.githubusercontent.com/abcd567a/rpi/master ./ Packages
        100 /var/lib/dpkg/status


pi@raspberrypi:~ $ apt-cache policy dump1090-mutability
dump1090-mutability:
  Installed: (none)
  Candidate: 1.15~20180310.4a16df3+dfsg-8
  Version table:
     1.15~20180310.4a16df3+dfsg-8 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages




Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 22, 2022, 09:13:47 PM
Thanks, I have dump1090-fa.

Will check my repeater (in which raspi is connected) to see if there are a mob of strange gremlins that avoid Radarbox to connect...

From now on, is a matter of personal challenge to connect RB24, cannot understand why is the only flight tracker software that is unable to relay information. And I don´t want to reformat my SD card because FR, FA and PlaneFinder work perfect...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 25, 2022, 10:36:41 PM
There is no firewall problem or port closed... Flightradar, Flightaware and Planefinder work straight with no network or router problems or firewall rules...

I´ve contacted RadarBox support, but would guess that there is no going to be any kind of solution. And the solution will be format and reinstall everything again, which I will not goint to do because I´m not going to reformat and reinstall for just one app...

still open to new ideas...
Title: Re: Radarbox connected for 3 days, then disconnected AGAIN
Post by: Av8tor_from_Argentina on August 25, 2022, 10:39:49 PM
Having a similar issue since yesterday, the connection is working fine for a while but will break eventually.

Hard to tell if Av8tor_from_Argentina is having the exact same issue, but the symptoms are the same

Dennis, good evening. Any news or solution to your problem?

Regards,