Vivek Garud writes:
> Ok. here is the link to the document. It is safe :) Please open it.
>
> http://vgarud.googlepages.com/ip-tunnel-req.doc
Tunnels are inherently point-to-point beasts. You should use routes
to direct other traffic over the tunnel.
The "Server" machine could have something like this:
route add 10.13.100.0/24 10.13.100.0
... see the man page for the "-p" option to make it persistent.
However, I'm not sure I understand you configuration. Why would the
tunnel's inner and outer addresses be equal? And why do you need a
tunnel here (as opposed to just plain old routes)?
Given the diagram, I would have expected something like this on the
"Server" machine:
ifconfig ip.tun0 plumb 10.5.22.87 10.5.22.39 \
tsrc 10.5.20.87 tdst 10.5.50.39 up
route add 10.13.100.0/24 10.5.22.39
along with this on the "Gateway" machine:
ifconfig ip.tun0 plumb 10.5.22.39 10.5.22.87 \
tsrc 10.5.50.39 tdst 10.5.20.87 up
You may need other routes on that "Gateway" machine if there are other
things attached to "Server."
And you may want to consider using a regular routing protocol here
rather than explicitly configuring everything. It's tedious and
error-prone.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
