742
Configuring an Interface with NAT
N0008589 3.3
Configuring NAT to change the source IP address used for WAN
traffic
Normally, when traffic originates from the Business Communications Manager, the source IP
address of the data packets is the IP address of interface that is on the edge. For example, if the
traffic is sent out of the WAN1 interface, the source IP address of the data packets is the IP address
of WAN1.
You can use NAT rules to change the source IP address of the data packets to one of the other data
network interfaces. To create this type of NAT rule, you must comply with the following rules:
•
The IP addresses you enter must be addresses that can be correctly routed.
•
The IP address you enter in the
Public IP
box must be the IP address of one of the other data
interfaces (for example, LAN1 or LAN2).
•
The source or destination port must match the ports specified in the
Public Port Range
box.
•
These NAT rules are only available on the WAN interface and the ISDN WAN backup
interface. They are not available on the V.90 WAN backup interface.
For an example of this configuration, refer to
“Example 3: Changing the source IP address of
WAN traffic” on page 745
.
Deleting a Rule to an Interface
1
Click the
Rule Setting
tab.
The Rule Setting screen appears.
2
Click the rule you want to delete.
3
On the
Configuration
menu, click
Delete Rule
.
A message appears that asks you to confirm the deletion.
4
Click the
Yes
button.
Configuring the Rule order
1
When you finish adding rules, click the
Rule Order
tab.
The Rule Order screen appears.
2
In the
Rule Order
box, configure the order of the rules.
3
Press
Tab
to update the screen.
Note:
Configure the rule order from most specific to most general. For example, a TCP
rule for one port should come before a general rule for all TCP traffic. IP rules should
come last.
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...