[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=446631. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-05-15T14:05:51+00:00 Tom wrote: Description of problem: The traditional way to provide information which cannot be provided by DHCP (specifically in my case additional DNS domain names in search path) has been by writing an /etc/dhclient-exit-hooks script which can be used to edit the /etc/resolv.conf file after it is created by DHCP. This script is no longer being run when NetworkManager creates resolv.conf Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64 How reproducible: Every time I boot. Steps to Reproduce: 1. Boot system, observe NetworkManager generated resolv.conf does not have the changed dhclient-exit-hooks would have made. Actual results: see above Expected results: augmented search path in resolv.conf Additional info: I'd be happy to learn the "new way" to achieve the same thing dhclient-exit-hooks did, but on the other hand, I'd really wonder why there would need to be a "new way" other than obsessive OCD on the part of developers. How hard is it to just run the dadgum script if it exists? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/293139/comments/0 On 2008-05-18T22:51:47+00:00 Todd wrote: NetworkManager provides its own hooks into dhclient so that it can do its thing. You can get NetworkManager to call your script though. NetworkManager runs all scripts that are in /etc/NetworkManager/dispatcher.d. There should be at least one script in there to show you how things work. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/293139/comments/1 On 2008-07-10T18:51:02+00:00 Mike wrote: Scripts in /etc/NetworkManager/dispatcher.d/ do work, but they don't fully handle the sorts of things the dhclient-script and friends did. It's certainly less featureful. For example, when dhclient does a renew, NetworkManager does not run any script in /etc/NetworkManager/dispatcher.d/. Those only seem to be run when NetworkManager changes state on a device using either "up" or "down". NetworkManager's actions after the renew causes some other services to have to rediscover the interface: Jul 10 01:48:22 laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.1 port 67 Jul 10 01:48:22 laptop dhclient: DHCPACK from 192.168.1.1 Jul 10 01:48:22 laptop dhclient: bound to 192.168.1.6 -- renewal in 42559 seconds. Jul 10 01:48:22 laptop NetworkManager: DHCP: device wlan0 state changed bound -> renew Jul 10 01:48:22 laptop NetworkManager: address 192.168.1.6 Jul 10 01:48:22 laptop NetworkManager: netmask 255.255.255.0 Jul 10 01:48:22 laptop NetworkManager: gateway 192.168.1.1 Jul 10 01:48:22 laptop NetworkManager: nameserver '127.0.0.1' Jul 10 01:48:22 laptop avahi-daemon[2579]: Withdrawing address record for 192.168.1.6 on wlan0. Jul 10 01:48:22 laptop avahi-daemon[2579]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.6. Jul 10 01:48:22 laptop avahi-daemon[2579]: Interface wlan0.IPv4 no longer relevant for mDNS. Jul 10 01:48:22 laptop avahi-daemon[2579]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.6. Jul 10 01:48:22 laptop avahi-daemon[2579]: New relevant interface wlan0.IPv4 for mDNS. Jul 10 01:48:22 laptop avahi-daemon[2579]: Registering new address record for 192.168.1.6 on wlan0.IPv4. Jul 10 01:48:23 laptop NetworkManager: Policy set (wlan0) as default device for routing and DNS. I run openvpn as a service, outside of NetworkManager. Using the normal dhclient-script hooks, I can detect this action and restart the openvpn service when it happens. The /usr/libexec/nm-dhcp-client.action script NetworkManager runs from dhclient doesn't appear to be able to handle the same idea of hooks. Without a cronjob watching things, or modifying NetworkManager's init script to use the normal dhclient-script, I have to manually restart openvpn everytime DHCP renews. It tends to be less than transparent. Should this replacement for dhclient-script read and handle the same hooks files that dhclient-script itself uses, or should NetworkManager itself not make changes to an interface like this when a simple renew happens? Ideally, functionality replaced should not be a reduction. I'd like to see the hooks work. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/293139/comments/2
[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
** Changed in: network-manager (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager package in Debian: New Status in network-manager package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
** Bug watch added: Debian Bug tracker #537358 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537358 ** Also affects: network-manager (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537358 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager package in Debian: Unknown Status in network-manager package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
Has this been fixed in versions posterior to 14.04? Or is it waiting to reach "extra-hot" status? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
