I'm choosing between AWUS050NH and AWUS036H. What is the difference? Which one shall I choose?
it works for me, only diff i can think of is with BT4 pre final, u gotta unload the rt2870sta driver (that gets called when u plug in the USB device automatically as rt2x00 drivers do not come with BT4 pre final), and then blacklist it in /etc/modprobe.d/blacklist by adding the following to that file at the end ::
then, follow this tutorial as normal. worked for me, let me know if u get stuck.blacklist rt2870sta
------------------EDIT------------------
I updated the tutorial per your request for BT4 pre final, look near the bottom of the first post it explains it in more detail then this posting =) let me know if you have any trouble, I tested it on my BT4 pre final install, and it worked great here!
'see the fnords!'
I'm choosing between AWUS050NH and AWUS036H. What is the difference? Which one shall I choose?
FYI, if you are building from a relatively new compat-wireless-2.6 tarball [from 06-28 onward... I may be off by 1 or 2 dates here] you may run into some compilation hard ERRORs, namely ::
a kind person named johill from #linux-wireless @ irc.freenode.net was nice enough to help out.... he told me to REVERT the following git commitdiff's to get things working again ::Code:/root/compat-wireless-2009-07-05/drivers/net/wireless/at76c50x-usb.c: In function 'at76_config': /root/compat-wireless-2009-07-05/drivers/net/wireless/at76c50x-usb.c:1950: warning: 'radio_enabled' is deprecated (declared at /root/compat-wireless-2009-07-05/include/net/mac80211.h:607) CC [M] /root/compat-wireless-2009-07-05/drivers/net/wireless/rndis_wlan.o CC [M] /root/compat-wireless-2009-07-05/drivers/net/wireless/adm8211.o CC [M] /root/compat-wireless-2009-07-05/drivers/net/wireless/mwl8k.o /root/compat-wireless-2009-07-05/drivers/net/wireless/mwl8k.c: In function 'mwl8k_config_wt': /root/compat-wireless-2009-07-05/drivers/net/wireless/mwl8k.c:3032: warning: 'radio_enabled' is deprecated (declared at /root/compat-wireless-2009-07-05/include/net/mac80211.h:607) CC [M] /root/compat-wireless-2009-07-05/drivers/net/wireless/mac80211_hwsim.o /root/compat-wireless-2009-07-05/drivers/net/wireless/mac80211_hwsim.c: In function 'mac80211_hwsim_tx_frame': /root/compat-wireless-2009-07-05/drivers/net/wireless/mac80211_hwsim.c:416: error: implicit declaration of function 'skb_dst_drop' make[3]: *** [/root/compat-wireless-2009-07-05/drivers/net/wireless/mac80211_hwsim.o] Error 1 make[2]: *** [/root/compat-wireless-2009-07-05/drivers/net/wireless] Error 2 make[1]: *** [_module_/root/compat-wireless-2009-07-05] Error 2 make[1]: Leaving directory `/usr/src/linux-source-2.6.29.4' make: *** [modules] Error 2
git.kernel.org - linux/kernel/git/linville/wireless-testing.git/commitdiff
-AND-
git.kernel.org - linux/kernel/git/linville/wireless-testing.git/commitdiff
for example, this is what I changed the specified section in drivers/net/wireless/mac80211_hwsim.c TO ::
and this is what I changed the specified section in net/wireless/nl80211.c TO ::Code:@line 414 of mac80211_hwsim.c in compat-wireless-2.6-2009-07-05 /* release the skb's source info */ skb_orphan(skb); dst_release(skb->dst); skb->dst = NULL; /* skb_dst_drop(skb); */ skb->mark = 0; secpath_reset(skb); nf_reset(skb);
again, those are examples, I am SURE the line #s will change in the future, and I bet this will not be required to be done in the future. I figured I'd post this as I was unable to make/install any of the latest compat-wireless-2.6 tarballs due to this issue. and once more, all thanks and praises goes to user johill @ #linux-wirelessCode:@line 4073 of nl80211.c in compat-wireless-2.6-2009-07-05 int nl80211_init(void) { /* int err; */ int err, i; /* err = genl_register_family_with_ops(&nl80211_fam, * nl80211_ops, ARRAY_SIZE(nl80211_ops)); */ err = genl_register_family(&nl80211_fam); if (err) return err; for (i = 0; i < ARRAY_SIZE(nl80211_ops); i++) { err = genl_register_ops(&nl80211_fam, &nl80211_ops[i]); if (err) goto err_out; }
:: UPDATE compat-wireless-2.6 build from 2009-07-09 works without the above fix! ::
so, this post here really ONLY pertained to the compat-wireless-2.6 builds from 2009-06-28 thru 2009-07-08 (last I tried before 2009-07-09 was 2009-07-05 and it still required the fix posted here, so I could be off on a release or 2 --- but the UPDATE remains active with 2009-07-09 and newer = forget this post).
NOTHING to see here, all users of compat-wireless-2.6-2009-07-09 OR NEWER! move along please - nothing to see!
:: /UPDATE ::
'see the fnords!'
I must say thank you for this information. I am fairly new to backtrack and have tried every single tutorial on here with no success in getting awus050nh to inject or work properly until this one. This one worked perfect !! Thanks again !
I have meassured the output via Cisco AP and it seems with those drivers output power of Alfa AWUS050NH is no better than the internal 4965agn, BG200 of a laptop. I consider this beeing of concern since we can't reach APs which we can see, if there arent balance (ie big antenna reaches for high TX to acomplish greater distance). I saw on one forum a guy changed the drivers to always return 27dbm instead of the standard 10dbm which in fact could be any mw since those values are in no way accurate. But still one should allow to put it a bit higher than 10dbm to be able to experiement. I guess a sourcecode change is in need to allow 27dbm instead of 10 over all channels. But still remember that 10dbm and 27dbm is not nesecerily 10 and 27 dbm in real world.
Works well under BT4 , But in ubuntu 9.04 each time i try to load the rt2800usb module i get:
also when i try to repeat the process i cannot even "make clean" , "make"Code:WARNING: Error inserting mac80211 (/lib/modules/2.6.28-13-generic/updates/net/mac80211/mac80211.ko): Invalid module format WARNING: Error inserting led_class (/lib/modules/2.6.28-13-generic/kernel/drivers/leds/led-class.ko): Invalid module format WARNING: Error inserting rt2x00lib (/lib/modules/2.6.28-13-generic/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko): Invalid module format WARNING: Error inserting rt2x00usb (/lib/modules/2.6.28-13-generic/updates/drivers/net/wireless/rt2x00/rt2x00usb.ko): Invalid module format FATAL: Error inserting rt2800usb (/lib/modules/2.6.28-13-generic/updates/drivers/net/wireless/rt2x00/rt2800usb.ko): Invalid module format
Any tips ?! , ThanksCode:compat-wireless-2009-07-17# make clean test: 1: -le: unexpected operator test: 1: -ge: unexpected operator test: 1: -le: unexpected operator test: 1: -le: unexpected operator test: 1: -le: unexpected operator
I'm using the Belkin N Wireless F5D8053 I've installed the latest compat drivers(I think they were only released today) on x64 Karmic, they seem to have installed correctly and I can get into monitor mode (an additional mon0 interface is created) with aireplay confirming injection is working. However, I can't connect to any AP's. I get an error saying an IP couldn't be assigned and usually the LED on the adapter blinks, but it is constantly off.
Results of ifconfig:
Results of iwconfig:eth0 Link encap:Ethernet HWaddr 00:18:8b:5c:b9:21
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::218:8bff:fe5c:b921/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4582 errors:0 dropped:0 overruns:0 frame:0
TX packets:3665 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4531198 (4.5 MB) TX bytes:681381 (681.3 KB)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1240 (1.2 KB) TX bytes:1240 (1.2 KB)
wlan0 Link encap:Ethernet HWaddr 00:22:75:3b:e3:98
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Attempting terminal connect:lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"D-Link"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:65:4E:FE
Tx-Power=13 dBm
Retry long limit:7 RTS thrff Fragment thr
ff
Power Managementn
The Ralink driver doesn't build on my Kernel which is 2.6.31.4 and Apocalypse's driver doesn't work. Anyone know what the issue is here?sudo iwconfig wlan0 essid "D-Link"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such file or directory.
Output of dhclient wlan0
Some output of dmesgsudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 5361
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit ******
Listening on LPF/wlan0/00:22:75:3b:e3:98
Sending on LPF/wlan0/00:22:75:3b:e3:98
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 (x6)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
my /etc/network/interfaces file[ 1673.004028] No probe response from AP 00:0f:3d:65:4e:fe after 200ms, disconnecting.
[ 1674.917018] wlan0: no IPv6 routers present
[ 1677.572019] eth0: no IPv6 routers present
[ 1723.742188] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 1723.940034] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 1724.140027] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 3)
[ 1724.340026] wlan0: direct probe to AP 00:0f:3d:65:4e:fe timed out
[ 1777.804098] b44: eth0: Link is down.
[ 1785.804181] b44: eth0: Link is up at 100 Mbps, full duplex.
[ 1785.804188] b44: eth0: Flow control is off for TX and off for RX.
[ 1802.803188] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 1803.001040] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 1803.200031] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 3)
[ 1803.401036] wlan0: direct probe to AP 00:0f:3d:65:4e:fe timed out
[ 1809.441217] b44: eth0: powering down PHY
[ 1809.455769] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1809.770339] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1809.771189] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 1809.968061] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 1809.970853] wlan0 direct probe responded
[ 1809.970859] wlan0: authenticate with AP 00:0f:3d:65:4e:fe (try 1)
[ 1809.972445] wlan0: authenticated
[ 1809.972483] wlan0: associate with AP 00:0f:3d:65:4e:fe (try 1)
[ 1809.974578] wlan0: RX AssocResp from 00:0f:3d:65:4e:fe (capab=0x421 status=0 aid=1)
[ 1809.974583] wlan0: associated
[ 1809.983831] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1812.816186] b44: eth0: Link is up at 100 Mbps, full duplex.
^^^^^^^^^ This falls off so quick I wasn't aware it connected, the error still came up
[ 1812.816194] b44: eth0: Flow control is off for TX and off for RX.
[ 1812.816906] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1813.017034] No probe response from AP 00:0f:3d:65:4e:fe after 200ms, disconnecting.
[ 1820.476017] wlan0: no IPv6 routers present
[ 1823.384018] eth0: no IPv6 routers present
[ 1874.349189] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 1874.549030] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 1874.749024] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 3)
[ 1874.949026] wlan0: direct probe to AP 00:0f:3d:65:4e:fe timed out
[ 1887.341333] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1887.343190] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 1887.388240] b44: eth0: powering down PHY
[ 1887.513329] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1887.541092] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 1887.544328] wlan0 direct probe responded
[ 1887.544340] wlan0: authenticate with AP 00:0f:3d:65:4e:fe (try 1)
[ 1887.557188] wlan0: authenticated
[ 1887.557224] wlan0: associate with AP 00:0f:3d:65:4e:fe (try 1)
[ 1887.571712] wlan0: RX AssocResp from 00:0f:3d:65:4e:fe (capab=0x421 status=0 aid=1)
[ 1887.571720] wlan0: associated
[ 1887.585963] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1890.804180] b44: eth0: Link is up at 100 Mbps, full duplex.
[ 1890.804187] b44: eth0: Flow control is off for TX and off for RX.
[ 1890.804889] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1897.640014] wlan0: no IPv6 routers present
[ 1899.004032] No probe response from AP 00:0f:3d:65:4e:fe after 200ms, disconnecting.
[ 1901.616016] eth0: no IPv6 routers present
[ 2931.804096] b44: eth0: Link is down.
[ 2932.409211] b44: eth0: powering down PHY
[ 2932.424108] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2942.555188] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 2942.752029] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 2)
[ 2942.953038] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 3)
[ 2943.153026] wlan0: direct probe to AP 00:0f:3d:65:4e:fe timed out
[ 2961.697207] b44: eth0: powering down PHY
[ 2961.711062] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 2962.021348] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2962.027441] wlan0: direct probe to AP 00:0f:3d:65:4e:fe (try 1)
[ 2962.030836] wlan0 direct probe responded
[ 2962.030843] wlan0: authenticate with AP 00:0f:3d:65:4e:fe (try 1)
[ 2962.032564] wlan0: authenticated
[ 2962.032597] wlan0: associate with AP 00:0f:3d:65:4e:fe (try 1)
[ 2962.034692] wlan0: RX AssocResp from 00:0f:3d:65:4e:fe (capab=0x421 status=0 aid=1)
[ 2962.034697] wlan0: associated
[ 2962.044808] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
If I plug an ethernet cable in, it works fine, but not with wireless.
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
Hello there,
just wondering, these tests and working results have been done with AWUS050NH v1 or v2? cause these 2 seem to have different behaviors and results..
thanks