Comments like "arp -a" lead me to remind people that we are no longer in the world of Raspberry Pis and soldering irons. This is now a commercial product sold for a not inconsiderable amount of money, on the premise that it "just works."
This was a thrown away comment to say this it is easy for any device to find out what else is on the network, and act accordingly. Just one line of code.
So if you say:
"Indeed I do and I will check at the weekend, but I would be amazed if SafeSky can “see” PAW simply because it is using the iPhone as a hotspot!"I work with stuff that can see other stuff even when not on the same VLAN and with the ability to reconfigure network devices wrongly configured.
Very little to do with absence of callsigns, but I am very aware that SE2 and SafeSky, my previous solution, "just works".
Until you look at latency (SafeSky) and RF performance (SE2) - I've got side by side of SE2 and the older Rosetta in the same aircraft on the same flight. Just works... not for me. Ditto looking at SafeSky with aircraft flying over a reference point.
As I understand it, FX doesn't have log files. But I haven't looked at it for 4 months, as that aircraft has been getting fixed. Head over to playback and use the "groundstations" option for a track log.