From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC
Date: Thu, 13 May 2004 17:43:36 +0000 [thread overview]
Message-ID: <40A3B3C8.9000208@ornl.gov> (raw)
In-Reply-To: <marc-lartc-98548596122489@msgid-missing>
Patrick:
I tried that filter line, but it has incorrect syntax. But that isn't
the problem. The problem is the HFSC part... The traffic is indeed UDP
port 1234, and the HFSC qdisc functions for a short period of time
(between 5 and 60 seconds or so, and then stops passing any traffic on
the eth0 interface. You can look with ethereal, and the interface is
totally silent. Even weirder, if you wait, periodically (every several
minutes or so) you get another period of working. These are typically
5-10 seconds. What do I need to do to debug this? The machine is a
dual Xeon, if that matters.
Patrick McHardy wrote:
> Lawrence MacIntyre wrote:
>
>> Thanks, Patrick. That makes it a bit harder to manage from a remote
>> machine. I'll have to be very careful with that. I'll try to figure
>> out the implications of the default classification and send more email
>> if I can't get it.
>>
>> So I reordered the commands and changed them around. It looks like I
>> am either doing something strange or I have found a bug. When I
>> execute the following script, the UDP traffic on port 1234 continues
>> for a few seconds and then stops. When I examine the tc data, it
>> shows no change in the periods or amount of bytes flowing after the
>> flow stops. I am enclosing the command and the output.
>
>
> It is indeed strange. Only the qdisc drop counter is incremented, which
> means the packets are still unclassified. What happens if you change
> your filter to:
>
> /usr/local/bin/tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32
> match udp dport 1234 0xffff flowid 1:10 (match udp instead of ip)
>
> Are you sure the packets are sent to port 1234 ?
>
> Regards
> Patrick
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-05-13 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 2:14 [LARTC] HFSC Rick Goh
2004-02-26 2:39 ` syrius.ml
2004-02-26 13:39 ` Patrick McHardy
2004-02-28 2:59 ` syrius.ml
2004-02-28 6:22 ` Patrick McHardy
2004-02-28 6:42 ` Patrick McHardy
2004-05-12 16:36 ` Lawrence MacIntyre
2004-05-13 13:05 ` Patrick McHardy
2004-05-13 13:52 ` Lawrence MacIntyre
2004-05-13 14:23 ` Patrick McHardy
2004-05-13 17:43 ` Lawrence MacIntyre [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=40A3B3C8.9000208@ornl.gov \
--to=lpz@ornl.gov \
--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