I'm curious as to why this track doesn't appear on ADSBx global view, yet I can see it on my system. I'm running Piaware 3.5.3 feeding FA & ADSBx. I also run ModeMixer2 on the Pi, and feed into that the local dump1090 data, plus the MLAT returned by ADSBx. This screen shot shows an RCMP aircraft "practicing left turns" for about 4 hours north of Toronto earlier today. The pattern is not unusual for this aircraft. I've seen it many times before, but usually I can see it in ADABx Global view. The aircraft appeared on the list in Global view on ADSBx, but not on the map. Eventually, as the aircraft headed back home, which is near London Ont, it's track appeared on the Global view screen as an MLAT position, but there was no trace of the loops. Call sign is C-GMPB. ICAO is c065e0. It's blocked by FA, so even if I'd messed up the feed to MM2 by mistake, it's not FA data. Have I made a mistake setting up my ADSBx feed? But it is returning MLAT to me. What's up? TIA
OK, well I've discovered the answer. I was not feeding ADSB properly. I had 127.0.0.1:30005 in the socat statement. But I could see nothing on my custom feed. It started working when I changed to localhost:30005. Go figure. I'm still puzzled as to why one works and the other doesn't. but at least it is feeding properly now.
Interesting .. but you might not have 127.0.0.1 listed as same as localhost in your etc/hosts file .. linux can be funny like that What image are you using? .. EDIT. I see Piaware 3.5.3 ... hmmmm
Interesting. I did have a typo in my etc hosts file: 127.0.0.1 localhost 127.0.1.1 piaware The second line should, of course, read 127.0.0.1 as my system name is piaware. This forums software is pretty stupid. I wouldn't let me put the slashes in the (slash) etc (slash) hosts above.
Yeah it's not the forum software it's cloudflare ... wrap stuff in [ CODE ] [ /CODE ] without the spaces Using 127.0.1.1 in addition to 127.0.0.1 is just a Debian convention; here's the justification. It is not a bad thing. These two addresses amount to the same thing anyway; a more widespread methodology would be to use an alias: 127.0.0.1 localhost.localdomain raspberry https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution There is the justification since Raspbian is based on Debian and this new image is Debian Stretch based
anything that calls piaware host name will point to 127.0.1.1 in that config and anything that uses localhost will point to 127.0.0.1 seems to be a recent rasbian stretch thing as well in my custom image ... hosts file in etc has 127.0.0.1 localhost 127.0.1.1 adsbx-custom so if you bind something to localhost it can only be accessed using 127.0.0.1 or maybe not at all .. I guess we best be sure to use hostname localhost from now on and not 127 addresses
