Automatic DHCP assignment fails?

[Althernai]

Hi. I have just installed openSUSE 11.1 on my laptop and I am suffering from a rather strange problem: NetworkManager appears to be assigning completely bogus numbers for the IP address, Broadcast address and DNS of my wireless network.

The wireless card of my laptop is an Intel 4965 AGN. openSUSE interfaces with it using the iwlagn drivers and NetworkManager 0.70. The network is WEP and uses a shared key. The signal is strong (the router is across a single wall from me).

I have looked at dmesg and /var/log/NetworkManager and there are no errors -- in fact, if I switch to manual assignment of the IP and DNS numbers, the network works just fine. It also works just fine approximately 1 time out of 3 reboots with the automatic DHCP assignment.

Does anyone know what might be causing it screw up the IP assignment? The same exact network has been used by both this laptop and a different one (both with Windows) and we have never had this issue before.

[ab@novell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What do you mean by 'bogus numbers'? What is a normal set of values from
your other machine while it is working (or this one in the same state)?
You could try getting a LAN trace from the machine while it is doing the
DHCP negotiation to see if everything is working properly there.

Good luck.





Althernai wrote:
> Hi. I have just installed openSUSE 11.1 on my laptop and I am suffering
> from a rather strange problem: NetworkManager appears to be assigning
> completely bogus numbers for the IP address, Broadcast address and DNS
> of my wireless network.
>
> The wireless card of my laptop is an Intel 4965 AGN. openSUSE
> interfaces with it using the iwlagn drivers and NetworkManager 0.70. The
> network is WEP and uses a shared key. The signal is strong (the router
> is across a single wall from me).
>
> I have looked at dmesg and /var/log/NetworkManager and there are no
> errors -- in fact, if I switch to manual assignment of the IP and DNS
> numbers, the network works just fine. It also works just fine
> approximately 1 time out of 3 reboots with the automatic DHCP
> assignment.
>
> Does anyone know what might be causing it screw up the IP assignment?
> The same exact network has been used by both this laptop and a different
> one (both with Windows) and we have never had this issue before.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKG+3sAAoJEF+XTK08PnB5ASMP/3WHdc6VmF6gcb5va4uOGVwJ
WyHTALtBQQoo+YPf7XgDnbcc1dHRotUGYnnvb8X7FIhh2VsO9O QyMAQttaA58ZOU
xGqM3CzKVXmfRcFvHKriGvGRp49Kaxo2g4ObBuxTFP3UbM1qMU PyP/rK1grJ81ev
jUNOgcEbe98qlSmmpC3HT3KIZk1Ii5qpc47TrGYnmba5qM+9AM gC5EVy4Lx9aPlN
0dz3oiJDTR1ioUEBx4U+eCInBzHIN5wUyg7vicSIRnrYwjeD4V It5Dh10fuIKMkW
ZLEfmG/i0XZ2WNCOpLkF85RXE+Zdxt5kIaqK/iUx9Tyjr0x3RyHXjbjE6XKEq7zt
APEJo2OeVPs+aU8FIHJyZ5V7LksZcZqRM0IKSZbpaG5Rr8ZJfF tZkqmFJPeV17Mp
xOCNo/b1Sha4IDczO8ihLCpxATwMrKZaBCNi4IIxfuMQa6SAP6GPB5wM anC2VuyT
WnorTtluwQ2GBKw+X7IzQv2EnXPPZSDB25adfyo8RHQv41bUpV LiEheDiA5pPTWo
0pZJxYYErhn1f8knbl7NMmtfQ0dADkeDd7qiayYkUr9t6twAgv LNZYrxojfXz8gW
z/2oegDz5rUVPVqsWouruNsH0EK5Q6/DJbbWNJkFfepJ9d6JkFCne4YEC7Tdt32O
oDj/4wkWB7HjWnddVpD9
=wwl/
-----END PGP SIGNATURE-----

[Althernai]

By bogus numbers I mean that the numbers which work for that router are:

IP: 192.168.0.X
Broadcast: 192.168.0.255
Subnet: 255.255.255.0
DNS: 192.168.0.1

while the numbers it assigns automatically are something like 172.X.Y.Z for the IP and 64.X.Y.Z for the DNS. I will look into doing a LAN trace.

[ab@novell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'd definitely check a LAN trace. I'd be highly suspicious of Network
Manager just doing this on its own, though I think every network in the
world has had odd things like this happen from time to time when Virtual
Machine software was nearby and it had a rogue DHCP server, or whenever
there is a rogue DHCP server somewhere on the network. A LAN trace will
show this all fairly clearly.

Good luck.





Althernai wrote:
> By bogus numbers I mean that the numbers which work for that router
> are:
>
> IP: 192.168.0.X
> Broadcast: 192.168.0.255
> Subnet: 255.255.255.0
> DNS: 192.168.0.1
>
> while the numbers it assigns automatically are something like 172.X.Y.Z
> for the IP and 64.X.Y.Z for the DNS. I will look into doing a LAN trace.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKHHJ4AAoJEF+XTK08PnB53N8P/300sDhCONKZMvBiFaCbZndz
PFbzo5r89CJ5k84lPwcVC0gD38+9vpsJ9kwPNKkvZcwZvwVKZu eerCM3OvldmdXH
AQlkstAfvjEJqB436b7647/y+T/PXfz7ZFTD9q5yb0ZKzvQiPnGLVaoGPvJgDrs2
m+QJWSClu5yxGH7vYxMCYNjF02X27TTAEr9HJgV5izrYv/GgRlzMX64RaXSxPW9F
pqLFOgXDNhv2uWsYiQhFGBWvLYhCtE3SplSb1qc1JAuothYHGL oOaFsNJfBDJd44
ji0Sn/eaOhUoTICNvtkFt/2QWHNRNBEpYM6DZv/8U+tyv/FyEUqA0i3v2v+wROL8
IofQcoKcsPNB4dnm2yFbJJiUux3FXe5MjN2VAzMeBLBAB89ZIt SZVFJqh+JjN9iZ
siLlCkO/UR1JoYjNaWdA98aW2UbIIfeHNwaT6XAXEPSoQNRwuPfRzCNUDW 2FwykD
I+I1xp4u/bLu6rBaS203kWF+1LI9gZ7pZddUaZdLSmuzyArTbGxniwzyFNd BM4WS
XLo0NwOBjNan5By7Vr8SvtD4NjAegUesCWN2dMB0epYL5DsLQY 7iUhG6iVZMVAc7
RtXwlU2E9mmCqGS1Jgjnb9fQwwGMbD2O4Mme0W7Sox+i1EeHDi RUKD0OfeoSzOEr
Wu+sWJ2V7fMtV+L8WhHR
=+Jpe
-----END PGP SIGNATURE-----