I'd recommend grabbing Wireshark and capturing some of the data to make sure it really is going out unicast and not multicast. Multicast would certainly saturate the Wifi.
dkulp wrote:I'd recommend grabbing Wireshark and capturing some of the data to make sure it really is going out unicast and not multicast. Multicast would certainly saturate the Wifi.
I wondered about that. My e682 is running in unicast and is driving the pixels, just as I expect it to. Would it even pick up the multicast traffic, given that I have it set to unicast? Or, is it possible that the software is sending out both unicast and multicast traffic somehow?
What kind of router/nic are you using? ABGN? N would be your preferred considering it runs at ~300mbs sometimes because of signal strength it may drop down to G and gasp.. even B at times... so you need to see what speed you are transmitting on as part of your investigation.
Router is an Apple AirPort Extreme, running N. Wifi hardware in my PC is also N.
What I'm confused by is that I think I have it set up so that I'm not actually transmitting any of the e1.31 data over my wireless, leaving the home network to only handle the "normal" home network traffic (web browsing, music, etc.). The e1.31 is intended to be transmitted only on the wired connection from my second NIC. I've attempted to establish a route in the routing table (picture above) that accomplishes this. The trouble is that this doesn't appear to have solved the problem.
I think your getting a bleed over because the 10.10.10.0 route is to your own PC so it's not handling it right and trying to route it on (while still managing to work).
I'd try giving the the 10.10.10.0 network a gateway number like 10.10.10.254.
There's probably a better way. I'd have to research it some more.
-
Jason
