From: "David Busby" <busby@pnts.com>
To: Bobby Hitt <Bobby.Hitt@bscnet.com>, netfilter@lists.netfilter.org
Subject: Re: Exposing Internal Host on Private network to Internet
Date: Mon, 23 Jun 2003 10:26:34 -0700 [thread overview]
Message-ID: <00b701c339ac$a05f63b0$1100000a@busbydev> (raw)
In-Reply-To: 007901c33941$05434ce0$0a00000a@BOBHITT
A: SNAT/DNAT
Start here: http://www.netfilter.org/documentation/HOWTO//NAT-HOWTO-6.html
and read through section 10 then search archives for examples
/B
----- Original Message -----
From: "Bobby Hitt" <Bobby.Hitt@bscnet.com>
To: <netfilter@lists.netfilter.org>
Sent: Sunday, June 22, 2003 21:36
Subject: Exposing Internal Host on Private network to Internet
> Hello all,
>
> I have a network using Linux as a gateway/firewall running NAT. This works
> perfectly to allow 5 internal hosts running Windows 2000/XP/Win98/Linux
> access to the Internet. Also the Linux gateway is running openVPN which
> allows me a secure connection to my Linux server in Connecticut for my
> Windows machines.
>
> I have setup a Windows 2000 Server on my network here running VPN server
> that I want to be exposed to the the outside to allow Windows clients
> running the VPN client to access the inside network here via the Windows
> 2000 server. I know I need to route ports 1723 47 for PPTP and 500 and
50-51
> for IPSec to the Windows 2000 Server, but have no idea how to do this with
> iptables.
>
> I used to run a cable router that allowed one host to be exposed to the
> Internet, which is how I want to setup the Linux router.
>
> Any help is appreciated,
>
> Bobby
>
next prev parent reply other threads:[~2003-06-23 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 4:36 Exposing Internal Host on Private network to Internet Bobby Hitt
2003-06-23 17:26 ` David Busby [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 4:56 George Vieira
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='00b701c339ac$a05f63b0$1100000a@busbydev' \
--to=busby@pnts.com \
--cc=Bobby.Hitt@bscnet.com \
--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.