Are you certain your EAP225 is in AP mode ?
If not, if it is in router mode. Your client and your sat receiver will not be on the same lan subnet and the EAP225 is doing NAT between the 2 lan segment that can be a big pb for multicast packets.
in that case it is not routing but simple bridging, and that is what you want.
To be sure, do an 'ipconfig' on your client connected on the R6220 (or any other switch) and then again as an EAP client in Wi-fi, you should obtain IPs with on the same scope
I would try with every weird setting switched off.
It's not connected at all with your problem. If they were in different vlans, there would be no communication at all.
Last but not least, it seems to me that the problem is getting out of OpenWrt scope, as the EAP we are troubleshooting is running on stock firmware and the R6220, which runs OpenWrt, didn't have any issues with the streaming.
I agree. It may be due to the cable between EAP225 and R6220.
Let me explain. With CAT5 cable the link was only 100Mbps. So I bought a CAT6 cable and... violá: 1000Mbps!
But... This is the long stretch (5m or so) between the PoE adapter and the EAP225. There is still a patching cable of 10 or 20 cm between R6220 and PoE adapter. This patching cable may not even be CAT5 now.
I thought it wouldn't matter because it is so short but all data runs through it so maybe there is crosstalk or something.
I'm going to try and replace it, with CAT6 if necessary.
I did flash openwrt onto the EAP225. I wasn't going to but got desperate so took the risk. To my surprise there was no LuCI, but I got it working anyway.
Most importantly, the video streaming issue is still there .
I may need a hand to get the stock firmware back in, if I've got to return the device finally. I made a backup of the stock firmware following the guide for EAP-225 Outdoor but I've never flashed from the CLI, which is the only option now LuCI isn't there.
Cables are some (not so) simple mechanical things, and, as for all mechanical things, they can have defects.
Any other Cat5 can probably do the job without any pb.
This particular one has perhaps a shielding default or any other problem, resulting in bad performance.
These are things that happen, you can throw it away with no regrets
I found out that CAT5 cable works in the 5m stretch as well. It doesn't need to be CAT6. You do need to have the connectors crimped correctly,.... which I did not
I found out that the video to be streamed through wifi showed freezes as it left the SAT receiver already. I may falsely have blamed the wifi for this to happen and consequently the cable between router and AP
Sorry for the confusion this may have caused and thank you all for helping me out.
yeah... its pretty rare where cat5 wont do fine in residential settings... and even then it is usually when someone didn't bother to use solid core in the walls (long horizontal crossconnect runs)... or from some sort of localized emf...