DHCP Server MAC Address found, IP address not assigned
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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:
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?
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.
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?
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?
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.