600 likes | 813 Views
Extended VLAN. Extended VLAN. This example shows how to configure local bridging and tunneled bridging on the same WLAN (SSID ) The following slide shows the network setup that we ultimately want to configure here in this example:. Controller. VLAN 1 Untagged VLAN50 Tagged.
E N D
Extended VLAN • This example shows how to configure local bridging and tunneled bridging on the same WLAN (SSID) • The following slide shows the network setup that we ultimately want to configure here in this example:
Controller VLAN 1 Untagged VLAN50 Tagged VLAN 30 Untagged VLAN 50 Untagged DHCP Server 30.30.30.0 DHCP Server 50.50.50.0 Switch VLAN 1 Untagged VLAN 30 Tagged Access Point VLAN 50 Dynamically Assigned Both laptops on the same SSID VLAN 30 Dynamically Assigned
Extended VLAN • Let’s first look at the red laptop: • If you trace a path between the red laptop and the red DHCP server, you will see that the path simply goes through VLAN 30 • As long as you simply configure the WLAN for local bridging, then the red laptop will get an IP address from the red DHCP server
Extended VLAN • Next, let’s look at the purple laptop: • If you trace a path between the purple laptop and the purple DHCP server, you will see that there is no direct path to VLAN 50. • You would need to tunnel the traffic between the access point and controller through VLAN 1 in order to create a path to VLAN 50 • To do this, you simply configure the WLAN for tunneled bridging
Extended VLAN • But what if you needed to do both local bridging and tunneled bridging on the same WLAN at the same time? • Solution: You need to configureExtended VLAN
Extended VLAN • The rest of this slide deck shows a simple example to demonstrate an Extended VLAN setup to show you where to enter the Extended VLAN configuration
Extended VLAN • First, configure a switch like this: • NOTE: You don’t have to use the exact same interfaces (or even the same VLAN ID for that matter) that I’ve used above • But for this example, I will use a switch that’s configured like the one in the diagram above VLAN 1 Untagged VLAN50 Tagged VLAN 30 Untagged VLAN 50 Untagged Int 1 Switch Int 3 Int 4 Int 2 VLAN 1 Untagged VLAN 30 Tagged
Extended VLAN • Next, connect the DHCP servers • Note: You do not have to the exact same DHCP servers that I’m using in the above diagram • The purpose of the DHCP servers is to quickly and easily determine that my wireless clients are connected to the correct VLAN and that I can successfully forward to that VLAN • But please feel free to you other methods, if you want, to determine that your setup is running correctly VLAN 1 Untagged VLAN50 Tagged VLAN 30 Untagged VLAN 50 Untagged DHCP Server 30.30.30.0 DHCP Server 50.50.50.0 Int 1 Switch Int 3 Int 4 Int 2 VLAN 1 Untagged VLAN 30 Tagged
Extended VLAN • Next, connect the Controller to the Switch • In this example, I connect a factory default RFS4000 Controller interface Uplink 1 to the Switch interface 1 Controller Uplink 1 VLAN 1 Untagged VLAN50 Tagged VLAN 30 Untagged VLAN 50 Untagged DHCP Server 30.30.30.0 DHCP Server 50.50.50.0 Int 1 Switch Int 3 Int 4 Int 2 VLAN 1 Untagged VLAN 30 Tagged
Extended VLAN • In this example, I am going to start with a controller in factory default configuration and configure: • A Virtual Interface VLAN 1 with a static IP address of 192.168.0.1/24 (actually, I don’t need to do anything to configure this … it’s already there in the factory default configuration) • And I’m going to configure Uplink 1 in Trunk mode with VLAN 1 as the untagged Native VLAN and add VLAN 50 as an allowed (tagged) VLAN
Extended VLAN • Next, create a WLAN that has 802.1x EAP with WPA2 CCMP and dynamic VLAN assignment
Extended VLAN • Next, configure the GE1 interface for the AP for Trunked with untagged Native VLAN 1 and tagged VLAN 30
Extended VLAN • Next, connect a DHCP server to VLAN 30 on the switch • Use the controller’s onboard RADIUS server to configure a server that has username/password assigned to VLAN 30 • Test the setup with a wireless client • Associate client to the WLAN testssid • Enter username/password • Check DHCP address
Extended VLAN • Next, connect a DHCP server to VLAN 50 on the controller • For convenience, I will simply create a DHCP server on the controller’s virtual interface VLAN 50 • And then, create another username/password on the controller’s onboard RADIUS server that assigns the user to VLAN 50 • Then associate a wireless device and authenticate user the username/password for the user assigned to VLAN 50 and it will fail to get an IP address • Now we create our Extended VLAN for VLAN 50