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.
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
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