Michael Graff wrote:
|
|It seems to me this is written exactly backwards.  :)
|
|Suppose I want to set up a VNPish thing that has a remote network of
|192.168.42/24.  It appears I have to do this:
|
|	ifconfig ipip0 local-real remote-real netmask 0xffffffff up
|	route add 192.168.42.0 remote-real netmask 0xffffff00
|
|This does two things:
|
|	(1) makes it so I cannot ping the remote-real address any
|            longer.  Try it, it complains about "message too long"

Which version of the software? IIrc there was a bug with pmtu
discovery, which set the MTU of the IPIP tunnel to 0 (or better:
did not set it to a good value). This should have been changed
before 1.4.

|	(2) to be part of the VNP itself, I need to add an ifconfig
|	    alias for the local host.  If I do this on the ipip0
|	    interface itself, netstat -rn shows Bad Stuff.

What exactly?

|	(3) It seems to be very confusing, and basically a hack.

What is confusing?

In step one you build a tunnel and in step two you add a route over
it. This is not different from first establishing a ppp connection and
then routing a net over it.

|Or am I just totally confused about this whole thing, and it's not as
|hard as it appears to be?

Yes :)

|The real problem seems to be that I want to specify a source address
|to use for a route...  And not hack the routing table like is done
|now...

The problem lies deeper. We don't really support routes to interfaces.
Only to next hops.

-- 
          See <a href="http://www.netbsd.org">NetBSD</a> for a multiplatform OS
[...] Koennt Ihr nicht den naechstbesten User gegen die Wand rammen, um
Euch abzureagieren, wie andere normale Systemadministratoren auch?
                 -- Peter "g" Bouillon in <6479nq$f9s@hades.rz.uni-sb.de>