documentation-packages team mailing list archive

[Launchpad Bug Tracker <709910@xxxxxxxxxxxxxxxxxx>]

[Expired for ubuntu-docs (Ubuntu) because there has been no activity for
60 days.]

** Changed in: ubuntu-docs (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/709910

Title:
  SSH VPN document stelist not working in Ubuntu 10.10.

Status in “ubuntu-docs” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ubuntu-docs

  I have implemented the SSH VPN as explained in the document:

  https://help.ubuntu.com/community/SSH_VPN/

  But at least I can confirm that it is not working with Ubuntu 10.10 as Machine B and Ubuntu 8.04 as Machine A.
  I managed to make it work by using smaller netmask on the tun0 interfaces in both endpoints smaller.
  I used netmask 255.255.255.255 in Machine A, like shown below, for an eth0 IP address of 192.168.0.15 in Machine A  ethernet:

  Machine A:

   iface tun0 inet static
          pre-up sleep 5
          address 192.168.0.15
          pointopoint 192.168.0.14
          netmask 255.255.255.255
          up arp -sD 192.168.0.14 eth0 pub

  I suspect that if you use the same netmask in Machine A as in the
  ethernet interface there is a route conflict, but if you use a more
  restrictive netmask that one will be the preferred route.

  Also when I bring down the tunnel in Machine B with the command "sudo
  ifdown tun0" this will bring down the tunnel, but it will not bring
  down the ssh session. That one you have to kill it manually. Otherwise
  if you bring again the tunnel up with "sudo ifup tun0" the tunnel
  creation will fail!

  To fix this, in the "Automating it all with ifup/down" section in
  Machine B you have to add a new entry in the very bottom:

                    down pkill -9 -f 'ifup tun0'

  This will kill the ssh session when you execute "sudo ifdown tun0" in
  Machine B.

  It would be good also to include that you should run "sudo ifup tun0"
  to bring up the tunnel and "sudo ifdown tun0" to bring it down and
  recover the proper interface configuration and routes in order to
  continue using Internet just as you were doing in the very moment
  before the tun0 was brought up.

  Thanks for the step-list,

  Juan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/709910/+subscriptions