From: Alan Goodman <notifications@yescomputersolutions.com>
To: lartc@vger.kernel.org
Subject: Re: tc filter hash table
Date: Fri, 15 May 2015 12:40:37 +0000 [thread overview]
Message-ID: <5555E945.3040106@yescomputersolutions.com> (raw)
Stats you see are 'smoothed' in my experience. So percieved 'lag' of a
few seconds is normal in my experience.
HTB does not drop unclassified packets when used with no default.
Alan
On 15/05/15 13:30, ravin goyal wrote:
> I have seen unknown behaviour as
> i have not setup default class for unclassified data still it is going
> thro seen from nowhere and i am still in doubt how is it possible ?
>
> Another thing i observe ,sent bytes in classes for respective data
> comes after some delay for instance
>
> as i have set class 1:20 for tcp port 80 when i test , bytes seen in
> class coming after some delay or lag
>
> same for other class(udp port 53) except with icmp related class (it
> works just fine )
>
> bytes come after some time when I ran dig or nslookup like I have to
> run tc -s -d class show dev wlan0 multiple time again and again to see
> the bytes reflected and after some time data comes seen through class
>
> what could be the issue .Please go through this and suggest some corrections
>
>
> Rav
> --
> To unsubscribe from this list: send the line "unsubscribe lartc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next reply other threads:[~2015-05-15 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 12:40 Alan Goodman [this message]
2015-05-15 12:42 ` tc filter hash table ravin goyal
2015-05-15 14:58 ` Alan Goodman
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=5555E945.3040106@yescomputersolutions.com \
--to=notifications@yescomputersolutions.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.