FA feeder works locally only, no feed to FA


#1

Hello Everyone,

here is a list of main points:

  1. I received a free feeder from FA. :smiley:
  2. It worked for a week then the Ethernet port went down.
  3. I replaced the original Raspberry Pi card with a new one, soldering done by a professional. (RP pi Model B)
  4. The new one worked fine and I can access the unit locally via ip_address:8080 and I can see the planes. So dump1090 seems to work just fine. I tried re-register the unit again.
  5. The main issue is that my feeder does not upload any records to FA website and there is no stats for my account “ncascis”
  6. Note: my router assigned IP address by DHCP and I can see it just fine in my DHCP table.

I am just wondering what could prevent my unit from uploading what it sees locally to FA website?

Note:I enabled SSH but cannot access it so far through SSH. I am running version 5.5

Thanks in advance


PiAware - build your own ADS-B receiver
#2

What’s the serial #?


#3

#1120


#4

If you can view the planes locally on port 8080 but the box doesn’t connect to flightaware usually means that the secured ports are blocked.
Here is the complete list of ports and how they should be configured.


FlightFeeders need to be able to make outbound connections to the Internet on TCP ports 53, 80, 443, 2222 and 7912 and to be able to send traffic on UDP port 53 for DNS.

FlightFeeders do not need a global IP address (they can be behind a NAT-translating router) nor do they need any firewall changes to allow inbound connections from the global Internet, although users on the local network can direct a web browser to port 8080 on the FlightFeeder.

The TCP ports are 53 for DNS, 80 for http (for downloading software updates), 443 for https, 2222 for SSL-encrypted connection and 7912 for TLS-encrypted connection.



#5

[quote=“david.baker”]If you can view the planes locally on port 8080 but the box doesn’t connect to flightaware usually means that the secured ports are blocked.
Here is the complete list of ports and how they should be configured.


FlightFeeders need to be able to make outbound connections to the Internet on TCP ports 53, 80, 443, 2222 and 7912 and to be able to send traffic on UDP port 53 for DNS.

FlightFeeders do not need a global IP address (they can be behind a NAT-translating router) nor do they need any firewall changes to allow inbound connections from the global Internet, although users on the local network can direct a web browser to port 8080 on the FlightFeeder.

The TCP ports are 53 for DNS, 80 for http (for downloading software updates), 443 for https, 2222 for SSL-encrypted connection and 7912 for TLS-encrypted connection.


[/quote]

Right on the problem. It seems that my iptables firewall is wrong. Can you please or anyone with a working feeder post a typical iptables rules.


#6

Just wondering if this is ok,

Every time I issue the command

sudo iptables-save

I get different rules!!!