LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Wireless card FINALLY configured but can't connect to NET (https://www.linuxquestions.org/questions/linux-wireless-networking-41/wireless-card-finally-configured-but-cant-connect-to-net-479489/)

littlec 09-01-2006 12:52 PM

Wireless card FINALLY configured but can't connect to NET
 
the progression is at: (cant post url yet)

I've been running ubuntu and just purchased a D-Link DWL-G132 usbcard for wireless internet. I have the drivers and settings using ndiswapper.

iwconfig returns:

wlan0 IEEE 802.11g ESSID:"(essid)"
Mode:Managed Frequency:2.457 GHz Access Point: 00:C0:02:F9:EE:D0
Bit Rate:54 Mb/s
Encryption key:(keyname) Security mode:open
Link Quality:0/100 Signal level:-53 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

------------------

When i try to renew the dhcp settings from the router, it gives me no DHCPoffers received.

Any suggestions? I tried /etc/resolv.conf and also disabling ip4 but still no luck.

This is so frustrating. I've been spending over 20 hours reading/configging now and still nothing.

Any help is greatly appreciated

thank you

2Gnu 09-01-2006 01:01 PM

Link Quality:0/100

That doesn't look right. Double-check the WEP key. Look at the router logs to see if there's any indication that association is taking place (not all routers will show this) or if there are any errors relative to the DHCP server.

Make sure wlan0 is up before trying to get an IP:
ifconfig wlan0 up
dhclient wlan0 (I think that's the correct syntax for Ubuntu)

littlec 09-01-2006 01:40 PM

2gnu, thanks for the quick reply.

wlan0 is up, and i even put it down then back up several times just to be safe. here is what the dhclient replies.

Listening on LPF/wlan0/00:11:95:bb:59:a8
Sending on LPF/wlan0/00:11:95:bb:59:a8
Sending on Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
Trying recorded lease 192.168.0.4
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.585/0.585/0.585/0.000 ms
bound: renewal in 48820 seconds.
-----------

the WEP key i entered is correct, but I do not know if the syntax is correct (when i left the network as unsecured I had no problems connecting to the internet). So as I suspected earlier, it's possible that it is something to do with the wep?

sudo iwconfig wlan0 key s:(enter Ascii key here) open

then when i do an iwconfig, it lists the encrypted key in xxxx-xxxx-xxxx-xxxx form (all numerical).

maybe i'll just try it as hexadecimal too. (didnt 'work before but i'l give it atry)/

littlec 09-01-2006 01:49 PM

YES!

FINALLY WORKING.

I went into my Router settings and looked more carefully into the WEP settings....

there was a setting for 'keytype' either open or shared or automatic. It was set on auto, i put it on 'open'. And now i am surfing wirelessly:)

Now i want to try and get wpa working (wpa supplicant), as well as my card to work in the i686 kernel. It creates hard locks in the i686 kernel. I believe i need to blacklist some drivers.

I also no longer used the key as s:(ascii string). Perhaps the key i had was hexidecimal?

I entered the key as:

sudo iwconfig wlan0 key (XyyXyXyXXX) where X is #'s and y = letters.
did a dhclient and it gave me success:

DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPNAK from 192.168.0.1
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1


-------

perhaps i simply entered hte key wrong?

littlec 09-01-2006 01:59 PM

*edit: i am the dork that entered a hexidecimal key as a string
ALL other settings have to be in check as well at the same time for everything to work. It's like a game of combinations.

2Gnu 09-01-2006 04:16 PM

Makes you wonder about those guys who show up a security conference and demonstrate the latest exploit that has them breaking into a secure WLAN in 30 seconds, huh?

:)

littlec 09-02-2006 02:04 AM

Quote:

Originally Posted by 2Gnu
Makes you wonder about those guys who show up a security conference and demonstrate the latest exploit that has them breaking into a secure WLAN in 30 seconds, huh?

:)

forget a password? nahhh no problem, we'll just exploit it:D


All times are GMT -5. The time now is 01:19 AM.