Results 1 to 8 of 8

Thread: WPA-PSK not working

  1. #1

    Question WPA-PSK not working

    Hello,

    i have installed the Version 1.9.2.7-6b on my Asus WL-500b. I think the router is hardware revision 1.

    WPA-PSK is not working, my laptop (windows xp) shows me a unsecured open network.

    WEP seems working well.

    Here a system log:

    Jan 1 01:00:05 syslogd started: BusyBox v1.00 (2005.05.11-18:29+0000)
    Jan 1 01:00:05 kernel: IP Protocols: ICMP, UDP, TCP
    Jan 1 01:00:05 kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
    Jan 1 01:00:05 kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Jan 1 01:00:05 kernel: ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
    Jan 1 01:00:05 kernel: ip_conntrack_pptp version 1.9 loaded
    Jan 1 01:00:05 kernel: ip_nat_pptp version 1.5 loaded
    Jan 1 01:00:05 kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Jan 1 01:00:05 kernel: ipt_time loading
    Jan 1 01:00:05 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Jan 1 01:00:05 kernel: IPv6 v0.8 for NET4.0
    Jan 1 01:00:05 kernel: IPv6 over IPv4 tunneling driver
    Jan 1 01:00:05 dnsmasq[51]: reading /tmp/resolv.conf
    Jan 1 01:00:05 kernel: NET4: Ethernet Bridge 008 for NET4.0
    Jan 1 01:00:05 kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
    Jan 1 01:00:05 kernel: All bugs added by David S. Miller <davem@redhat.com>
    Jan 1 01:00:05 kernel: FAT: bogus logical sector size 13056
    Jan 1 01:00:05 kernel: FAT: bogus logical sector size 13056
    Jan 1 01:00:05 kernel: NTFS: Unable to set blocksize 512.
    Jan 1 01:00:05 kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Jan 1 01:00:05 kernel: Mounted devfs on /dev
    Jan 1 01:00:05 kernel: Freeing unused kernel memory: 72k freed
    Jan 1 01:00:05 kernel: Warning: unable to open an initial console.
    Jan 1 01:00:05 kernel: Algorithmics/MIPS FPU Emulator v1.5
    Jan 1 01:00:05 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
    Jan 1 01:00:05 kernel: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
    Jan 1 01:00:05 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
    Jan 1 01:00:05 kernel: eth2: Broadcom BCM4301 802.11 Wireless Controller 3.90.23.0
    Jan 1 01:00:05 kernel: device eth0 entered promiscuous mode
    Jan 1 01:00:05 kernel: device eth2 entered promiscuous mode
    Jan 1 01:00:05 kernel: br0: port 2(eth2) entering listening state
    Jan 1 01:00:05 kernel: br0: port 1(eth0) entering listening state
    Jan 1 01:00:05 kernel: br0: port 2(eth2) entering learning state
    Jan 1 01:00:05 kernel: br0: port 1(eth0) entering learning state
    Jan 1 01:00:05 kernel: br0: port 2(eth2) entering forwarding state
    Jan 1 01:00:05 kernel: g
    Jan 1 01:00:05 kernel: br0: port 1(eth0) entering forwarding state
    Jan 1 01:00:05 kernel: br0: topology change detected, propagating
    Jan 1 01:00:06 kernel: usb.c: registered new driver usbdevfs
    Jan 1 01:00:06 kernel: usb.c: registered new driver hub
    Jan 1 01:00:06 kernel: usb-ohci.c: USB OHCI at membase 0xb8004000, IRQ 2
    Jan 1 01:00:06 kernel: usb-ohci.c: usb-00:04.0, PCI device 14e4:4715
    Jan 1 01:00:06 kernel: usb.c: new USB bus registered, assigned bus number 1
    Jan 1 01:00:06 kernel: hub.c: USB hub found
    Jan 1 01:00:06 kernel: hub.c: 2 ports detected
    Jan 1 01:00:07 kernel: hub.c: new USB device 00:04.0-1, assigned address 2
    Jan 1 01:00:07 kernel: usb.c: USB device 2 (vend/prod 0x482/0xe) is not claimed by any active driver.
    Jan 1 01:00:07 kernel: lp0: using parport0 (polling).
    Jan 1 01:00:08 kernel: usb.c: registered new driver usblp
    Jan 1 01:00:08 kernel: printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x0482 pid 0x000E
    Jan 1 01:00:08 kernel: printer.c: usblp0 Device ID string [146]='ID:FS-1020D;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1020D;CLS:PRINTER;DES:Kyocera Mita FS-1020D;CID:HP Laserjet 1300 Series;'
    Jan 1 01:00:08 kernel: printer.c: v0.13: USB Printer Device Class driver
    Jan 1 01:00:10 kernel: usb.c: registered new driver audio
    Jan 1 01:00:10 kernel: audio.c: v1.0.0:USB Audio Class driver
    Jan 1 01:00:10 kernel: Linux video capture interface: v1.00
    Jan 1 01:00:11 kernel: SCSI subsystem driver Revision: 1.00
    Jan 1 01:00:12 kernel: Initializing USB Mass Storage driver...
    Jan 1 01:00:12 kernel: usb.c: registered new driver usb-storage
    Jan 1 01:00:12 kernel: USB Mass Storage support registered.
    Jan 1 01:00:13 pppd[82]: Plugin rp-pppoe.so loaded.
    Jan 1 01:00:13 pppd[82]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
    Jan 1 01:00:13 pppd[83]: pppd 2.4.2 started by admin, uid 0
    Jan 1 01:00:13 kernel: lp driver: get device ID
    Jan 1 01:00:14 kernel: neg fail
    Jan 1 01:00:16 kernel: printer.c: usblp0 Device ID string [146/max 1552]='ID:FS-1020D;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1020D;CLS:PRINTER;DES:Kyocera Mita FS-1020D;CID:HP Laserjet 1300 Series;'
    Jan 1 01:00:16 kernel: printer.c: Parsing USBLPID...
    Jan 1 01:00:18 pppd[83]: PPP session is 61049
    Jan 1 01:00:18 pppd[83]: Using interface ppp0
    Jan 1 01:00:18 pppd[83]: Connect: ppp0 <--> eth1
    Jan 1 01:00:18 pppd[83]: PAP authentication succeeded
    Jan 1 01:00:18 pppd[83]: peer from calling number 00:03:FE:**:**:38 authorized
    Jan 1 01:00:19 pppd[83]: local IP address 10.255.1.154
    Jan 1 01:00:19 pppd[83]: remote IP address 10.3.0.1
    Jan 1 01:00:19 pppd[83]: primary DNS address 212.80.224.161
    Jan 1 01:00:19 pppd[83]: secondary DNS address 212.80.247.158
    Jan 1 01:00:19 dnsmasq[51]: read /etc/hosts - 4 addresses
    Jan 1 01:00:19 dnsmasq[51]: reading /tmp/resolv.conf
    Jan 1 01:00:19 dnsmasq[51]: using nameserver 212.80.247.158#53
    Jan 1 01:00:19 dnsmasq[51]: using nameserver 212.80.224.161#53
    Jan 1 01:00:19 kernel: lp driver: get device ID
    Jan 1 01:00:19 kernel: neg fail
    Jan 1 01:00:19 kernel: neg fail
    Jan 1 01:00:20 PPPoE: connect to ISP


    Can anybody help me?

  2. #2
    Join Date
    Mar 2004
    Location
    Czech Republic
    Posts
    7

    Talking Same issue WPA-TKIP is not functional

    Hello, I'm facing the same problem. According to tests I've made, there is a major bug that disables the WPA to run. Found some scenarios that behave differently:
    If there is only WPA-TKIP configured, the network is unprotected and it is not a problem to connect anonymously.
    If there are both WPA-TKIP _and_ WEP configured, it is possible to connect via WEP seamlessly, but WPA is still out-of-order, however the client is able to see the WPA protected network, trying to authenticate and get a IP from DHCP server but this never finished.

    When gone through the logs, I found that in web interface on "Wireless status" threre is only "associated" status in comparison to wl sta_info <MAC addr> command where both "associated" and "authenticated" are being listed. Moreover, when listed the wl wpa_auth, the result was "0" (ie no authentication) and wl tkip was disabled in both cases (the WEP encryption was correctly enabled in second configuration).
    I tried to tweak these settings but with no luck (I agree that I'm not a wl-command-guru )

    This issue concerns only to Wl-500b revision1 (Broadcom chipset), as I've tested Wl-500b rev.2 with no problems on WPA-TKIP and Wl-500gx aswell.

    Does anybody have any solution, hint, hammer or whatsoever to solve this issue? The last Oleg's firmware is rockstable and I'm too paranoid to run a simple WEP encryption for a long time.

    P.S.: I tried to reinitialize the setup by resetting to default, tried to reflash the firmware... problem persists :-(
    HELP please!!!
    Last edited by zelva; 02-12-2005 at 10:45.

  3. #3
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    WPA-PSK works fine. You're just a bit confused regarding WEP: in fact it does not secure network, it just allows to connect WEP only devices to this network, but this way your network could be cracked as just simple WEP network.
    So, you've to choose WPA-PSK and set WEP to None for highest security. It also a good idea to use AES instead of TKIP.

  4. #4
    Join Date
    Mar 2004
    Location
    Czech Republic
    Posts
    7
    Quote Originally Posted by Oleg
    WPA-PSK works fine. You're just a bit confused regarding WEP: in fact it does not secure network, it just allows to connect WEP only devices to this network, but this way your network could be cracked as just simple WEP network.
    So, you've to choose WPA-PSK and set WEP to None for highest security. It also a good idea to use AES instead of TKIP.
    With all respect, Oleg, there is no AES in old Wl-500B routers, only a TKIP, so the highest encryption provided by these routers is WPA-TKIP (this info contains even orignal Asus printed manuals AFAIK and even your custom firmware behaves equally). I know that WEP is weak, but this "encryption" is the most safe yet operable at this moment. :-( I know how to set-up a pure WPA protected network using another system (wl-500gx for example), done it already many times.

    The web interface differs from other products of Wl-500 family, including the 500b-rev.2 or 500g & 500gx - don't know if this affects anything...
    Last edited by zelva; 02-12-2005 at 21:14.

  5. #5
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    So, why don't you use WPA-PSK with TKIP?

  6. #6
    Join Date
    Mar 2004
    Location
    Czech Republic
    Posts
    7
    Quote Originally Posted by Oleg
    So, why don't you use WPA-PSK with TKIP?
    Because of that if there is WPA-PSK set (only WPA-PSK, not in combination with WEP for backward compatibility), the wireless network acts like nonencrypted

    If enabled both WPA-PSK and WEP, the network is visible as encrypted, but WPA-PSK clients never get authenticated. I tried a Centrino notebook, Standard PC with PCI wireless card and Ovislink WL-5450AP client/bridge/AP (btw, it has very similar hardware to the Asus products, there is a MIPS CPU but ethernet is based on Realtek chipset). The result is the same in all the cases: If only WPA-PSK enabled, there is no possiblity to connect at all, as the network acts as unencrypted, if both WPA-PSK and WEP are enabled, the network IS encrypted, but the whole process freezes just after association of clients (Windows clients are telling "getting DHCP lease", HW client sees the network, but BSSID is 00:00:00:00:00:00). Regardless if there is a fixed IP or DHCP on the client, there is no successful connect. On the AP side there is only "associated" in wlan log on the respective client MAC addresses BUT, if listed its status through "wl" command, it's saying "associated, authenticated". I'm just confused from the "wl" command, because it tells that WPA is NOT enabled (TKIP is OFF, and wpa_auth is set to 0) -- I'm just confused if this settings play any role, because when changed to values I'd expect to see on WPA-TKIP protected system (ie. TKIP on (hw or sw) and wpa_auth set to 4 (WPA-TKIP mode) nothig happens, even if the wlan port gets down and up. To be honest, I'm not a linux-wl skiller, that's why I' confused on the "wl" status.

    First of all I thought that I'm just wrong and did some mistake. Doublechecked the config, then reset the router to its default, nothing helped. Tried to setup the router using "wizard", tried to setup manually. After that I tried to re-flash the firmware (it's the only one that's stable enough), tried to flash a different one and then reflash the latest. Nothing helped. If tried a borrowed Wl500gx, everything worked on a first shot using the same setting data (ie. SSID, channel, WPA-TKIP auth, passphrase)

    If there's any way I could help track down this issue, just let me know

  7. #7
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    Quote Originally Posted by zelva
    Because of that if there is WPA-PSK set (only WPA-PSK, not in combination with WEP for backward compatibility), the wireless network acts like nonencrypted
    Hm... That's a bit strange... Have you tried older firmwares, like 1.6.5.3? And the newer one - 1.9.5.0?
    You could also flash wl500g firmware using a firmware restoration tool (but do not select 11g mode).

  8. #8
    Join Date
    Mar 2004
    Location
    Czech Republic
    Posts
    7
    Quote Originally Posted by Oleg
    Hm... That's a bit strange... Have you tried older firmwares, like 1.6.5.3? And the newer one - 1.9.5.0?
    You could also flash wl500g firmware using a firmware restoration tool (but do not select 11g mode).
    Well, flashing the "B" unit with WL-500g firmware of the same flavour (1.9.2.7-6b) had helped (just simple reflash without any need to reconfigure the config except disabling the WEP). I'm now running WPA-TKIP wireless network (tried AES too, but with no success, I think there is no HW support in the old Wl-500B models for it).

    Thanks Oleg for hint, a little bit hackish , but functional.

Similar Threads

  1. WL-HDD USB Hub not working
    By r0ll3r in forum WL-HDD Q&A
    Replies: 3
    Last Post: 07-07-2005, 11:20
  2. WPA not working
    By Panja in forum WL-500g Q&A
    Replies: 8
    Last Post: 25-06-2004, 12:36
  3. usb hub working
    By justwords in forum WL-500g Q&A
    Replies: 1
    Last Post: 23-12-2003, 22:45

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •