> > In some revere cases, this may cause some confusion with some > > applications and routing from a client side. I am not to sure however. > > Hmm, lack of insight prevents me from seeing a problem here. > Are you thinking of apps, that should not be able to 'see' across > different segments, courtesy of firewallrules, but may be able to do so > due to the broadcasts allowed by dhcrelay? > The latter should AFAIK broadcast only dhcp-stuff. Like I pointed out, I am talking under correction. But I believe that (especially NT servers), relies on broadcasts for the ability to change / update / figure out routes. The bottom of the line is just that arp cache may become messy if and when a server / client on one segment ads a machine to asp while the machine is on another segment. In this case, the client will not send data to its default gateway, and thus the route will be seen as a local one, which in fact it is not. Bottom of the line, the client will not route. There is however options you can specify in your DHCP scope to 1) force all clients to ALWAYS use the default gateway for routing, and 2) you can force a broadcast address to be used, which means that you will be able to perhaps minimise the mess of broadcasts :) --- Regards, Chris Knipe Cell: (083) 430-8151 - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
