Specifications

Configuring the BSC Managed Interface

BlueSecure™ Controller Setup and Administration Guide 4-21

• Netmask of Remote Subnet - When handing out addresses to wireless clients via

DHCP, the BSC must include the clients' netmask address. This is the netmask

address that is assigned to clients on the managed remote subnet.

• Additional IP addresses that DHCP relay packets can be sourced from - Used

only for HSRP, put all the physical router addresses here (a comma separated list

of additional DHCP relay endpoints).

• NAT the addresses to the protected interface address - Mark this checkbox to

map all client IP addresses on the managed remote subnet to the IP address of

the BSC protected interface.

If this checkbox is cleared, NAT is disabled.

Substitute IP address for remote clients NAT - If you have marked the preceding

NAT checkbox, and you want remote subnets to use a substitute NAT IP instead

of protected interface address, enter the substitute NAT IP in this field. This allows

you to determine the point of origin for traffic originating in a remote subnet.

5. Optional. Using the IP Range Assignments table, define role assignments for devices/

users that have been assigned static IP addresses as they connect to the BSC on the

managed remote subnet. Enter a range of IP addresses using the From and To fields.

6. Optional. Using the Custom User Login drop-down menu, specify which login page

to display to users logging into the BSC on the managed remote subnet—the default

user login page or a customized page you have defined. See “Customizing the User

7. Click Save to save the settings to the BSC database. Click Save and create another to

continue creating Managed Remote Subnets. Click Next to set up the DHCP

parameters on the DHCP settings for new Managed Remote Subnet page as shown in

Figure 4-14.

a) Configure the BSC DHCP server settings, as appropriate for your network:

Figure 4-14: DHCP Settings for New Managed Remote Subnet Page