From: "Rick Goh" <rickgoh@cyberway.com.sg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Tcpdump capturing faulty???
Date: Thu, 22 Mar 2001 22:55:02 +0000 [thread overview]
Message-ID: <marc-lartc-98530121713173@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98529557829288@msgid-missing>
New results:
I realised that if i reduce the number of flows to 3 instead of 5, tcpdump
will show graphs which will corresponds to that of TTT.
Anyone has any idea why??
I doubt it is the snaplen.
----- Original Message -----
From: "Rick Goh" <rickgoh@cyberway.com.sg>
To: "lartc" <lartc@mailman.ds9a.nl>
Sent: Friday, March 23, 2001 5:07 AM
Subject: [LARTC] Tcpdump capturing faulty???
> Hello,
> I am testing traffic control on linux. I used Tele-traffic tapper
> (http://www.csl.sony.co.jp/person/kjc/programs.html) to see real-time
> throughput of my client and it shows that traffic control of different
type
> of traffic flow works! However when i used tcpdump, it shows that priority
> doesn't work, meaning all flows have the same bandwidth => tc doesn't
work.
>
> In detail:
>
> Experiment 1: With borrow, FAILED. With all streams bounded, works.
> When i set on 192.168.1.10:
> port 42011 --> 5 (Mbps)
> port 42012 --> 10
> port 42013 --> 15
> port 42014 --> 20
> port 42015 --> 50
>
> Experiment 2:
> When i set on 192.168.1.10:
> port 42011 --> Priority 1
> port 42012 --> Priority 2
> port 42013 --> Priority 3
> port 42014 --> Priority 4
> port 42015 --> Priority 5
>
>
> On Tele traffic tapper (TTT), works fine but not tcpdump. What do i mean
by
> tcpdump cannot work:
> 1. After i tcpdump it, TTT can actually read from the dump file. But it
> shows Traffic control doesn't work; i.e. Meaning all 5 streams share the
> same bandwidth.
>
> 2. I tcpdump into a file and post analysis it by breaking it into the
> traffic from each different port. And i graph it. DOesn't work!! Meaning
all
> 5 streams share the same bandwidth.
>
> Has anyone come across this major hiccup???
>
>
> Regards.
>
>
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-03-22 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 21:07 [LARTC] Tcpdump capturing faulty??? Rick Goh
2001-03-22 22:55 ` Rick Goh [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=marc-lartc-98530121713173@msgid-missing \
--to=rickgoh@cyberway.com.sg \
--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.