Tag Info

New answers tagged


In the absence of DHCP opt as mentioned above you need to create a DNS A record for a specific host which points to the WLC IP: CISCO-LWAPP-CONTROLLER such as CISCO-LWAPP-CONTROLLER.mydomain.com Of course Cisco only publishes half the story; the other half is that other APs use different DNS A record to locate the WLC and that is CISCO-CAPWAP-CONTROLLER ...


(clientsOfLan1) ))> RB1 <---> SXT1 ))> <(( SXT2 <---> switch <(( (clientsOfLan2) if you want LAN1 and LAN2 use the same subnet, just make RB1 as the main router. LAN1 and LAN2 assign DHCP from RB1. i did it on my office. thank you.


Clearly you have an interference problem. Interference can come from passive elements like aluminum wall studs or thick floors, but those are not likely to show the periodic pattern you see. So something electric or electronic is periodically emitting. Finding it may be expensive or tough, but you have a few options. Graph more. It would be nice to make ...


To me, the intermittent nature indicates a hardware problem. Wireless routers go bad often. I'd try a new router and see if that doesn't resolve it. Maybe you can replace under warranty with Netgear if it's not too old? Or you could always run a bunch of cat-5 and mini switches everywhere, the wired part of the router's probably fine


You need a RADIUS server! But today, even small home routers have enough power to allow this. I have a Asus RT-N65U and a Asus RT-N56U at my parents house with custom firmware and FreeRadius2. You do need some Linux knowledge to set it up! The router allows to set a RADIUS server in the web interface. After you set one up, you just enter localhost there!


Another possible solution is to set up multiple SSIDs and provide separate passwords for each one. It's not as elegant as having multiple passwords for the same SSID, but it would accomplish the same thing and would be easy to manage if your router supports multiple SSIDs. One such router is Asus' RT line of consumer-level dual-band routers (I have the ...


I would answer your question with another question...what do you hope to gain by having each user connect using a different password? The exercise seems somewhat pointless to me unless you're also hoping to attach some sort of network policies to the different credentials that you didn't mention in your original question. Other respondents are correct, ...


What you need is WPA-2 Enterprise, combined with a RADIUS server for authenticating users. If you have an existing Active Directory infrastructure, then you can use the Network Policy Server role in Windows to do the authentication and allow users to log on with their AD username/password.

Top 50 recent answers are included