Re: (ASCEND) Pipeline 50 and NAT

["Patrick Marshall" <patrick@digital.net>]

You can have the ISP assign you one static IP and then run nat.   On your
end
just set the pipeline for NAT.  Here is a good example on the setup.
http://aos.ascend.com/aos:/gennavviewer.html?doc_id=0900253d80006ce6&doc_hea
der=terminal
If you still need to run SMTP email, make sure to have the ISP point your
mail
to the single IP and then map port 25 to your SMTP server.

Thanks
Patrick


----- Original Message -----
From: <hjong@triview.nl>
To: <ascend-users@max.bungi.com>
Sent: Thursday, November 11, 1999 6:23 AM
Subject: (ASCEND) Pipeline 50 and NAT


> I'm using a Pipeline 50 to connect our network to the Internet. We have an
> ISP account that includes Internet access via the Pipeline 50, SMTP e-mail
> relay, and domain name registration. We also got 32 IP addresses to use on
> our internal systems. The company is growing, and soon we'll be out of
> addresses.
>
> I could request more IP numbers from the ISP, but I'd rather implement
NAT.
> Now the Pipeline manuals are a bit fuzzy on this (well, not just this...);
> AFAI understand, when I use NAT on the Pipeline, it will request IP
> addresses from the remote server for each connection. Is this correct?
> At the moment, the Pipeline has a fixed address, and I don't think the ISP
> does DHCP on these links, so I'd be stuck.
>
> Other solutions?
>
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>