If so, I see no reason for this not to work, but it will suffer from any of
the limitations of not having a 'real ip' address. It's kinda like dialing
a RAS server in a clients office that uses NAT for Internet connectivity.
If the only purpose is to surf then should be adequate, programs requiring
real static IP (like SMTP delivery with ETRN) definitely pose some problems.
----- Original Message -----
From: Josh Hillman <firstname.lastname@example.org>
Sent: Tuesday, October 26, 1999 9:03 PM
Subject: Re: [NTISP] Does anyone use NAT for dialup?
> From: David Payer <email@example.com>
> > I might be able to ask my upstream for more address space but if I use
> > dialups I could get around doing that.
> > Has anyone done that before and if so was there a problem you found in
> > so?
> We have a couple customers that are doing this. As far as we're
> they're no different from any other customer. The NAT is handled by their
> ISDN routers. We just assign them either a dynamic or static (one
> is static, the other is dynamic) IP and their ISDN router handles the
> > (NAT = Network Address Translation, using RFC defined space like
> 10.10.10.X or
> > 192.168.0.1, etc and using a box to translate that to your customers)
> > I have done it in a proxy situation on a network using Wingate before
> > network had no problem but the rule typically is, if you don't define
> > want passed through, it isn't passed through on that kind of software
> > don't want to have to be making up new rules for the box as I go. I
> it to
> > be seamless for the customer of course.
> > I would appreciate comments.
> > David Payer
> > OMNI Internet
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: