From owner-freebsd-net@FreeBSD.ORG Mon Nov 22 20:00:06 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FE8316A4CF for ; Mon, 22 Nov 2004 20:00:06 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58BEF43D31 for ; Mon, 22 Nov 2004 20:00:05 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CWKLz-0004Nn-00; Mon, 22 Nov 2004 21:00:03 +0100 Received: from [217.83.10.145] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CWKLz-0001uE-00; Mon, 22 Nov 2004 21:00:04 +0100 From: Max Laier To: freebsd-net@freebsd.org Date: Mon, 22 Nov 2004 21:00:18 +0100 User-Agent: KMail/1.7.1 References: <867joeau4r.fsf@srvbsdnanssv.interne.kisoft-services.com> <20041122182331.GB20652@odin.ac.hmc.edu> In-Reply-To: <20041122182331.GB20652@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1455302.KRKWpJPmgl"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411222100.26580.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: gif4) & AltQ X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 20:00:06 -0000 --nextPart1455302.KRKWpJPmgl Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 22 November 2004 19:23, Brooks Davis wrote: > On Mon, Nov 22, 2004 at 02:30:28PM +0100, Eric Masson wrote: > > Hello, > > > > In a vpn application, I'm using gif tunnels backed by ipsec transport > > mode beetween two hosts on the Internet. > > > > Is there any hope to see gif(4) modified to integrate AltQ framework or > > is there any reason (except lack of maintainer/coder time) that would be > > a showstopper ? > > I'm not sure ALTQ makes sense on a gif interface. ALTQ's operation > depends on being fairly close to the point where packets hit the wire > and gif is quite a ways from there (since it's riding on top of IP). Very true. It's more worthwhile to classify on gif and queue on the real=20 interface. Queueing on gif will only work in rate-limiting mode. > I don't think there would be any objection to adding support, but gif > does not have have a maintainer so you'd have to convince someone to > find it intresting (or figure it out yourself.) I gather the changes > aren't all that complex in general. That's true as well. Take a look at the patches on:=20 http://people.freebsd.org/~mlaier/ALTQ_driver/ and the altq(9) manpage to=20 learn how to modify a driver. It's more or less looking for if_snd and=20 modifying it according to the rules in altq(9). Not sure how *exactly* gif(= 4)=20 works, but I'll put it on my list (just not a high priority, right now). =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1455302.KRKWpJPmgl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBokVaXyyEoT62BG0RApdmAJ9Fz3p9Uiy2UZ4hTuHW9ayzR7wMQwCdER3j x6Rm+vYaxaVG3eCvvjBwmK8= =6CUv -----END PGP SIGNATURE----- --nextPart1455302.KRKWpJPmgl--