netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ivan <lagigliaivan@gmail.com>
To: "James King" <t.james.king@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: L2 NAT
Date: Thu, 4 Dec 2008 11:34:12 -0200	[thread overview]
Message-ID: <f4d9d6df0812040534i7053483eh49d20b08afa26296@mail.gmail.com> (raw)
In-Reply-To: <38bcb3ec0812031701k3df95b38y5bf4c77686a2347f@mail.gmail.com>

James,

Thanks for your soon reply!

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.

Please, let me know if you have any idea.

Thanks again.

ivan.




On Wed, Dec 3, 2008 at 11:01 PM, James King <t.james.king@gmail.com> wrote:
> On Wed, Dec 3, 2008 at 9:22 AM, ivan <lagigliaivan@gmail.com> wrote:
>> I would like to pass parameters to the kernel module in run time from
>> user space. These parameters could be IP address and MAC. Somebody
>> know how I can do this??
>
> Use the module_param functions (you probably want the string variant).
>  See http://tldp.org/LDP/lkmpg/2.6/html/x323.html for examples.
>
>> I was thinking about passing this parameters thorough a sysctl syscall
>> or using /proc filesystem, but I beleave that this is not the correct
>> way.
>
> Depends on if you need to be able to modify it after the module has
> already been loaded.  If not, a module parameter should suffice.
>
>
> HTH,
> James
>

  reply	other threads:[~2008-12-04 13:34 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 [this message]
2008-12-04 14:38     ` John Haxby
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=f4d9d6df0812040534i7053483eh49d20b08afa26296@mail.gmail.com \
    --to=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).