Flightaware not receiving data from my feeder using dydns.
I recently added a new feeder on a mountain top, it is on a network using dydns (satellitearc.com). It has never been seen by Flightaware, although I can browse to it and see it processing data. Using the ‘top’ command, I can see dump1090, fa-mlat, fr24feed and faup1090 services running.
Is this normal for a feeder behind a dydns?
John
What does piaware.log say? Probably you have a connectivity problem of some sort which prevents piaware from reaching the FA servers.
pi@W6ABADSB:/var/log $ tail -f piaware.log
May 30 16:28:03 W6ABADSB piaware[433]: 6828311 msgs recv’d from dump1090 (2761 in last 5m); 6794950 msgs sent to FlightAware
May 30 16:33:03 W6ABADSB piaware[433]: 6830897 msgs recv’d from dump1090 (2586 in last 5m); 6797536 msgs sent to FlightAware
May 30 16:38:03 W6ABADSB piaware[433]: 6833482 msgs recv’d from dump1090 (2585 in last 5m); 6800121 msgs sent to FlightAware
May 30 16:43:03 W6ABADSB piaware[433]: 6836395 msgs recv’d from dump1090 (2913 in last 5m); 6803034 msgs sent to FlightAware
May 30 16:48:03 W6ABADSB piaware[433]: 6839106 msgs recv’d from dump1090 (2711 in last 5m); 6805745 msgs sent to FlightAware
May 30 16:53:03 W6ABADSB piaware[433]: 6842109 msgs recv’d from dump1090 (3003 in last 5m); 6808748 msgs sent to FlightAware
May 30 16:58:03 W6ABADSB piaware[433]: 6845913 msgs recv’d from dump1090 (3804 in last 5m); 6812552 msgs sent to FlightAware
May 30 17:03:03 W6ABADSB piaware[433]: 6848308 msgs recv’d from dump1090 (2395 in last 5m); 6814947 msgs sent to FlightAware
May 30 17:08:03 W6ABADSB piaware[433]: 6850741 msgs recv’d from dump1090 (2433 in last 5m); 6817380 msgs sent to FlightAware
May 30 17:13:03 W6ABADSB piaware[433]: 6853284 msgs recv’d from dump1090 (2543 in last 5m); 6819923 msgs sent to FlightAware
May 30 17:18:03 W6ABADSB piaware[433]: 6855839 msgs recv’d from dump1090 (2555 in last 5m); 6822478 msgs sent to FlightAware
pi@W6ABADSB:/var/log $ ping flightaware.com
PING flightaware.com (70.42.6.250) 56(84) bytes of data.
64 bytes from webfarm.flightaware.com (70.42.6.250): icmp_seq=1 ttl=50 time=63.0 ms
64 bytes from webfarm.flightaware.com (70.42.6.250): icmp_seq=2 ttl=50 time=67.8 ms
64 bytes from webfarm.flightaware.com (70.42.6.250): icmp_seq=3 ttl=50 time=64.4 ms
64 bytes from webfarm.flightaware.com (70.42.6.250): icmp_seq=4 ttl=50 time=66.5 ms
64 bytes from webfarm.flightaware.com (70.42.6.250): icmp_seq=5 ttl=50 time=94.9 ms
Well, that says that it’s feeding data just fine… Why do you think it’s never been seen by FlightAware?
It has not appeared as a feeder I can claim. Is it lost in the bowels of FA somewhere?
pi@W6ABADSB:~ $ ifconfig eth0
eth0 Link encap:Ethernet HWaddr b8:27:eb:a1:23:96
How are you trying to claim it?
Usually, when I bring up a new feeder, it appears in the ‘Nearby Sites’ pane. It has not appeared there since it was placed on the mountain top.
How am I to correctly claim it?
The same way you always claim a new feeder: visit flightaware.com/adsb/piaware/claim (from the same network as the new feeder, may be hard in this case) or follow the claim link in the top-level piaware status page on the feeder.
I may have to take a trip to get on the same network as the feeder. Thanks.
The status page claim link works from anywhere, so if you can reach the status page remotely that’ll be fine.
Or given the feeder ID you can manually construct the claim link (it’s just a bit easier if the status page does it for you)
I went here, flightaware.com/adsb/piaware/claim and it could not locate a feeder. But, it said it was checking on IP 147.xxx.xxx.xxx, which is not the IP address of the feeder in question.
Like I said above, that URL only works from the same network. You need to go to the status page on the feeder and follow the claim link there; that link includes the feeder ID.
Not quite sure how to do this. If the feeder is not showing up on FA, where can I find the status page of the feeder?
I mean the status page that is present at ](http://)/ if you are using the piaware sdcard image.