...

I want my linux clients to setup their host names from a dhcp server. The IP-numbers works fine but the host name is always set to "linux".

Using Yast2 I have in the "Host name and DNS" module checked the "Change host name via DHCP". This I believe sets the variable DHCLIENT_SET_HOSTNAME=yes in the file /etc/sysconfig/network/dhcp. But nothing seemingly takes notice of that since host name still is "linux".

Does your DHCP server SEND a hostname to the clients. dhclient can't set the hostname unless it is actually sent. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.

For your question about the statement use-host-decl-names, I found the following reference in the man page for dhcpd.conf file (...) The use-host-decl-names statement use-host-decl-names flag; If the use-host-decl-names parameter is true in a given scope, then for every host declaration within that scope, the name provided for the host declaration will be supplied to the client as its hostname. So, for example, group { use-host-decl-names on; host joe { hardware ethernet 08:00:2b:4c:29:32; fixed-address joe.fugue.com; } } is equivalent to host joe { hardware ethernet 08:00:2b:4c:29:32; fixed-address joe.fugue.com; option host-name "joe"; } An option host-name statement within a host declaration will override the use of the name in the host declaration. It should be noted here that most DHCP clients completely ignore the host-name option sent by the DHCP server, and there is no way to configure them not to do this. So you generally have a choice of either not having any hostname to client IP address mapping that the client will recognize, or doing DNS updates. It is beyond the scope of this document to describe how to make this determination. (...) Hope that will help you. Bye Claude andersn@isy.liu.se wrote:

Hmm.. I suppose you mean the "use-host-decl-names on;" statement on the server side? What does that do?

Actually I'm pretty sure the server side works because many other PC's get their host names successfully (BSD and XP clients that is).

However, I just discovered that there is an executable, /sbin/dhclient, which in turn calls the script /sbin/dhclient-script, which looks for the file /etc/sysconfig/dhclient. BUT, I have no such file. So I made a soft link from /etc/sysconfig/dhclient to /etc/sysconfig/network/dhcp wich seems to be the file containing all the useful dhcp settings.

And now it works, host name is setup accordingly at startup. However I would not think this is the right way to do it, right?

Any thoughts upon this?

/Anders

On Mon, 30 Sep 2002 22:34:10 -0400 Claude Thibeault wrote:

...

Hi

In your file /etc/dhcpd.conf did you set the following?

group { use-host-decl-names on;

host little-blaine { hardware ethernet 00:04:5A:63:0A:EB; fixed-address 192.168.1.101; } }

good luck

Claude

andersn@isy.liu.se wrote:

...

Hi.

I want my linux clients to setup their host names from a dhcp server. The IP-numbers works fine but the host name is always set to "linux".

Using Yast2 I have in the "Host name and DNS" module checked the "Change host name via DHCP". This I believe sets the variable DHCLIENT_SET_HOSTNAME=yes in the file /etc/sysconfig/network/dhcp. But nothing seemingly takes notice of that since host name still is "linux".

The script /etc/init.d/boot.localnet sets host name to whatever is found in the file /etc/HOSTNAME, which currently is "linux.local". However I expected the DHCP setup to override this.

What am I missing here?

The clients are running SuSE 8.0.

/Anders

Anders Nilsson wrote:

Thanks, I suspected that "use-host-decl-names" would do something like that. Right now our server is using the 'option host-name "name";' syntax.

No thoughts upon my link to the /etc/sysconfig/network/dhcp file?

My gut feeling is that something is missing here. Like there is some package I have not installed that would tie things together for me so that I would not have to make that link.

Which dhcp client are you using? There are 2, dhcpcd and the ISC dhclient. You sound like you are getting info about the ISC dhcp server, which man dhcp-options is for both client/server, depending on option. Maybe you have dhcpcd installed, which would not be the same. YMMV. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.

Hello Anders Concerning your /etc/sysconfig/network/dhcp file, I don't have this file on my systems. As I see from one of your other E-mail, I don't use the same dchp client. Unfortunately, I have no knowledge of your dhcp client. Bye. Claude Anders Nilsson wrote:

Thanks, I suspected that "use-host-decl-names" would do something like that. Right now our server is using the 'option host-name "name";' syntax.

No thoughts upon my link to the /etc/sysconfig/network/dhcp file?

My gut feeling is that something is missing here. Like there is some package I have not installed that would tie things together for me so that I would not have to make that link.

/Anders

On Tue, 01 Oct 2002 18:54:50 -0400 Claude Thibeault wrote:

...

For your question about the statement use-host-decl-names, I found the following reference in the man page for dhcpd.conf file (...)

The use-host-decl-names statement

use-host-decl-names flag;

If the use-host-decl-names parameter is true in a given scope, then for every host declaration within that scope, the name provided for the host declaration will be supplied to the client as its hostname. So, for example,

group { use-host-decl-names on;

host joe { hardware ethernet 08:00:2b:4c:29:32; fixed-address joe.fugue.com; } }

is equivalent to

host joe { hardware ethernet 08:00:2b:4c:29:32; fixed-address joe.fugue.com; option host-name "joe"; }

An option host-name statement within a host declaration will override the use of the name in the host declaration.

It should be noted here that most DHCP clients completely ignore the host-name option sent by the DHCP server, and there is no way to configure them not to do this. So you generally have a choice of either not having any hostname to client IP address mapping that the client will recognize, or doing DNS updates. It is beyond the scope of this document to describe how to make this determination. (...)

Hope that will help you.

Bye

Claude

andersn@isy.liu.se wrote:

...

Hmm.. I suppose you mean the "use-host-decl-names on;" statement on the server side? What does that do?

Actually I'm pretty sure the server side works because many other PC's get their host names successfully (BSD and XP clients that is).

However, I just discovered that there is an executable, /sbin/dhclient, which in turn calls the script /sbin/dhclient-script, which looks for the file /etc/sysconfig/dhclient. BUT, I have no such file. So I made a soft link from /etc/sysconfig/dhclient to /etc/sysconfig/network/dhcp wich seems to be the file containing all the useful dhcp settings.

And now it works, host name is setup accordingly at startup. However I would not think this is the right way to do it, right?

Any thoughts upon this?

/Anders

On Mon, 30 Sep 2002 22:34:10 -0400 Claude Thibeault wrote:

...

Hi

In your file /etc/dhcpd.conf did you set the following?

group { use-host-decl-names on;

host little-blaine { hardware ethernet 00:04:5A:63:0A:EB; fixed-address 192.168.1.101; } }

good luck

Claude

andersn@isy.liu.se wrote:

...

Hi.

I want my linux clients to setup their host names from a dhcp server. The IP-numbers works fine but the host name is always set to "linux".

Using Yast2 I have in the "Host name and DNS" module checked the "Change host name via DHCP". This I believe sets the variable DHCLIENT_SET_HOSTNAME=yes in the file /etc/sysconfig/network/dhcp. But nothing seemingly takes notice of that since host name still is "linux".

The script /etc/init.d/boot.localnet sets host name to whatever is found in the file /etc/HOSTNAME, which currently is "linux.local". However I expected the DHCP setup to override this.

What am I missing here?

The clients are running SuSE 8.0.

/Anders