AP+WDS Setup w/Static DHCP & Wireless Filter

Discussion in 'Tomato Firmware' started by brookie, Oct 9, 2010.

  1. brookie

    brookie LI Guru Member

    Hello everybody,

    I have a few questions, so I'll explain my setup first. Please bear with me. I am running Tomato 1.28 SpeedMod by Rodney from his site on two routers.

    Both routers setup as AP+WDS, WPA/WPA2 Personal + AES.

    First router - WRT54GS v.2/WDS-Host is connected to the SB5101 Cable modem/wan. One PC is directly conected to this router as well.

    Second router - WRT54G v2.2/WDS-Client is on the other side of the house. A PS3 and a PC are directly connected to the this router. Another PC connects to the this router wirelessly.

    :confused: For security, I am using Wireless Filtering on both routers. I added the wireless mac of each router to the Wireless Client Filter list on the other router. Is this part necessary?

    :confused: I am also using Static DHCP. I added the hardware mac & ip of each router into the Static DHCP list of the other router. Is this part necessary as well?

    It seems like the two steps above are redundant but that's how I set it up and everything works. In the Status/Device List each router shows the wireless WDS of the other (wds0.49153).

    :confused: On the same Status/Device List the static dhcp ip of the WDS-Client or WDS-Host only shows up sporadically (br0). Sometimes it's on the list, and sometimes it's not. What's going on here?

    The WDS setup has been running great for some time but I wanted a better signal strength/signal quality from one router to the other, and the one wireless PD, so I added 7db antennas to each router. The signal has improved and the wireless PC seems to have a better connection.

    I also increased transmit power from 42 to 48 mw on each router. Also, Frame Burst was disabled on the WRT54G so I enabled it.

    After the increase in power or enabling frame burst on the WRT54G/WDS-Client, this old reliable router will sometimes just hang. I can't access it via web/gui or ssh. The PS3 will get kicked off too.

    After some time it will come back to life. No reboot or anything. It just suddenly works fine again.

    :confused: I checked dmesg and /var/log/messages, top as well, and can't find any errors. Any ideas on how to troubleshoot this when it happens? Could it be the power increase or frame burst?

    My appologies for the long post, but any input will be appreciated.


    ps networking, beer, pizza... mmm, :biggrin:
  2. Toastman

    Toastman Super Moderator Staff Member Member

    The power increase is so incredibly small that it won't affect anything, any change you see is likely to be something else. Many people find WDS to be unstable, and frame burst is known to be troublesome. Anyway, why not just turn it off and see if things improve? Similarly, the other things you mention are easy to troubleshoot by disabling them. If they are redundant, don't use them. You didn't say if the problem with accessing the web GUI of that router occurs on radio, LAN, or both.
  3. brookie

    brookie LI Guru Member

    Hi Toastman,

    Thanks for your response.

    To answer your queston, the problem is when that router goes down the PS3 and PC connected to it can't reach that router or the WDS-Host router which is connected to the WAN. From my machine hard connected to the WDS-Host I can still reach the internet but can't ping that funky router on my LAN via the antennas on this host. I am not using wireless on my machine, only cat5.

    So it's wireless in respect that I can't ping it from my machine through the WDS Host.

    We are using WDS because each person wants to plug into their own router and there is only one cablemodem attached to one internet source. Guests that come over use wireless from anywhere in the house.

    I found this error this morning but it may be from services being restarted after changing some settings and saving them.

    Oct 9 01:41:08 ? user.info init[1]: Linksys WRT54G/GS/GL
    Oct 9 01:41:08 ? cron.err crond[16205]: crond (busybox 1.14.4) started, log level 9
    Oct 9 02:00:01 ? syslog.info root: -- MARK --

    I found this error on the speedmod blog, and elsewhere in Chinese (I can't read Chinese) but no one seems to know what is going on with this error. I don't think I had this with regular Tomato 1.28.

    I am going to do an NVRAM erase and import my saved oconfiguration. I can turn off frame burst as well, but I wish I could actually figure out if that is what caused the issue in the first place. Okay, let's see what happens.
  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