Message from discussion
PF inadequacy: queue download
Path: g2news2.google.com!news3.google.com!news.glorb.com!pln-e!spln!dex!newsgate.newsguy.com!newsp.newsguy.com!mdrn
From: stha...@tehran.lain.pl (Stanislaw Halik)
Newsgroups: bit.listserv.openbsd-pf
Subject: Re: PF inadequacy: queue download
Date: 29 Apr 2006 09:16:41 -0700
Organization: None
Lines: 44
Message-ID: <20060429151040.GA11282@tehran.lain.pl>
References: <1146315947.065791.306090@i40g2000cwc.googlegroups.com> <20060429142538.GP19449@insomnia.benzedrine.cx>
NNTP-Posting-Host: sthalik
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S"
NNTP-Posting-Date: 29 Apr 2006 16:16:41 GMT
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Apr 29, 2006, Daniel Hartmeier wrote:
>> I know this is possible because IPFW with dummynet doesn't have any
>> problems. If everyone loves PF because of its elegance why can't it do
>> something as simple as queue download traffic?
> http://lists.freebsd.org/mailman/htdig/freebsd-pf/2005-November/001657.html
| But it wouldn't change anything, because the congestion is upstream of
| your ALTQ box. You can drop as many packets as you like after you
| received them, that doesn't free up any bandwidth on your downlink.
It surely has its caveats, but has its use, too. I'm stuck with ipfw on
one last machine, because I can't limit bulk TCP traffic with pf. Of
course, downstream limiting will never throttle DoS attacks, ICMP or
'dumb' UDP traffic with no acknowledgements, but works just fine for
everything else. Even on ipfw's contemptible 'dummynet'.
| If you want to do this with ALTQ, you can do so by limiting outgoing
| packets on the "other" interface, assuming the box is forwarding all
| packets between two interfaces.
I can speak for myself - I can't afford both the hardware and the
electricity bill for a separate machine. Maybe downstream limiting isn't
very robust, but IMO is the biggest thing pf/altq lacks.
-- sh
--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)
iD8DBQFEU4HwadU+vjT62TERAkuUAJ9W3M0fryN3zRrUMEm0wDMuSvwJ9QCfVZwq
ky+ERwX+43rkrang73tmFTo=
=MuS+
-----END PGP SIGNATURE-----
--AhhlLboLdkugWU4S--
|
