Am Freitag, den 09.10.2015, 07:56 +0300 schrieb Kimmo Paasiala:
> On Thu, Oct 8, 2015 at 4:26 PM, Christer Solskogen
> > I boiled the rule down to this:
> > match proto tcp to port { http https } set prio 7
> >
> > But I still can't see that it does anything useful, as I don't see
> > any
> > better speed on http with or without that rule.
> > What have I missed? :(
[..]
> Your downloads from the internet are
> incoming traffic on your internet facing network interface and can not
> be prioritized.
Well, actually it can[1]. But it involves some kind of reverse thinking
and hsfc queues. And if this link is indeed not the bottleneck, even in
the best case you can't win, but in the worst, you can screw up awfully.
This is why I asked Christer to try to identify the exact limit that is
being hit.
Christer, if you find out that traffic on the incoming connection (i.e.
the one from the last router of your provider to your OpenBSD machine)
is indeed the problem, post it to the list and I may give you better
instructions.
[1] The basic idea is to limit traffic to the internal LAN to a bit less
than the current bottleneck. This way you have control over the outgoing
traffic on the (artificial) bottleneck link and you may indeed be able
to do shaping.
But this approach is of course complicated by the fact that (a) it would
involve hsfc queues instead of the default prio ones and it will only
work, if the protocols running are cooperative enough (i.e.
predominantly TCP and no massive amounts of flows).
Cheers
David
