Thank you for all your support, your motivation is very important for me

I appreciate your comment, this motivate me to continue

Thank you for all your support, I appreciate it

Thank you for all your support

Glad it helped. I appreciate all your support!!!

Thank you very much, I will try to do it as soon as possible, by the way, you can review this kzfaq.info/get/bejne/g7OYlJZ9l9mZf3k.html

Glad it helped. I appreciate all your support and good comments.

Glad it helped! Thank you for all your support!

Glad it helped . thank you for all your support

Grazie per tutto il vostro supporto, lo apprezzo davvero tanto!!

Thank you for all your support. Thanks for the sub!

Glad it helped, thank you for all your support

You're very welcome! Thank you for all your kind support!

Glad it was helpful! I appreciate it

Thank you for all your support

Glad it helped, Thank you

I appreciate all your support my friend!!!

thank you for all your support

Thank you for all your support

Thanks

thank you for all your support

Glad it helped, thank you for all your support

Thank you for all your support

Thank you for all your support

You can use any native vlan, but in this case the only limitation of packet tracer is that the WLC can use only the VLAN 1, but on real life you can choose another vlan number on the WLC

Si, hay una forma de hacerlo por grupos de APs, eso lo pobré en el mismi packet tracer con este mismo WLC

Hello, thank you for all your support, the problem for now is that WLC on packet tracer will not support all functionality, will be little different like real WLC.

On packet tracer. You need to use the management and native on the same vlan.

I tried creating a native vlan 99 and management vlan 88, I tried to manage the WLAN in the vlan 88, but did not work, the native vlan should be the same where you manage the WLAN and the link to the WLAN should be trunk because will Manage more than one VLAN, for the admin the port should be access because is managing only one VLAN

Thank you my friend

Trunk should be the Management because Management needs to access APs and WLCs

for packet tracer, use 1 and will work, on real life use 99 or the native number

VLAN 99 is the Management and Native, LAPs use the VLAN 99 to connect with the WLC, WLC use trunk port because it is managing various VLANs (10, 20 , 99)

Also on WLC configure the primary DHCP server with the IP address of external server, for each VLAN or WLAN. Also use ip helper address to reach the server

the video shows you all but, the connections from WLC and LAP are trunks

on real device you alright, but packet tracer has some limitations, like this on WLC use management with 1 also if you will use another number on the switch

I can figure out, on real WLAN you will select 99 management vlan and will work, in packet tracer will not work, only if you select vlan 1

@@romeroc24 thanks your awnser helped me alot understanding it : )

@@DovaBro thanks to you

Thank you, the reason I used trunk is because that port will manage various vlans, not only one

Please be careful where to use a trunk link or access ports on the switch, view the complete video, maybe something is missing about the WLC, please save and commit every time you make a modification to WLC

thank you

Thank you my friend, on Packet Tracer change the native vlan to 1 and all will work, on real scenario change native vlan on switch and on WLC

please try again, the switch should use vlans to separate the networks

ping test verify connectivity between devices, the CAPWAP tunnel is working between LAPs and WLC anywhere the LAPs are, so you can´t use ping to test CAPWAP tunnel

thank you for all your support

@@romeroc24 Hi Christian, thanks for replying I am studying vlan configuration in WLC and your video is a great help, but as far as i know 1) tunnel CAPWAP is used for control messages between WLC and LWAP using UDP port 5246: OK i saw these messages 2) but data from and to wifi clients is also encapsulated in a similar CAPWAP tunnel using UDP ports 5247 That is to say: when a ping is sent from Laptop0 in vlan 10, the ICMP packet is tunneled directly from the AP to the WLC That is : it is included in a new IP packet build by the LWAP and send to the WLC IPs in the external packet are IPs of AP and WLC; IPs in the internal ICMP packet should be IP laptop0 for the src and the IP dest of the ICMP packet So the link between 3702i and the switch has not to be a trunk: it should only be an access link in vlan 99, because external IP packets between 3702i and WLC (and the opposite when returning) are in the network 172.16.99.0/24 and are carried by vlan 99 in layer 2 But when link between AP and switch is set "switchport access vlan 99", ping does not work anymore ! That is why something i think something has to be clarified In any case your video helps me, but your configuration is unclear for me Regards

you need to use trunk because a lot of vlans will be used in the link

I think there's an issue with Packet Tracer and CAPWAP tunnel for data. The link from the switch to LAP should be an access link but in packet tracer it won't work unless it's configured as a trunk.

the WLC manage multiple VLANs, so is necessary a native VLAN to support those VLANs, also WLC has IP addresses for remote administration, you need to access those IP addresses using the Management VLAN that is the same of NAtive

@@romeroc24 Thank you for the quick response. Just another question, can we just allow the VLANs needed instead of setting up the mgmt VLAN as Native VLAN? For example, allowing the mgmt VLAN, SSID VLANs? I know that it's best practice to change the default Native VLAN but is there a special reason why the Native VLAN has to be the mgmt VLAN? Apologies for having too many questions.

@@rawlee205 i think the problem is with packet tracer. From the perspective of security i don't think it's good idea to use native vlan in allowed vlans/management vlan.

On pakcet tracer only, if you modify the management vlan identifier in the WLC, will not work (packet tracer limits), on real lab you need to match the management vlan in the WLC with the management VLAN on the network

@@romeroc24Thank you so much for ur reply, appreciate it

please contact me using social media shown in 00:03 , so you will send me details

yes you can do it my friend

Em um AP real você pode ter dois SSIDs, mas no packet tracer apenas um SSID

Yes, the default VLAN for switch and WLC

maybe the ip is incorrect or is used by another device

porque es una limitación del WLC en packet tracer, debería usar la 99 pero sólo funciona con 1

yes but please try and let me know, for now I'm using trunk because there are various vlans on that place

ON packet tracer will work using the DHCP server on the router, on real life you can use the DHCP server on the WLC

@@romeroc24 sure, but how to do that? I mean, how to configure that that new AP will be on VLAN100? I have read at the documentation, that mentioned VLAN must be connected to WLC via separate LAN cable e.g. to port 2 of WLC than the WLC will able to manage APs on the different VLAN connected... any ideas?

@@MrDome110 in the video, I created the DHCP pool for management VLAN, so is the same process to create a DHCP pool for another VLAN

@@romeroc24 I tried it, but in reality the WLC says that I cant use same IP as dhcp server and interface IP... but thanks for reply...

@@MrDome110 so you need to create another interface for another VLAN and use that new interface with new ip address on different subnet as the DHCP server

en este video el switch y el wlc son troncales, necesitaría algunoms detalles si deseas para resolver el problema

thank you for all your support

that was my question too,i think LAP should be on access mode,this is the most confusing stuff + the native vlan

Just only add more LAPs, and configure the switch ports

vlans are isolated by default

yes, not problem