From: "Hime Junior" <hime@engineer.com>
To: li9@expert.ics.purdue.edu
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2] Re: what's the lockingrules for ip_conntrack_expect _list?
Date: Mon, 14 Oct 2002 08:35:23 -0500 [thread overview]
Message-ID: <20021014133524.75717.qmail@mail.com> (raw)
Hi ,
I believe the following book (by Rubini and Corbet) may be helpful in the module programming part of the task ...
ItŽs free and very well written .
If you have interest , just follow the link
http://www.oreilly.com/catalog/linuxdrive2/
to the online book .
Regards .
----- Original Message -----
From: Min Li <li9@expert.ics.purdue.edu>
Date: Sat, 12 Oct 2002 09:59:56 -0500 (EST)
To:
Subject: Re: [PATCH 2] Re: what's the lockingrules for ip_conntrack_expect_list?
>
> Dear All,
>
> I have to implement one senario which is to differentiate traffic coming
> through the router. For any new connections forwarded by the router, I
> have to change the source address of those packets. Also, the new
> source addresses are known at user space only. So, by simply using
> iptables NAT table, I won't be able to do that. In my application, I plan
> to inform the kernel about the new source addresses, and then create a
> address mapping table in the kernel. Then add a new module in iptables to
> take care of specially my scenario. So, in the kernel, I will do all the
> address translation based on the connection tracking results. However,
> that means I need to change iptables tool as well as adding a new module.
> I have never done linux kernel module programming before. Will it be
> possible for you to give me some advice?
>
> Thanks a lot.
>
> Min
>
>
>
>
Hime Junior
___________________________
Electronic and Control Engineer
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
"Free price comparison tool gives you the best prices and cash back!"
http://www.bestbuyfinder.com/download.htm
reply other threads:[~2002-10-14 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021014133524.75717.qmail@mail.com \
--to=hime@engineer.com \
--cc=li9@expert.ics.purdue.edu \
--cc=netfilter-devel@lists.netfilter.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 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.