![usb redirector 2wire att uverse usb redirector 2wire att uverse](https://i.pinimg.com/736x/44/58/59/445859ce265eaa14caf9933388c6bf83--wireless-modem-router-wireless-network.jpg)
To get the proper results, I also discovered that when testing wifi to wifi I had to remove both LAN connections, and when testing LAN to LAN I removed both wifi dongles. I am testing between two Model B Rev 2 pis, with the LAN and TL-WN722N dongles connected via a router in the same room. I am running the latest Raspbian with all updates (except rpi-update), so can I assume that there has not been a fix for this? I hope this is not hardware related and unfixable, as I am testing two pis that I just purchased. I am still able to use wifi without any major glitches, but this has to be killing the performance drastically. I am also seeing very high packet loss on wifi. that sounds like fun - from your post, can i assume that this will compile on the Pi (raspbian)?
#USB REDIRECTOR 2WIRE ATT UVERSE DOWNLOAD#
Took a look at nuttcp and noticed that the download page is hosted at. is it possible that the Pi simply can't operate faster than about 20 Mbs over wireless? as i recall, on my linux laptop, the standard monitoring tool reports lower links speeds with increasing distance iwconfig on the Pi, even at 50 ft and 50% packet loss reports, claims 54 Mbs - is that how it ought to work? will also be more rigorous in testing at different distances in my test the Pi was 45-50 ft away from the station, and the link itself runs at 54 Mbs max. in the set-up reported in my previous post, the Pi was running wireless *only*, but the other machine (a laptop) was tethered to the switch. interesting - i never thought to run the iperf test with both ends wired. Even if you use the wifi ip as connection point, the Pi returns it's packets over the wired connection.Īppreciate the helpful reply.
![usb redirector 2wire att uverse usb redirector 2wire att uverse](http://jackkozik.com/wp-content/gallery/uverseinstall053113/dsc_7261.jpg)
You need to disconnect your wired connection before you can test. Both were tested in close range to the access point. So, basically, I couldn't see a difference between the stick giving packet loss and the other who wasn't showing any packet loss. My guessing is that me SSHing over the WAN network would of made no difference but the fact that the first time was done by SSHing into the Pi and the second time was done through the local terminal on the Pi might have something to do with it since SSHing into the Pi probably initilised the network on the Pi backing up what I said earlier about the wireless possibly being in like a sleep mode that its taking to long to get out of. The tests after that were done from my home by running terminal on the Pi and SSHing into the MyBook World from my Galaxy S2 using connectbot. The only difference was that in the first test I did it from work by SSHing into the Pi and SSHing into the MyBook World from my Galaxy S2 using connectbot over a 3G network. Is it just random chance on bootup whether you get first behaviour or second? I'm not understanding why the second iperf test was much worse that the first. Well I think you'd agree that the iperf test was a deffinate improvement over LAN than over WLAN right?