If you set up a test and then don't transfer much information over the network, then you won't see a problem.rocco said:My understanding is that there is a reference number in each packet, and that you need to capture the full cycle of reference numbers in order to decipher the key (the reference numbers are encrypted, but predictable). On a heavily trafficked business network, it might take a few hours. On a home network, it could take days, or even weeks.Chakara said:After a couple of days I gave up....
Skibum said:I only did it to keep "E" happy...
And 2 miles.... obviously you have never tested your claim.
(Don't mistake my comment on POSSIBLE 802.11 range. Point to Point communication over that distance is easy, as long as it is line of sight. It's all about the Db's)
And 2 miles.... obviously you have never tested your claim.
It isn't bad advice, but don't consider it "secure".stealth said:Don't broadcast ssid, and use mac filtering. When you use other encryption it slows down your data through-put
Yes, and even then they will probably blame the cable company or the web site.stealth said:Most people at home aren't gonna see the lose of bandwidth ether, unless someone is really flogging the system.