Specifications

configured, as soon as traffic is received from a client on that interface, the BSC automatically
puts the user in that role.
1. Go to Network>Managed.
2. If you have more than 1 managed interface click to edit the appropriate one that corresponds to
the client. If you only have 1 managed interface configured the properties of that interface will
be displayed.
3. Click the interface tab if not already selected.
4. Scroll down to the default role.
5. Select un-registered. Clients will now be redirected to the login page.
Can I disable https on the login page of the BSC or vWLAN and use http instead so I do
not get a certificate error?
No, https (http over ssl) is required to encrypt login transactions and cannot be disabled. It is
recommended you purchase and install a certificate from a trusted certificate authority such as
Verisign or Godaddy.
Clients are not able to obtain an IP address on the managed remote subnet of the BSC and
I am seeing no free leases errors under status>logs.
Examples of error messages under status>logs:
# Time Level Application Function Operation Name Message
779885 7/22/2008 12:22 Error DHCP Server dhcp discover no user DHCPDISCOVER from
00:09:1d:00:ee:84 via 172.31.56.253: network 172.31.56.128/25: no free leases
773989 7/22/2008 10:04 Error DHCP Server dhcp discover no user DHCPDISCOVER from
00:11:85:80:3d:15 via 172.31.56.253: network 172.31.56.128/25: no free leases
779980 7/22/2008 12:25 Error DHCP Server dhcp discover no user DHCPDISCOVER from
00:02:3f:81:ba:fd via 172.31.56.253: network 172.31.56.128/25: no free leases
By default the BSC expects the DHCP requests to be sourced from "Default gateway IP address
for remote clients to reach the BSC" configured under the managed remote subnet. If dhcp
requests can be sourced from addresses other than the "default gateway address for remote
clients to reach the BSC" then the "Additional IP addresses that DHCP relay packets can be
sourced from" must be populated with these addresses. For example in the error messages above
we can see the dhcp discovers are being sourced from 172.31.56.253. This IP address should be
configured in the "Additional IP addresses that DHCP relay packets can be sourced from" field
under the 172.31.56.128/25 managed remote subnet. If there are multiple IP addresses add them
comma separated. This is common for example with environments that use Hot Standby Router