SMTP goes to 123.123.123.123:25 WWW to 123.123.123.123:80 Telnet to 123.123.123.123:23 FTP to 123.123.123.123:21 etc... As the only address that's visible to the outside world is that assigned by the MAX (or whatever the Pipeline's connecting into) then ALL services behind the Pipeline are known by that address. All the hard work is done by the Pipeline with what it calls 'Static Mappings' - these simply map traffic with a destination address of the Pipeline coming in on (say) TCP port 25 to the local IP address of the server running that service and the port it's running the service on. ie SMTP traffic comes in (Port 25) and needs to go to server 11.22.33.44 on port 25, so the static map says 'Any traffic inbound on 25 gets routed to 11.22.33.44 on 25' You can even set a default 'route' for traffic not covered by the static maps. I'm not clear as to what path to take if multiple servers exist for a service but it'd probably involve a bit of port-mapping somewhere along the line. Check the release notes for V5.1a on Ascend's FTP server for a more detailed discussion of NAT and it's implementation. Hope this heps Tony Lloyd - Network Sstems Engineer Onyx Internet -----Original Message----- From: Edwin Yeh [SMTP:ery2@po.cwru.edu] Sent: Wednesday, November 12, 1997 10:00 PM To: edwin_yeh Cc: ascend-users@bungi.com Subject: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)? I don't know exactly how NAT works. (I'll be interested to know. All I can guess, is that when the packet exists the router, somehow the header information is wrapped.) But can you run servers (such as ftp server or web server) behnid the Pipeline router (running NAT)? In other words, is there a way for outside users to point to a specific machine inside the NAT subnet. Thanks. Edwin P.S. I can think of a solution. That is, don't use NAT and run DNS after the pipeline router. The DNS effectively become the router and the pipeline effectively become a Terminal Adapter. But if this is the case, why buy the pipeline. We can do it with ~$150 ISDN TA. We are using pipeline because it's cost effective for a subnet running multiple machines and the router performs better than the computer. However, functionality will come before performance. If we cannot solve this problem, we will be forced to drop the pipeline solution. ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <STRONG>Follow-Ups</STRONG>: <UL> <LI><STRONG><A HREF="msg10720.html">Re: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)?</A></STRONG></LI> <UL> <LI><EM>From</EM>: Kevin Smith <kevin@ascend.com></LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10717.html">Re: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)?</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10705.html">Re: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)?</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10767.html">Re: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)?</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10720.html">Re: (ASCEND) Q. Can you run servers behind Pipeline (running NAT)?</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail3.html#10704"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd240.html#10704"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>