Looks like it’s what i reported in a different thread already:
Now i have connected my Jetvision device which is still on PiaWare 5.0.
After rebooting the Repeater and reconnect of the device, the issue seem to be gone:
Sep 03 16:08:34 AirSquitter piaware[363]: mlat-client(686): Route MTU changed to 1492
Sep 03 16:08:54 AirSquitter piaware[363]: mlat-client(686): Route MTU changed to 1476
Sep 03 16:14:28 AirSquitter piaware[363]: mlat-client(1093): Route MTU changed to 1500
This was after i exchanged the devices. It started with the adept server notice. Then i rebooted the repeater:
Sep 03 16:08:32 AirSquitter piaware[363]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 03 16:08:32 AirSquitter piaware[363]: Connection with adept server at piaware.flightaware.com/1200 established
Sep 03 16:08:32 AirSquitter piaware[363]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Sep 03 16:09:34 AirSquitter piaware[363]: NOTICE from adept server: 30% of multilateration messages (UDP) are not reaching the server - check your network?
Sep 03 16:10:34 AirSquitter piaware[363]: NOTICE from adept server: 27% of multilateration messages (UDP) are not reaching the server - check your network?
Sep 03 16:11:35 AirSquitter piaware[363]: NOTICE from adept server: 36% of multilateration messages (UDP) are not reaching the server - check your network?
Sep 03 16:12:35 AirSquitter piaware[363]: NOTICE from adept server: 29% of multilateration messages (UDP) are not reaching the server - check your network?
Sep 03 16:13:51 AirSquitter piaware[363]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 03 16:13:51 AirSquitter piaware[363]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Sep 03 16:13:57 AirSquitter piaware[363]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 03 16:13:57 AirSquitter piaware[363]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Sep 03 16:14:01 AirSquitter piaware[363]: Connecting to FlightAware adept server at 70.42.6.232/1200
Sep 03 16:14:01 AirSquitter piaware[363]: Connection to adept server at 70.42.6.232/1200 failed: couldn't open socket: network is unreachable
Sep 03 16:14:06 AirSquitter piaware[363]: Connecting to FlightAware adept server at 70.42.6.224/1200
Sep 03 16:14:21 AirSquitter piaware[363]: Connection attempt with adept server at 70.42.6.224/1200 timed out
Sep 03 16:14:26 AirSquitter piaware[363]: Connecting to FlightAware adept server at 70.42.6.156/1200
Sep 03 16:14:26 AirSquitter piaware[363]: Connection with adept server at 70.42.6.156/1200 established
Sep 03 16:14:26 AirSquitter piaware[363]: TLS handshake with adept server at 70.42.6.156/1200 completed
Time is UTC as the Jetvision gets it via GPS
With this PiaWare 5.0 device, i am getting only the warning about PiaWare itself:
Once i connect the Raspbery 4 where PiaWare 6.0 is running, the errors are coming back.
Can you please confirm that it’s not a local issue and i can connect the RPi 4 again?