In any case, on each tunnel endpoint system (not the eventual
end-system, but the point where the packets are `detunnelled'):
-* Install userv, 0.95.0 or later. This should be in Debian.
-* Get userv-utils 0.1.9 from the location above, unpack it, cd to the
- `ipif' subdirectory, and say `make' then `really make install'.
+* Install userv, 1.0.1 or later. This should be in Debian. Get this
+* package, userv-utils from the location above, unpack it, cd to the
+ `ipif' subdirectory, and say `make' then as root `make install'.
-The tunnel is always set up by one of its endpoints, using ssh. So
-the active endpoint must have ssh installed; the passive endpoint must
-have sshd accessible to the active endpoint, and be willing to allow
-the active endpoint to run the appropriate command.
+The tunnel is always set up by one of its endpoints, using ssh (we
+recommend you use OpenSSH). So the active endpoint must have ssh
+installed; the passive endpoint must have sshd accessible to the
+active endpoint, and be willing to allow the active endpoint to run
+the appropriate command.
So: create an account for the active endpoint on the passive. You
probably want to use RSAAuthentication, so configure the relevant key
If you see a message from `slattach' about being unable to open /dev/2
or some such, then you need to upgrade your `slattach'. In Debian
GNU/Linux it's in the `netbase' package, and the fix is in 3.16-3 and
-later. The relevant Debian bug reports are #45515 and #45944, and Ian
-Jackson can supply the patch to slattach or a working binary.
+later; however the bug has regressed, and is known to be in 3.18-4 and
+earlier. The relevant Debian bug reports are #45515 (now closed) and
+#45944. A patch to correct 3.18-4 is in this directory as
+`slattach.diff'.
$Id$
~ian / userv-utils.git / blobdiff