1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Some devices cannot connect to WPA2 AES

Discussion in 'Tomato Firmware' started by mp3markel, Dec 11, 2009.

  1. mp3markel

    mp3markel Addicted to LI Member

    I have Tomato version 1.27 recently upgraded from 1.25 because of these issues I am having.

    1 laptop = XP SP3
    1 laptop = Windows 7 updated
    1 laptop = Vista updated
    Nintendo Wii
    Ipod Touch
    2 Sony PSPs (use 802.11B WPA1 AES supported only)

    Network & Router:
    Linksys WRT54GL
    WPA/WPA2-PSK AES
    /27 - 255.255.255.224 (30 host addresses)
    Static DHCP set in Tomato to recognize MACs and send connection information to nodes

    Issue:
    Wired devices are fine, laptops connect via WiFi fine. Wii, PSP and Ipod cannot connect to the network. I view the the device list under Basic settings and see the request to connect but never succeed. They have been connecting for months without a problem, all of a sudden they have issues. Before purchasing the WRT54GL I had an SRX200 router that did this very same thing. I thought having multiple devices using AES caused an issue so i got the new router... not the problem apparently...

    I used to have all the devices set to static with the information pre-configured. I recently discovered the static DHCP feature on Tomato and used that to send the DNS and IP information to the devices. I set the devices to auto get information (DHCP enabled). After doing this wired nodes and laptop on Wifi still work without a glitch. Wii PSPs and Ipod do not.

    Whats really frustrating and embarrassing is that I'm CCNA, Network+ and Security+ certified and feel like I should be able to solve this but cannot. I appreciate anyone being able to shed light on my WiFi issues! -Mark
     
  2. jan.n

    jan.n Addicted to LI Member

    Hi Mark,

    perhaps you can post a portion of your syslog so we can see what's happening.

    Cheer up, that happens to all of us sometimes...
     
  3. mp3markel

    mp3markel Addicted to LI Member

    I've read at some other forums that people are having the same issues with 1.25 and it seems 1.27 as well: tbird2340 - http://www.myopenrouter.com/forum/thread/12820/Tomato-1.25-issues/

    Here is a section of my syslog of when i attempt to connect. Thanks again for the help!

    Code:
    Dec 11 23:27:21 ? user.notice kernel: klogd started: BusyBox v1.14.4 (2009-11-29 06:50:47 PST)
    Dec 11 23:27:21 ? user.info kernel: vlan1: del 01:00:5e:00:00:01 mcast address from master interface
    Dec 11 23:27:21 ? user.info kernel: vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
    Dec 11 23:27:21 ? user.info kernel: br0: port 2(eth1) entering disabled state
    Dec 11 23:27:21 ? user.info kernel: br0: port 1(vlan0) entering disabled state
    Dec 11 23:27:21 ? user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 11 23:27:21 ? user.info kernel: br0: port 1(vlan0) entering disabled state
    Dec 11 23:27:21 ? user.info kernel: device vlan0 left promiscuous mode
    Dec 11 23:27:21 ? user.info kernel: br0: port 2(eth1) entering disabled state
    Dec 11 23:27:21 ? user.info kernel: device eth1 left promiscuous mode
    Dec 11 23:27:21 ? user.info kernel: device eth1 entered promiscuous mode
    Dec 11 23:27:21 ? user.info kernel: br0: port 2(eth1) entering learning state
    Dec 11 23:27:21 ? user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 11 23:27:21 ? user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 11 23:27:21 ? user.info kernel: br0: topology change detected, propagating
    Dec 11 23:27:21 ? user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 11 23:27:21 ? user.info kernel: br0: topology change detected, propagating
    Dec 11 23:27:21 ? user.warn kernel: vlan1: Setting MAC address to  00 25 9c 30 72 35.
    Dec 11 23:27:21 ? user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: started, version 2.51 cachesize 150
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Dec 11 23:27:22 ? daemon.info dnsmasq-dhcp[2437]: DHCP, IP range 192.168.1.2 -- 192.168.1.30, lease time 1d
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: reading /etc/resolv.dnsmasq
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: using nameserver 65.32.5.112#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: using nameserver 65.32.5.111#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: using nameserver 207.69.188.186#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: read /etc/hosts - 0 addresses
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: read /etc/hosts.dnsmasq - 6 addresses
    Dec 11 23:27:22 ? user.info init[1]: Linksys WRT54G/GS/GL
    Dec 11 23:27:22 ? cron.err crond[2443]: crond (busybox 1.14.4) started, log level 9
    Dec 11 23:27:22 ? daemon.info dnsmasq[2437]: exiting on receipt of SIGTERM
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: started, version 2.51 cachesize 150
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Dec 11 23:27:22 ? daemon.info dnsmasq-dhcp[2450]: DHCP, IP range 192.168.1.2 -- 192.168.1.30, lease time 1d
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: reading /etc/resolv.dnsmasq
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: using nameserver 65.32.5.112#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: using nameserver 65.32.5.111#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: using nameserver 207.69.188.186#53
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: read /etc/hosts - 0 addresses
    Dec 11 23:27:22 ? daemon.info dnsmasq[2450]: read /etc/hosts.dnsmasq - 6 addresses
    Dec 11 23:27:26 ? daemon.notice miniupnpd[2531]: HTTP listening on port 5000
    
     
  4. Engineer

    Engineer Network Guru Member

    FWIW, I had the same issues with earlier firmwares. Had to set the security to WPA/WPA2 Personal with AES to get everything to work.
     
  5. mp3markel

    mp3markel Addicted to LI Member

    Yeah mine is currently WPA/WPA2-PSK AES. The issue has got to be WPA2 because with no security everything connects fine. I've read on other forums about bugs in the drivers that control the radios on the WRT54GL. I'm thinking of loading DDWRT firmware or going back to linksys...
     
  6. TexasFlood

    TexasFlood Network Guru Member

    You might try WPA/AES before you bail. I don't think it is any less secure than WPA2 from a practical perspective and works great for me and most who I've seen discuss it. And it's not just Tomato for me, I use the same with DD-WRT, if for no other reason than it improves interoperability.
     
  7. SL83

    SL83 Addicted to LI Member

    Yup.

    WPA-AES offers the same level of security as WPA2-AES.

    Both are using the same type of encryption - AES-CCMP.
     
  8. gawd0wns

    gawd0wns LI Guru Member

    Give the ND ("New Driver") firmware version a try, I currently run it on my WRT54GL with no problems.

    I bet it is something small, like a misplaced character in the password...Also, look at the wifi channel Tomato is broadcasting on. If you are in North America, channels 13 and 14 are not to be used. I tend to keep my wifi on one channel as opposed to auto. Since you have old devices, you will have to set B/G mode on mixed, and security as WPA/WPA2 Personal.

    As usual, ensure you do a 30-30-30 reset before and after flashing the firmware.

    Cheers
     

Share This Page