Ubuntu network configuration

[Star]

On Wed, Oct 8, 2008 at 2:52 PM,  <bruce.labitt at autoliv.com> wrote:
> I'm slowly getting things running on my ubuntu based system.  I have a few
> network questions.
> I have two NICs, one to the corporate network, and a local one that only
> runs to a blade computer.
> eth0 is set up as dhclient.  No issues there.
>
> I need eth1 to be a dhcp server.  So I installed dhcp3.
> I editted /etc/default/dhcp3-server to include the line INTERFACES="eth1".
>
>
> The contents of /etc/dhcp3/dhcpd.conf are:
>
> allow bootp;
> ddns-update-style interim;
> default-lease-time 60000;
> option domain-name-servers 192.168.3.1;
> subnet 192.168.3.0 netmask 255.255.255.0 {
> host bch-amm {
>        hardware ethernet xx.xx.xx.xx.xx.xx;
>        fixed-address   192.168.3.99;
> }
> host qs22-001 {
>        hardware ethernet       yy.yy.yy.yy.yy.yy;
>        filename                "qs22-001-nfsroot-2.6.22-1.ydl.1.img";
>        fixed-address   192.168.3.100;
> {
>
> option routers          192.168.3.1;
> option subnet-mask      255.255.255.0;
> filename                        "ydl-cell.img";
> next-server                     192.168.3.1;
> allow bootp;
> range dynamic-bootp     192.168.3.2 192.168.3.98;
> }
>
> I see there are two allow bootp's.  Which one do I take out?  Is there
> anything else wrong?
>
> I am attempting to run atftpd also.  The contents of /etc/default/atftpd
> is:

Looking at your dhcpd.conf, you can remove either of the allow bootp
entries.  The first is "global" to any server requesting from that
dhcp server, the second (if i'm reading it right) is specific to the
dhcp zone that's configured.  Since you only have one zone,  removing
either, or neither should work fine.




>
> USE_INETD=true
> OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5
> --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread
> 100 --verbose=5 /tftpboot"
>
> I would expect that I need to edit the 239.239. . address to be =
> 192.168.3.0-255?  anything else?  I read on ubuntugeek that some
> recommended that USE_INETD=false.  Why would that be?
>

the mcast address is for multi-cast.  It lives in a world of it's own,
and you should probablly leave that IP address alone.  any multicast
connections to that service will expect a mcast address.

setting USE_INETD=false will cause the service to run on its own vs.
being initiated through InetD services.  If you're only using this
service to give out bootp stuff to your one client, I'd go ahead and
turn it off.


> -Bruce
>

~ Star

-- 
~ *