Thanks for the help - it’s running perfectly now, but without your help I would have given up feeding FlightAware.
1 Like
Glad to know your install is working now.
Just curious to know weather you used option-1 or option-2. Although both options solve the problem, they have different strategies.
In Pi24 image, the dump1090-mutability is configured to be controlled by fr24feed, and only fr24feed can get its feed directly, but data availability on network at its ports 30002, 30003, 30005 are blocked. Hence other sites feeding software say dump1090 is not running, although it is running.
In option-1, a line procargs=" --net " is added. This open the dump1090-mutability’s data ports on network, and other sites feeder start getting data from dump1090-mutabity.
In option-2, the lines added (receiver=avr-tcp and host=127.0.0.1:30002), pull out dump1090-mutability from control of fr24feed, and blockage of its ports 30002, 30003, and 30005 is removed. Other sites feeder softwsre now start getting data from it.
There was one more restriction put on dump1090-mutability by fr24feed. It was blocked from starting automatically at boot. It was started by fr24feed when it started. To remove this restriction, in file /etc/default/dump1090-mutability , the setting START_DUMP1090=no was changed from no to yes.
I first tried Option 1, then I decided to try Option 2, and this is my fr24feed.ini file to day:
Per
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.