User's Manual

Rajant Corporation ME BreadCrumb User Guide
- 24 -
• The IPv4 port(s) at the destination address to which the forwarded traffic is to be forwarded (usually the
same as the ports described above).
The checkbox marked ‘Enable’ specifies whether a particular forward configuration is active. This allows an
administrator to pre-configure port forwards and selectively enable or disable them in the future.
When a port forward has been configured, click the ‘Add’ button to the right in order to add it to the current
configuration.
You may add as many port forwards as necessary to a BreadCrumb.
Example: Port Forwarding Configuration for a Web Server
Suppose a web server exists somewhere within a BCWN, and one of the BCWN BreadCrumb devices is serving
as a Gateway connected to the Internet. In order to allow users on the Internet to access the web server, the
following port forward configuration is required:
3.6.1 EXT. PORTS
We will allow Internet users to access the internal web server using port 80, the default for web traffic.
The external port range is therefore 80-80.
3.6.2 PROTOCOL
Web traffic uses TCP, not UDP, so only the TCP checkbox should be checked.
3.6.3 IP ADDRESS
This is the IP address of the web server on the BCWN. Note that this should be a fixed IP address, as addresses
obtained via DHCP can change overtime and thereby cause the port forwarding to fail.
3.6.4 TO PORTS
The web server on the BCWN is listening for connections on port 80, so the port range should be 80-80.
Once this port forward is enabled and saved to the BreadCrumb, Internet users may direct their web
browsers to the Gateway BreadCrumb device’s external IP address in order to reach the web server on
the BCWN.
3.7 SECURITY
Several levels of security are available for the BreadCrumb Wireless Network, which may be used individually or
in combination with one another. We are constantly adding security features, so please contact your Rajant
Account Representative if you have specific needs not included in this section.
3.7.1 WEP
WEP (Wired Equivalency Protocol) was the first scheme to provide security for IEEE 802.11 communications.
Although since its release it has been determined to contain serious weaknesses, WEP remains an effective means
to prevent casual eavesdropping.
WEP settings are made network-wide; all BreadCrumb devices and wireless clients must agree on a WEP key in
order to establish and maintain communications.
To enable WEP on a BCWN, make sure that all of the BreadCrumbs to configure are visible in BCAdmin. Then
choose Security, then WEP Settings to display the following window: