All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: Problem to priorize SSH traffic
Date: Sat, 17 Dec 2016 15:49:13 +0000	[thread overview]
Message-ID: <58555E79.1060401@gmail.com> (raw)
In-Reply-To: <1737987792.142216491.1481907014295.JavaMail.root@zimbra45-e7.priv.proxad.net>

Ludovic Leroy wrote:
> Hello Andy,
>
> I have put it badly. My linux system is used as a firewall/router for a
> small local network that is connected to eth0 interface.
> I have created a dedicated class on eth1 interface to access files on a
> shared network drive integrated into the DSL modem.

If you are shaping on eth you need to be careful what you do with arp.

Using htb default in your setup sends arp to 99, but as you have sfq on
that it will work. If say you had pfifo on it then the arp may get
delayed long enough for the kernel to thing that the remote has gone,
which is not good.

The default default for htb lets things through unshaped which is good
for arp.

> Le 17/12/2016 12:19, Andy Furniss a écrit :
>> Ludovic Leroy wrote:
>>> Thanks for replying. The script is attached. Hope this helps.
>>
>> $TC qdisc add dev $NETCARD root handle 1: htb default 99 r2q 5
>>
>> SFQ saves the day, but you should be aware that using default on eth in
>> this case catches arp and sending arp to a low bandwidth class is not a
>> good thing to do.
>
> .
>


  parent reply	other threads:[~2016-12-17 15:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 16:50 Problem to priorize SSH traffic Ludovic Leroy
2016-12-16 20:34 ` Alan Goodman
2016-12-16 21:16 ` Ludovic Leroy
2016-12-17 10:23 ` Alan Goodman
2016-12-17 10:56 ` Andy Furniss
2016-12-17 11:19 ` Andy Furniss
2016-12-17 12:27 ` Ludovic Leroy
2016-12-17 14:45 ` Ludovic Leroy
2016-12-17 14:50 ` Ludovic Leroy
2016-12-17 15:14 ` Alan Goodman
2016-12-17 15:44 ` Andy Furniss
2016-12-17 15:49 ` Andy Furniss [this message]
2016-12-17 16:04 ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58555E79.1060401@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.