I'm sorry, I didnt explain what I was doing with the Linksys.  It will
be the WRT54G, which has wireless capabilities, and will be used to
create a wireless link between my NOC and the offices around me. 
Since it is already being used for the wireless link, I thought it
would be an easy solution to turn DHCP on and have it handle each
users office.  That way their router is managed by me, and all they
have to do is plug a hub/switch in their office to get more ports, no
configuration necesary.

Joe


On Wed, 18 Aug 2004 14:43:40 -0400, Melvin Backus
<melvin at sleepydragon dot net> wrote:
> Joe Lagreca wrote:
> 
> >After I posted this message to the group I thought of increasing the
> >subnet size to give each office more address.  I think I will do that.
> >
> >I'm unclear on your suggestion about not having the linksys do DHCP.
> >I don't really want the offices networks to be NAT behind a NAT.  So I
> >will do the NAT, and run it to the LAN of the offices.  I will then
> >turn DHCP on the LAN of the Linksys and it can assign the IP addresses
> >for the subnet I assign them.  I would love to have my m0n0 handle the
> >whole thing, but I dont see how m0n0 can assign DHCP to multiple
> >subnets.  If someone knows how to have m0n0 to handle DHCP for
> >multiple subnets I would love to hear your suggestion.
> >
> >Thank you.
> >
> >Joe
> >
> >
> 
> Actually I was suggesting load a DHCP server implementation on one of
> the machines on that subnet and eliminate the need for the Linksys since
> it sounded like you weren't going to use the WAN interface at all
> anyway.  The extra overhead to do DHCP for a small lan is minimal.
> 
> --
> Melvin Backus
> Principal Wizard
> Sleepy Dragon Enterprises
> --
> Do not meddle in the affairs of dragons, for
> you are crunchy, and taste good with ketchup!
> --
> 
>