MLAT Problem stopped at my location In The Netherlands at 15:58Z on one system.
Other system last reported it at 09:05Z today
Both systems are Raspberry Pi’s.
Two other systems, based on Orange Pi 2+E board running armbian haven’t had any MLAT issues since the upgrade 24 hrs ago.
All 4 feeders are on the same internetconnection.
So the network change had a positive effect for me.
I’m running a PiZero, and the problem (clock unstable) seems to be gone for about an hour now by confuguring slow-cpu=no.
Are you guys seeing the issue now? The issue seems to be improving on the server side.
Fingers crossed its all sorted no more udp error
I haven’t had a single warning for a bit now, thank you for fixing this
2 Likes
As of right now, the errors are gone on my side.
1 Like
Thanks for fixing the issue
It does not appear any longer on my Raspberry with Piaware 6.0 installed
1 Like
The MTU change notification seem to be not related to Piaware 6
I have connected my Jetvision device which still runs Piaware 5 and the message is the same.
But it does not lose any MLAT packets, so i think it’s good to ignore it
Sep 04 18:07:27 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:07:47 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 18:17:32 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:17:55 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 18:27:42 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:28:01 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 18:38:04 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:38:28 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 18:48:28 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:48:50 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 18:58:46 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 18:59:10 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
Sep 04 19:09:28 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1492
Sep 04 19:09:52 AirSquitter piaware[354]: mlat-client(2716): Route MTU changed to 1476
SoNic67
September 5, 2021, 2:20pm
29
My sites, updated to 6.0, started to show MLAT issues this morning.
The only one that still works is a FlightFeeder 9.2~bpo8+1 (I guess that’s the old version of software?).
The other FlightFeeder 9.2~bpo9+1 (UAT978) has the newer version (?) and shows errors.
For me the issues are gone. Only the MTU size changes every 10 Minutes between 1492 and 1476.
But no further loss of MLAT data
obj
September 5, 2021, 3:46pm
31
These are the same version, just built for different distributions.
No recent FlightFeeder upgrades. You’re seeing something else, not a software change.
1 Like
SoNic67
September 5, 2021, 3:50pm
32
Thanks, I wasn’t sure, hence the (?).
The MLAT issue is fixed now.
system
Closed
September 5, 2022, 3:50pm
33
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.