I used the piaware image and everything works ok UNTIL I change from an Ethernet cable to WIFI and then it stops or rather is doesn’t connect to the piaware server anymore because faup1090 is not running
This is from my working B+
dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
This is from my non-working 2
dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
And all because I have set a static wifi up and removed the dhcp Ethernet.
It would seem the error of faup1090 not connecting lies in the following line in my interfaces file
I had
auto wlan0
at the start to auto connect to my Wifi. This however knocks out faup1090 connecting to localport so, I’ve had to revert back to
auto lo
which I had on my B+. I’ve also have to add a DNS line as the Pi 2 doesn’t find anything without it even though it connect to the local lan alright. The B+ didn’t need this line.
LMMS works as well, got to ask them how to supress the output though.
Disabling the loopback interface is going to break tons of things. Don’t do that.
(It may be related to the DNS issue too, if you end up running dnsmasq or similar; that will set up resolv.conf to point to localhost, and if you’ve broken the loopback interface then that’s not going to work…)
I have just tried the latest arm7 build of fr24 - fr24feed_1.0.13-2_armv7l.deb - and its running fine with the piaware dump1090 mlat version. Cant get Mlat to run on fr24feed (which I expected) but other than that its working fine.
Fairly happy, got all my feeds working - I think. Just awaiting conformation from LMMS.