Article View: uk.comp.home-networking
Article #74Re: Networking 20-30 PC's to the internet ..
From: Yousuf Khan
Date: Wed, 14 Nov 2001 14:03
Date: Wed, 14 Nov 2001 14:03
40 lines
3599 bytes
3599 bytes
"Peter Kirby" <peter.news@aworld.demon.co.uk> wrote in message
news:MPG.165c6c7b20e9b93c9896f2@news.demon.co.uk...
> I noticed this recently in iptraf. I don't know what game it is but it
> uses UDP and packets go from port 27005 to port 27005. This means that
> on any NAT based network I believe only 1 person could connect and play
> at once. That is unless the server has some fallback measure which uses
> a different port number, or allows the remote port to be different that
> the server port.
A NAT firewall/router should still able to track which packets go to which
machines, simply with the combination of incoming and outgoing port numbers
and their IP addresses. It is simply a matter of making the NAT software
smarter and able to track more things in its tables.
For example, you got an external IP (to the Internet) address attached to
the router, say n.n.n.n. It's got an internal IP address (to the LAN) of
x.x.x.1. There are two clients on the inside, say x.x.x.2, and x.x.x.3. So
if the clients need to connect to port 27005 on the same server on the
Internet simultaneously, they would each select a random outgoing port
number and connect to port 27005 of x.x.x.1. The internal table would look
like this:
Outgoing Incoming
x.x.x.2:2000 x.x.x.1:27005
x.x.x.3:4500 x.x.x.1:27005
So as you can see even though both clients are hooking to the same IP and
incoming port on the NAT router, they have their own unique IP and outgoing
port numbers which the NAT software should be easily able to track.
The NAT router then regenerates the requests over the Internet for each of
the clients. It will then generate separate random outgoing ports for each
client and and connect to a server on incoming port 27005 on the internet.
It will have a separate table for the Internet side of the connection.
This should all work as long there isn't any connect backs from the outside
servers back to the clients in the LAN. But even that could be handled with
enough intelligence.
Yousuf Khan
Technical Details
Message-ID:
<xQuI7.527030$j65.130271595@news4.rdc1.on.home.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news4.rdc1.on.home.com.POSTED!not-for-mailReferences:
<3bf0633e.4633566@news.demon.co.uk> <oNZH7.563$pp4.156233@dfiatx1-snr1.gtei.net> <miu1vtg0sqcvn44eehropefa60u7jk6737@4ax.com> <MPG.165c6c7b20e9b93c9896f2@news.demon.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1036bc,79d2afd0f99f8b0a X-Google-Attributes: gid1036bc,public X-Google-Thread: 10869b,79d2afd0f99f8b0a X-Google-Attributes: gid10869b,public X-Google-Thread: f5142,79d2afd0f99f8b0a X-Google-Attributes: gidf5142,public X-Google-Thread: 101fc4,79d2afd0f99f8b0a X-Google-Attributes: gid101fc4,public X-Google-ArrivalTime: 2001-11-14 06:03:10 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news4.rdc1.on.home.com.POSTED!not-for-mail From: "Yousuf Khan" <bbbl67@nospam.yahoo.com.spam> Newsgroups: uk.comp.home-networking,demon.tech.pc,uk.comp.misc,comp.sys.ibm.pc.hardware.networking References: <3bf0633e.4633566@news.demon.co.uk> <oNZH7.563$pp4.156233@dfiatx1-snr1.gtei.net> <miu1vtg0sqcvn44eehropefa60u7jk6737@4ax.com> <MPG.165c6c7b20e9b93c9896f2@news.demon.co.uk> Subject: Re: Networking 20-30 PC's to the internet .. Lines: 42 Organization: My own man X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <xQuI7.527030$j65.130271595@news4.rdc1.on.home.com> Date: Wed, 14 Nov 2001 14:03:09 GMT NNTP-Posting-Host: 24.112.132.79 X-Complaints-To: abuse@home.net X-Trace: news4.rdc1.on.home.com 1005746589 24.112.132.79 (Wed, 14 Nov 2001 06:03:09 PST) NNTP-Posting-Date: Wed, 14 Nov 2001 06:03:09 PST