From: Nataniel Klug <nata@cnett.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS - Ping problem
Date: Wed, 12 Apr 2006 19:26:42 +0000 [thread overview]
Message-ID: <443D5472.2050709@cnett.com.br> (raw)
In-Reply-To: <44340CD6.1030907@cnett.com.br>
Andy,
I will try to make this rule and see what happens. Thanks.
Att,
Nataniel Klug
Andy Furniss escreveu:
> Nataniel Klug wrote:
>
>> # Regras para a placa eth1
>> #------
>> $TC qdisc add dev $DL root handle 1: htb default 50
>
> You are using htb default on eth - unless you make a filter for arp it
> will also end up in 1:50 which may or may not be the problem - you
> should fix it anyway.
>
> tc filter add ..... protocol arp u32 match u32 0 0 ....
>
> or stop using htb default class and make a catch all ip filter to send
> the rest to 50.
>
> Andy.
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-12 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 18:30 [LARTC] QoS - Ping problem Nataniel Klug
2006-04-05 21:11 ` Jody Shumaker
2006-04-06 13:03 ` Nataniel Klug
2006-04-06 16:18 ` Nataniel Klug
2006-04-12 18:51 ` Andy Furniss
2006-04-12 19:26 ` Nataniel Klug [this message]
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=443D5472.2050709@cnett.com.br \
--to=nata@cnett.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox