** Bug watch added: Red Hat Bugzilla #446631
https://bugzilla.redhat.com/show_bug.cgi?id=446631
** Also affects: network-manager (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=446631
Importance: Unknown
Status: Unknown
--
NetworkManager does not use
** Changed in: network-manager (Fedora)
Status: Unknown = Confirmed
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree with Denis Benoit's last comment, and I have a little more to
add. The reason that /etc/NetworkManager/dispatcher.d/* scripts do not
provide the wealth of information as input that a dhclient-enter/exit-
hook script can take. According to the NetworkManagerDispatcher man
page, only two
A possible workaround, as well as additional confirmation of the bug,
is mentioned here: http://www.webtatic.com/blog/2009/03/workaround-so-
networkmanager-runs-dhclient-hooks/
From the site:
Sadly NetworkManager fails to call any hooks on dhcp renew, which is
what my script needed. It only
Summary changed to reflect the broader impact of this bug.
--
NetworkManager does not use dhclient-exit-hooks.d
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I encountered this bug too when debugging why the ntp information from
the DHCP server was ignored by the clients. Since all the information
from the DHCP server is not propagated by NetworkManager, the
/etc/NetworkManager/dispatcher.d/* scripts do not help. All the
necessary scripts/config
Alexander,
My question is, why is NM presuming to bypass the standard dhclient
actions? There are other packages that have specifically been
integrated with dhclient, and this integration is completely ignored
when using NM. If the /sbin/dhclient-script default action is
unsuitable, shouldn't
Also, having a look at the environment variables exposed to scripts in
/etc/NetworkManager/dispatcher.d, the WINS variables are *not* exposed,
only the basic TCP/IP options are; so this doesn't help samba or ntp.
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
Johan Ehnberg wrote:
My use case: Johan needs to access his laptop for doing backups and for
remote desktop services. :)
I can think of a few reasons why resolvconf is suboptimal:
- It is not the standard/recommended solution for DNSSEC, which is optimally
integrated with dhclient
- It
It turns out NetworkManager has its own mechanism for this. It took me a
while (almost no documentation...) to figure it out.
NM uses a dispatcher much like dhclient-exit-hooks.d. Instead of
separate directories, the script is always started, and given two
arguments: interface and action (which
NM runs dhclient with its own configs (from 'ps'):
/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/var/run/dhclient-eth0.pid -lf /var/run/dhclient-eth0.lease -cf
/var/run/nm-dhclient-eth0.conf eth0
ifup runs dhclient with the defaults:
dhclient3 -e IF_METRIC=100 -pf
Three confirmed reports.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirming this bug on KUbuntu Intrepid AMD64.
This also breaks automatic setting of WINS servers (/etc/dhcp3/dhclient-
enter-hooks.d/samba), which is necessary for proper SMB networking if
the network setup is non-trivial. In my case, I have a Samba server in a
different subnet that isn't
why do you need this? would using resolvconf and its hook mechanism
enough? we support resolvconf properly in intrepid.
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of
I can confirm this bug in intrepid.
I'm using a similar script in /etc/dhcp3/dhclient-exit-hooks.d to make a
ddnsupdate in my network and it is no more executed in intrepid. It was in
gutsy and hardy.
Removing network-manager or managing the relative interface in
/etc/network/interfaces solves
My use case: Johan needs to access his laptop for doing backups and for
remote desktop services. :)
I can think of a few reasons why resolvconf is suboptimal:
- It is not the standard/recommended solution for DNSSEC, which is optimally
integrated with dhclient
- It requires additional packages
** Attachment added: Output from manual run of dhclient
http://launchpadlibrarian.net/19287152/dhclient
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of Ubuntu
** Attachment added: Dynamic DNS update script
http://launchpadlibrarian.net/19287118/99dnssec
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: Relevant parts from /var/log/daemon.log
http://launchpadlibrarian.net/19287325/daemon.log
--
NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work
https://bugs.launchpad.net/bugs/293139
You received this bug notification because you are a member of
19 matches
Mail list logo
