The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Wildly OT: "Time" magazine


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hosting multiple internal web servers behind a single IP


  • To: ukha_d@xxxxxxx
  • Subject: Re: Hosting multiple internal web servers behind a single IP
  • From: "mark_harrison_uk2" <mph@xxxxxxx>
  • Date: Thu, 22 May 2003 14:41:08 -0000
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

--- In ukha_d@xxxxxxx, "Dan" <dtoma@f...> wrote:
> Hi Mark,
>
> Please let me comment your startements:
> > Actually, using different ports is a bad idea.
> >
> > A good number of UKHAers work for employers / clients where
internet
> > access is limited to port 80.
> Usually is limited to HTTP, but HTTP can be on another port too.
> So... even a Proxy/Firewall server is used then you can acces other
ports
> like:
> http://server.site.com:81 for
example.

Dan,

Yes, you can do that ...

BUT

... a large number of large companies that set up their firewalls to
allow port 80 access only.

I am happy to believe that you can access a wide range of ports from
YOUR office... I just wish that I had a similar set of firewall rules
on my clients' firewalls.

If you run http over port 81, a large number of companies will simply
not allow you to access it from the office.

The relevance to PAT? If you have a single IP address, then you
obviously need a router/firewall capable of sending different port
addressing to different internal machines. Router/firewall vendors
tend to call this "PAT" these days, to distinguish it from NAT.

You and I know that PAT is simply a special case of NAT, but, heh,
it's a term that seems to be growing in usage, so let's go with the
flow and use it.

Regards,

Mark



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.