Tomato WRT54GL problems with AP side

Discussion in 'Tomato Firmware' started by likuidkewl, Jan 6, 2009.

  1. likuidkewl

    likuidkewl Network Guru Member

    From the start I _think_ this is hardware related but would like some more input from the community.

    We have 2 WRT54GL's setup, one is the router and another is setup as a AP in the other building. They are connected with cat5e over a 150ft professionally installed cable run (port 2 on the router to port 2 on the client or AP)

    Tomato is on both of them 1.23 on the router(host) and 1.23 on the client, the client is only setup as an access point ie. no dhcp, static lease, WPA2 encryption.

    The client stops responding after a unspecified amount of time, lights still on but no love from the internets or the ping.

    SSH from Host to client after boot of client works fine, let no activity happen for a little while(real time unknown) and client stops responding!
    PIng same as above
    Wireless connection:
    Will connect ok after boot, but after idle time will see the SSID but will not connect, due to possible lack of DHCP from host.
    DHCP works after boot, but after lockup only static works but still cannot get to host.
    Rebooting the client then allows connection again.

    Notes 2:
    We have 3 other WRT54GL's elsewhere in the wild setup as Wireless AP's and have not had this issue, the only difference is that they are running off of a actual linux server and not another WRT54GL with Tomato.

    Changing ports on the host and the client
    Downgrading to Tomato 1.19
    Swapping out host router with old linksys.

    Anyone got any ideas?
    We would like to stay with Tomato and would need a real BIG reason to switch.

  2. Toastman

    Toastman Super Moderator Staff Member Member

    Dan, this is very strange. I have over 50 AP's running and never seen this, the only difference appears to be that you are using WPA2 and I use WEP. I supposed it might be possible that you have a hardware fault, try swapping out the client - also check out the power supplies. Also, I know cable problem seems unlikely, but I would bring the client to your place and connect it by a short length of cable to check it is not the problem. (A lot of the CAT5 cable on the market is substandard and does not work up to 100m - a good proportion of chinese-made cable is no use over about 30m).

    Just one other thought, after flashing the routers did you erase NVRAM before setting up the AP's?
  3. likuidkewl

    likuidkewl Network Guru Member

    Thanks for the reply. We are ordering a new unit tomorrow so I will be able to swap it out soon.
    I totally biffed on the power issue I will check it tomorrow.

    Thanks again.
  4. likuidkewl

    likuidkewl Network Guru Member

    Well I dropped in the replacement last week and all went well for about 4-5 days now there is a report of the same issue again. But this didn't appear for a few days. So now I am not sure what the deal is.

    I guess it could be power spikes, as I stated before there is no real difference between my current locations setup and that one beside the WAPs are coming from switches in the closet vice another WRT54GL.

    Clients cannot get dhcp from WAP after a unspecified amount of time.
    WRT54GL 1.1, Tomato 1.23, WAN is OFF, LAN is Wired to Main WRT54GL Running 1.23 connected to DSL, MAIN WRT54GL never goes "down" can always access it.
  5. FRiC

    FRiC LI Guru Member

    Is the problem not being able to connect to the access point or not getting an IP by DHCP?
  6. likuidkewl

    likuidkewl Network Guru Member

    I installed the latest Linksys FW today and dropped in the other router a little after everyone left. So in a few days we will see.

    I did try the DD-WRT route as I use it at home, but something really odd would happen, once i changed the IP to something not after the ensuing reboot it seems that the language displayed on the page is garbled, as in a unsupported way. This kind of makes me wonder if the flash was damaged in someway, maybe by a power spike. Yuck, especially if it happened again to the replacement too.
  7. likuidkewl

    likuidkewl Network Guru Member

    Well now we know it is not a Tomato issue, as over the weekend it is seems to have happened again. So now I am stumped.

    What would make an Access Point stop responding, seems almost like the switch is shutting down due to inactivity. But only recently say withing the last two months.

    I set up a cron/cru to ping from main WRT54GL to the AP we will see how it goes.
  8. Toastman

    Toastman Super Moderator Staff Member Member

    Just a suggestion - try new wireless driver version of tomato - soon to be released by Teddy Bear (USB Mod) and Victek (WRT etc).
  9. likuidkewl

    likuidkewl Network Guru Member

    Thanks for the heads up, I think the Ping will fix this issue. I just wonder what it is that is doing it. IT could be the wireless but the cards in use over there are Dell whatevers, rebranded broadcoms. I didn't think they caused issue, I thought it was limited to Intel. hrmm
  10. likuidkewl

    likuidkewl Network Guru Member

    Looks like it died after around two days of uptime. No ideas why, this is insane.
  11. likuidkewl

    likuidkewl Network Guru Member

    Still fighting with this, but I have replaced everything(router/pws/ups/cable) except the cable between the buildings so I guess we will see next week if it something to do with the cabling. It is now worse it may stay up for about 30 minutes to an hour.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice