Bug 546581 - NetworkManager does not send hostname to dhcp server
Summary: NetworkManager does not send hostname to dhcp server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-11 10:17 UTC by James Begley
Modified: 2010-12-04 01:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 469336
Environment:
Last Closed: 2010-12-04 01:48:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Begley 2009-12-11 10:17:24 UTC
+++ This bug was initially created as a clone of Bug #469336 +++

Description of problem:
NetworkManager does not send hostname to dhcp server

Version-Release number of selected component (if applicable):
NetworkManager-0.7.997-1.fc12.i686.rpm

How reproducible:
Always

Additional info:
I have a small home network, 2 laptops and a server.  I'm trying to connect the laptops to the server by specifying the hostname of the server, not the IP address - this used to work when the server was running ubuntu, but I've just put a completly clean install of fedora on it instead, and now I have to specify the IP address of the server to connect.

BZ #469336 seems to be exactly the issue that I'm seeing, but that claims to have been fixed against a fedora 11 build ... has there been a regession at some point in the last few builds?

[root@jumbo ~]# cat /var/run/nm-dhclient-wlan0.conf
# Created by NetworkManager



--- Additional comment from dcbw on 2008-10-31 11:51:40 EDT ---

fixed upstream either yesterday or the day before...

--- Additional comment from updates on 2008-11-23 17:55:19 EDT ---

NetworkManager-pptp-0.7.0-0.12.svn4326.fc10,NetworkManager-openvpn-0.7.0-16.svn4326.fc10,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc10,NetworkManager-0.7.0-0.12.svn4326.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/NetworkManager-pptp-0.7.0-0.12.svn4326.fc10,NetworkManager-openvpn-0.7.0-16.svn4326.fc10,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc10,NetworkManager-0.7.0-0.12.svn4326.fc10

--- Additional comment from updates on 2008-11-23 18:04:39 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc9,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc9,NetworkManager-openvpn-0.7.0-16.svn4326.fc9,NetworkManager-pptp-0.7.0-0.12.svn4326.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/NetworkManager-0.7.0-0.12.svn4326.fc9,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc9,NetworkManager-openvpn-0.7.0-16.svn4326.fc9,NetworkManager-pptp-0.7.0-0.12.svn4326.fc9

--- Additional comment from updates on 2008-11-23 18:07:13 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc8,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc8,NetworkManager-openvpn-0.7.0-16.svn4326.fc8,NetworkManager-pptp-0.7.0-0.12.svn4326.fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/NetworkManager-0.7.0-0.12.svn4326.fc8,NetworkManager-vpnc-0.7.0-0.11.svn4326.fc8,NetworkManager-openvpn-0.7.0-16.svn4326.fc8,NetworkManager-pptp-0.7.0-0.12.svn4326.fc8

--- Additional comment from john.uk on 2008-11-24 05:09:18 EDT ---

OK...but how do you get NetworkManager to send the hostname. Setting the desired hostname isn't nm-applet's UI (even in Fedora 10 Preview) and the hostname doesn't seem to get sent...

--- Additional comment from dcbw on 2008-11-24 10:46:06 EDT ---

Is this a system connection (ie an ifcfg file) or a connection you created yourself from the applet?

For the ifcfg file, make sure DHCP_HOSTNAME=<your desired hostname>.

For the user connection, use gconf-editor to drill down to your connection (in /system/networking/connections/) and in the ipv4 directory, add a string property with the name 'dhcp-hostname' and your desired hostname value there.  It's unlikely this will ever make it into the applet's UI, instead NM will (by default unless you override it with the methods above) simply send the current hostname of the machine, which I'm sure you've set to what you want it to be.

--- Additional comment from john.uk on 2008-11-24 11:04:41 EDT ---

OK, so that's rather what I expected the behaviour should be, but for me it's not working in a Fedora 10 Preview installation.

NetworkManager-glib-0.7.0-0.11.svn4229.fc10.i386
NetworkManager-gnome-0.7.0-0.11.svn4229.fc10.i386
NetworkManager-0.7.0-0.11.svn4229.fc10.i386
dhclient-4.0.0-30.fc10.i386

I'm trying to configure a system connection, but my chosen hostname does not end up being sent to the DHCP server.

/etc/sysconfig/network-scripts/ifcfg-eth0:
# Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
DEVICE=eth0
HWADDR=00:50:56:8a:2c:83
ONBOOT=yes
DHCP_HOSTNAME=vm-f10test.pace.internal

/var/run/nm-dhclient-eth0.conf:
# Created by NetworkManager


So, the dhclient config doesn't contain 'send host-name "vm-f10test.pace.internal";', like it needs to...

--- Additional comment from updates on 2008-11-26 01:14:44 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc8, NetworkManager-vpnc-0.7.0-0.11.svn4326.fc8, NetworkManager-openvpn-0.7.0-16.svn4326.fc8, NetworkManager-pptp-0.7.0-0.12.svn4326.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update NetworkManager NetworkManager-vpnc NetworkManager-openvpn NetworkManager-pptp'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-10263

--- Additional comment from updates on 2008-11-26 01:18:45 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc9, NetworkManager-vpnc-0.7.0-0.11.svn4326.fc9, NetworkManager-openvpn-0.7.0-16.svn4326.fc9, NetworkManager-pptp-0.7.0-0.12.svn4326.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update NetworkManager NetworkManager-vpnc NetworkManager-openvpn NetworkManager-pptp'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-10321

--- Additional comment from updates on 2008-11-26 01:22:59 EDT ---

NetworkManager-pptp-0.7.0-0.12.svn4326.fc10, NetworkManager-openvpn-0.7.0-16.svn4326.fc10, NetworkManager-vpnc-0.7.0-0.11.svn4326.fc10, NetworkManager-0.7.0-0.12.svn4326.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from john.uk on 2008-11-26 08:09:19 EDT ---

svn4326 doesn't fix it for me...

[root@localhost ~]# rpm -qa|grep NetworkManager
NetworkManager-gnome-0.7.0-0.12.svn4326.fc10.i386
NetworkManager-glib-0.7.0-0.12.svn4326.fc10.i386
NetworkManager-0.7.0-0.12.svn4326.fc10.i386
[root@localhost ~]# cat /var/run/nm-dhclient-eth0.conf 
# Created by NetworkManager

[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
DEVICE=eth0
HWADDR=00:50:56:8a:2c:83
ONBOOT=yes
DHCP_HOSTNAME=vm-f10test.pace.internal

--- Additional comment from updates on 2008-12-21 18:37:12 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc9, NetworkManager-vpnc-0.7.0-0.11.svn4326.fc9, NetworkManager-openvpn-0.7.0-16.svn4326.fc9, NetworkManager-pptp-0.7.0-0.12.svn4326.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from updates on 2008-12-21 18:42:26 EDT ---

NetworkManager-0.7.0-0.12.svn4326.fc8, NetworkManager-vpnc-0.7.0-0.11.svn4326.fc8, NetworkManager-openvpn-0.7.0-16.svn4326.fc8, NetworkManager-pptp-0.7.0-0.12.svn4326.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from axel.azerty on 2009-04-21 06:11:44 EDT ---

Doesn't work for me, using Fedora 11 beta :
NetworkManager-0.7.1-3.git20090414.fc11.i586 
NetworkManager-gnome-0.7.1-3.git20090414.fc11.i586


[root@axel-asus ~]# cat /var/run/nm-dhclient-eth0.conf
# Created by NetworkManager

[root@axel-asus ~]#

Comment 1 Bug Zapper 2010-11-04 03:37:41 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-12-04 01:48:48 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.