Re: Understanding ports?

From: Barry Margolin (barmar@genuity.net)
Date: 12/12/02


From: Barry Margolin <barmar@genuity.net>
Date: Thu, 12 Dec 2002 20:38:57 GMT

In article <H70v4y.HKB@news.boeing.com>, tofu <tofu@synergy.com> wrote:
>I often see "ports" discussed in regard to networks, routers and computer
>security.
>
>What are ports? Is there an easy tutorial URL you can refer me to, to help
>me understand whats being talked about when someone refers to a particular
>port number?

The best way to understand this is to get a basic tutorial on TCP/IP. I'll
try to answer very briefly and superficially (and not even very accurately
-- I'm purposefully omitting some details because I want it to be simple).

Port numbers are the way that correspondents of TCP and UDP packets are
identified. Servers typically listen for connections on a well-known port
that's associated with the service they provide (e.g. port 25 for SMTP).
There's also a port at the client end that's dynamically allocated, for use
in routing the replies back to the client application.

You could think of ports as being analogous to extension numbers in a phone
system. The IP address is like the main phone number, which gets you to
the machine or company, and the port/extension identifies the specific
process/office.

>Say if I was watching network activity with Wallwatcher. What do the port
>numberings signifiy? What would be important to look for in terms of
>unauthorized attempts to access my computer.

You need to know which services you're intentionally accessing, and their
associated port numbers. For instance, when you're accessing a web server,
you'll usually be connecting to its port 80 and/or 443 (the latter is used
for SSL-encrypted connections), so packets with those remote ports are OK.

For the most part, port numbers under 1024 are used for well-known
services. If your computer is not a server, you should rarely see incoming
packets with low destination ports; such packets suggest someone is trying
to access your system (they may be doing a port scan, trying to find any
ports your system is listening on).

-- 
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


Relevant Pages

  • Re: What is going on with my Dialup?
    ... also forward it to an unused port, and have that port provide the ... verses the RST or ICMP 3,3. ... The lack of response causes the remote computer to make ... Others think that by not responding to unwanted packets, ...
    (comp.os.linux.networking)
  • Re: OT .. Road Warrior communications question
    ... The data on the Internet is sent in little packets. ... The packets addressed to port 80 ... Likewise, at the mail server receiving the packets, it knows the return ... Why would e-mail work on the web but not from your e-mail software? ...
    (alt.guitar.bass)
  • Re: Logs: Many hits with source port of 80
    ... The hits from source port 80 to dest port 37852 are IMHO almost ... you should probably see a couple other packets - perhaps ... packets if either you send the load balancer a packet, ... >>I have seen similar hits for the past three months. ...
    (Incidents)
  • Re: Error 720 connecting to server via VPN
    ... By default the router's firewall is configured to drop ICMP packets ... Select WAN Setup> Advanced> Respond to Ping on Internet Port. ... server and the Internet allow GRE packets. ... routers on the user's network are also configured to allow GRE packets. ...
    (microsoft.public.windows.server.sbs)
  • Re: WORM? ... server generating NBT-NS (port 137) traffic on WAN interface
    ... You have a concern about the outbound port 137 traffic in the SBS domain. ... The UDP 137 is related to the NetBIOS Over TCP/IP name service. ... I did run NETMON on the SBS2003 box, it did find the extraneous packets ... ... connected to the Internet (If the SBS server is the 2 NICs scenario). ...
    (microsoft.public.windows.server.sbs)

Quantcast