[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dev tun0 and ping
- To: misc@openbsd.org
- Subject: Re: dev tun0 and ping
- From: Claudio Jeker <cjeker@ee.ethz.ch>
- Date: Fri, 2 Feb 2001 10:21:28 +0100
- Content-Disposition: inline
- Mail-Followup-To: Claudio Jeker <cjeker@ee.ethz.ch>, misc@openbsd.org
- References: <20010202080614.A16492@ee.ethz.ch> <20010201232240.D18778@willamette.edu>
- User-Agent: Mutt/1.2.4i
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