Filter
Top Products
Modifying Port Settings
171
Modifying the ADSL Barricade’s port numbers
In some cases, you may want to assign non-standard port
numbers to the HTTP and Telnet servers that are embedded
on the ADSL Barricade. The following scenario is one example
where changing the HTTP port number may be necessary:
You have an externally visible Web server on your LAN,
with a NAT Rule (RDR flavor) that redirects incoming HTTP
packets to that Web server. When incoming packets contain
a destination IP address of your public IP address (which is
assigned to the ADSL Barricade’s WAN port) and the standard
Web server port number 80, the NAT Rule recognizes the
port number and redirects the packets to your Web server’s
local IP address.
Assume in this scenario that you also want to enable external
access to the ADSL Barricade's Configuration Manager,
so that your ISP can log in and manager your system,
for example. Accessing the Configuration Manager requires
accessing
the ADSL Barricade's own Web server (also called
its HTTP server). In this case, you would want to use the Port
Settings feature to assign a non-standard port number to the
ADSL Barricade
's HTTP server. Without a non-standard port
number,
the NAT Rule would redirect your ISP's log in
attempt to your LAN HTTP server rather than to the HTTP
server on the ADSL Barricade.
Thereafter, when your ISP wants to log on to your
Configuration Manager, they would type your IP address in
their browser, followed by a colon and the non-standard port
number, as shown in this example: http://10.0.1.16:61000.
Your ISP may also have special circumstances that require
changing the port numbers; contact them before making any
changes here.