On Wed, 9 Mar 2016 21:28:10 +0200
Mihai Popescu <mih...@gmail.com> wrote:
> > -----
> > queue download on $if_int bandwidth 10M max 10M
> > queue ssh parent download bandwidth 1M
> > queue web parent download bandwidth 8M
> > queue bulk parent download bandwidth 1M default
> >
> > match to port ssh set queue ssh
> > match from port ssh set queue ssh
> > match to port { 80 443 } set queue web
> > match from port { 80 443 } set queue web
> > -----
>
> Pardon me, but are you assigning by this both in and out ssh packets
> to the same ssh queue?
>
I do. I noticed, by monitoring systat queues, that assigning queue to
request packet that enters internal interface, puts corresponding reply
traffic into that queue, which is logical if we take into account that
by default a request creates state, and - by means of keeping state
- reply is the same state. If I assign queue only to traffic leaving
internal interface, only requests initiated from the Internet (the
ones that create states) are put into that queue, which is never in my
case - I don't have ssh server on my LAN to which I grant access from
the Internet. Moreover, this would not be what I am trying to achieve -
I want to improve my experience of connecting to ssh servers on the
Internet, so that typing in remote ssh session does not lag because I
have active http transfers which eat up all my bandwidth.
--
Before enlightenment - chop wood, draw water.
After enlightenment - chop wood, draw water.
Marko Cupać
https://www.mimar.rs/
