10:08 a.m.
I don't think you need to mess with the DHCP template at all; It's just
a matter of making sure you have --static enabled so the installed host
doesn't try to do a DHCP query. Here's my /etc/dhcp/dhcpd.conf which
uses 10.1.1.1 as my cobbler server. The host gets installed over a
crossover cable to my laptop, and then, I plug it in to the real network
and it runs statically as 10.16.253.14.
Sorry it's so hard to read with the multiple levels of NAT!
/a
# ******************************************************************
# Cobbler managed dhcpd.conf file
# generated from cobbler dhcp.conf template (Mon Mar 21 02:02:54 2011)
# Do NOT make changes to /etc/dhcpd.conf. Instead, make your changes
# in /etc/cobbler/dhcp.template, as /etc/dhcpd.conf will be
# overwritten.
# ******************************************************************
ddns-update-style interim;
allow booting;
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 10.0.0.0 netmask 255.0.0.0 {
option routers 10.0.0.1;
option domain-name-servers 192.168.1.1, 68.237.161.12;
option subnet-mask 255.0.0.0;
range dynamic-bootp 10.1.1.100 10.1.1.254;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.1.1.1;
}
# group for Cobbler DHCP tag: default
group {
host generic4 {
hardware ethernet 00:21:9B:FC:26:C3;
fixed-address 10.16.253.14;
option host-name "wb2zii-15";
option subnet-mask 255.255.255.224;
option routers 10.16.253.1;
filename "/pxelinux.0";
next-server 10.1.1.1;
}
On 03/21/2011 10:53 AM, Daniel Kertby wrote:
That's right, I don't want the DHCP server to answer DHCP
requests
from nodes not setup using Cobbler during
the installation part (after assigning hostname/ip/mac). The system
then should have the same IP which was assigned during the Cobbler
setup/install.
As soon as I remove 'range dynamic-bootp' from the dhcp.template file,
it stops working,
How should I set this up in the cleanest/simpliest way?
We will also have it multi-homing for appr. 10 networks (vlans)
/Daniel
On Mon, Mar 21, 2011 at 3:30 PM, Alan Crosswell <n2ygk(a)weca.org
<mailto:n2ygk@weca.org>> wrote:
If I understand what you are saying, I believe what you do is have the
DHCP server assign IP addresses that it will respond to (so you have
supply your system's MAC address) to that it can properly do the PXE
boot and kickstart installation. You can then configure your
system to
use static addresses (non-DHCP) going forward by doing whatever the
command line equivalent of unchecking the DHCP box is in the web UI.
--static=1?
On 03/21/2011 10:13 AM, Daniel Kertby wrote:
>
> Hi,
>
> I've been investigating how to setup Cobbler to use the local DHCP
> server to setup static entries but
> without success.
>
> when executing 'cobbler system add ...' I want Cobbler to use the
> --ip-adress= and mac-address= variables to
> setup the DHCP server to have the static mapping. I cannot find any
> good documentation and my trials have failed.
>
> Anyone?
>
> Regards,
> Daniel
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
<mailto:cobbler@lists.fedorahosted.org>
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org>
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler