Um did you read all of my posting? There is no information in the datagram pertaining to a port # other than the udp port. If I send a packet from any machine with a specific port destionation to a Pipeline (doing Single IP NAT) the port # gets mangled. This is perfectly fine. Everyone knows that unless you tell the Pipeline to do a specific mapping for that port this will happen. This is what NAT does. Perfectly normal. Its not a problem with Quake, its not a problem with the Pipeline. It just the way NAT works. ++ 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="msg10353.html">Re: (ASCEND) Quake/QW and Pipeline 75 and NAT</A></STRONG></LI> <UL> <LI><EM>From</EM>: Jason Eggleston <jason@jet.net></LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10351.html">Re: (ASCEND) Quake/QW and Pipeline 75 and NAT</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10342.html">(ASCEND) FUSES !!</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10345.html">Re: (ASCEND) Quake/QW and Pipeline 75 and NAT</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10353.html">Re: (ASCEND) Quake/QW and Pipeline 75 and NAT</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#10350"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd226.html#10350"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>