over Baltic Sea, nothing was logged at all. Click for an interactive map!īetween Poland and Denmark, i.e. Lithuanian and Latvian signals (red) and the corresponding geolocation (blue). Furthermore, the location of each logged signal is based on interpolation of ADS–B data from Flightradar24. They do not correspond to the exact location of a network. The listed distances are just rough information due to nature of Wi-Fi geolocation. W – geolocation, T – tentative location based on SSID or radio name.Īlmost all networks listed above were logged at an altitude of 10 – 11 km, except the unidentified one ( kvt-kmb-4), which was logged at a height of around 7 km. N – number of received beacons or probe responses, Sia-link18 RRL_RadviliskisVB_PolekelesVB_AP Later, when the airplane was at a higher altitude above ground I logged networks from Lithuania and presumably Latvia. I received some Wi-Fi networks that I’m getting at my QTH near Płock during enhanced tropospheric conditions. I was checking the possibility of scanning and trying different antenna tilt angles down to Earth. I was sitting next to a window with a view to north-east Poland, Lithuania and Latvia. After the trip I downloaded all JSON files with flight information from FlightRadar24 website.ĭuring my first flight I was not using any GNSS at all. The RTC module in Raspberry PI was synchronized beforehand, so the ADS-B flight path points can be interpolated and used for determining the latitude, longitude and altitude of each received network signal. It is not really suitable for GNSS bands, as the measured SWR for GPS/GLONASS frequencies is between 2.5 and 3.5, but the receiver sensitivity is good anyway.ĭuring the flight I was also able to follow the results in real-time via VNC client on a tablet, connected to Raspberry PI via Wi-Fi (2.4 GHz). I don’t have any passive GPS antenna with SMA connector, so I used a random LTE rubber antenna. Of course, I decided to keep the device quiet during flight. The installed loudspeaker indicates new network detection or some problems like GPS fix loss or antenna connection failure. ![]() Actually such activity in an airplane has its own name too and it is called warflying. The primary residence of this Raspberry PI setup is inside my car, together with 3× MikroTik OmniTik antennas for 5 GHz Wi-Fi scanning, also known as wardriving. All beacons and probe response packets are being parsed on the Raspberry PI computer that runs Arch Linux ARM. ![]() The software used for scanning is called MTscan and it has a passive mode which relies on sniffer tool in MikroTik RouterOS that streams packets via TZSP protocol. It was connected to Raspberry PI single board computer. The dual-polarization antenna rated at 16 dBi is even smaller, at just 11×11 cm. I was scanning using MikroTik SXT antenna with a built-in radio module. Raspberry PI 3B with GNSS receiver, RTC and 10 V PoE output – see more: Wardriving 5 GHz,.Mikrotik Routerboard SXT 5HPnD (AR9280),.I took the following equipment for Wi-Fi scanning onboard: Of course, I could not resist to check what could be received on 5 GHz there, at an altitude of over ten kilometers… Recently I was traveling by plane over Europe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |