For quite a long time, my feeder has been operating under a cloned MAC address to keep the site the same after replacement of a Raspberry Pi about a year ago. Due to a failed power supply, it was offline for a week. Because I lost the always-on streak, I stopped the cloning of the MAC address and reverted to it’s natural MAC address. The problem is that FA now claims my PiAware version doesn’t support MLAT. It also displays the version on the web site differently. On the “old site”, MAC b8:27:eb:2e:85:aa, it refers to the version as "PiAware (Debian Package Add-on) 2.1-5.
On the “new” site it claims it’s “PiAware 2.1-5”. It also states “Receiver Not Supported” under MLAT. The location and elevation is manually set. The only thing that had changed was removing the MAC address cloning under /boot/cmdline.txt
$ cat /tmp/piaware.out
06/01/2016 20:54:33 ****************************************************
06/01/2016 20:54:33 piaware version 2.1-5 is running, process ID 2363
06/01/2016 20:54:33 your system info is: Linux antenna1090mhz 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l GNU/Linux
06/01/2016 20:54:33 Connecting to FlightAware adept server at piaware.flightaware.com/1200
06/01/2016 20:54:33 ADS-B data program 'dump1090-mutab' is listening on port 30005, so far so good
06/01/2016 20:54:33 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 35.757 --lon -79.296
06/01/2016 20:54:33 Started faup1090 (pid 2503) to connect to dump1090-mutab
06/01/2016 20:54:33 Connection with adept server at piaware.flightaware.com/1200 established
06/01/2016 20:54:33 FlightAware server SSL certificate validated
06/01/2016 20:54:33 encrypted session established with FlightAware
06/01/2016 20:54:33 autoUpdate in adept config is disabled, disallowing update
06/01/2016 20:54:33 manualUpdate in adept config is disabled, disallowing update
06/01/2016 20:54:33 multilateration support enabled (use piaware-config to disable)
06/01/2016 20:54:34 logged in to FlightAware as user N456TS
06/01/2016 20:54:34 piaware received a message from dump1090-mutab!
06/01/2016 20:54:34 piaware has successfully sent several msgs to FlightAware!
06/01/2016 20:54:34 multilateration support enabled (use piaware-config to disable)
06/01/2016 20:54:34 multilateration data requested, enabling mlat client
06/01/2016 20:54:34 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --udp-transport 70.42.6.198:9452:3192033169
06/01/2016 20:54:35 mlat(2508): fa-mlat-client 0.2.4 starting up
06/01/2016 20:54:35 mlat(2508): Using UDP transport to 70.42.6.198:9452
06/01/2016 20:54:35 mlat(2508): Input connected to localhost:30005
06/01/2016 20:54:35 mlat(2508): Beast-format results connection with localhost:30104: connection established
06/01/2016 21:07:27 61 msgs recv'd from dump1090-mutab; 61 msgs sent to FlightAware
06/01/2016 21:07:28 timed out waiting for alive message from FlightAware, reconnecting...
06/01/2016 21:07:28 TLS alert: close notify
06/01/2016 21:07:28 multilateration data no longer required, disabling mlat client
06/01/2016 21:07:28 reconnecting in 107 seconds...
06/01/2016 21:07:28 mlat(2508): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
06/01/2016 21:07:28 mlat(2508): Exiting on connection loss
06/01/2016 21:07:28 the system told us that process 2508 exited cleanly
06/01/2016 21:07:28 the system confirmed that process 2508 exited with an exit status of 0
06/01/2016 21:07:58 164 msgs recv'd from dump1090-mutab (103 in last 1m); 61 msgs sent to FlightAware