On Thu, Mar 10, 2005 at 1:51AM +0200, Boian Bonev wrote: > you can do that but you omit the interface addresses - suppose ext net > is 10.20.10.1/24, internal is 10.10.10.1/24, no matter what routing > policies and rules you put, both interface ips will be visible from > both interfaces. What do you mean by "visible"? If you're referring to arp, the arp sysctls are probably adequate, and there's arpfilter if not. > now imagine you have another external net 10.30.10.1/24 and customer > wants to route e.g. 10.10.0.0/16 from 10.20.10.1/24 via 10.30.10.5... > at least host 10.10.10.1 will not route but arrive locally to your > blade host Not if you take 10.10.10.1 out of the "local" routing table, and policy route that traffic only through tables that don't consider 10.10.10.1 local. I'm not saying it's trivial, but if you set your rules up right, you can make some packets be routed by *completely different routing tables* than others. Jason - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
