Specifically, I'm trying to encapsulate the traffic for a single host
through a tunnel.
I create the tunnel and ifconfig it with
ifconfig tunl0 169.229.40.76 netmask 255.255.255.255
The trouble occurs when I try to route through tunl0:
route add -host gallia.cs.berkeley.edu gw 169.229.40.35 tunl0
This fails with a host unreachable error. I was able to workaround
the problem by setting the mask on tunl0 to be 255.255.255.0.
Then, I could do
route add -net 169.229.40.0 tunl0
route add -host gallia.cs.berkeley.edu gw 169.229.40.35 tunl0
route del -net 169.229.40.0 netmask 255.255.255.0
ifconfig tunl0 netmask 255.255.255.255
Since I should be able to route to an arbitrary destination through a
tunnel, it really shouldn't be checking if the destination is reachable
using the normal logic. It checks to see if there is a path from tunl0
to the destination host. This is incorrect because the packet passes
through tunl0 onto eth0 and uses eth0's routing table. I do have a
route from eth0 to 169.229.40.35.
- Gordon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu