From: John Haxby <john.haxby@oracle.com>
To: ivan <lagigliaivan@gmail.com>
Cc: James King <t.james.king@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: L2 NAT
Date: Thu, 04 Dec 2008 14:38:34 +0000 [thread overview]
Message-ID: <4937EB6A.9050109@oracle.com> (raw)
In-Reply-To: <f4d9d6df0812040534i7053483eh49d20b08afa26296@mail.gmail.com>
ivan wrote:
> I think that your answer is a good approach, but I would like to
> pass/modify the module parameters while this one is running. I believe
> this way allows to the user more flexibility to add/configure the
> module behavior.
>
You can do that with module parameters, they appears as files in
/sys/module/<module-name>/parameters and, given the right permissions,
you can modify them as you see fit.
jch
next prev parent reply other threads:[~2008-12-04 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 17:22 L2 NAT ivan
2008-12-04 1:01 ` James King
2008-12-04 13:34 ` ivan
2008-12-04 14:38 ` John Haxby [this message]
2008-12-04 15:43 ` ivan
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=4937EB6A.9050109@oracle.com \
--to=john.haxby@oracle.com \
--cc=lagigliaivan@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=t.james.king@gmail.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).