All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:58:55 -0400	[thread overview]
Message-ID: <1208786335.12249.194.camel@localhost> (raw)
In-Reply-To: <480C96D3.5050809@trash.net>

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"
I think it should be easier to do with cooked mode and i will look into
it.

> It would be nice to dump it in a format that can be piped
> into batch mode without further changes, so it would have
> to insert "add" between "filter" and "protocol".

An additional processing may be needed in the save script.

cheers,
jamal


  reply	other threads:[~2008-04-21 13:59 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 [this message]
2008-04-21 14:15         ` 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=1208786335.12249.194.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 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.