lynn said the following on 04/03/2012 02:29 AM:
On 02/04/12 20:21, Anton Aylward wrote:
lynn said the following on 04/02/2012 12:26 PM:
El 02/04/12 14:29, Anton Aylward escribió:
Carlos E. R. said the following on 04/02/2012 05:18 AM:
On 2012-04-02 10:13, lynn wrote:
Every linux machine should have that. I don't know if the dhcp server can assign it.
Yes it can; yes it should. But lynn says that here DHCP server is only handing out IP addresses, therefore she has not configured it correctly.
I don't want just any name. I want the name that I give to the computer.
Yes I can understand that. By my assertions still hold. The DHCP server should be handing out more than just IP addresses.
Have you read /etc/sysconfig/network/dhcp? DHCLIENT_BIN=""
DHCLIENT6_BIN=""
DHCPCD_USER_OPTIONS=""
DHCLIENT_USER_OPTIONS=""
DHCP6C_USER_OPTIONS=""
DHCLIENT_DEBUG="no"
DHCLIENT_PRIMARY_DEVICE=""
DHCLIENT_SET_HOSTNAME="no"
DHCLIENT_SET_DEFAULT_ROUTE="no"
DHCLIENT_LEASE_TIME=""
DHCLIENT_USE_LAST_LEASE="yes"
DHCLIENT_TIMEOUT="0"
DHCLIENT_HOSTNAME_OPTION=""
DHCLIENT_CLIENT_ID=""
DHCLIENT_VENDOR_CLASS_ID=""
DHCLIENT_RELEASE_BEFORE_QUIT="no"
DHCLIENT6_RELEASE_BEFORE_QUIT="no"
DHCLIENT_SLEEP="0"
DHCLIENT_WAIT_AT_BOOT="15"
WRITE_HOSTNAME_TO_HOSTS="no" DHCLIENT_MODIFY_SMB_CONF="yes"
Maybe WRITE_HOSTNAME_TO_HOSTS="yes" ?
I asked for the result of running "ps -ef | grep dhcpcd" on the client after its up and running.
ps -ef | grep dhcpcd root 2108 1 0 08:21 ? 00:00:00 /sbin/dhcpcd --netconfig -L -E -G -c /etc/sysconfig/network/scripts/dhcpcd-hook -t 0 eth0
Well, there's one problem. You DHCP isn't doing what you thought it was doing. Check you MAN page for DHCPCD. There is the "-f" parameter in which the client tells the server what name it wants to use. You have said you want the clients determining their won names, not having one forced on them by the DHCP server. However that is *NOT* how you have it set up. The WRITE_HOSTNAME_TO_HOSTS="yes" means that host name supplied by the DHCP server gets written to the clients /etc/host file. Based on what you told us in previous emails that is *NOT what you want. The So what does that DHCPCD parameter set mean? Dis this what you really want? -t 0 <quote> -t, --timeout seconds Timeout after seconds, instead of the default 20. A setting of 0 seconds causes dhcpcd to wait forever to get a lease. </quote> That is your
DHCLIENT_TIMEOUT="0" setting. Do you want to 'wait forever"?
-G <quote> -G, --nogateway Don't set any default routes. </quote> That is your
DHCLIENT_SET_DEFAULT_ROUTE="no" setting. That must mean your network has no connectivity to any other network.
-L <quote> -L, --noipv4ll Don't use IPv4LL at all. </quote> See http://en.wikipedia.org/wiki/Link-local_address This suppresses the use of the Link-local route - (165.254.0.0/16) and repeated retries if the server isn't responding. See "-t 0" Is this what you want? Do you understand why you should or should not want this fall-back mode? My best guess is that your problems arise because of naming and identification issues doe to an incomplete configuration. The default of dhcpcd is to send the host name to the DHCP server but you have
DHCLIENT_SET_HOSTNAME="no" and there is no "-h hostname". In my /etc/dhcp.conf I have hostnames, as I mentioned in a previous post, and the stanzas determine specific characteristics for those hosts; this I can set specific routers, name severs, lease times and whatever.
You have said that you want the hosts to always have the same names. There are basically two ways to do that. 1) they know their names and they tell the DHCP server In this case the DHCP server should also be able to use the DDNS protocol -- if you have that set up, and the evidence is that you don't - to tell the DNS server to dynamically insert forward and reverse RRs into its in-memory DNS map. *NOT* the on-disk file. 2) the dhcp server is configured in terms of names and maps MAC addresses to names because the stanzas are written that way. Those same stanzas can arrange that a particular MAC address is always assigned the same IP address (BTDT)and so you can set up static (aka on disk files) DNS tables. This is what I refer to as a "cheat". DHCP makes sense when you have a large number of possible clients but only a few connected at a particular time and so need to re-assign IP addresses. It worked great when I was running a dial-up ISP :-) But on a lot of LANs its not used like that. The number of clients is fixed and does not exceed what's available on the RFC1918 subnet (192.168.1/24 in your case). In this situation the fixed binding of MAC address to IP address and the stanza having the name of the host is fine. It simplifies debugging and set up of DNS. Example: host trixbox0 { hardware ethernet 00:60:B0:F7:1B:3C ; fixed-address 192.159.2.10 ; } If you are not willing to adopt that approach, then I would at least set
DHCLIENT_SET_HOSTNAME="yes" so the client *does* tell the DHCP server its name and there is no ambiguity about that.
As for
DHCLIENT_MODIFY_SMB_CONF="yes" I'm sorry, I have no idea what that is doing.
This is back to network sniffing .... -- "Television is a medium because it is neither rare nor well done." -- Fred Friendly -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org