From: Simon Oosthoek <simon.oosthoek@ti-wmc.nl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Herman Elfrink <herman.elfrink@ti-wmc.nl>
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Tue, 23 May 2006 16:51:14 +0200 [thread overview]
Message-ID: <44732162.6080107@ti-wmc.nl> (raw)
In-Reply-To: <20060523073851.39c3b5fe@localhost.localdomain>
Stephen Hemminger wrote:
> O
>> Usage
>> =====
>> - Load module:
>> modprobe flame [debuglevel=] [flm_topo_timer=]
>> : debug level, default: 1
>> : topology check timer (in seconds), default: 5
>> - Open/close a device with:
>> echo "up []" > /proc/net/flame/cmd
>> echo "down " > /proc/net/flame/cmd
>> : name of FLAME device, e.g. flm0
>> : comma-separated list of MAC devices (at least one) that are
>> used below the FLAME device. All of these must be up.
>> : comma-separated list of MAC addresses of devices
>> for which traffic should be ignored; each MAC address should
>> be a semicolon-separated list of 6 hex-pairs
>> - Get current forwarding info from FLAME:
>> cat /proc/net/flame/fwd
>> - Get nodes/cost information from MACINFO:
>> cat /proc/net/macinfo
>
>
> Use of /proc for an API is no longer desirable. Please rewrite.
> -
hmm, ok, I'm not sure this will happen anytime soon (being a rather low
priority thing, which is also the reason it's not submitted as patch to
the kernel and not signed off), but what is currently the desirable method?
Cheers
Simon
PS, I'm replying for my colleague, who will see this Monday at the
earliest ;-)
next prev parent reply other threads:[~2006-05-23 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 14:07 [ANNOUNCE] FLAME: external kernel module for L2.5 meshing Herman Elfrink
2006-05-23 14:38 ` Stephen Hemminger
2006-05-23 14:51 ` Simon Oosthoek [this message]
2006-05-23 15:09 ` Steven Rostedt
2006-05-23 15:20 ` Alan Cox
2006-05-23 14:48 ` Alan Cox
2006-05-23 14:41 ` Simon Oosthoek
2006-05-23 14:55 ` Erik Mouw
2006-05-23 15:00 ` Simon Oosthoek
2006-05-23 15:14 ` Alan Cox
2006-05-30 6:42 ` Herman Elfrink
2006-05-30 8:43 ` Herman Elfrink
2006-05-23 16:43 ` Stephen Hemminger
2006-05-23 17:43 ` Simon Oosthoek
2006-05-24 18:43 ` jamal
2006-05-25 10:53 ` Simon Oosthoek
2006-05-25 15:38 ` jamal
2006-05-30 7:01 ` Herman Elfrink
2006-05-24 20:50 ` Pavel Machek
2006-05-25 9:36 ` Simon Oosthoek
2006-05-30 8:29 ` Herman Elfrink
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=44732162.6080107@ti-wmc.nl \
--to=simon.oosthoek@ti-wmc.nl \
--cc=herman.elfrink@ti-wmc.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).