>>>>> "Mike" == Mike C <[email protected]> writes:

Russell> Not such a good idea, IMHO.  The "access point" dhcp server
Russell> is going to be giving itself out as the default route, unless
Russell> you can tell it otherwise.

[...]

Mike> With that being said, the standard issue dhcleint,conf file
Mike> would request routers from the DHCP server and would need to
Mike> modified.

Having to modify the client device means you have already failed.  It
is supposed to be "just works".

Russell> Also, some embedded dhcp servers listen for other dhcp
Russell> servers on the network before starting.  If they hear one,
Russell> they'll disable themselves.  Others, stomp right ahead
Russell> blindly.

Mike> I've been working with computer networks for 15 yrs and I have
Mike> yet to see this behavior. 

Let me tell you, I have.  And I'd be happy to introduce you to them.

I wouldn't swear to it, but I think dnsmasq might do the former out of
the box.  In any case, I know for certain I have seen this behavior
multiple times, enough to learn to watch out for it.  Looking back
through my notes, it might have been seen with a stock WRT54G and
another device with OpenWrt dnsmasq.

The Zhone/Paradyne DSL modems that Integra deploys are in the latter
category.  In fact, by default, they hand out leases over the entire
available address range (.2 through .254 in a /24).  They don't bother
to check whether the IP address is in use (e.g. by pinging) before
hand.  This makes trying to use static IPs on these networks highly
problematic. It is just a matter of time before the helpful DHCP
server cheerfully stomps on your carefully chosen IPaddr.  Just as a
capper, Integra refuses to provide a login to let you configure the
DSL modem yourself.  Which means, every trivial little change you
might want to make requires a support call.


-- 
Russell Senior, President
[email protected]
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to