I have a 871w router up and running with dhcp on the router for vlan 1 assigning 10.1.5 addresses to cabled clients. I also have the nating working correctly for the outside interface and VPN working correctly as well. I can't get dhcp working on the wlan interface. The clients can see k-wirless ssid, but cannot connect to it. I have gotten them to connect successfully but they are not getting a 10.1.5 address, but a 169 instead. I have also removed the subinterface in this example and tried some other suggestions on this forum so the bridge 1 commands are not the wizard defaults. Any help would be greatly appreciated!
This sounds like exactly what I need. Only problem is - I have VLAN1 clients that are wired Nat'ing to get internet connection to the WAN interface... as soon as I remove the IP address from VLAN1, they go down :( Any way around this?
Previous posts do suggest the correct action - adding briding to your wireless VLAN. If this does not work
out for you, you could always define your wieless network as a separate routed interface. In this case you might want to add:
ip address 10.1.6.0 255.255.255.0
ip nat inside !<<< NOTE >>>> need NAT inside here
no vlan 1!!!!!! <<<< NOTE >>>> vlan assign removed
! ...and a new DHCP pool
ip dhcp pool K-wireless-client
network 10.0.6.0 255.255.255.0
dns-server x.x.x.30 x.x.x.y
! ...and optionally an exclude(or two) for DHCP
! to provide some room for the wireless print server
ip dhcp excluded-address 10.1.5.1 10.1.5.9
ip dhcp excluded-address 10.1.6.1 10.1.6.9
With my suggested changes above you would also have to remove any bridging configuration that you have added.
If multiple wired VLANs are required this has implications to the software required(adv sec will not handle multiple VLANs). Multiple Wired Vlans are supported only with the Advanced IP services and Advanced Enterprise services images.
But multiple wireless vlans are supported with base image itself ie Advanced Security image. Wired Vlan (Vlan1) and the wireless Vlans are totally different entities and they are completely unrelated.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...