Avaya WLAN 8100 Technical Configuration Manual page 14

The final result should look something like this:
3 Configure a Routed Interface for the Guest VLAN
By default, the Captive Portal is hosted on the System IP interface. Guest users can be in a different
VLAN and their traffic is internally routed to the System IP when "captured" and redirected. While this
does not actually give them access to the controller management interface, it does give the appearance
that the users are being redirected to the private network. There is no real security risk, but many
administrators would still prefer to have the Captive Portal hosted on an interface that is local to the guest
users. This step shows how to accomplish this.
Since the "guest" VLAN you previously created will need to host an instance of the Captive Portal, you will
need to perform one additional task in the controller CLI to create a routed interface on the VLAN.
On a WLAN Controller 8180, "routed" interfaces are not used for general routing of client traffic.

Client VLANs are still treated strictly as Layer 2 forwarded VLANs. Routed interfaces are only
used to capture and redirect Captive Portal sessions. So only the initial client HTTP session is
captured by the routed interface, and then after authentication, client traffic is L2 forwarded.
Telnet or use a console cable to access the controller CLI. From the CLI follow the commands, assuming
your guest VLAN has a VLAN ID of "4". If you used a different VLAN ID and/or IP address, then adjust
your configuration commands accordingly.
WC8180> en
August 2011
Avaya Inc. –External Distribution
avaya.com
14