> > In your setup, however, you've only got one internal NIC on the LRP, so
all
> > you need is the proper static routes configured on the LRP system. Note
> > that you will probably also need the proper static routes setup on your
> > clients, or you may still see connection problems. AFAIK, the LRP box
will
> > likely drop traffic that should have gone to your internal network
gateway
> > rather than forward it (I think an ICMP redirect will be sent
regardless)
> > due to the firewall rules. Just be aware this might be a problem...if
> > you're lucky, you can setup your internal systems static routes with
DHCP to
> > avoid the headaches of keeping all the systems properly configured.
> >
>
> I'm running your Eiger Static image. It doesn't have DHCP on it does it?
I
> have two floppy drive in the box so I can add a bunch more stuff. I
thought DHCP
> only provided IP's for boxes that needed them. How can it provide routes?
Is
> there a doc I can read on that? I'm really more of a developer but I'm
enjoying
> this working with this stuff.
You can easily install the dhcp server package on a second disk. As you
discovered, dhcp is setup to provide clients with just about any
configuration information you can imagine, and you can even create your own
configuration elements if dhcp doesn't already have provisions for what you
want to do. The problem is on the client end. Pretty much all clients
support setting up an IP/subnet info, default gateway, and dns
servers...support for more advanced options (like static routes) may require
some scripting (on *nix) or configuration (windows?), or may not even be
possible for some clients. You'll have to test the systems you're running
and see how they behave when given various options by the dhcp server.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
