Trouble obtaining ip address...

[eeijlar]

Hi,

I am using Opensuse 11.1 and the traditional network setup (ifup). Sometimes when I am establishing a wireless connection it gets stuck at 'Obtaining ip address...'. If I boot into windows I don't get this problem on the same network and the same machine. It happens on other networks too - a local café - works in Windows, but not Opensuse. This leads me to believe that there is something I don't have setup correctly in Opensuse since all the other factors (network, wireless keys etc) can be ruled out. Does anyone else have this problem?

Incidentally I am using wicd (wicd - home) to connect to the network. Knetwork manager doesn't work... probably for the same reason. Even if I rule out wicd by connecting manually from a command prompt it still gets stuck at the ip address stage. Again, not all the time, but often enough for it to be a pain )-:

[nimnull22]

Hi.

You can look into /var/log/messages or /var/log/warn and search for DHCP.

And when you will find out what is the problem or problems.

[eeijlar]

Thanks! I always forget about those logs. Here's /log/warn/

Oct 31 22:53:35 apollo kernel: nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
Oct 31 22:53:44 apollo kdm[3014]: XDMCP socket creation failed, errno 97
Oct 31 22:53:54 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:53:54 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:53:54 apollo dhcpcd[2968]: eth0: poll: No such file or directory
Oct 31 22:53:56 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:53:56 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:53:57 apollo dhclient: send_packet: Network is unreachable
Oct 31 22:53:57 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 22:53:59 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:53:59 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 22:54:05 apollo powersaved[3906]: WARNING (continueEvent:250) Could not execute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory
Oct 31 22:54:27 apollo smartd[4372]: Problem creating device name scan list
Oct 31 22:54:28 apollo SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Oct 31 22:54:29 apollo smartd[4372]: Device: /dev/sda, 1 Currently unreadable (pending) sectors
Oct 31 22:54:29 apollo smartd[4372]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost produced unexpected output (67 bytes) to STDOUT/STDERR:  method return sender=:1.9 -> dest=:1.21 reply_serial=2    uint16 0
Oct 31 22:54:35 apollo kernel: CE: hpet increasing min_delta_ns to 15000 nsec
Oct 31 23:02:11 apollo xinetd[3900]: Exiting...
Oct 31 23:03:04 apollo kernel: nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
Oct 31 23:03:13 apollo kdm[2511]: XDMCP socket creation failed, errno 97
Oct 31 23:03:24 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:24 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:24 apollo dhcpcd[2968]: eth0: poll: No such file or directory
Oct 31 23:03:27 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:27 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:28 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:03:28 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:03:32 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:32 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:03:52 apollo powersaved[3944]: WARNING (continueEvent:250) Could not execute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory
Oct 31 23:03:54 apollo kernel: CE: hpet increasing min_delta_ns to 15000 nsec
Oct 31 23:04:44 apollo dhclient: could not restore resolv.conf: No such file or directory
Oct 31 23:04:44 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:04:44 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:04:46 apollo dhcpcd[3272]: wlan0: poll: No such file or directory
Oct 31 23:04:46 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:04:46 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:04:46 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:04:46 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:04:52 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:04:52 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:06:01 apollo dhclient: could not restore resolv.conf: No such file or directory
Oct 31 23:06:01 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:06:03 apollo syslog-ng[1931]: last message repeated 3 times
Oct 31 23:06:03 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:06:03 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:06:41 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:06:41 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:07:11 apollo smartd[4566]: Problem creating device name scan list
Oct 31 23:07:11 apollo SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Oct 31 23:07:12 apollo smartd[4566]: Device: /dev/sda, 1 Currently unreadable (pending) sectors
Oct 31 23:07:12 apollo smartd[4566]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost produced unexpected output (68 bytes) to STDOUT/STDERR:  method return sender=:1.15 -> dest=:1.24 reply_serial=2    uint16 0
Oct 31 23:07:53 apollo dhclient: could not restore resolv.conf: No such file or directory
Oct 31 23:07:53 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:07:53 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:07:56 apollo kernel: iwl4965: Can't stop Rx DMA.
Oct 31 23:07:56 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:07:56 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:07:56 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:07:56 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:08:02 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:08:02 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:10:00 apollo dhclient: could not restore resolv.conf: No such file or directory
Oct 31 23:10:00 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:10:00 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:10:00 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:10:00 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:10:03 apollo kernel: iwl4965: Can't stop Rx DMA.
Oct 31 23:10:03 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:10:09 apollo syslog-ng[1931]: last message repeated 5 times
Oct 31 23:10:09 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:10:09 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:10:29 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:10:29 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:11:36 apollo dhclient: could not restore resolv.conf: No such file or directory
Oct 31 23:11:36 apollo dhclient: wmaster0: unknown hardware address type 801
Oct 31 23:11:38 apollo syslog-ng[1931]: last message repeated 3 times
Oct 31 23:11:38 apollo dhclient: send_packet: Network is unreachable
Oct 31 23:11:38 apollo dhclient: send_packet: please consult README file regarding broadcast address.
Oct 31 23:11:42 apollo xinetd[3951]: Exiting...

and /var/log/messages

Oct 31 23:10:32 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Oct 31 23:10:34 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Oct 31 23:10:37 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Oct 31 23:10:43 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Oct 31 23:10:50 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Oct 31 23:11:04 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Oct 31 23:11:18 apollo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Oct 31 23:11:33 apollo dhclient: No DHCPOFFERS received.
Oct 31 23:11:33 apollo dhclient: No working leases in persistent database - sleeping.

I don't know why it says No DHCPOFFERS??

[growbag]

Have you tried turning off ipv6? You can do that through the network devices part of Yast.

Maybe it's a driver problem, which wireless adapter do you have (use lspci or lsusb to find out).

Maybe also try using the latest 11.2 release candidate liveCD, see if the newer kernel helps. If it does, possibly change to a newer kernel.

NB These are just some simple suggestions until someone with more knowledge than me comes along .

[buckesfeld]

* eeijlar

as growbag said, 11.2RC2 is an option. It is *very* stable and it is the first version where KNetworkmanager in KDE4 actually does its job.

I've used wicd with 11.1 and had similar problems. Please check the wicd repo to get the latest version. This should normally fix it. If not: wicd handles different DHCP clients. If the "Auto" option in wicd doesn't work for you, try setting a DHCP client manually.

HTH
Uwe

[Akoellh]

Just a hint.

Would you expect to get an address for your wired ethernet interface via DHCP when the cable is not plugged in?

No, you wouldn't and the log does not show any information if your card was actually associated to the AP, although I can not say if it was associated or not, because there are no outputs on that either.

Without any useful information, making suggestions in what to update in which manner is just (maybe even good) guessing.

Updating the drivers for the already installed version (hint: compat-wireless) and actually posting valuable information on the problem (hint: read the stickies and provide outputs af the diagnostic script mentioned there) is certainly a more productive way.

[eeijlar]

Ok, thanks everyone for their replies. That's great. I think I will get 11.2 as soon as it is formally released.

[nimnull22]

That is not great.
If you want to do some more things, you can start "dhclient" manually.
After your network card associates with AP (under root and type "iwconfig wlan0" you have to see MAC address of the AP) type under root "dhclient" and see if it can get IPs.
But make sure that your wlan0 is associated with AP!

[soundlord]

Greetings !!

I have similar issue with suse 11.1, I'm trying to connect with the wireless interface I have but dhclient never received any dhcoffers...

I disabled the firewall but there is still issue with obtaining ip address from a router that I'm associated with... the signal is not good (2/5 under windows or 40% under linux iwlist) but under windows it works (i'm actualy connected with the same machine, same interface on the same router)...

I tried manually but it seems to fail again...
Impossible to ping the default gateway that is commonly 192.168.1.1 and I choosed the usual ip address given under windows as 192.168.1.7 with the usual 255.255.255.0 net mask...

knetworkmanager won't work also, impossible to connect I don't know where I could find logs to check what is wrong, ifup works better (at least i'm associated regarding iwconfig results) but I have no dhcp running... I disabled ipv6 feature and dhcpv6 there is nothing to do to get connected wireless under suse 11.1, that is frustrating because I did the live installation and I only remembered that the network was open at this time, now I got a wep (open) security established... when disabled it doesn't work anymore...

I can agree with switching to windows to have network but I need to do updates under linux (kernel headers needed) and now I will use another computer and connect the ethernet interface to have the network by sharing connexions using windows xp...

I will check the logs you refered to, I didn't checked it deeply to be true.

[lwfinger]

soundlord wrote:

Please do not hijack a thread with your problem. Each problem has a potential to
have a different solution. That way, someone else with a problem has a better
chance of finding the answer.

Before you open a new thread, please supply the PCI of USB IDs for your wireless
adapter. From that information, we will have a better chance of guiding you.