[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/105251
Title:
NetworkManager wrongly releases DHCP IP
Is this bug still present in Precise?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/105251
Title:
NetworkManager wrongly releases DHCP IP
To manage notifications about this bug
After upgrading to Jaunty, DHCP worked for Ethernet Connections (before
Jaunty, dhcp worked neither with eth nor with wlan). So i replaced the
ath5k driver with the atheros madwifi one, and now everything workes
without problems. Hmm - would be interesting if the problem was caused
by the wlan
Can somebody please fix this problem in the PPA port for Hardy, please.
We run our servers in Hardy and we would not want to upgrade system to
Intrepid. Hardy is a LTTS.
We are experiencing exactly same problem described here.
Please if you can help.
--
NetworkManager wrongly releases DHCP IP
can't confirm dependency of protected vs open mode - for me, problem
occurs in any case - connecting via ethernet cable, via open Wifi and
via WPA-PSK-protected wifi. tested with two different routers.
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received
I've the same problem on a just installed ubuntu. I took notice that
this issue arose only when my wifi router configured in a protected mode
(WPA-PSK/WPA2-PSK, TKIP+AES). In an open mode wifi is OK. Hope this
notice will helpful.
--
NetworkManager wrongly releases DHCP IP
fix mentioned by austriaco: https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/105251/comments/24 doesnt work
** Changed in: network-manager (Ubuntu)
Status: Fix Released = Confirmed
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You
Network-manager calls dhclient with -sf option set to
/usr/lib/NetworkManager/nm-dhcp-client.action which means dhclient
doesn't run the traditional dhclient-script upon acquiring the Lease.
$ sudo /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/var/run/dhclient-eth0.pid
sorry, still not working. i've installed the version
0.7-0ubuntu1~nm1~intrepid1, but no change. The following versions are
installed:
flor...@qacha:~$ sudo apt-cache showpkg libnm-glib0
[sudo] password for florian:
Package: libnm-glib0
Versions:
0.7-0ubuntu1~nm1~intrepid1
I have the same problem and still the hardy versions of network manager,
libnm and libdus (?), but updating them to intrepid didn't help form me.
I've attached the content of dhcp.debug and the apt-cache information
regarding network-manager and libnm-glib0.
** Attachment added: Output of
** Attachment added: Output of 'sudo apt-cache showpkg libnm-glib0'
http://launchpadlibrarian.net/22982397/apt-get-libnm-glib0.txt
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Server
For some reason I still had the old hardy packages of network-manager
and libnm installed. Note that I came the upgrade path 7.10-8.04-8.10
. After forcing the versions from intreprid-updates everything is fine
again.
--
NetworkManager wrongly releases DHCP IP
Marius: no, the reason for that is, that dhclient-script is not started.
Just uncomment the dhclient-scprit entry and set it to the right path
does fix that issue and you get the debugging output. But then it does
not return to nm. wich is the real issue.
--
NetworkManager wrongly releases DHCP
Reopening as requested
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
The timeout bugs you see in syslog attached are fixed in latest WPA
supplicant in combination with improved driver runtime behaviour. Thus,
I assume this is fixed in intrepid now. if you can still reproduce
there, please reopen.
** Changed in: network-manager (Ubuntu)
Status: Confirmed =
Interesting about the whereami thing, but I have never installed
whereami and still experiencing this bug. May be a solution for others
though...
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of
Motin: check the other dhclient hooks:
grep exit /etc/dhcp3/dhclient-exit-hooks.d/*
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
The whereami bug was already reported as bug 239740
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
@Guillaume (Blog post author): I tried your proposed workaround (adding
|new_server_name|old_server_name to the dhcdbd exit hook) but
unfortunately it didn't change the situation at all for me. I am still
getting...:
Jul 16 03:18:44 motin-laptop NetworkManager: info dhclient started with pid
Note once again, however, that the bug is not evident on a freshly
installed system.
We ought to be able to inspect the differences in /etc between working
and non-working systems to able to work out a solution for affected
systems without needing to reinstall Ubuntu...
** Also affects: dhcp3
21 matches
Mail list logo
