[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.
[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
Bugs, which is subscribed to 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
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/105251
Title:
NetworkManager wrongly releases DHCP IP
To manage
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
Is this bug still present in Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/105251
Title:
NetworkManager wrongly releases DHCP IP
To manage notifications about this bug go to:
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
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 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
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
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
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
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
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 network-manager'
http://launchpadlibrarian.net/22982362/apt-get-network-manager.txt
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
** 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
Bugs,
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
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
When I understand this right, following stuff appeared from Hardy to
Intrepid:
a) (minor issue) dhclient-script is not started per default. So the path
to dhclient-script should be set right (to /sbin/dhclient-script) in
/etc/dhclient.conf
b) up to hardy, at the end in the dhclient-exit-hooks.d
Hm, interesting. I didn't know things changed in Intrepid. I changed
/etc/dhcp3/dhclient-exit-hooks.d/debug and asked it to print debugging
output to /tmp/dhclient-script.debug, yet when I reconnected to the
network, that file was not created. So it seems that network-manager
talks to the dhcp
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
Just a comment: 'exit' is not the only way to terminate a shell script
prematurely; if any of the scripts call 'set -e' and then any of the
commands executed after that fails (i.e. returns a non-zero exit code)
the script will terminate.
I would suggest the same debugging technique: adding
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
I can reproduce this in Intreprid since about one month. Note that I
came the upgrade path 7.10-8.04-8.10
DHCP via NetworkManager fails on wireless and wired interfaces.
package 'whereami' is not installed, the dpkg --purge workaround does not work
even after reinstalling whereami
and removing
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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 =
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.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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
Adding
exec /tmp/dhcp.debug 21
set -x
to the end of /etc/dhcp3/dhclient-exit-hooks.d/debug showed that the
culprit on one system was a whereami script that did 'exit 1'
prematurely, stopping /etc/dhcp3/dhclient-exit-hooks.d/_dhcdbd from
being run. Here's the relevant line of code:
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-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
The bug has now returned, after having installed ppa version of network-
manager 0.7 as well as tried (but reverted from) a customly compiled
2.6.25.8-rt7 kernel. This time however, I have not touched dhcp settings
files nor installed dnsmasq...
As stated in the very interesting blog post on this
@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
*** This bug is a duplicate of bug 45696 ***
https://bugs.launchpad.net/bugs/45696
Same here, this is not a duplicate of bug #45696 !
This bug is _not_ present in a clean install of Hardy. It seems to be
related to the installation of dhcp3-server and/or dnsmasq. A forum
thread describing
** This bug is no longer a duplicate of bug 45696
NetworkManager can't find interface on resume from suspend
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It is now correctly marked as a duplicate of Bug #155885 instead.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Bugs,
Typo, of course I meant the other way around:
Bug #155885 is now correctly marked as a duplicate of this bug.
Also, a better summary for this bug could be:
NetworkManager wrongly disconnects wireless after 99s, ignores working DHCP
lease. Bug evident after installing/configuring dhcp3-server
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
*** This bug is a duplicate of bug 45696 ***
https://bugs.launchpad.net/bugs/45696
I don't think this is a duplicate of bug #45696. I'm having the same
problem without any suspend to RAM or hibernation actions.
NetworkManager started showing this behaviour right after I ticked off
my Atheros
*** This bug is a duplicate of bug 45696 ***
https://bugs.launchpad.net/bugs/45696
** This bug has been marked a duplicate of bug 45696
NetworkManager can't find interface on resume from suspend
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You
Syslog output is attached.
** Attachment added: Syslog
http://librarian.launchpad.net/7243878/syslog.0
--
NetworkManager wrongly releases DHCP IP
https://bugs.launchpad.net/bugs/105251
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
56 matches
Mail list logo
