NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bin/39233: OpenSSH fails to initialize tun(4) tunnels correctly

The following reply was made to PR bin/39233; it has been noted by GNATS.

From: Quentin Garnier <>
Subject: Re: bin/39233: OpenSSH fails to initialize tun(4) tunnels correctly
Date: Mon, 28 Jul 2008 16:25:07 +0200

 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 On Mon, Jul 28, 2008 at 02:00:01AM +0000, Taylor R Campbell wrote:
 > >Number:         39233
 > >Category:       bin
 > >Synopsis:       OpenSSH fails to initialize tun(4) tunnels correctly
 > >Description:
 >      After running `ssh -w 0:1' (the numbers don't matter; they just
 >      help me to keep from getting mixed up) to create a tun(4)
 >      tunnel over ssh, and after configuring the tun(4) interfaces
 >      appropriately on both machines, no packets actually get through
 >      the tunnel.
 I think this is because OpenSSH's code is specific to OpenBSD.  Their
 tun(4) covers both our tun(4) and our tap(4), and has a different
 interface.  The fact that it compiles is actually the main bug.
 Now, it'd probably be good to add support for that in NetBSD, and it
 shouldn't be too difficult, given it's mostly the initialisation of
 devices that matters.  Well, the code might also be expecting a header
 or something on read packets, or even try to prepend one on written
 Quentin Garnier - -
 "See the look on my face from staying too long in one place
 [...] every time the morning breaks I know I'm closer to falling"
 KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: GnuPG v1.4.9 (NetBSD)

Home | Main Index | Thread Index | Old Index