UPnP vs. Port Address Translation

  • Thread starter Thread starter Tim Callaghan
  • Start date Start date
T

Tim Callaghan

I'm looking to purchase an inexpensive router (with wireless) for my
office to backup the firewall (in case the firewall goes down).

I need the device to support Port Address Translation (PAT) so I can
create rules like sending all TCP Port 26 Traffic to an internal IP of
192.168.0.51 on Port 25.

Many new devices do not mention PAT but talk about supporting UPnP,
which looks quite similar to PAT. I spoke with LinkSys technical
support but the engineer didn't even come close to answering my
question about the differences.

Can someone let me know if UPnP is just a fancy name for PAT or if
it's something entirely different?

Thanks,
Tim
 
Hi Tim,

Interesting question. UPnP is at the device level and allows a device t be detected on a
network when it is connected. It is limited/allowed to function as a network device based on
the device's built in properties. The "port address translation" is done automatically based on
what ports the device OS needs to function.

I think where the confusion comes in is that there are UPnP devices that have the ability to
configure ports, such as routers and firewalls that are UPnP compliant. If the device allows
port configuraiton, then that is an option. But the UPnP architecture itself is an "automatic
detection standard" for the device itself.

Here are a few links to some resources:
http://www.upnp.org/
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/winxppro/evaluate/upnpxp.asp?frame=true

Hope this helps,
Gary






--------------------
'--'From: Tim Callaghan <[email protected]>
'--'Newsgroups: microsoft.public.win2000.networking
'--'Subject: UPnP vs. Port Address Translation
'--'Organization: CrunchTime!
'--'Message-ID: <[email protected]>
'--'X-Newsreader: Forte Agent 1.93/32.576 English (American)
'--'MIME-Version: 1.0
'--'Content-Type: text/plain; charset=us-ascii
'--'Content-Transfer-Encoding: 7bit
'--'Lines: 17
'--'Date: Wed, 28 Jan 2004 11:26:28 -0500
'--'NNTP-Posting-Host: 209.58.165.58
'--'X-Complaints-To: (e-mail address removed)
'--'X-Trace: nntp-post.primus.ca 1075306860 209.58.165.58 (Wed, 28 Jan 2004 11:21:00 EST)
'--'NNTP-Posting-Date: Wed, 28 Jan 2004 11:21:00 EST
'--'Path: cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!
newsfeed00.sul.t-online.de!t-online.de!npeer.de.kpn-eurorings.net!news2.telebyte.nl!
news.moat.net!news.primus.ca!news.primus.ca!nntp-post.primus.ca!53ab2750!not-for-mail
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:52920
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'I'm looking to purchase an inexpensive router (with wireless) for my
'--'office to backup the firewall (in case the firewall goes down).
'--'
'--'I need the device to support Port Address Translation (PAT) so I can
'--'create rules like sending all TCP Port 26 Traffic to an internal IP of
'--'192.168.0.51 on Port 25.
'--'
'--'Many new devices do not mention PAT but talk about supporting UPnP,
'--'which looks quite similar to PAT. I spoke with LinkSys technical
'--'support but the engineer didn't even come close to answering my
'--'question about the differences.
'--'
'--'Can someone let me know if UPnP is just a fancy name for PAT or if
'--'it's something entirely different?
'--'
'--'Thanks,
'--'Tim
'--'


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included
script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best
directed to the newsgroup/thread from which they originated.
 
Back
Top