Eric,

/etc/dhcp3/dhcpd.conf contains (after stripping out all the comments):

ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
option domain-name "localdomain";
option domain-name-servers 192.168.2.1;

default-lease-time 600;
max-lease-time 7200;

allow booting;
allow bootp;
subnet 192.168.2.0 netmask 255.255.255.0 {
        get-lease-hostnames on;
        use-host-decl-names  on;
        range 192.168.2.50 192.168.2.99;
        option routers 192.168.2.1;
        option subnet-mask 255.255.255.0;
        option broadcast-address 192.168.2.255;
        filename "pxelinux.0";
        next-server 192.168.2.10;
}
host shuttle {
        hardware ethernet 00:30:1b:ba:89:31;
        fixed-address 192.168.2.20;
        option routers 192.168.2.1;
        option subnet-mask 255.255.255.0;
        option broadcast-address 192.168.2.255;
        option host-name "shuttle";
        filename "pxelinux.0";
        option root-path "/home/shuttle";
        next-server 192.168.2.10;
}
host nfsroot {
        hardware ethernet 08:00:27:bb:74:dd;
        fixed-address 192.168.2.30;
        option routers 192.168.2.1;
        option subnet-mask 255.255.255.0;
        option broadcast-address 192.168.2.255;
        option host-name "nfsroot";
        filename "pxelinux.0";
        option root-path "/home/nfsroot";
        next-server 192.168.2.10;
}

Larry a.k.a. Dazed_75
======================================================

Craig Said:

     You need to edit the settings for the eth1 so that it is NOT controlled
     by Network Manager and it IS started up when the computer starts.

Craig,

That may be true, but the DHCP is failing before the computer finishes
booting, it succeeds after logging in when NM is fully in operation.  Also,
the goal here is to normally run headless with no one logging in.  Except
for the DHCP server that all seems to be working.  I may have tio try that
but since everyone points at different solutions, I am being cautious about
moving forward.

Larry a.k.a. Dazed_75
======================================================


On Thu, Oct 1, 2009 at 6:26 PM, ryan <[email protected]> wrote:

> <snip my original stuff>



> I may be mistaken but I think ubuntu doesn't start the network interfaces
> until a user has logged on and the network manager applet is running.
>

Actually, if you turn off the windows-ish quiet boot even leaving the silly
splash screen on, you will see that the network elements are initialized (to
some degree) long before the user is able to log in.  And lets distinguish
between the NM applet which is ONLY used after there is a GUI to work in and
the software that actually manages the interfaces.

I am sorry, that sounds like I think I know what I am doing here when
actually I am poking and praying.  But this part at least I KNOW that some
of it is done before a user is even allowed to log in.

>
> I found this https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/392826via a 
> quick google search so the answer to your question about reordering
> the script doesn't seem like it would work.
>

Good find.  Thanks.  The problem I first see is that that user moved his
DHCP server to S99 but there are services starting before that that might
then not be able to run so he may have caused his own continued failure.  I
really do not know.

>
> I believe you would have to switch your network preferences away from
> networkmanager back to the older /etc/network/interfaces method or restart
> the dhcp server after you have logged in and the networkmanager applet has
> started as you've been doing.
>
> Perhaps, that would be Craig's opinion too.  I just think it should not be
necessary because I CAN start the DHCP server while NM/-applet is running
and it works.

>
>

-- 
Dazed_75 a.k.a. Larry

The spirit of resistance to government is so valuable on certain occasions,
that I wish it always to be kept alive.
 - Thomas Jefferson
_______________________________________________
PLUG-applications mailing list
[email protected]
http://lists.plug.phoenix.az.us/cgi-bin/mailman/listinfo/plug-applications

Reminder: All replies will go back to this mailing list. If you wish to send a 
reply to a specific person, please use the reply function and change the 
&quot;To:&quot; address to that person before sending.

Reply via email to