On Mon, 17 Jun 2002, Walter Zimmer wrote: > remote host main network > --- --- > | | | | > --- --- > | | > | | > | | > --- --- > | |---access network---| | > --- --- > router1 (linux) router2 (linux) > [snip] > 2. Solution > =========== > Use proxy ARP. As I understand, this only works for networks which are > directly connected to the router. So, router2 can't use proxy ARP. You add so many restrictions, many of them arbitrary (e.g. tunneling) that I doubt this will be possible. I think proxy arp is about the only applicable technique here, but there are problems with it. An idea is hatching in me. 1) Configure remote host with 10.x.y.z/32, and additional address from current network it roams in. This way it will look for the rest of "10" from elsewhere. 2) router1 injects host route for 10.x.y.z/32 to the routing system (more specific than "10". 3) router2 enables proxy ARP. Now, this just _might_ work IF proxy ARP will work with non-connected (but still more specific, dynamic host-) routes. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
