From: Eric Leblond <eric@inl.fr>
To: Andreas Micklei <andreas.micklei@ivistar.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Explicit source port mapping
Date: Wed, 01 Nov 2006 16:48:12 +0100 [thread overview]
Message-ID: <1162396092.4395.14.camel@localhost> (raw)
In-Reply-To: <200611011624.21822.andreas.micklei@ivistar.de>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hi,
I've never heard about such a feature.
Just a simple question :
Why do you want to do this ?
BR,
Le mercredi 01 novembre 2006 à 16:24 +0100, Andreas Micklei a écrit :
> Greetings,
>
> I have an unusual (maybe?) request. I have several private IPs (192.168.x.x)
> behind a Linux gateway. All are NATed to the Internet. Now I want to
> explicitely map each private IP to a fixed source port range on the WAN
> interface of the gateway.
>
> Example:
>
> Connections from 192.168.42.1 are mapped to source ports 1024 - 1279
> Connections from 192.168.42.2 are mapped to source ports 1280 - 1343
> Connections from 192.168.42.3 are mapped to source ports 1344 - 1408
> ...
>
> Quetions 1: Can netfilter do this for me?
> Question 2: If not, would it be easy to implement, and can someone give a
> suggestion where I should start? - Or even better: Has someone already
> implemented this?
>
> Sorry if my question sounds stupid. In the HOWTOs I could only find implicit
> source port mapping. Also I did not find a search interface for the
> mailinglist. So if this question is already answered, pointers are
> appreciated.
>
> regards,
> Andreas Micklei
>
>
--
Eric Leblond <eric@inl.fr>
INL
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-01 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 15:24 Explicit source port mapping Andreas Micklei
2006-11-01 15:48 ` Eric Leblond [this message]
2006-11-01 16:02 ` Andreas Micklei
2006-11-01 16:02 ` Frank Bulk
2006-11-01 16:10 ` Andreas Micklei
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=1162396092.4395.14.camel@localhost \
--to=eric@inl.fr \
--cc=andreas.micklei@ivistar.de \
--cc=netfilter@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.