From: "Denys" <denys@visp.net.lb>
To: hadi@cyberus.ca
Cc: Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: one more... iproute commands lockup whole system
Date: Wed, 4 Apr 2007 17:35:12 +0300 [thread overview]
Message-ID: <20070404143256.M86656@visp.net.lb> (raw)
In-Reply-To: <1175695810.4063.10.camel@localhost>
Yes, it is real setup by the way, i just copy&paste script here. I tried to
remove some commands to leave only minimum to reproduce the problem.
Right now i dont have another ethernet card on that system, i will add it
today, when i come back home and i will test in different situations. Also it
is interesting, how system will act when i will redirect from eth0 to ppp0,
tunnels, device with hardware offloading to device without hardware
offloading and etc.
On Wed, 04 Apr 2007 10:10:10 -0400, jamal wrote
> On Wed, 2007-04-04 at 15:56 +0300, Denys wrote:
>
> > Rules:
> > tc qdisc del dev eth0.5 root
> > tc qdisc add dev eth0.5 handle 1: root htb
> > tc class add dev eth0.5 parent 1:0 classid 1:2 htb rate 128Kbit
> >
> > tc qdisc add dev eth0.5 parent 1:2 handle 2: prio
> >
> > tc filter add dev eth0.5 parent 1: protocol ip prio 10 u32 \
> > match ip src 195.69.208.253/32 flowid 1:2
> >
> > tc filter add dev eth0.5 parent 2: protocol ip prio 10 u32 \
> > match ip src 195.69.208.253/32 flowid 2:1 \
> > action mirred egress redirect dev eth0.6
> >
> > (it is not working, but just i tried few things)
> >
>
> This will still mean the physical device is eventually going to be
> eth0. You are hanging, correct?
> If you redirected to another vlan ontop of a different physical
> ethernet, and the problem persists then it will be worrisome.
> Actually i am begining to doubt myself. Maybe the vlan device is acting
> strangely. I will try to test your simple setup towards the end of
> day and see what happens.
>
> cheers,
> jamal
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2007-04-04 15:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:00 iproute2-2.6.20-070313 bug ? Denys
2007-03-22 11:23 ` Patrick McHardy
2007-03-22 12:46 ` Denys
2007-03-22 13:09 ` Patrick McHardy
[not found] ` <20070322131245.M85528@visp.net.lb>
2007-03-22 13:23 ` Patrick McHardy
2007-03-22 13:35 ` Denys
[not found] ` <20070322132637.M88445@visp.net.lb>
2007-03-22 13:43 ` Patrick McHardy
2007-03-22 13:47 ` Denys
2007-03-22 13:26 ` Denys
2007-03-22 17:12 ` Stephen Hemminger
2007-03-22 17:14 ` Patrick McHardy
2007-03-26 18:49 ` more... iproute2/htb/whatever critical " Denys
2007-03-27 15:10 ` Patrick McHardy
2007-03-27 15:18 ` Denys
2007-03-27 16:00 ` Denys
2007-03-27 16:21 ` Patrick McHardy
2007-03-28 17:38 ` another " Denys
2007-03-28 23:55 ` Denys
2007-03-29 10:58 ` Patrick McHardy
2007-03-31 2:26 ` more iproute2 issues (not critical) Denys
2007-03-31 2:31 ` Denys
2007-03-31 14:16 ` Patrick McHardy
2007-04-04 0:03 ` one more... iproute commands lockup whole system Denys
2007-04-04 1:10 ` jamal
2007-04-04 1:39 ` Patrick McHardy
2007-04-04 2:09 ` jamal
2007-04-04 2:11 ` Denys
2007-04-04 10:55 ` jamal
2007-04-04 12:56 ` Denys
2007-04-04 14:10 ` jamal
2007-04-04 14:35 ` Denys [this message]
2007-04-04 14:13 ` HTB/act_mirred problem [was: one more... iproute commands lockup whole system] Patrick McHardy
2007-04-04 14:33 ` jamal
2007-04-04 14:50 ` Patrick McHardy
2007-04-05 1:33 ` jamal
2007-04-04 13:36 ` one more... iproute commands lockup whole system Patrick McHardy
2007-04-04 13:58 ` jamal
2007-04-04 14:07 ` Patrick McHardy
2007-04-04 14:30 ` jamal
2007-04-04 14:39 ` Patrick McHardy
2007-04-05 2:14 ` jamal
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=20070404143256.M86656@visp.net.lb \
--to=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).