Double SSID wep/wpa2

Hello,
I want to know how to have a double SSID but it's forbidden to have a wireless interruption with the wep which is on my cisco aironet 1242AG. I need to have wpa2 in addition of the wep. For the moment i use this site to help me :
http://idum.fr/spip.php?article182
http://idum.fr/spip.php?article181
http://www.forohuelga.org/configuring-wpa-and-wpa2-on-cisco-aironet.html/
Sorry for my english.

Can you clarify your question please? It sounds like you're wanting two of the "same" SSIDs, but with different encryption, however your examples refer simply to two "different" SSIDs using different encryption.
Do you need two "identical SSIDs" on the "same" IOS AP? If so; the AP will not allow you to create two SSID's with the exact same name. This is "possible" from a WLC using lightweight APs making sure you have a unique "profile" and "L2 security" config, but I don't believe you can accomplish this on an IOS AP.

Similar Messages

HP 7410 Printer will not accept a 12 digit WEP/WPA2

I just got a new FIOS router. It has an "ESSID" (extended SSID) which has 12 hex digits for the WEP/WPA2, instead of the 10 that the old SSID had. HP 7410 printer set-up will not accept 12 digits, only 10 or 26 is the warning message. I cannot get the printer on my home wireless network now. I have several laptops which I had set up for wireless access with the old router which had a lot of problems - Win 7, Win 8 and Vista, which is why Verizon sent me the upgraded router. I reset the HP 7410 to factory settings, powered down and unplugged for 15 seconds, and held down the #6 on power up. Still no luck. Is there any way to force the printer to accept 12 hex digits for the WEP/WPA2?

What router brand/model?
Try restarting the router just before trying to connect the printer.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Accept Certificate when connecting to an SSID with WPA2-AES encryption.

When I try to Connect my Iphone to an SSID with WPA2-AES encryption,i need to accept the certificate and gets authenticated.When i switchover to different SSID and reconnect again to the same WPA2-AES SSID i do not get the Certificate accept page.
When i click on the Forget Network and deisconnect from the SSID and re-connect again,i will be prompted to acept the certificate.Is this a normal behavior in Iphone.
Any suggestions would be greatly appreciated.
Thanks and regards,
Sendhil Balakrishnan

Hi
with the config i have i seem to be able to login using either tkip or aes, but i don't think i have got mixed mode configured on the AP so it should only accept WPA2-AES encryption but it also accepts TKIP making me believe something is configured incorrectly.
should i change anything in the config on the AP to only allow WPA2-AES encryption?
many thanks
rogier

WRT54GS v1.1 (4.71.4): Wifi won't work with wpa/wep/wpa2

Yesterday, I was using wi-fi connection normally when it just died without any warning. It was only my netbook that couldn't use the connection, my phone and other laptop were able to connect and transmit with wpa2-personal (tkip-aes) on. Now they aren't working either. Strange isn't it?
I tried to switch wifi's channel with no help, but I discovered that if I disable the security completely from the router it start's to work. With any security on dhcp wont even give any IPs for the devices trying to connect.
Has anyone else experienced such death with this model? What could be the reason?

[SOLVED]
I followed these instructions to install a third party firmware after my mate's recommendation. Wi-fi began to work straight away!
http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54GS_v1.1
Warning: There is a risk to break your router by following these instructions, don't know how big it is but if you can't take that chance then don't try this
Edit. I guess that user cant edit thread title to add that the problem is solved?

SSID WPA/WPA2 PSK Issues

I have a customer who is having issues with one SSID. He claims that when he changes the PreShared Key, clients that had previously had the old key can connect, and new clients can connect with the new key.
When the PSK is chaned in the Layer2 section of Security of the WLAN, is the previous key deleted?

clients that had previously had the old key can connect
This is my understanding:
Let say I have PSK "abcdef" and I am able to authenticate and get into the internet. While I'm connected, let's say some changes the PSK to "asdfed". So when the key changes, and as long as I am still connected, I don't get kicked out. This is probably what your customer is looking at.
If I log off and log back in, I won't be able to get back in.

3GS WEP/WPA2 passwords not accepted

I just replaced a failing Netgear Wireless-G router and now I just put in a Fry's generic Wireless-N router with my Comcast hi-speed internet. I put in a WEP security password and my MacBook Pro and HP laptops connected perfectly. My 3GS & 4GS kept saying the password was invalid. I then changed the router security code to a WPA version. Both laptops connected fine, but the two iPhones still say the password or code is invalid. After about 5 hours i came back tried the wi-fi on the phones with the code and they work, but if i change the router back to a WPA code, the phones won't connect. And despite them finally connecting, the speed of page loads is extremely slow, yet blazing fast on the laptops. I've never had speeds on the 3GS this slow. no matter what site it just drags even with the wi-fi icon showing full strength (i'm right next to the router) Any ideas?

i am in exactly the same boat as of last night!? very wierd, and like you everything else is connected ok via wep key password but the iphone does not want to know. i tried manually entering the hub name and wep key but this method the iphone cannot find the hub (i have a BT hub )

New SSID/WEP key, how to update Airport Express?

A simple change to my access point, and I can't find a way to actually configure my Airport Express with the new info. I have Mac OS 10.4.10, and using the Airport Setup Assistant doesn't help - the AE doesn't show up in any list. Can anyone help?

Hello jvreagan. Welcome to the Apple Discussions!
To set up the AirPort Express Base Station (AX), temporarily connect your computer directly (using an Ethernet cable) to the Ethernet port of the AX, and then, using the AirPort Admin Utility (located in the \Applications\Utilities folder), to change settings.

Running WEP and WPA2 on the same virtual AP

Hi Forum,
Is it advisable to run WEP and WPA2 on the same virtual AP sharing the same antenna?
rgds,
paul

Paul,
This shouldn't be a problem, so long as you have one SSID for WEP, and one SSID for WPA2. The antenna itself will not come into play for what type of encryption that is used.

Airtunes dropouts - AE firmware 6.3 / WPA2 personal network

I finally managed to set up a proper airtuning of my Airport Express (AE) without having the regular streaming dropouts I used to have before (happening a few minutes after every hard/soft reset of my AE, AE still showing solid green light but suddenly not pingable anymore, iTunes stopping the playing, airport channel name displayed in italic at the bottom right of iTunes).
I think I found a solution (further testing required but so far much better) and would like to share my story for the eventual benefit of others. Since I am convinced there might be other reasons than the one I found to such a problem, I will try to carefully describe my network/systems settings.
> My network/systems:
. ADSL/WiFi router Xavi 7868r 54 Mbps configured for mac filtering, no ssid broadcasting, wpa2 personal auth/encrypt using 64 ascii psk, dhcp with fixed ip adressing for my AE
. MacBook Pro Intel Core 2 Duo running Mac OS X (10.4.8) with iTunes 7.0.2 (15) connected to the network through Airport Extreme
. Airport Express with latest firmware (6.3) and regular speakers directly connected to it through audio jack
> My attends to narrow down the problem (OK means dropouts solved, NOK means dropouts not solved):
. putting all my network elements closer to each other (half a meter away from each other) -> NOK
. connecting my Macbook through Ethernet instead of WiFi -> NOK
. disconnect my DECT phone standing close the WiFi router -> NOK
. monitoring of neightbouring WiFi networks -> NOK (I have the strongest signal, almost 100% of signal level)
. checking interference robustness boxes on AE and my laptop -> NOK
. broadcasting my WiFi SSID -> NOK
. turn my WiFi security setting off (i.e. open network without even a WEP) -> OK
. move to WEP 128 security -> OK
. move to WPA2 security -> NOK
. downgrade AE firmware to the previous one (6.1.1) -> OK
So I finally have my AE airtuning working without these sudden dropouts and without any concession regarding the security of my network (WPA2 personal).
Link for AE firmware 6.1.1 download: http://www.apple.com/support/downloads/airportexpressfirmware611formacosx.html
Hope it will help some people getting crazy around. Anyway, thanks for all the ones who posted messages on related issues since they surely helped me in some way. Will try to answer to your eventual questions as well.
Mabook Pro Intel Core 2 Duo Mac OS X (10.4.8)
Mabook Pro Intel Core 2 Duo Mac OS X (10.4.8)

So let me be sure what you're saying. You had fairly new AE with V6.3 on it and you downgraded to 6.1.1? I'm a little nervous to try this, but the drop-outs are killing me. I had an older AE that finally died. I think it probably was running 6.1.1 and I hardly ever experienced any problems with it. So maybe you have found the solution, but wouldn't you think Apple would pick up on this and fix whatever is wrong with 6.3? Go figure!

IPad can't get in the internet via a WPA2 Enterprise setup

I've seen some similar posts and no real answers. My Office just got set up with Wireless, it's cisco gear and using RADUIS to authenticate. What they told us to do on the windows boxes was this:
Connect to the SSID
use WPA2 Enterprise Authentication
TKIP Encryption
Use PEAP Authentication
Uncheck the "Validate Server Certificate"
Authentication Method is EAP-MSCHAP v2 on the PEAP properties screen
Following these instructions on Windows 7 I can get on the network.
I tried this on my iPad:
connected to the network
selected WPA2 Enterprise
It Prompted my for my login/password
I entered them....
Then I got a certificate and it asked me to accept/install it, and I did
Then it connects to the access point and gets a signal
Even though I am connected and authenticated I can't get on the internet, and I get no IP address. Not a DHCP issue since other devices work.
Any ideas on alternate configurations, or what I'd need to do with the iPhone Configuration Utility to get this working?

"Unsupported" device - I've heard that before, too many times... =)
So after thinking on everything you've tried, it's safe to say that your AP is running PEAPv0 with EAP-MSCHAPv2 for Authentication. This is good news - as it is probably the most widely used Enterprise WiFi configuration, iOS devices should absolutely be compatible with this. Getting a non-domain XP PC connected was a great idea, as I have discovered that Windows XP is kind of "loose" in the way it handles PEAP certificates - it will accept any certificate given to it by a RADIUS server without question. Undoubtedly a big security hole, but it does have the advantage of being "user friendly." I don't think Apple's implementation is quite as loose, so even though you are manually accepting one certificate, you probably need more to complete the chain of trust required for your device to authenticate the server. This is a requirement for PEAP to function.
So at this point, I think your best bet would be to migrate over to the Credentials tab. If you're running the iPhone Config Utility on a PC which connects to the AP, you already have the certificates in your trusted certificate store - so simply hit the add button and add any relevant certificates. For example, if your domain is named "corporate", import any certificates bearing that domain. Once you've done this, head over to the Trust tab under WiFi and check off your newly imported certificates as being trusted for your connection.
In addition, if you can figure out what the name of the RADIUS server on the other end of the AP is doing the authentication, add it under "Trusted Certificate Names" - if you don't know it, you can also add a wildcard like "*.corporate" to trust any servers in your domain. This shotgun approach is probably your best bet for making it go initially.
You will know this is all working when you no longer get the dialog on your iPad to accept the certificate, and hopefully, you get an IP address.
We're truly in the thick of it now, and this is my last idea - so if this does not work, we will need to call on those stronger than I with iOS networking... or, you can call up your IT department and start the conversation off with the words "I bet you can't figure this out" - that always gets IT people going =)
Best of luck!
Sources:
http://howto.techworld.com/mobile-wireless/3451/use-peap-for-wireless-authentica tion/
http://images.apple.com/ipad/business/pdf/iPadDeploymentScenarios.pdf

WLC 5508 cannot change SSID

Hello,
I have an issue where I cannot get clients to change SSID. I have two SSID, one WPA2 secure, one open guest. The secure is locally switched via Flexconnect and the guest is centrally switched. Both of them work. I have been able to test this and both work as intended. The problem is that once you connect to one of them, either secure or guest, you cannot then change to the other. The only way to change is to delete the dhcp entry from the scope and then do it.
Fast SSID change is enabled. I also have debug client output from when the client fails when you try to switch which I will include below. I also pulled some wireshark captures and those show me that the DHCP ack packets are trying to give the client the ip address from the incorrect/previous scope. So basically it's like FAST SSID change is not working and the client is never being disassociated properly??
I am totally stumped and even though the client will most likely not be switched between SSID that often I would still like to know the solution.
Cisco 5508 running 7.2.110.0
Cisco 3502 LWAPP
windows server 2008 dhcp server
DHCP Socket Task: Dec 07 09:37:23.023: a4:d1:d2:14:fc:51 DHCP successfully bridged packet to DS
*apfMsConnTask_0: Dec 07 09:39:35.149: a4:d1:d2:14:fc:51 Association received from mobile on AP 18:33:9d:5e:c8:70
*apfMsConnTask_0: Dec 07 09:39:35.149: a4:d1:d2:14:fc:51 0.0.0.0 WEBAUTH_REQD (8) Changing IPv4 ACL 'Guest - Internet Only' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1709)
*apfMsConnTask_0: Dec 07 09:39:35.149: a4:d1:d2:14:fc:51 0.0.0.0 WEBAUTH_REQD (8) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1876)
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 Applying site-specific Local Bridging override for station a4:d1:d2:14:fc:51 - vapId 3, site 'VanBuren', interface 'wireless guest'
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 Applying Local Bridging Interface Policy for station a4:d1:d2:14:fc:51 - vlan 50, interface id 11, interface 'wireless guest'
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 Applying site-specific override for station a4:d1:d2:14:fc:51 - vapId 3, site 'VanBuren', interface 'wireless guest'
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 0.0.0.0 WEBAUTH_REQD (8) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'Guest - Internet Only' (ACL ID 0) --- (caller apf_policy.c:1795)
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 0.0.0.0 WEBAUTH_REQD (8) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1876)
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 processSsidIE statusCode is 0 and status is 0
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 processSsidIE ssid_done_flag is 0 finish_flag is 0
*apfMsConnTask_0: Dec 07 09:39:35.150: a4:d1:d2:14:fc:51 STA - rates (8): 140 18 152 36 176 72 96 108 0 0 0 0 0 0 0 0
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 suppRates statusCode is 0 and gotSuppRatesElement is 1
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 apfMs1xStateDec
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 WEBAUTH_REQD (8) Change state to START (0) last state WEBAUTH_REQD (8)
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 pemApfAddMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 START (0) Initializing policy
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state WEBAUTH_REQD (8)
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state WEBAUTH_REQD (8)
*pemReceiveTask: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 Removed NPU entry.
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 L2AUTHCOMPLETE (4) DHCP Not required on AP 18:33:9d:5e:c8:70 vapId 3 apVapId 2for this client
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 Not Using WMM Compliance code qosCap 00
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 18:33:9d:5e:c8:70 vapId 3 apVapId 2 flex-acl-name:
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state WEBAUTH_REQD (8)
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) pemApfAddMobileStation2 3124, Adding TMP rule
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
type = Airespace AP - Learn IP address
on AP 18:33:9d:5e:c8:70, slot 1, interface = 13, QOS = 0
IPv4 ACL ID = 255, IP
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206 Local Bridging Vlan = 50, Local Bridging intf id = 11
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) pemApfAddMobileStation2 3268, Adding TMP rule
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Replacing Fast Path rule
type = Airespace AP - Learn IP address
on AP 18:33:9d:5e:c8:70, slot 1, interface = 13, QOS = 0
IPv4 ACL ID = 255,
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206 Local Bridging Vlan = 50, Local Bridging intf id = 11
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 apfPemAddUser2 (apf_policy.c:270) Changing state for mobile a4:d1:d2:14:fc:51 on AP 18:33:9d:5e:c8:70 from Associated to Associated
*apfMsConnTask_0: Dec 07 09:39:35.151: a4:d1:d2:14:fc:51 Scheduling deletion of Mobile Station: (callerId: 49) in 1800 seconds
*apfMsConnTask_0: Dec 07 09:39:35.152: a4:d1:d2:14:fc:51 Sending Assoc Response to station on BSSID 18:33:9d:5e:c8:70 (status 0) ApVapId 2 Slot 1
*apfMsConnTask_0: Dec 07 09:39:35.152: a4:d1:d2:14:fc:51 apfProcessAssocReq (apf_80211.c:6309) Changing state for mobile a4:d1:d2:14:fc:51 on AP 18:33:9d:5e:c8:70 from Associated to Associated
*pemReceiveTask: Dec 07 09:39:35.152: a4:d1:d2:14:fc:51 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*pemReceiveTask: Dec 07 09:39:35.152: a4:d1:d2:14:fc:51 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   xid: 0xbdc7df36 (3183992630), secs: 0, flags: 0
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   chaddr: a4:d1:d2:14:fc:51
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP   requested ip: 10.2.4.42
*DHCP Socket Task: Dec 07 09:39:35.178: a4:d1:d2:14:fc:51 DHCP successfully bridged packet to DS
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   xid: 0xbdc7df36 (3183992630), secs: 2, flags: 0
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   chaddr: a4:d1:d2:14:fc:51
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP   requested ip: 10.2.4.42
*DHCP Socket Task: Dec 07 09:39:36.972: a4:d1:d2:14:fc:51 DHCP successfully bridged packet to DS
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP   xid: 0xbdc7df36 (3183992630), secs: 4, flags: 0
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP   chaddr: a4:d1:d2:14:fc:51
*DHCP Socket Task: Dec 07 09:39:39.351: a4:d1:d2:14:fc:51 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:39.352: a4:d1:d2:14:fc:51 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 07 09:39:39.352: a4:d1:d2:14:fc:51 DHCP   requested ip: 10.2.4.42
*DHCP Socket Task: Dec 07 09:39:39.352: a4:d1:d2:14:fc:51 DHCP successfully bridged packet to DS
*DHCP Socket Task: Dec 07 09:39:39.352: a4:d1:d2:14:fc:51 Failed to get response for 3 dhcp attempts from client.Total DHCP failed count for the interface wireless guest : 10

External windows 2008 dhcp server. The ip-helper on the L3 interface is working because it will pull dhcp just fine as long as it is the first SSID you connect with. Once you have the an address from dhcp and try to change it keeps wanting to give me that same address even though my L3 interfaces for the two SSIDs are on two separate vlans each with a separate scope (vlan 31 and vlan 50). Although each vlan uses the same dhcp server but that does not matter since I have two different scopes setup. One for each subnet.

11xx able to handle multiple SSID's and encryption?

Has anyone configured a 11xx series AP with 3 SSID? and more importantly can I have 1 SSID WEP and the others WPA? I have a client that wants to use VoIP phones that only support WEP, but I would like the guest and LAN SSID VLAN to use WPA...
Any comments welcome,
Chris Serafin
[email protected]

Hi Chris
Since WEP and WPA uses uses different encryption standards, it would not be possible to configure 2 different SSID's on the same AP with different encyrptions on them. Reason is that whatever encyrption you apply on the AP, applies to the radio inteface not to a specific SSID. BUT you can always uses VLAN's on the AP (if you have VLAN's configured on the switch) and then you will find the option to configure a different encryption for a every VLAN and further you can map those VLAN's to your respective SSID's.
In your scenario, you can configure 3 VLAN's on the AP and map them to 3 different SSID's and then configure WEP on one VLAN for VOIP phones and configure WPA on other 2 VLAN's for your guest users.
Hope the above information helps.
Basant

E4200 Guest SSID Login page fails

Config:
Netgear ProSafe Gigabit Router is my DHCP Server -- The entire home net work is on the same subnet (192.168.15.xxx)
Linksys E4200 configured as an access point ONLY -- wired connection -- static IP assigned -- DHCP server turned off
Linksys WRT610N configured as an access point ONLY -- wired connection -- static IP assigned -- DHCP server turned off
3 -- 5 port gigabit switches
1 -- 8 port gigabit switch
No more than two switches between any two wired devices
Both Linksys access points have the same SSID and WPA2 security phrase -- total of 4 radios
Nonoverlapping channels are selected on both the 2.4Ghz and 5.0Ghz radio to minimize interference
All computers are running Windows 7 Professional 64bit with all the latest updates
Two iPhones and one iPad also access the network
All LAN and WAN connectivity is working as designed
Problem:
guest SSID is turned on
password is established
All devices will connect to the guest SSID and the E4200 is assigning an ip address to the device in the 192.168.33.xxx range which is what it's supposed to do.
When I open a web browser, I am not automatically redirected to the Cisco Login Page. If I enter 192.168.33.1 as the URL, the login screen is presented. I enter the password I have created in the guest admin page on the wireless guest tab. I then see a blank page and a URL of 192.168.33.1/guestnetwork.asp. THIS IS WHERE I GET STUCK. THE ONLY WAY TO EVER SEE THE LOGIN PAGE AGAIN IS TO REBOOT THE E4200, otherwise you just get unable to connect messages when opening web browsers and the wireless status icon in the system tray shows a yellow exclamation mark.
I successfully connect to the guest SSID but I do not get access to the internet. When I type ipconfig, I see that the DNS is set to 192.168.33.1 which does not exist on my network. I assume there's some internal NAT magic that is supposed to happen in the E4200 to bridge me over to my 192.168.15.xxx network but it doesn't seem to be happening.
At the beginning of the call I specifically asked them if the E4200 must be the DHCP server in order for the guest SSID feature to work and they said no. 1.5 hours later they had no answers so they told me that it wasn't working because the E4200 was not the DHCP server. The documentation says nothing about a DHCP requirement for guest AP service. Linksys support further could not answer what you would do if you needed more than one AP with guest service enabled.
It seems like this is a firmware issue but it may be the guest SSID service requires the E4200 to also act as the DHCP server. Can anyone shed any light on whether this is a bug or if the router/AP is working as designed?
Thanks,
(Mod note: Edited for guideline compliance.)

Yes the E4200 must have DHCP turned on in order to pass out IP's to your Guest Network. No DHCP, no Guest Network.

Airport express with wep

i have been able to connect my AX to my network if i disable WEP and broadcast my SID (i have never broadcast my SID and always use WEP)...so, my next endeavor is to get AX to connect to my network with WEP enabled and my SID not broadcast...
here's what i've done...did a hard reset on the AX...plug it in...have my network setup to use WEP..via Airport Setup Asst i connect to the AX...it finds the AX and says it wants to connect to the network "Airport Express 3452" (or something to that effect)...if i say NO, i'm stuck...if i say YES, my laptop (where i'm running the setup) disconnects from my network to the "Airport Express 3452" network, thus leaving WEP off and broadcasting my SID...if i then try to go and change my laptop back to my network, the AX is unable to update the settings...
so how in the world do i connect to my network with the ultimate goal of using WEP and not broadcasting my SID?
running win xp pro with a linksys wrt54g router...

It use to be useful, but closing your Airport or wireless network (sometimes referred to as not broadcasting your SSID) is really no longer a real option when it comes to wireless security.
Unfortunately "Closed" networks, MAC access control lists, and reduction in transmission power are all more "feel good" security rather than real security. All these various approaches are dated and mistakenly lead to overconfidence.
WPA is your only real option if you value wireless security.
My recommendation is not to worry about broadcasting your SSID but use WPA. This will be more secure than a closed WEP encrypted network. Closing your network makes it very difficult for neighbouring networks to see which channels are free thus causing potential interference problems.
Another thing to consider is that a closed network is still broadcasting and therefore is detectable (regardless of whether it is broadcasting a SSID). If someone was determined to hack into your network, then not broadcasting your SSID, WEP and/or MAC address access control is not going to stop them.
WPA is virtually uncrackable (only really vunerable to a dictionary attack if a real word is used as a password) and therefore will stop the casual user and the determined hacker.
One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
AirPort: Joining an encrypted wireless network
http://docs.info.apple.com/article.html?artnum=106424
Choosing a password for networks that use Wired Equivalent Privacy (WEP)
http://docs.info.apple.com/article.html?artnum=108058
WPA
"WPA Personal" on the Mac corresponds to plain WPA, with a pre-shared key (PSK) and TKIP encryption, on non-Apple wireless routers. The same alphanumeric password should work on both.

Trouble Connecting To Wireless Network

Greetings,
New iTouch with the new 3.0 software installed.
iMac with Leopard 10.5.8
Using a Linksys Wireless Router WRT54G, settings:
- Home wireless network does not broadcast SSID
- WEP with 10-key password
- MAC filter enabled
Issue 1:
I entered my iTouch MAC address into the router's MAC filter list
Using the wireless on iTouch entered the SSID and Password
Result: Does not connect. What am I missing?
Issue 2:
Do I have to enter the network password every time or can I save the password in my ITouch?
Thanks for your help,
Matt

Thanks for the help,
So, my kids don't use the Internet function with their DS, and the Wii takes WPA . . .
I changed my wireless security settings to WPA2 with AES algorithms.
Still didn't work . . .
I then had to disable the MAC address filtering and . . . Presto! Connection Heaven.
Don't like having to had disabled my MAC address filtering though. I double checked the MAC in the list for the iTouch and it was fine.
Any known issues with the iTouch and MAC address filtering in wireless routers?
Thanks everyone,
Matt

Double SSID wep/wpa2

Similar Messages

Maybe you are looking for