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.
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.
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.
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.
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?
â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
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.
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