LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (http://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   DHCP Server MAC Address found, IP address not assigned (http://www.linuxquestions.org/questions/linux-wireless-networking-41/dhcp-server-mac-address-found-ip-address-not-assigned-248768/)

wmburke 10-29-2004 11:04 AM

DHCP Server MAC Address found, IP address not assigned
 
I just installed Suse Linux 9.1. Everything is very fine, except for wireless networking.

At first:
My ethernet card installed properly and got an IP from the DHCP wireless access point.
My Linksys WPC11 V3 did the same.
I could connect to the internet through the ethernet card, but not the wireless.
Through the wireless, I could ping the access point and even access it via the browser interface, but not get to the outside world, not even able to ping an internet DNS server or google.com.

I added a gateway through YAST2 to the wireless card and disabled the ethernet card and now, no matter what I do I can't even get an IP address from the DHCP access point.

currently, ifconfig -a gives:

Quote:

eth0 Link encap:Ethernet HWaddr 00:01:03:83:A0:95
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)
Interrupt:10 Base address:0xe800

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:212 errors:0 dropped:0 overruns:0 frame:0
TX packets:212 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15968 (15.5 Kb) TX bytes:15968 (15.5 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:06:25:17:53:D3
inet6 addr: fe80::206:25ff:fe17:53d3/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16006 (15.6 Kb) TX bytes:3928 (3.8 Kb)
Interrupt:3 Base address:0x100
iwconfig shows:

Quote:

lo no wireless extensions.

wlan0 IEEE 802.11-DS ESSID:"."
Mode:Managed Frequency:2.437GHz Access Point: 00:80:C8:19:4A:15
Bit Rate:2Mb/s Tx-Power:2346 dBm
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:58/92 Signal level:-57 dBm Noise level:-98 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.
and the MAC address for the Access Point is accurate.

It seems that I'm getting a good hardware connection, but it's not being recognized somehow.

Thanks in advance for any advice.

darkleaf 10-29-2004 11:16 AM

RX packets:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:1 overruns:0 carrier:0

That's your error. Don't know what it is though. Maybe googling finds something?

wmburke 10-29-2004 11:35 AM

You mean because it dropped a packet? What should I google? I'm a little confused, please spell it out a little more for me...


By the way, this ifconfig and iwconfig were done not long after a reboot.

darkleaf 10-29-2004 11:50 AM

Uhmm I'm sorry I don't know where I got that from lol. Maybe I should go sleeping. Really sorry :(

wmburke 10-29-2004 12:47 PM

It's all cool...I just want my wireless card to work!

darkleaf 10-29-2004 02:18 PM

Can you try to set the IP and the rest manually the GUI sometimes doesn't work properly and in the command line you can easier find errors. The commands:
Code:

iwconfig wlan0 essid xxxx
ifconfig wlan0 x.x.x.x
route add default gw x.x.x.x

If you have set your AP as DNS server in /etc/resolv.conf it should work. If that works we can find how to get your dhcp working.

wmburke 10-29-2004 03:18 PM

Firstly, it didn't work. the only thing funny was when I entered the first command:
Code:

iwconfig wlan0 essid .
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; Operation not supported.

I checked my /etc/resolv.conf and saw the line:
Code:

nameserver: 192.168.0.1
which is as it should be.

After all of that, I end up with:
Code:

# ifconfig wlan0
wlan0    Link encap:Ethernet  HWaddr 00:06:25:17:53:D3
          inet addr:192.168.0.115  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::206:25ff:fe17:53d3/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8737 errors:0 dropped:0 overruns:0 frame:0
          TX packets:270 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2717962 (2.5 Mb)  TX bytes:147344 (143.8 Kb)
          Interrupt:3 Base address:0x100

the ip address is right...
Code:

# route
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
192.168.0.0    *              255.255.255.0  U    0      0        0 wlan0
loopback        *              255.0.0.0      U    0      0        0 lo
default        192.168.0.1    0.0.0.0        UG    0      0        0 wlan0

and Destination Host Unreachable when I ping the access point (192.168.0.1)

Now, I assume this doesn't matter, but in order to use the internet currently, I'm running a cable into eth0, and usiing:

Code:

ifdown wlan0
ifup eth0

and the opposite before testing out what you tell me to do...I assume this is ok?

when I run
Code:

ifdown eth0
ifup wlan0

I get the reply:
Code:

    wlan0    device: "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA"
    wlan0    configuration: wlan-bus-pcmcia
    wlan0    warning: using NO encryption
Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding.

I hope that the info I'm providing is useful and not just crap-filler to you.

It seems to be an interesting problem, no?

darkleaf 10-29-2004 03:21 PM

There's one thing that I see is kind of weird to me. It's your IP address. It's 192.168.0.0. while your router is 192.168.0.1 Doesn't it have to be something like 192.168.0.100 then?

darkleaf 10-29-2004 03:23 PM

And for the error with setting your essid, if your essid is correct now it doesn't matter. Otherwise you have to keep setting it till it works. But from your iwconfig it looks like it at least picks up an AP.

wmburke 10-29-2004 03:33 PM

hmmm...as

I assume your referring to the response to the route command. It shows the Destination as 192.168.0.0, but honestly, I'm not sure what that means. The IP address established for the wlan0 is 192.168.0.115 as shown in the ifconfig response.

Unless I'm misunderstanding what I'm reading.

I just did a route command while hooked up with eth0 and I get:
Code:

# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
192.168.0.0    *              255.255.255.0  U    0      0        0 eth0
link-local      *              255.255.0.0    U    0      0        0 eth0
loopback        *              255.0.0.0      U    0      0        0 lo
default        192.168.0.1    0.0.0.0        UG    0      0        0 eth0

so it seems that must be normal....thoughts????

Yeah, and on the essid, it does seem right, although it's strange that it wouldn't let me reset it...maybe it's because I was trying to reset it to the same thing?

darkleaf 10-29-2004 03:39 PM

Yeha now I notice it's the same for me. I don't have the link-local and loopback in it though. I don't know if it tells much but I have lo set to auto as well as wlan0 but lo doesn't show in my route. Could that be shown for you because it doesn't have a proper connection to the AP?

wmburke 10-29-2004 03:50 PM

I am certainly open to any possibility that leads to a solution...

How's that for a nice way of saying, "I really don't know."

Actually, the last route I posted was when I'm hooked to the internet through eth0, so there is a proper connection to the access point. The other end of the ethernet cable goes to a wireless bridge which communicates with the same AP, same DNS server, but it works through the eth0 and not through the wlan0...

So that must mean something else.

darkleaf 10-29-2004 03:55 PM

I don't know either. One last thing if that's a direct quote from your /etc/resolv.conf I'm not sure if the colon should be there. Mine just says

nameserver 192.168.1.1

wmburke 10-29-2004 04:05 PM

No. not a direct quote, just a paraphrase, as it were...

Well, thanks for the help. I'm not sure what else to do.

wmburke 11-09-2004 06:33 PM

Hey, here's something interesting:
Quote:

# /etc/init.d/pcmcia restart
Shutting down PCMCIA FATAL: Module ds is in use.
FATAL: Module pcmcia_core is in use.
failed
Starting PCMCIA done
Although, I admit I have no idea what it means...anyone?


All times are GMT -5. The time now is 08:59 AM.