FlightAware Discussions

Piaware 3.7.2 New Flash and Ethernet/Wifi

Long story short; previously covered in another thread. Data to FA dropped out but my location was pinged successfully. Logs refreshed and updated. Individual flights tracked. No skyview. Skyview had worked fine. I installed a new flash and could not get my stats page to update. Three in the red. I tried ethernet but no luck. I have a wifi range extender which I believe may be a problem as my rasp pi easily appears in router administration in both static and dhcp, wired or wireless with (when in range of the central access point, not through relay) and without the wireless extender. Like others, I can’t speak Debian yet.

tnx

vb77

Please contact adsbsupport@flightaware.com for assistance.

Hello. Thanks for the help! I have my node up and running (claimed a new one with a new flash) and successfully merged my stats. I’m still not seeing skyview, so I have to see what I can find in the knowledge bank.

If you know the IP address of the device, it should be easy to access via the webbrowser.

You can check if you router has features like Wireless Isolation or a guest network.
That can prevent you from accessing the webinterface.

Got it! Easy-peasey. Is there a port issue when http://192.168.[static].[ip]:8080 is requested directly and doesn’t respond or times out? Cache is cleared regularly.

Tnx

Most likely it’s an issue with your local network setup, not allowing you access to other devices on the network.
I’ve outlined the possible reasons (guest WiFi network, Wireless Isolation).

You can always try pinging the IP if you think it’s an issue with the webserver (unlikely).

I moved a few days ago and now have two additional WiFi Repeater as Mesh network enabled.
My Raspi is connected to one of them.
Sometimes i fail connecting to it using local IP adress, but the tracker runs fine and delivers data all the time.

Once i access the device via PortForwarding on my router it works without issues
After some minutes later, i can also access it via local network again.

Maybe your device is running in the same situation.

piaware_node_ping_231120191531

pi’s static port pings.

Maybe that’s not really the IP address of the RPi but the range extender?

https://superuser.com/questions/586901/does-a-wi-fi-range-extender-create-a-separate-network

Seems range extenders do stupid stuff and create problems.
If you can use the WiFi created by the range extender, then you might have better luck accessing the RPi?

1 Like

“Once i access the device via PortForwarding on my router it works without issues
After some minutes later, i can also access it via local network again.”

My router admin shows the device working. I think it may be a port issue here. My node’s static ip request times out. weidehopf has the solution for my particular problem. I do not know why my skymap url times out when I use the direct map url.

[wiedehopf]

If you know the IP address of the device, it should be easy to access via the webbrowser

I know. My extender was easily identifiable. It is offline. No prob. :slight_smile:

If :8080 is a problem just use /dump1090-fa instead.

Right. Will do. It’s a little more difficult do know that particular work-around if you are expecting plug-and-play (say, deployment issues). :slightly_smiling_face:

Most problems are due to home networks doing non-standard stuff, disallowing interconnectivity between devices.

If port 8080 is really the issue, i don’t even want to know if it’s you local firewall or something else is doing really stupid things.

You can’t expect plug and play if your home network is screwed up, that’s beyond anyones control.

1 Like

For the router that is used as “WiFi extender”, is better to get it connected via Ethernet to the main WiFi router.
Plug the incoming cable not in the WAN port but in one of the LAN ports - and disable it’s internal DHCP. It will gen an IP address from the first router and then can be accessed there.

Routers that use instead the (same) WiFi channel for “extender” function, will be suffering from congestion, especially in a 2.4GHz band and with lots of networks around you.

Even without an extender, my MAC address as reported by flightaware differs from the device when pinged from my router. My command-line ping (Windows) returns a different ip than what my piaware configuration file uses as a static ip (192.168.0.22 - command line ping returns 192.168.0.24 with “destination host unavailable,” 4-sent 4-received, 0% loss.

Interestingly, my PuTTy install is no longer working after having been fine.

vb77

Also, what is the easiest confirmation of the correct wireless nameserver in the piaware configuration text?

Thanks.

In an Airspy thread you offered:

sudo sed -i <<* ‘s/LAT/PIAWARE_LAT/;s/LON/PIAWARE_LON/’ /usr/share/skyview978/start-skyview978

sudo systemctl restart skyview978

… in order to re-acquire skyview. I don’t use the 978, but is there a similar proof for 1090? Sorry, still a little confused. My node static port is assigned outside the dchp range but, skyview only works after a device reboot. Working piece by piece and (almost) line by line, I’ve narrowed my ocassional loss of piaware sky view to either my rasp or my router. Everything else on the router wifi works fine. I think recent diagoses are:

journalctl -eu dump1090-fa

Jan 08 13:05:07 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware
Jan 08 13:05:07 piaware dump1090-fa[462]: Wed Jan 8 13:05:07 2020 UTC dump1090
Jan 08 13:05:07 piaware dump1090-fa[462]: rtlsdr: using device #0: Generic RTL28
Jan 08 13:05:07 piaware dump1090-fa[462]: Detached kernel driver
Jan 08 13:05:07 piaware dump1090-fa[462]: Found Rafael Micro R820T tuner
Jan 08 13:05:08 piaware dump1090-fa[462]: rtlsdr: enabling tuner AGC

/journalctl -eu piaware

Jan 08 13:15:42 piaware piaware[472]: 2755 msgs recv’d from dump1090-fa (1302 in last 5m); 2171 msgs sent to FlightAware
Jan 08 13:20:42 piaware piaware[472]: 4093 msgs recv’d from dump1090-fa (1338 in last 5m); 3509 msgs sent to FlightAware
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Receiver status: connected
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Server status: synchronized with 462 nearby receivers
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Receiver: 394.2 msg/s received 144.7 msg/s processed (37%)
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.7kB/s UDP to server
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Results: 1.6 positions/minute
Jan 08 13:22:18 piaware piaware[472]: mlat-client(1294): Aircraft: 10 of 11 Mode S, 43 of 49 ADS-B used
Jan 08 13:25:42 piaware piaware[472]: 5139 msgs recv’d from dump1090-fa (1046 in last 5m); 4555 msgs sent to FlightAware
Jan 08 13:30:42 piaware piaware[472]: 6197 msgs recv’d from dump1090-fa (1058 in last 5m); 5613 msgs sent to FlightAware
Jan 08 13:35:42 piaware piaware[472]: 7463 msgs recv’d from dump1090-fa (1266 in last 5m); 6879 msgs sent to FlightAware
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Receiver status: connected
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Server status: synchronized with 370 nearby receivers
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Receiver: 379.1 msg/s received 136.5 msg/s processed (36%)
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.6kB/s UDP to server
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Results: 0.3 positions/minute
Jan 08 13:37:18 piaware piaware[472]: mlat-client(1294): Aircraft: 8 of 9 Mode S, 46 of 55 ADS-B used
Jan 08 13:40:42 piaware piaware[472]: 8664 msgs recv’d from dump1090-fa (1201 in last 5m); 8080 msgs sent to FlightAware
Jan 08 13:45:42 piaware piaware[472]: 9747 msgs recv’d from dump1090-fa (1083 in last 5m); 9163 msgs sent to FlightAware
Jan 08 13:50:42 piaware piaware[472]: 10621 msgs recv’d from dump1090-fa (874 in last 5m); 10037 msgs sent to FlightAware
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Receiver status: connected
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Server status: synchronized with 407 nearby receivers
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Receiver: 269.4 msg/s received 99.8 msg/s processed (37%)
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.2kB/s UDP to server
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Results: 0.1 positions/minute
Jan 08 13:52:18 piaware piaware[472]: mlat-client(1294): Aircraft: 6 of 9 Mode S, 34 of 38 ADS-B used
Jan 08 13:55:42 piaware piaware[472]: 11554 msgs recv’d from dump1090-fa (933 in last 5m); 10970 msgs sent to FlightAware

These reports are when I can see skyview on my local network.

I would much rather you used DHCP …

Anyhow please post the output for this

sudo piaware-config

Also check this how to for proper formatting here on the forum:
https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#posting-logs-on-the-flightaware-forum