From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] [TC/U32] Infrastructure for pretty printing
Date: Mon, 21 Apr 2008 10:15:55 -0400 [thread overview]
Message-ID: <1208787355.12249.199.camel@localhost> (raw)
In-Reply-To: <1208786335.12249.194.camel@localhost>
On Mon, 2008-21-04 at 09:59 -0400, jamal wrote:
> On Mon, 2008-21-04 at 15:29 +0200, Patrick McHardy wrote:
>
> > Something like that. But it used to already work the
> > way I described, at least for all parts where I tested
> > it so far (IIRC routes/rules/addresses/qdiscs/classes/filters).
>
> ok, missed that - i dont recall ever using it like that. But i will test
> and make sure it works. Now i get more of what you are saying with the
> env variables.
>
> > Yes, the first part needs to be stripped (filter/qdisc/class/...).
> > I usually do something like
> >
> > "ip link/route/addr del <paste dump without first word here>".
> >
> > Similar for tc.
>
> Ok, just tried it on my laptop; u32 (and maybe the rest of the filters)
> doesnt work in this mode. Essentially inputting is of the form
> "match u{8,16,32} value mask" and output is of form "match
> 32bitval/32bitmask"
Actually it is easy to fix but it may break existing scripts again.
Certainly will break mine. The simple solution would be:
Change output which goes like:
-------
match 00000000/00ff0000 at 4
-----
to
---------
match 00000000 00ff0000 at 4
---
So maybe just make sure the cooked mode works in the future and ignore
all the rest. Or for the raw format (when someone explicitly calls it
with -raw) output it with the space instead of /.
cheers,
jamal
prev parent reply other threads:[~2008-04-21 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 14:49 [PATCH 3/3] [TC/U32] Infrastructure for pretty printing jamal
2008-04-21 11:52 ` Patrick McHardy
2008-04-21 13:23 ` jamal
2008-04-21 13:29 ` Patrick McHardy
2008-04-21 13:58 ` jamal
2008-04-21 14:15 ` jamal [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=1208787355.12249.199.camel@localhost \
--to=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).