Novell BorderManager provides Remote Access Solution through IPSec and IKE technologies. Administrators can define the networks to allow or deny access for specific users using iManager framework.

In BM 3.8 and BM 3.8 SP1 a traffic rule can contain multiple Destination Networks. But with later support packs a traffic rule can hold only one Destination network. The iManager framework restricts the administrator from adding more than one Destination network to a traffic rule. The Destination network can be either IP Address Range or a Network. So the Migration from BM 3.8 or BM 3.8 SP1 to Later Versions will have problems with Client-To-Site functionality. In the sense though the traffic rules are pushed to the client the networks cannot be accessed because of the technical constraint.

This tool will split the single rule with multiple networks into individual rules each containing a single network.

Prerequisites

1. Linux OS

• Perl 5.8 or above is installed in the machine.

Instructions

1. Unzip the file (tar -zxvf traffic_tool.tar.gz)s

• cd traffic_tool

• ./script.sh

• Enter the BM VPN Server IP

• Enter the BM VPN Server Port(Enter the clear text LDAP Port eg 389)

• Enter the administrator username

• Enter the administrator password

• Enter the Traffic rule name in the following format(This the Traffic rules in the Traffic Rules Tab in the iManager
  policyRuleName=<PolicyRuleName<,cn=VPN Rules,cn=<C2S Service Name>,<container>
  Example: policyRuleName=TheRule,cn=VPN Rules,cn=NovellC2S,o=novell
  
  
  Note: Make sure there is no space after the commas

• If you have more rules, enter y and enter the rules in the above format.

• You can retain the original rule or delete the original rule. Press 'n' if you do not want to retain the old rule.

Result

The rule with multiple networks will be split and added as single rules with corresponding networks.