Henrik Nordstrom wrote:
On Tue, 6 Sep 2005, yenganti pradeep wrote:
The ip of my comp is 10.6.15.43. I want to reach
10.6.128.32 subnet through 10.6.128.33 which is not
directly connected to me. As 10.6.128.33 is not
directly in my reach, I want the kernel to contact
10.6.128.33 itself using 10.6.128.0 entry, ie through
10.6.0.115.
Then your route should point to 10.6.0.115, and the routing table on
10.6.0.115 must in turn have proper routing entry for
10.6.128.32/255.255.255.224 via 10.6.128.33.
I don't think that's what he's trying to do... He asks to send packets
for 10.6.128.32 to 10.6.128.33, and I assume that he is not counting on
10.6.0.115 to do that, or have that routing in place. One solution is to
set up a VPN between 10.6.15.43 and 10.6.128.33 so that it appears
directly connected, and which avoids depending on the intermediate hops
to do what you want.
Sorry if this isn't what yenganti was asking.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
: 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
