From: Michael Gale <mgale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: public ip on LAN
Date: Fri, 2 Jan 2004 10:42:33 -0700 [thread overview]
Message-ID: <20040102104233.17d29742.mgale@utilitran.com> (raw)
In-Reply-To: <1073064684.2995.37.camel@jasiiitosh.nexusmgmt.com>
I have never used VoIP .. but would it not be easier to setup a separate box with a VPN server and all the needed software ... of place it on the firewall box .. but a separate one is nice ... then have the clients use it for VPN access and tunnels ?
Michael.
On Fri, 02 Jan 2004 12:31:24 -0500
"John A. Sullivan III" <john.sullivan@nexusmgmt.com> wrote:
> Are these users running VoIP and others through a VPN tunnel and the
> problem is using NAT on an IPSec tunnel or are they using VoIP AND an
> IPSec VPN tunnel and each presents a problem. If it is just using NAT
> and an IPSec VPN, investigate using NAT Traversal. Otherwise, if you
> cannot find an application proxy or an iptables helper for every
> application they want to use, you may be stuck with DNAT and SNAT for
> those users - John
>
> On Fri, 2004-01-02 at 12:40, Amit Pasari wrote:
> > Dear Antony,
> >
> > 1. Do your clients *really* need public IPs on the machines themselves, or is
> > it sufficient if you use NAT and ensure that packets to some public IP reach
> > a specific client, and packets from that client have the public IP when they
> > return to the Internet? What protocols / services are you using which
> > require public IPs on the client machines?
> > >>
> > Well my clients wants to use Voip / Webserver and other VPN applications .
> > So they need public ip .
> >
> > 2. We can't answer your question in any detail without more information about
> > the topology of your network, in particular whether your ISP provides a small
> > subnet to you, terminated at your netfilter machine, or whether that subnet
> > block can be routed across the netfilter machine so that thLet me explain
> > on My LAN i have ip address - 172.16.1.1
> > subnet - 255.255.0.0
> > on My WAN i have ipaddress - 203.122.51.178
> > subnet - 255.255.255.240
> >
> > Yes i have read many things , but didn't find the solution.
> >
> > Regards
> > Amit
> --
> John A. Sullivan III
> Chief Technology Officer
> Nexus Management
> +1 207-985-7880
> john.sullivan@nexusmgmt.com
>
>
--
Michael Gale
Network Administrator
Utilitran Corporation
next prev parent reply other threads:[~2004-01-02 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 16:30 public ip on LAN Amit Pasari
2004-01-02 16:22 ` Michael Gale
2004-01-02 16:30 ` Antony Stone
2004-01-02 16:47 ` Michael Gale
2004-01-02 16:23 ` Antony Stone
2004-01-02 17:40 ` Amit Pasari
2004-01-02 17:31 ` John A. Sullivan III
2004-01-02 17:42 ` Michael Gale [this message]
2004-01-02 16:24 ` John A. Sullivan III
[not found] ` <6.0.0.22.0.20040102223444.0305cdb0@amitpasari.com>
2004-01-02 17:01 ` John A. Sullivan III
-- strict thread matches above, loose matches on Subject: below --
2004-01-02 17:19 Amit Pasari
2004-01-02 17:15 ` Michael Gale
2004-01-02 17:27 ` Fabien LE BLEVEC
2004-01-02 18:30 ` Craig Steadman
2004-01-02 18:42 ` Antony Stone
2004-01-02 18:46 ` Michael Gale
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=20040102104233.17d29742.mgale@utilitran.com \
--to=mgale@utilitran.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox