Re: [Cooker] Trouble with hostname on dhcp network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg Meyer wrote: I am having trouble with the hostname on my cooker box and can't figure out what is going on. I am updated through 20030227's Cooker. I am on a network with a dhcp server and have set a hostname in drakconnect. When I reboot, the machine is assigned an ip address by the dhcp server (192.168.0.6) and the hostname is set to dhcppc5. I know that the dhcp server is providing the hostname, but why doesn't the OS use the hostname I entered in drakconnect? The contents of my /etc/sysconfig/networking file: NETWORKING=yes GATEWAY=192.168.0.1 If I add a hostname and domain name to /etc/sysconfig/networking, it still boots up using dhcppc5 as the hostname. What is going on here? What have you got in /etc/sysconfig/network-scripts/ifcfg-eth? (NO I am not saying people should have to edit this by hand, I am trying to see what drakconnect should be doing). This is what I have to get the behaviour I want: [EMAIL PROTECTED] bgmilne]$ grep -i hostname /etc/sysconfig/network-scripts/ifcfg-eth0 NEEDHOSTNAME=yes DHCP_HOSTNAME=bgmilne-thinkpad [EMAIL PROTECTED] bgmilne]$ grep -i hostname /etc/sysconfig/network #HOSTNAME=localhost.localdomain HOSTNAME=bgmilne-thinkpad Shouldn't the hostname I provide in drakconnect override anything the DHCP server provides. I am not sure. What about in corporate networks, where if the name is assigned by dhcp, then dns entries get added (DDNS). If the user did not know this, and gets a different name as hostname to what was assigned to them, then we have the hostname lookup problem again. I see this has been dicussed before, but I don't see resolution. Why should I have to manually edit /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/networking to set a hostname on this machine. - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+XyYsrJK6UGDSBKcRAv2nAKCRDv1XFq35Cr9oz99lzdJhU9Y9OQCdFdHF FrOcAO1+83z6svNe4p/xMSQ= =lB9L -END PGP SIGNATURE-
Re: [Cooker] Trouble with hostname on dhcp network
On Friday 28 February 2003 04:04 am, Buchan Milne wrote: What have you got in /etc/sysconfig/network-scripts/ifcfg-eth? (NO I am not saying people should have to edit this by hand, I am trying to see what drakconnect should be doing). This is what I have to get the behaviour I want: [EMAIL PROTECTED] bgmilne]$ grep -i hostname /etc/sysconfig/network-scripts/ifcfg-eth0 NEEDHOSTNAME=yes DHCP_HOSTNAME=bgmilne-thinkpad [EMAIL PROTECTED] bgmilne]$ grep -i hostname /etc/sysconfig/network #HOSTNAME=localhost.localdomain HOSTNAME=bgmilne-thinkpad I can't be 100% sure Buchan because it was late when I did this last night. I do know that /etc/sysconfig/network-scripts/ifcfg-eth0 did not have an entry for DHCP_HOSTNAME until I ran drakconnect post-install. Perhaps this is because it never ran during install because I did a network install. But if drakconnect did not run during install because the network was already configured, that means the installer is not configuring the network properly when network.img is used. assigned by dhcp, then dns entries get added (DDNS). If the user did not know this, and gets a different name as hostname to what was assigned to them, then we have the hostname lookup problem again. Well, I would think that an admin on a corporate network that has dhcp set up is not going to want to fight with this, they would accept the default. What about the people on home network's that are the one's that will really care about this. Joe User, who really wants to name his computer after a famous jazz musician. How can you accomodate both sets of users? Here is what I am going to do to help the situation. I can't do it today, but I should have time to do about 5 installs this weekend using various scenarios of dhcp, non-dhcp, network vs. cd install. I will update Cooker tonight and create a set of install CD's (hopefully Warly has fixed the kernel selection issue) and do various network and cd installs and document my findings. I know time is of the essence at this pint (I meant point, maybe that is my subconscious rising to the surface ;-) ), and it would be nice to see this fixed/understood before rc2, but this is the best I can do given the rest of my schedule. To make sure I am looking at everything relevant, confirm these are the configuration files that matter. /etc/hosts /etc/host.conf /etc/resolve.conf /etc/dh-client.conf /etc/tmdns /etc/sysconfig/hostname /etc/sysconfig/network-scripts/ifcfg-eth0 Anything I missed? -- Greg
Re: [Cooker] Trouble with hostname on dhcp network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg Meyer wrote: On Friday 28 February 2003 04:04 am, Buchan Milne wrote: I can't be 100% sure Buchan because it was late when I did this last night. I do know that /etc/sysconfig/network-scripts/ifcfg-eth0 did not have an entry for DHCP_HOSTNAME until I ran drakconnect post-install. Perhaps this is because it never ran during install because I did a network install. But if drakconnect did not run during install because the network was already configured, that means the installer is not configuring the network properly when network.img is used. That is the case, and needs to be fixed ... when doing network installs, we actually do reset DHCP_HOSTNAME (or on 9.0 we ran drakconnect again) post-install. The installer should really give an option to reset configuration at the end IMHO ... assigned by dhcp, then dns entries get added (DDNS). If the user did not know this, and gets a different name as hostname to what was assigned to them, then we have the hostname lookup problem again. Well, I would think that an admin on a corporate network that has dhcp set up is not going to want to fight with this, they would accept the default. What about the people on home network's that are the one's that will really care about this. Joe User, who really wants to name his computer after a famous jazz musician. How can you accomodate both sets of users? tmdns should really handle this case AFAIK. Otherwise some test with $ host `hostname` |(test for good answer) || echo -e 127.0.0.1\t\t `hostname` /etc/hosts in initscripts. Here is what I am going to do to help the situation. I can't do it today, but I should have time to do about 5 installs this weekend using various scenarios of dhcp, non-dhcp, network vs. cd install. I will update Cooker tonight and create a set of install CD's (hopefully Warly has fixed the kernel selection issue) and do various network and cd installs and document my findings. Cool. But maybe also we need to have a summary of the desired behaviour? Fred? Florin? Otherwise we don't know what to file bugs for ... I know time is of the essence at this pint (I meant point, maybe that is my subconscious rising to the surface ;-) ), and it would be nice to see this fixed/understood before rc2, but this is the best I can do given the rest of my schedule. To make sure I am looking at everything relevant, confirm these are the configuration files that matter. /etc/hosts /etc/host.conf /etc/resolve.conf /etc/dh-client.conf /etc/tmdns IIRC, /etc/tmdns.conf /etc/sysconfig/hostname /etc/sysconfig/network-scripts/ifcfg-eth0 Output of 'hostname' Output of 'host `hostname`' Output of 'nslookup -sil `hostname`' Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+X31JrJK6UGDSBKcRAq6cAKCRUwj8tYOc6UYvm9E6r8r+1/4h6wCgiREd 8OPXGmVVYi4qaQHH9GeEa50= =Sre2 -END PGP SIGNATURE-
Re: [Cooker] Trouble with hostname on dhcp network
On Friday 28 February 2003 10:16 am, Buchan Milne wrote: Cool. But maybe also we need to have a summary of the desired behaviour? Fred? Florin? Otherwise we don't know what to file bugs for ... That would be great. Of course I don't need it in time to do the testing, but it would be needed to evaluate the results. /etc/hosts /etc/host.conf /etc/resolve.conf /etc/dh-client.conf /etc/tmdns IIRC, /etc/tmdns.conf /etc/sysconfig/hostname /etc/sysconfig/network-scripts/ifcfg-eth0 Output of 'hostname' Output of 'host `hostname`' Output of 'nslookup -sil `hostname`' Thank you -- Greg
Re: [Cooker] Trouble with hostname on dhcp network
On Thursday 27 February 2003 10:51 pm, Greg Meyer wrote: I am having trouble with the hostname on my cooker box and can't figure out what is going on. I am updated through 20030227's Cooker. I am on a network with a dhcp server and have set a hostname in drakconnect. When I reboot, the machine is assigned an ip address by the dhcp server (192.168.0.6) and the hostname is set to dhcppc5. I know that the dhcp server is providing the hostname, but why doesn't the OS use the hostname I entered in drakconnect? The contents of my /etc/sysconfig/networking file: NETWORKING=yes GATEWAY=192.168.0.1 If I add a hostname and domain name to /etc/sysconfig/networking, it still boots up using dhcppc5 as the hostname. What is going on here? I'll confess that i forgot to check the contents of /etc/sysconfig/network-scripts/ifcfg-eth0 after I reran draconnect, and the hostname is set in there properly. If that is the case, why would that not override the dhcp server assigned hostname? -- Greg
Re: [Cooker] Trouble with hostname on dhcp network
On Thursday 27 February 2003 11:04 pm, Greg Meyer wrote: On Thursday 27 February 2003 10:51 pm, Greg Meyer wrote: I am having trouble with the hostname on my cooker box and can't figure out what is going on. I am updated through 20030227's Cooker. I am on a network with a dhcp server and have set a hostname in drakconnect. When I reboot, the machine is assigned an ip address by the dhcp server (192.168.0.6) and the hostname is set to dhcppc5. I know that the dhcp server is providing the hostname, but why doesn't the OS use the hostname I entered in drakconnect? The contents of my /etc/sysconfig/networking file: NETWORKING=yes GATEWAY=192.168.0.1 If I add a hostname and domain name to /etc/sysconfig/networking, it still boots up using dhcppc5 as the hostname. What is going on here? I'll confess that i forgot to check the contents of /etc/sysconfig/network-scripts/ifcfg-eth0 after I reran draconnect, and the hostname is set in there properly. If that is the case, why would that not override the dhcp server assigned hostname? Okay, I got the hostname to change by manually adding a hostname to /etc/sysconfig/network. This did not work before I reran drakconnect post install. So it seems bith files must have the hostname set in order to override the dhcp assigned name. So, to summarize, the installer did nothing on network configuration to set hostname and just accepted the default provided by the dhcp server, despite the fact that I had set hostname during install. I had to run drakconnect post install to set the dhcp-hostname name in /etc/sysconfig/network-scripts/ifcfg-eth0 and then make a manual entry in /etc/sysconfig/hostname to get the hostname to be applied. Can this be possible. Do I need to try this again to make sure this is what happened. Does the fact that I had to do this manually indicate a bug in drakconnect, or did I do something wrong? And even though I set the hostname/domain during install, why didn't either /etc/sysconfig/network-scripts/ifcfg-eth0 or /etc/sysconfig/hostname reflect what I entered when examined immediately following install. -- Greg
Re: [Cooker] Trouble with hostname on dhcp network
On Friday 28 February 2003 03:51, Greg Meyer wrote: I am having trouble with the hostname on my cooker box and can't figure out what is going on. I am updated through 20030227's Cooker. I am on a network with a dhcp server and have set a hostname in drakconnect. When I reboot, the machine is assigned an ip address by the dhcp server (192.168.0.6) and the hostname is set to dhcppc5. This is because of the default behavoiur of dhclient (the now default dhcp client). You need to create an overly complex dhclient.conf man dhclient.conf Really dhclient.conf looks like something that you need to be an administrator to configure, and while that is OK for most of the loonies on this list, IT IS NOT OK for normal people. -- John Allen, Email: mailto:[EMAIL PROTECTED] MandrakeClub Silver Member.
