there should be no need for port forwarding.
this router interface looks like utter crap. if there would be a lower level than low i would probably set it.
maybe check the firewall Event log that is shown in the screenshot by biekerc?
disabling ipv6 is always worth a try but flightaware seems to have tons more of network knowledge compared to the competitors cough so i doubt it’s a problem upstream.
A strange problem i had was with a channel bundeling service allowing simultaneous use of wired broadband and mobile broadband.
My suspicion is that if the UDP packets arrive at the flightaware server out of order they are discarded.
Wouldn’t make much sense but hey.
Maybe someone from the flightaware team can elaborate on the out of order issue even if its’ only a guess.
This out of order problem could also occur when there is congestion at your provider as UDP packets are not ordered by design.
I guess on my setup the udp packets look like this:
UDP (582 bytes) from pi:53309 to gales.hou.flightaware.com:7773 on wlan0
So the local port is 53309 and the remote port 7773.
That’s information you could check with you Firewall event log.
Apart from that it’s not much use because those packets are outbound and should not be filtered by your router.
It’s really tricky to track down intermittent UDP problems i switched off this channel bundeling i had going on but that was just a lucky guess. The reason why it didn’t work with this bundeling enabled i never figured out. (apart from my guess it was an out of order problem)