hadi@xxxxxxxxxx said:
> Are we still talking about the same problem? The linecards addresses
> and interconnect interfaces are "internal". They are never
> advertised/seen outside of the chasis. So if you choose 18.7.22.69/32
> to use internally you make sure it is never advertised to the outside
> world as belonging to you. If you have to advertise it or actually
> know it is used, then you must deal with the conflict.
I think you're both in agreement, however violently you try not to be.
The question, though, is: *How* do you configure the nodes within the
chassis such that the internal IPs (whatever they are) _stay_ internal,
and any non-127/8 addressing can be used for the external interfaces?
I've done something similar, for example, using policy routing and the
arp sysctls. Suppose you have a machine with 2 interfaces, and you want
IP routing to happen on each of the two interfaces as independently as
possible. My solution involves using the "iif" modifier in your routing
rules ("ip rule" rules) to send packets to two completely different
routing tables, and making sure arp doesn't bleed across the two
interfaces. I don't know whether policy routing gives enough control to
do this in a general fashion; i did it only for very specific types of
traffic. But I suspect you could come up with something workable.
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
