V3.81 new user failed to claim feed

FlightAware ADS-B Flight Tracking
1

Hi there,

I have followed instructions here (PiAware - dump1090 ADS-B integration with FlightAware - FlightAware) and installed dump1090, piaware on an existing Pi Zero W.

Since I have something else listening on http port 80, I updated /etc/lighttpd/lighttpd.conf and changed the port from 80 to 8888, and then I restarted PI.

Now I’ve waited more than a few minutes but still fail to claim my feed. Besides, I can not open page on port 8888, but I CAN open page on 8080 showing Piaware Skyaware maps etc.

Please see below information I’ve obtained for troubleshooting purposes. Can you please help? Much appreciated.

pi-star@pi-star(rw):html$ sudo piaware-status
PiAware master process (piaware) is running with pid 773.
PiAware ADS-B client (faup1090) is running with pid 1074.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 769.

dump1090-fa (pid 769) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

You dont have a feeder ID yet.
pi-star@pi-star(rw):html$

pi-star@pi-star(rw):html$ tail -f /var/log/piaware.log
Apr  8 20:55:41 pi-star piaware[773]: reconnecting in 6 seconds...
Apr  8 20:55:47 pi-star piaware[773]: Connecting to FlightAware adept server at 70.42.6.156/1200
Apr  8 20:56:02 pi-star piaware[773]: Connection attempt with adept server at 70.42.6.156/1200 timed out
Apr  8 20:56:02 pi-star piaware[773]: reconnecting in 53 seconds...
Apr  8 20:56:55 pi-star piaware[773]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Apr  8 20:57:10 pi-star piaware[773]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Apr  8 20:57:10 pi-star piaware[773]: reconnecting in 4 seconds...
Apr  8 20:57:14 pi-star piaware[773]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Apr  8 20:57:29 pi-star piaware[773]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Apr  8 20:57:29 pi-star piaware[773]: reconnecting in 6 seconds...
Apr  8 20:57:32 pi-star piaware[773]: 23 msgs recvd from dump1090-fa (4 in last 5m); 0 msgs sent to FlightAware
Apr  8 20:57:35 pi-star piaware[773]: Connecting to FlightAware adept server at 70.42.6.191/1200
^C
pi-star@pi-star(rw):html$
pi-star@pi-star(rw):html$ sudo ping 70.42.6.224
PING 70.42.6.224 (70.42.6.224) 56(84) bytes of data.
64 bytes from 70.42.6.224: icmp_seq=1 ttl=48 time=46.2 ms
64 bytes from 70.42.6.224: icmp_seq=2 ttl=48 time=60.9 ms
64 bytes from 70.42.6.224: icmp_seq=3 ttl=48 time=50.6 ms
64 bytes from 70.42.6.224: icmp_seq=4 ttl=48 time=87.2 ms
^C
--- 70.42.6.224 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 46.169/61.208/87.174/15.913 ms
2

You have a network problem; piaware can’t connect to the FlightAware servers.
Given that you can ping the server, this sounds like a firewall problem on your side.

(the port 8888 issue may be related)

3

:8888/dump1090-fa

you tried this?

4

So I’ve solved the problem. It was a firewall problem on the PI.
I was not aware that iptables was enabled and its outgoing rules did not allow connection on port 1200.

I diagnosed the issue by using tcpdump to catch all packets to port 1200 and discovered it did not even see the first TCP handshake packet. That made me suspect the packet was dropped at the first place.

After I cleaned the iptables rules, everything back to normal, I was able to claim my new feed.

Many thanks @obj

5

After I cleaned up iptables rules, I was able to open page on port 8888 :slight_smile:

6

Can you explain how to cleaned up iptables? I have the same issue.

Thanx before

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.