Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Søren Kent Jensen" <soren@familie-jensen.dk>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>,
	Ben Becker <bbecker2@cfl.rr.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT setup
Date: Sat, 20 Dec 2003 10:07:01 +0100	[thread overview]
Message-ID: <000901c3c6d8$a30a4260$0223a8c0@soren> (raw)
In-Reply-To: 20031220003051.GI17702@cannon.eng.us.uu.net

What you need is:
arp -s <Outside IP> <Outside MAC> pub
and a route to the <Outside IP> via the internal interface.

That should do the trick.

Regards
Søren Kent Jensen


----- Original Message -----
From: "Ramin Dousti" <ramin@cannon.eng.us.uu.net>
To: "Ben Becker" <bbecker2@cfl.rr.com>
Cc: <netfilter@lists.netfilter.org>
Sent: Saturday, December 20, 2003 1:30 AM
Subject: Re: NAT setup


> Hi Ben,
>
> Very interesting concept. There are two major parts to this:
>
> 1) Outbound packets from those static IP's to your gateway.
>    this can be done by enabling proxy-arp on your gateway
>    to answer to any arp request. This way the clients would
>    hand over their traffic to your gateway. Subsequently
>    your gateway would SNAT them and throw it on the Internet.
>
> 2) Inbound reply packets coming from the outside. This is a bit
>    tricky because, once they're in and de-SNATed, your gateway
>    must know where to send them to.  Since your gateway has only
>    one default route and no knowledge about those static IP's
>    behind it, it would automatically send the reply packets back
>    to the Internet. You might overcome this by blindly forwarding
>    these ESTABLISHED incoming packets through your internal interface
>    but you still need to somehow do an ARP for an IP outside your
>    LAN segment. At this point I don't have any simple solution
>    for that. But there are some very sharp ARP people here on the
>    list who could hack something together for you or give you
>    a pointer to an already hacked solution.
>
>
> Ramin
>
>
> On Fri, Dec 19, 2003 at 05:21:29PM -0500, Ben Becker wrote:
>
> > Hello everybody,
> >
> > I'm trying to figure out a way to set up basic NAT, but with the ability
> > to allow users on the local side to use any static IP configuration.
> > Quick Example: somebody has a static IP configured on their laptop,
> > stays at a hotel with Internet access, and will be able to browse the
> > Internet without changing their IP settings.
> >
> > My first question is: does anybody know what this feature is called?
> > Second question: Is it possible to do this with netfilter?  I'm thinking
> > this would require creating a new virtual interface for each user's
> > configuration to match their gateway (among other things), but I'm
> > hoping netfilter has some magical way of doing this (hoping).  If not,
> > does anybody know of any software that can do this?
> >
> > Regards,
> > Ben Becker
> >
>
>




  reply	other threads:[~2003-12-20  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 22:21 NAT setup Ben Becker
2003-12-20  0:30 ` Ramin Dousti
2003-12-20  9:07   ` Søren Kent Jensen [this message]
2003-12-20 15:36     ` Ramin Dousti

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='000901c3c6d8$a30a4260$0223a8c0@soren' \
    --to=soren@familie-jensen.dk \
    --cc=bbecker2@cfl.rr.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=ramin@cannon.eng.us.uu.net \
    /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