Eric,
If you go into /etc/init.d/dhcpd and change the RCDLINKS value to be
around 42 if memory serves... This should cause dhcpd to start after
shorewall.
I don't have any configurations available to me right now, but you could
look at the shorewall script and check the RCDLINKS value in there.
Ensure dhcpd gets a larger value. Note you will have to change several
numbers on that line...
Assuming your wireless stuff is coming up OK, this will (should!) solve
the DHCPD issue.
Brock
> Date: Wed, 15 May 2002 09:57:59 -0700 (PDT)
> From: Eric House <[EMAIL PROTECTED]>
> To: Ray Olszewski <[EMAIL PROTECTED]>
> cc: LEAF <[EMAIL PROTECTED]>
> Subject: Re: [leaf-user] What should dhcpd.conf look like for eth2?
>
> > Your dhcpd.conf entry for the 192.168.2.0 subnet looks
> fine. Given that, the
> > problem is probably that dhcpd is starting before whatever
> interface network
> > 192.168.2.0 is on (I infer eth2 from what you say) gets
> configured. At the
> > point at which dhcpd starts, eth2 is probably (implicitly) network
> > 0.0.0.0/something, and you have no subnet declaration for that bogus
> > network. That it works fine from a console restart reinforces this
> > interpretation of the symptom you describe.
> >
> > Since you tell us so little about your setup (not even
> which LEAF version
> > you are using), it's not really possible to be more
> specific than that.
>
> Sorry. Bering, rc2. eth0 and eth2 are 3c509; eth2 is a wireless card
> using ray_cs plus whatever it takes to run the ISA->PCMCIA adapter.
> eth0 is outbound, and connected to a cable modem (ATT) with IP
> assigned over dhcp.
>
> The card on eth2 *does* take a few seconds to come up. Is this just a
> timing issue? Should I be delaying dhcpd somehow? (I suppose a
> 'sleep 5' in init.d/dhcpd would do it, but there's sure to be a better
> way.)
>
> Thanks,
>
> --Ericn
>
> > At 09:35 AM 5/15/02 -0700, Eric House wrote:
> > >I want dhcpd to serve both eth1 and eth2. My dhcpd.conf looks like
> > >this, with the second subnet changing '1' to '2' for everything but
> > >the name server:
> > >
> > >dynamic-bootp-lease-length 604800;
> > >max-lease-time 1209600;
> > >
> > >subnet 192.168.1.0 netmask 255.255.255.0 {
> > > option routers 192.168.1.254;
> > > option domain-name "private.network";
> > > option domain-name-servers 192.168.1.254;
> > > range 192.168.1.1 192.168.1.199;
> > >}
> > >
> > >subnet 192.168.2.0 netmask 255.255.255.0 {
> > > option routers 192.168.2.254;
> > > option domain-name "dmz.network";
> > > option domain-name-servers 192.168.1.254;
> > > range 192.168.2.1 192.168.2.199;
> > >}
> > >
> > >When the router boots, I get error messages from dhcpd (on
> the console
> > >and in syslog) telling me I need a subnet declaration for
> eth2 in my
> > >dhcpd.conf file. Oddly, if after I get a prompt I run
> > >'/etc/init.d/dhcpd restart' (without changing anything) I don't get
> > >those errors.
> > >
> > >(dhcpd works only intermitently on eth2, but that may be shorewall
> > >problems.)
> > >
> > >I have this in /etc/init.d/dhcpd, BTW:
> > >
> > ># Add interfaces, separated by a space (ie "eth0 eth1")
> > ># Typically your internal interface: eth1 for cable modems/DSL, or
> > ># eth0 for ppp/dialup
> > >ifs="eth1 eth2"
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
