Page 51 / 77 Scroll up to view Page 46 - 50
Advanced Settings
51
Wireless Cable Voice Gateway CG3700EMR-1CMNDS
Wireless Card Access List
By default, any wireless computer or device that is configured with the correct SSID is
allowed access to your wireless network. For increased security, allow only specific wireless
computers and devices to access the wireless network based on their MAC addresses.
To set up wireless card access:
1.
Select
ADVANCED > Advanced Setup > Wireless Features
.
2.
Click the
Set Up Access List
button.
3.
Select the
Turn Access Control On
check box.
If the Turn Access Control On check box is selected, and the access control list is blank,
then no wireless computers or devices can connect to your wireless network.
4.
Click the
Add
button.
The Wireless Card Access List setup screen displays.
Page 52 / 77
Advanced Settings
52
Wireless Cable Voice Gateway CG3700EMR-1CMNDS
This screen displays a list of currently active wireless computers and devices and their
Ethernet MAC addresses.
5.
If the wireless computer or device you want displays in the list, select its radio button to
capture its MAC address. Otherwise, type its MAC address.
The MAC address is found on the computer or device.
6.
If no device name displays, type a descriptive name for the computer or device that you are
adding.
7.
Click the
Add
button.
The Wireless Card Access List screen displays.
8.
Click the
Apply
button.
Port Forwarding and Port Triggering
By default, the gateway blocks inbound traffic from the Internet to your computers except for
replies to your outbound traffic. Create exceptions to this rule for these purposes:
To allow remote computers on the Internet to access a server on your local network.
To allow certain applications and games to work correctly when your gateway does not
recognize their replies.
Your gateway provides two features for creating these exceptions: port forwarding and port
triggering. The next sections provide background information to help you understand how
port forwarding and port triggering work, and the differences between the two.
Remote Computer Access Basics
When a computer on your network accesses a computer on the Internet, your computer
sends your gateway a message containing the source and destination address and process
information. Before forwarding your message to the remote computer, your gateway must
modify the source information and create and track the communication session so that
replies can be routed back to your computer.
Here is an example of normal outbound traffic and the resulting inbound responses:
1.
You open a browser, and your operating system assigns port number 5678 to this
browser session.
2.
You type http://www.example.com into the URL field, and your computer creates a web page
request message with the following address and port information. The request message is
sent to your gateway:
Source address
. The IP address of your computer.
Source port number
. 5678, which is the browser session.
Destination address
. The IP address of www.example.com, which your computer
finds by asking a DNS server.
Page 53 / 77
Advanced Settings
53
Wireless Cable Voice Gateway CG3700EMR-1CMNDS
Destination port number
. 80, which is the standard port number for a web server
process.
3.
Your gateway creates an entry in its internal session table describing this communication
session between your computer and the web server at www.example.com. Before sending
the web page request message to www.example.com, your gateway stores the original
information and then modifies the source information in the request message, performing
Network Address Translation (NAT):
The source address is replaced with the public IP address of your gateway. This step
is necessary because your computer uses a private IP address that is not globally
unique and cannot be used on the Internet.
The source port number is changed to a number that is chosen by the gateway, such
as 33333. This step is necessary because two computers could independently be
using the same session number.
Your gateway then sends this request message through the Internet to the web server at
www.example.com.
4.
The web server at www.example.com composes a return message with the requested web
page data. The return message contains the following address and port information. The
web server then sends this reply message to your gateway:
Source address
. The IP address of www.example.com.
Source port number
. 80, which is the standard port number for a web server
process.
Destination address
. The public IP address of your gateway.
Destination port number
. 33333.
5.
When your gateway receives the incoming message, it checks its session table for an active
session for port number 33333. Finding an active session, the gateway then modifies the
message to restore the original address information that is replaced by NAT. Your gateway
sends this reply message to your computer, which displays the web page from
www.example.com. The message now contains the following address and port information:
Source address
. The IP address of www.example.com.
Source port number
. 80, which is the standard port number for a web server
process.
Destination address
. The IP address of your computer.
Destination port number
. 5678, which is the browser session that made the initial
request.
6.
When you finish your browser session, your gateway eventually detects a period of inactivity
in the communications. Your gateway then removes the session information from its session
table, and incoming traffic is no longer accepted on port number 33333.
Port Triggering to Open Incoming Ports
In the preceding example, requests are sent to a remote computer by your gateway from a
particular service port number, and replies from the remote computer to your gateway are
directed to that port number. If the remote server sends a reply to a different port number,
your gateway does not recognize it and discards it. However, some application servers (such
Page 54 / 77
Advanced Settings
54
Wireless Cable Voice Gateway CG3700EMR-1CMNDS
as FTP and IRC servers) send replies to multiple port numbers. Using the port triggering
function of your gateway, you can tell the gateway to open more incoming ports when a
particular outgoing port originates a session.
An example is Internet Relay Chat (IRC). Your computer connects to an IRC server at
destination port 6667. The IRC server not only responds to your originating source port, but
also sends an “identify” message to your computer on port 113. Using port triggering, you can
tell the gateway, “When you initiate a session with destination port 6667, you must allow
incoming traffic also on port 113 to reach the originating computer.” Using steps similar to the
preceding example, the following sequence shows the effects of the port triggering rule you
have defined:
1.
You open an IRC client program to start a chat session on your computer.
2.
Your IRC client composes a request message to an IRC server using a destination port
number of 6667, the standard port number for an IRC server process. Your computer then
sends this request message to your gateway.
3.
Your gateway creates an entry in its internal session table describing this communication
session between your computer and the IRC server. Your gateway stores the original
information, performs Network Address Translation (NAT) on the source address and port,
and sends this request message through the Internet to the IRC server.
4.
Noting your port triggering rule and having observed the destination port number of 6667,
your gateway creates an additional session entry to send any incoming port 113 traffic to
your computer.
5.
The IRC server sends a return message to your gateway using the NAT-assigned source
port (as in the previous example, say port 33333) as the destination port. The IRC server
also sends an identify message to your gateway with destination port 113.
6.
When your gateway receives the incoming message to destination port 33333, it checks its
session table for an active session for port number 33333. Finding an active session, the
gateway restores the original address information that is replaced by NAT and sends this
reply message to your computer.
7.
When your gateway receives the incoming message to destination port 113, it checks its
session table and finds an active session for port 113 associated with your computer. The
gateway replaces the destination IP address of the message with the IP address of your
computer and forwards the message to your computer.
8.
When you finish your chat session, your gateway eventually senses a period of inactivity in
the communications. The gateway then removes the session information from its session
table, and incoming traffic is no longer accepted on ports 33333 or 113.
To configure port triggering, you need to know which inbound ports the application needs.
Also, you need to know the number of the outbound port that triggers the opening of the
inbound ports. You can usually find this information by contacting the publisher of the
application or user groups or newsgroups.
Note:
Only one computer at a time can use the triggered application.
Page 55 / 77
Advanced Settings
55
Wireless Cable Voice Gateway CG3700EMR-1CMNDS
Port Forwarding to Permit External Host Communications
In both of the preceding examples, your computer initiates an application session with a
server computer on the Internet. However, you need to allow a client computer on the
Internet to initiate a connection to a server computer on your network. Normally, your
gateway ignores any inbound traffic that is not a response to your own outbound traffic. You
can configure exceptions to this default rule by using the port forwarding feature.
A typical application of port forwarding can be shown by reversing the client-server
relationship from the previous web server example. In this case, a browser on a remote
computer accesses a web server running on a computer in your local network. Using port
forwarding, you can tell the gateway, “When you receive incoming traffic on port 80 (the
standard port number for a web server process), forward it to the local computer at
192.168.0.123.” The following sequence shows the effects of the port forwarding rule you
have defined:
1.
The user of a remote computer opens a browser and requests a web page from
www.example.com, which resolves to the public IP address of your gateway. The
remote computer composes a web page request message with the following destination
information:
Destination address
. The IP address of www.example.com, which is the address of
your gateway.
Destination port number
. 80, which is the standard port number for a web server
process.
The remote computer then sends this request message through the Internet to your
gateway.
2.
Your gateway receives the request message and looks in its rules table for any rules
covering the disposition of incoming port 80 traffic. Your port forwarding rule specifies that
incoming port 80 traffic is forwarded to local IP address 192.168.0.123. Therefore, your
gateway modifies the destination information in the request message:
The destination address is replaced with 192.168.0.123.
Your gateway then sends this request message to your local network.
3.
Your web server at 192.168.0.123 receives the request and composes a return message
with the requested web page data. Your web server then sends this reply message to your
gateway.
4.
Your gateway performs Network Address Translation (NAT) on the source IP address, and
sends this request message through the Internet to the remote computer, which displays the
web page from www.example.com.
To configure port forwarding, you need to know which inbound ports the application needs.
Usually you can find this information by contacting the publisher of the application or the
relevant user groups and newsgroups.
How Port Forwarding Differs from Port Triggering
The following points summarize the differences between port forwarding and port triggering:

Rate

4 / 5 based on 1 vote.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top