> To clarify one thing about my setup before someone points out it could > cause problems. > I talk about a wifi router. Note that I'm using an ethernet port on the > wifi router, so I have no wifi bridging involved.
Well, exept for the part on my setup being free soft that I can play with... your setup is not that much different from the one on my workstation, with a bridge (of two cards, but usually just one plugged) going to my server wich runs a bridge over wifi and copper, but I'm going through copper anyway. > Also, you may have something in all of that acting as an IGMP querier. > It's certainly complicated enough that I wouldn't know how to go about > isolating differences between it and something that doesn't work. Nope, I don't have any querier unless Linux does that by default. Anyway, I tried to build a more complicated setup just in case the problem was going through a bridge or things like that, in fact, I have now gone to the normal setup of just the server and the workstation. > Admittedly that's probably Linux under the covers, and it's probably > bridging the wifi to the ethernet ports, but in debugging this sort of > thing I tend to find a big difference between equipment under one's > control and equipment not under one's control. Yes, that is true, so... we can only tcpdump one of the sides :-( I suggest you do more testing whenever you can reach the equipment doing a tcpdump of the traffic so that we know where the problem is, also, take a look to the firewalling you have just in case igmp or other traffic is being cut somewhere. Regards... -- Manty/BestiaTester -> http://manty.net
