jetlib.sec » BackTrack Linux Forums » AWUS036H won't get IP but connects to network through Backtrack...

Feeds

132763 items (0 unread) in 27 feeds

• 1337day (was: Inj3ct0r, 1337db)
• OSVDB Vulnerabilities
• Exploit-DB
• SecurityFocus Vulnerabilities
• Bugtraq
• Full Disclosure
• XSSed
• Packet Storm Security Headlines
• Packet Storm Security Advisories
• Packet Storm Security Exploits
• Packet Storm Security Recent Files
• Packet Storm Security Tools
• Packet Storm Security Misc. Files
• Sophos security news
• Sophos product advisories
• Penetration Testing
• SecuriTeam
• BackTrack Linux Forums
• Threatpost
• SecDocs
• carnal0wnage.attackresearch.com
• Carnal0wnage
• Kernel Fun
• Darknet
• The Exploitant
• Hack a Day
• Wirevolution

BackTrack Linux Forums

• October 05, 2011
• 

  AWUS036H won't get IP but connects to network through Backtrack...

  Posted: October 5th, 2011, 7:19am PDT by wlandymore

  Tags:   

  I know this sort of bridging between the actual NIC and Backtrack but I was wondering if someone could help me out with this.
  
  I have managed to get the built-in wireless on my laptop working properly with Backtrack and now I was going to use my Alpha Networks USB nic with Backtrack. I setup an 'open' network and it works for other computers getting an IP and connecting to the internet. I can also connect using the built-in wireless. However, the Alpha networks one doesn't get an IP like it's supposed to.
  
  When I run the 'iwconfig wlan1 essid "test" it connects and I can see the MAC of the AP, etc. However, it doesn't get the IP from the DHCP. Does anyone have any ideas about what might be preventing it? All of the other things seem okay and I didn't have to mess with the NIC to get it to plug and play. It just doesn't seem to get the IP so it can get out.
  
  I also can't seem to find a way to totally disable the built-in nic as well. I ran 'ifconfig wlan0 down' and it shuts off, but then when I try to use the Alpha one it comes back on and gets an IP and starts working again.
  
  Sorry, new to all of this.... :)
  
  may have been because I didn't boot up with it plugged in. I just put it in after BT was already loaded. Seems to have made a difference after I restarted it and then it came back up because I could get the monitoring going and was capturing packets with Wireshark using that interface. After I re-installed the driver for the built-in NIC that's working better too and is going up and down properly with the ifconfig.