--- b...@iguanasuicide.net wrote:
From: "Boyd Stephen Smith Jr." <b...@iguanasuicide.net> To: debian-user@lists.debian.org Cc: urp...@linuxwaves.com Subject: Re: dhcpd tftp boot server configuration Date: Sun, 27 Feb 2011 12:36:20 -0600 In <20110225224107.36ea4...@resin06.mta.everyone.net>, urpion urpion wrote: ><DIV style="font-family:Arial, sans-serif; font-size:10pt;">Hello! I need [...] >declaration?<DIV><BR></DIV><DIV>here's what I got in >/etc/dhcp/dhcpd.conf</DIV><DIV><BR></DIV><DIV><DIV>#</DIV><DIV># Sample >configuration file for ISC dhcpd for >Debian</DIV><DIV>#</DIV><DIV>#</DIV><DIV><BR></DIV><DIV># The I can't understand you through the HTML. Also, it is against list policy to post in HTML. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/ Hello again! Sorry about the HTML. I don't know why that happened. I don't have any options to chang the content. If this doesn't work I'll have find another e-mail provider. Here I go again. I need some help configuring the isc-dhcp-server to serve squeeze boot images with tftp. The machine I want to serve with is an old PowerBook running squeeze. The client is an eMac. The network is private (not connected to the internet in any way. I have a router, but I may just use a crossover cabel. I'm not very good with networking. I'm not sure what to put for the domain-name option. Do I make this up? Do I need a DNS server like Bind, or will something in /etc/resolve.conf suffice?. The installation manual doesn't say anything about using a DNS server. Is the server-name the host name of the server? And am I defining the client host name in the host declaration? here's what I got in /etc/dhcp/dhcpd.conf # # Sample configuration file for ISC dhcpd for Debian # # # The ddns-updates-style parameter controls whether or not the server will # attempt to do a DNS update when a lease is confirmed. We default to the # behavior of the version 2 packages ('none', since DHCP v2 didn't # have support for DDNS.) ddns-update-style none; # option definitions common to all supported networks... option domain-name "local"; option domain-name-servers 192.168.1.254; #ns1.magnet.org, ns2.magnet.org; option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; server-name "macro"; default-lease-time 600; max-lease-time 7200; subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.10 192.168.1.100; option routers 192.168.1.1; } host emac { filename "yaboot"; server-name "macro"; next-server macro; hardware ethernet 00:0a:95:c2:30:54; fixed-address 192.168.1.10; } # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. # authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). # log-facility local7; # No service will be given on this subnet, but declaring it helps the # DHCP server to understand the network topology. #subnet 10.152.187.0 netmask 255.255.255.0 { #} # This is a very basic subnet declaration. # subnet 10.254.239.0 netmask 255.255.255.224 { # range 10.254.239.10 10.254.239.20; # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; } # This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend. #subnet 10.254.239.32 netmask 255.255.255.224 { # range dynamic-bootp 10.254.239.40 10.254.239.60; # option broadcast-address 10.254.239.31; # option routers rtr-239-32-1.example.org; #} # A slightly different configuration for an internal subnet. #subnet 10.5.5.0 netmask 255.255.255.224 { # range 10.5.5.26 10.5.5.30; # option domain-name-servers ns1.internal.example.org; # option domain-name "internal.example.org"; # option routers 10.5.5.1; # option broadcast-address 10.5.5.31; # default-lease-time 600; # max-lease-time 7200; #} # Hosts which require special configuration options can be listed in # host statements. If no address is specified, the address will be # allocated dynamically (if possible), but the host-specific information # will still come from the host declaration. #host passacaglia { # hardware ethernet 0:0:c0:5d:bd:95; # filename "vmunix.passacaglia"; # server-name "toccata.fugue.com"; #} # Fixed IP addresses can also be specified for hosts. These addresses # should not also be listed as being available for dynamic assignment. # Hosts for which fixed IP addresses have been specified can boot using # BOOTP or DHCP. Hosts for which no fixed address is specified can only # be booted with DHCP, unless there is an address range on the subnet # to which a BOOTP client is connected which has the dynamic-bootp flag # set. #host fantasia { # hardware ethernet 08:00:07:26:c0:a5; # fixed-address fantasia.fugue.com; #} # You can declare a class of clients and then do address allocation # based on that. The example below shows a case where all clients # in a certain class get addresses on the 10.17.224/24 subnet, and all # other clients get addresses on the 10.0.29/24 subnet. #class "foo" { # match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; #} #shared-network 224-29 { # subnet 10.17.224.0 netmask 255.255.255.0 { # option routers rtr-224.example.org; # } # subnet 10.0.29.0 netmask 255.255.255.0 { # option routers rtr-29.example.org; # } # pool { # allow members of "foo"; # range 10.17.224.10 10.17.224.250; # } # pool { # deny members of "foo"; # range 10.0.29.10 10.0.29.230; # } #} ... and my syslog has this: Feb 26 16:30:35 macro dhcpd: /etc/dhcp/dhcpd.conf line 33: expecting a declaration Feb 26 16:30:35 macro dhcpd: # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; Feb 26 16:30:35 macro dhcpd: ^ Feb 26 16:30:35 macro dhcpd: Configuration file errors encountered -- exiting Feb 26 16:30:35 macro dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1 Feb 26 16:30:35 macro dhcpd: Copyright 2004-2010 Internet Systems Consortium. Feb 26 16:30:35 macro dhcpd: All rights reserved. Feb 26 16:30:35 macro dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Feb 26 16:30:35 macro dhcpd: /etc/dhcp/dhcpd.conf line 33: expecting a declaration Feb 26 16:30:35 macro dhcpd: # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; Feb 26 16:30:35 macro dhcpd: ^ Feb 26 16:30:35 macro dhcpd: Configuration file errors encountered -- exiting ... line 33 is a closing bracket of the host declaration, which is for the eMac client? I haven't physically connected anything yet, but I believe that doesn't matters yet, right? I'll start plugging things in when the errors stop. Thank you kindly for your time and condiderstion. Yours sincerely Urpion _____________________________________________________________ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110310213327.36f23...@resin17.mta.everyone.net
