Menu ▾ ▴

#718 dhcp configuration issues

open
nobody
Packages (227)
5
2005-09-05
2005-09-05
Carl Staelin
No

In our case, we sometimes boot cluster machines with
other operating systems, but still use DHCP to assign
IP addresses, get gateway/routing information, and find
nameservers. The default (OSCAR 4.1) scripts to call
mkdhcpconf don't properly initialize all this
information based on the root node's configuration. I
modified /opt/oscar/lib/OSCAR/MAC.pm to correctly
handle this information based on /etc/resolv.conf and
'netstat -rn' output, at least for our system(s).

I have attached a patch file which shows my changes.

Discussion

  • Carl Staelin

    Carl Staelin - 2005-09-05

    patch file for /opt/oscar/lib/OSCAR/MAC.pm

     
    MAC.pm.diffs

  • Erich Focht

    Erich Focht - 2005-09-05

    Logged In: YES
    user_id=338721

    Hmm, the added gateway and nameserver are the gateway and
    nameservers of the master node. Inside an OSCAR cluster you
    usually won't have access to these! Except you enable IP
    forwarding on the master node OR you have a setup where your
    nodes are not isolated in a private subnet.

    I aknowledge that there is a potential problem here, but I do not
    agree to the solution because it would break all my normal
    setups.

    Actually the gateway should come from the SIS database. And it
    should be set up correctly when defining the OSCAR nodes.

    I'd also find it useful to have non-OSCAR nodes in the
    dhcpd.conf which just get their IP address but are otherwise left
    alone (rather an RFE...).

    Regards,
    Erich