So obviously you should have injection working, and working reasonably well. When you have some sequence recorded, you can replay it (using aireplay) required number of times, or using different adapters. Injection is also useful to observe behavior in stress situation and sustainability of your network. Most likely, some packets were lost or coming damaged to wireless client. With wireless network monitoring you can see what's going on. I was really confused, as in one room everything worked ok, and connection was hanging when I am at my kitchen.
That was when I had test with two concrete walls between AP and computer, and weak wireless adapter (RT2500 on old notebook) I had situations when my computer doesn't want to connect via Wi-Fi to my Access Point. May be they would tunnel traffic using VPN, but for people who want to hijack and just use someone else's connection it's still fine.Ībout packet injection/network monitoring.įor me network monitoring is more important. So if someone needs a wireless bridge, and needs it fast - they would deploy it using WEP, with all consequences out of this. In particular - Wireless Bridge configuration, or WDS works only with WEP, and doesn't work with WPA (on some branded hardware, don't want to mention its name here) I guess we are still far away from situation when everyone is aware about WEP weakness and uses WPA or WPA2.īesides, there are some specific configurations when you have no choice but WEP. Interestingly enough, it looks like the firmware /lib/firmware/ar9271.fw is available for Fedora 13 (I see it on my installation). There are probably dependency issues, but it might be worth a shot. Are the modules owned by the kernel package? It might be a long shot due to dependency issues, but you could try downloading the Fedora 14 Beta kernel RPM and installing it on a NST system (I would recommend trying it on a Live boot first). You said that the Fedora 14 Beta kernel supported you Wi-Fi USB stick. Unfortunately, after a bit of googling I was unable to locate the source code as a tar.gz file for the modules your hardware requires.
ATHEROS TP LINK DRIVERS DRIVERS
That's my typical approach at adding drivers for specific hardware to the kernel.
Locate the source code for the for the ath9k_htc and ath9k_hif_usb modulesģ.
ATHEROS TP LINK DRIVERS INSTALL
Install the kernel-devel and kernel-headers packageĢ. I've poked around a bit, but have not come across a easy solution to build the driver. The detachable antenna sounds like a nice feature.
0 kommentar(er)
