Bug in piaware with ppp interface


#1

Two days ago, I tried to install your software on my linux pc x86_64.
To my regret, I discovered that the client piaware does not transmit any data to the server, here is a sample log file:


02/20/2015 03:02:57 ****************************************************
02/20/2015 03:02:57 piaware version 1.20 is running, process ID 2040
02/20/2015 03:02:57 your system info is: Linux htpc 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
02/20/2015 03:02:57 connecting to FlightAware eyes.flightaware.com/1200
02/20/2015 03:03:17 got 'couldn't open socket: no such device or address (Temporary failure in name resolution)' to adept server at eyes.flightaware.com/1200, will try again soon...
02/20/2015 03:03:42 ADS-B data program 'dump1090_mr' is listening on port 30005, so far so good
02/20/2015 03:03:42 i see dump1090_mr serving on port 10001
02/20/2015 03:03:42 connecting to dump1090_mr on port 10001...
02/20/2015 03:03:42 piaware is connected to dump1090_mr on port 10001
02/20/2015 03:03:42 dump1090_mr is listening for connections on FA-style port 10001
02/20/2015 03:03:42 piaware received a message from the ADS-B source!
02/20/2015 03:04:12 67 msgs recv'd from dump1090_mr; 0 msgs sent to FlightAware
02/20/2015 03:04:28 connecting to FlightAware 70.42.6.203/1200
02/20/2015 03:04:29 FlightAware server SSL certificate validated
02/20/2015 03:04:29 encrypted session established with FlightAware
02/20/2015 03:04:29 autoUpdate in adept config is disabled, disallowing update
02/20/2015 03:04:29 manualUpdate in adept config is disabled, disallowing update
02/20/2015 03:05:29 server is sending alive messages; we will expect them
02/20/2015 03:05:35 connecting to FlightAware eyes.flightaware.com/1200
02/20/2015 03:05:36 FlightAware server SSL certificate validated
02/20/2015 03:05:36 encrypted session established with FlightAware
02/20/2015 03:05:36 autoUpdate in adept config is disabled, disallowing update
02/20/2015 03:05:36 manualUpdate in adept config is disabled, disallowing update
02/20/2015 03:06:36 server is sending alive messages; we will expect them
02/20/2015 03:06:51 connecting to FlightAware 70.42.6.203/1200
02/20/2015 03:06:52 FlightAware server SSL certificate validated
02/20/2015 03:06:52 encrypted session established with FlightAware
02/20/2015 03:06:52 autoUpdate in adept config is disabled, disallowing update
02/20/2015 03:06:52 manualUpdate in adept config is disabled, disallowing update
02/20/2015 03:07:52 server is sending alive messages; we will expect them
02/20/2015 03:08:49 connecting to FlightAware eyes.flightaware.com/1200
02/20/2015 03:08:50 FlightAware server SSL certificate validated
02/20/2015 03:08:50 encrypted session established with FlightAware
02/20/2015 03:08:50 autoUpdate in adept config is disabled, disallowing update
02/20/2015 03:08:50 manualUpdate in adept config is disabled, disallowing update
02/20/2015 03:09:14 509 msgs recv'd from dump1090_mr (442 in last 5m); 0 msgs sent to FlightAware
02/20/2015 03:09:50 server is sending alive messages; we will expect them
02/20/2015 03:10:04 connecting to FlightAware 70.42.6.203/1200 
and so on

A lot of experimentation and attempts to understand the source code, I found that the failure is due to the interface that PPP is the default gateway. pologayu that it is connected with an unusual kind ip-address string “92.248.151.xx P-t-P: 217.76.183.xx”.
Unfortunately my meager experience in programming has allowed me to find a workaround, replacing the address 0.0.0.0 to address LAN. (Line 370 in file piaware.tcl)
I know what x86 is not in your priority, but if you fix this bug then it would be awesome!
Thanks!