dhcp 3.1.0 and Networkmanager

Message

pv23083 · Post by **pv23083** » Sat Sep 01, 2007 10:01 am

Hi!

I just updated to dhcp 3.1.0 and after that NetworkManager 0.6.5 couldn't get a correct ip address.
After downgrading again to dhcp 3.0.6 it start working well again.
Did this happen to anyone else?
Because dhclient works well so it should be any compatibility problem between dhcp 3.1.0 and Networkmanager or dhcdbd.

gotgot · Post by **gotgot** » Sat Sep 01, 2007 10:32 am

Hi!

It happens also to me... solved downgrading, as you did!

I have a problem also with wireless interface that still remains, but I'm not sure it is a dhcp issue.

di1bert · Post by **di1bert** » Sat Sep 01, 2007 10:33 am

What problem are you having with the Wireless connection ? I'm also battling
with the wireless side of NM and I'm about to pull out my hair.

It's a pity because NM is a great application...

-m

pv23083 · Post by **pv23083** » Sat Sep 01, 2007 10:35 am

gotgot wrote:Hi!

It happens also to me... solved downgrading, as you did!

I have a problem also with wireless interface that still remains, but I'm not sure it is a dhcp issue.

About the wireless I've only tried it once but when I did it locked my computer. When I associated to a AP I couldn't open any other apps, but if I already had firefox opened I could surf the net, so this is a quite weird problem. Anyway I've got try it more times.

gotgot · Post by **gotgot** » Sat Sep 01, 2007 10:57 am

I've an ipw3945 card. I havn't tried many times but I can't get a valid dhcp address from my AP. Also installing masked ipw3945 module doesn't seem to change the behaviour.

It's the first time I use this cards so I don't know if it works with the some old version of ipw3945{d|-ucode|}.

If someone has any hints...

Atko · Post by **Atko** » Sat Sep 01, 2007 12:32 pm

I have exactly the same problem with dhcp-3.1.0 and the networkmanager-0.6.5_p20070823

Downgrading dhcp to the version 3.0.6 worked for me.

I put the following line into /etc/portage/package.mask

Code: Select all

=net-misc/dhcp-3.1.0

robnotts · Post by **robnotts** » Sat Sep 01, 2007 2:30 pm

I think the downgrade is the "official" way to achieve success, hopefully fixed in the next version of networkmanager, which is a beautiful piece of software.

Even though I had my /etc/conf.d/net file set up perfectly, have abandoned that and gone the networkmanager route, just for the share ease of use.

Rob.

hornett · Post by **hornett** » Sun Sep 02, 2007 9:43 pm

Shouldn't the new version of dhcp be masked by network-manager? It took me two hours to get my system back online because of this and not having any other online machines available to search for help

Braempje · Post by **Braempje** » Mon Sep 03, 2007 7:22 am

This problems corresponds to [bug=185888]this bug[/bug], multiple solutions included there

ChrisPage · Post by **ChrisPage** » Thu Sep 06, 2007 12:55 pm

I just upgraded to dhcp-3.1 and dhcdbd-3.0 and they now work with networkmanager-0.6.5!!

phanboy_iv · Post by **phanboy_iv** » Wed Sep 12, 2007 9:09 pm

I also upgraded to dhcdbd 3.0 and dhcp-3.1, and it worked for a while,
but yesterday, it just stopped working again.

Anyone else have this problem? I didn't do any upgrades/removals or anything that should
have caused breakage.

GNUtoo · Post by **GNUtoo** » Wed Sep 12, 2007 11:09 pm

gotgot wrote:I've an ipw3945 card. I havn't tried many times but I can't get a valid dhcp address from my AP. Also installing masked ipw3945 module doesn't seem to change the behaviour.

It's the first time I use this cards so I don't know if it works with the some old version of ipw3945{d|-ucode|}.

If someone has any hints...

try first without network manager...(if you like Graphicals frontends try wifi-radar)
because your wireless card driver could not be the problem...
i have some problems with networkmanager but my wireless card is fine
(i have a rt2500 and i can't connect to a wifi network and i don't know how to get my card automaticaly up so networkmanager detects my networks)

dhcp 3.1.0 and Networkmanager

dhcp 3.1.0 and Networkmanager

same problem here too