https://bugzilla.novell.com/show_bug.cgi?id=382693 User leo@nwfactory.net added comment https://bugzilla.novell.com/show_bug.cgi?id=382693#c1 --- Comment #1 from Leo Eraly <leo@nwfactory.net> 2008-06-05 08:07:22 MDT --- I did some further testing about this. It seems NetworkManager is using dhcpcd dhcpcd has a hook script (/etc/sysconfig/network/scripts/dhcpcd-hook) the hook script calls ifup ifup calls ifup-dhcp and in the ifup-dhcp script the following check is performed # send hostname for DDNS? case "$DHCLIENT_HOSTNAME_OPTION" in AUTO|auto) unset DHCLIENT_HOSTNAME_OPTION test -s /etc/HOSTNAME && read -t 1 FQHOSTNAME < /etc/HOSTNAME FQHOSTNAME=${FQHOSTNAME%%.*} # strip domain FQHOSTNAME=${FQHOSTNAME%% *} # must not contain spaces, just in case DHCLIENT_HOSTNAME_OPTION=$FQHOSTNAME ;; esac test -n "$DHCLIENT_HOSTNAME_OPTION" \ && args="$args -h $DHCLIENT_HOSTNAME_OPTION" This snippet will add a -h HOSTNAME option to the dhcp command

From the dhcpcd man page:

-h <hostname> specifies a string used for the hostname option field when dhcpcd sends DHCP messages. Some DHCP servers, notably those used by @Home Networks, require the hostname option field containing a specific string in the DHCP messages from clients. Some DHCP servers will use this hostname value to populate the DNS server. So the DNS registering is working in some cases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=382693 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382693#c2 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |leo@nwfactory.net --- Comment #2 from Tambet Ingo <tambet@novell.com> 2008-11-17 01:39:26 MST --- It doesn't matter which DHCP client (dhcpcd or dhclient), NetworkManager overrides these scripts in order to merge the IP information with existing info (like other active devices, possibly with VPN activated). NetworkManager doesn't try to do everything on it's own, it tries to provide hooks to be easily extensible. As you mention, the dispatcher scripts are ideal for that. They get called with two arugments: the interface name and string "up" or "down". The environment of the script has all the IP configuration information plus all the info from DHCP server. Specifically for this case, IP4_NAMESERVERS variable has all the name servers. To see all the information, create a dispatcher script that does "env >> /tmp/env" and activate a connection. It's probably not desirable to make this script run by default on all systems, but I think it would be nice to include such a script in the RPM package so it can be copied to the correct location. What's the exact command you'd like to execute? Use variables like $hostname $ip-address in your example. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.