Bug #8540
closed
Force network-manager not to send the hostname
Added by Lukas Zapletal about 10 years ago.
Updated over 8 years ago.
Description
It looks like NM is still sending the hostname, which is bad thing for DHCP (a conflict with dracut can occur).
Make sure NM is configured NOT to send the DHCP client hostname:
gconftool-2 --type bool --set /system/networking/connections/<NUM>/ipv4/dhcp-send-hostname true
https://bugzilla.redhat.com/show_bug.cgi?id=469336
Backport to 0.6.
Here is a snippet where we see that dhclient was started with different hostnames, this can lead to DHCP conflicts eventually:
3024 tty1 Ssl+ 0:00 ruby /usr/bin/discover-host.rb
3049 ? Ss 0:00 /sbin/dhclient -H localhost -1 -q -lf /var/lib/dhclient/dhclient--eno1.lease -pf /var/run/dhclient-eno1.pid eno1
3162 ? Ss 0:00 /sbin/dhclient -H localhost -1 -q -lf /var/lib/dhclient/dhclient--eno2.lease -pf /var/run/dhclient-eno2.pid eno2
3239 ? S 0:00 [kworker/18:3]
3283 ? Ss 0:00 /sbin/dhclient -H dhcp-111 -1 -q -lf /var/lib/dhclient/dhclient--enp2s0f0.lease -pf /var/run/dhclient-enp2s0f0.pid enp2s0f0
3866 ? Ss 0:00 /sbin/dhclient -H dhcp-111 -1 -q -lf /var/lib/dhclient/dhclient--eth0.lease -pf /var/run/dhclient-eth0.pid eth0
3972 ? Ss 0:00 /sbin/dhclient -H dhcp-111 -1 -q -lf /var/lib/dhclient/dhclient--eth1.lease -pf /var/run/dhclient-eth1.pid eth1
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-discovery-image/pull/65 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous