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

Stream drops every 2-4 minutes pretty consistently...

Discussion in 'Tomato Firmware' started by heydre, May 5, 2013.

  1. heydre

    heydre Reformed Router Member

    As I monitor the connection from bridge to AP, the streams, which vary from 100-400KBs, will bottom out for a second or two then usually restore itself and jump ahead. I can watch the same stream, at the same time, off a LAN port on the AP with no drops.

    1. RT-N56U as AP on Padavan's with channel 1..20mhz/WPA-2-AES/DHCP enabled
    2. RT-N16 in wireless ethernet bridge mode (STP and DHCP disabled) on Shibby with mirrored wireless settings (also tried Toastman with same results)

    - Wireless signal quality to bridge is always between 50-60 with a rare neighboring WiFi network near at 30 and usually 5-10 others around 10-20
    - I've noticed no significant CPU/memory usage on either AP or bridge during dropouts
    - Logs show no problem message to note (assuming I'd know one when I see one ;)
    - Occasional "gateway not found" issues on PC behind bridge (fixed with adapter reset usually)
    - Gateway and Static DNS are the AP router's IP
    - Network on bridge is AUTO and on AP is set to G/N
    - Tried MANY versions (RT, RT-N, Toastman, Shibby, different releases) of firmware on the AP and on the bridge with same results

    Frustrating to say the least...I am hoping there is a wireless/routing setting I am missing that will fix....
  2. Kevin Darbyshire-Bryant

    Kevin Darbyshire-Bryant Networkin' Nut Member

    This may be a function of the client's wireless adapter. It could be trying to roam for 'no good reason'. On the other hand wifi (alias radio) is inherently more unreliable than a bit of copper. What happens if you change the SSID of one of the APs as a test (will stop the client trying to roam)
  3. heydre

    heydre Reformed Router Member

    KDB...thanks for response. Not sure what you mean to do as the bridge has to have the same SSID as the AP. Clarify?
  4. Malitiacurt

    Malitiacurt Networkin' Nut Member

    Unfortunately Tomato does a poor job of implementing the repeater-bridge, which is why the 'wireless ethernet bridge' has to have the same SSID as the AP.

    For the repeater bridge to have a different SSID as the AP, you can either flash DDWRT or use flash a VLAN tomato build.

    DD-WRT actually recommends the 'repeater-bridge' use a different SSID to avoid these random disconnects from aggressive roaming wireless clients.


    To do it in Tomato, flash a multiple VLAN build and set up a secondary wireless network, bridge it with the first network that's in client mode.

    Basically the 'bridge' router's eth0 is used as a wireless client. Create a virtual interface (wl0.1) and set it up as an access point (with a different SSID). Under the VLAN tab just choose to Bridge wl0.1 to br0.
  5. mvsgeek

    mvsgeek Addicted to LI Member

    Am I missing something here? Don't clients connecting to the bridge have to be wired? (In a non-VLAN environment, that is).

    I'd try this :
    1. Disable the client's wireless adapter if it has one.
    2. Change AP and bridge to N-only mode.
    3. Disable security. If drop-outs persist, throw up hands in despair, admit defeat. Otherwise try with WPA/AES before jumping in with WPA2.

    I wonder if it's just a matter of the wifi link between the bridge and the AP becoming saturated. As KDB points out, a "bit of copper" beats a radio every time :)
  6. heydre

    heydre Reformed Router Member

    Figures the one detail I've left is the one that I should've said :confused: ...PC client on wireless bridge side IS wired to RT-N16.

    So even though the client PC is NOT wireless does that mean the recs by mvs and mal are STILL to:
    1. Flash VLAN build and setup network/SSID as stated (I've never seemed to get VLAN topology/logic understood)
    2. Essentially simplify setup and check for stability from there?

  7. Malitiacurt

    Malitiacurt Networkin' Nut Member

    No, that changes things, you do not need to flash VLAN build at all. It is likely an issue with the routers/settings on the routers.

    I do remember security issue popping up for many past users regarding wireless bridging. Definitely try what mvsgeek said in #3 (without security, then with WPA/AES before trying WPA2).

    The other thing you can try is to set the 2nd router as client bridge. Your Client PC is wired to the 2nd router so you can test stability that way before 'upping' the complexity to wireless ethernet bridge.

    (There have been previous issues reported with wireless bridging and WPA2, not sure if it was fixed recently but the issue has definitely been there before.




    http://www.linksysinfo.org/index.php?threads/simple-wireless-ethernet-bridge-woes.21216/#post-97955 )
  8. heydre

    heydre Reformed Router Member

    Thanks for patience..been a few weeks...trying out some things:

    0. Tried switching to Client bridge and had to enable DHCP which conflicted with RT-N56's DHCP (so couldn't see host router)
    1. Can't do N only mode (Tomato says so ;) and tried change to WPA (no diff in probs)
    2. Noticed after updating Padavan firmware on RT-N56U...only RT-N16 wan speed dropped to 3-5mbps (must have needed to settle)...but now speeds are back to 14mbps
    3. Considering other firmware mods: Kong/Fractal/BS builds from DD-WRT
    4. Tried 8 streams of hour long programs on Amazon/YouTube that didn't dropout for buffering (some @ 1080p)
    5. Other notes: "gateway not available" came up twice for client PC on RT-N16, NBC stream player had issues in recognizing my high bandwidth connection (kept streaming low quality)

Share This Page