OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Claudio Jeker (cjekeree.ethz.ch)
Date: Fri Feb 02 2001 - 03:21:28 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Thu, Feb 01, 2001 at 23:22:40 -0800, Seth Arnold wrote:
    > Claudio, I have never seen this sort of thing before, and frankly I am
    > very impressed so little was required to get this far. hehe. Cool.
    >
    > In any of my own 'ifconfig' outputs, the flags section always shows UP
    > if the interface is up. (even lo0.)
    >
    > Try breaking that ifconfig command into two lines:
    > ifconfig tun0 inet 192.168.2.1 192.168.2.2 mtu 1500
    > ifconfig tun0 up
    >
    > (It appears to have gotten the netmask correct, but it may not hurt to
    > specify the netmask as well....)
    >
    > Good luck, and be sure to write back to the list what fixes your
    > problem. This sounds neat. :)
    >

    You were right. It's needed to explicitly set the device up after the
    process reading from /dev/tun0 has connected.
    The man page for tun(4) should probably note that explicitly.

    Now I can ping 192.168.2.2 but ping 192.168.2.1 (local endpoint of point
    to point connection) gives still no reply (but this is not that
    important).

    -- 
    :wq Claudio