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

WDS Node can see 1 of two other nodes but not get to internet

Discussion in 'Tomato Firmware' started by Arghtastic, Nov 7, 2012.

  1. Arghtastic

    Arghtastic Networkin' Nut Member

    continuing my foray into maddening problems, I have one wds node that can't see the internet but works fine on the local network.

    Pings and traces from/to the main node fail, but form the other secondary node, all is fine. Would appreciate some guru help.
     
  2. mvsgeek

    mvsgeek Addicted to LI Member

    What are your hardware and firmware specs? Did this suddenly start failing or has it never worked?
    I would start by verifying that all MAC addresses in the WDS link definitions are correct, on both main and slave nodes.
    On the main node's device display, can you see the non-functioning slave node? If so, does the displayed MAC address match the actual wireless MAC address of the slave?
    Questions, questions...

    Edit : I found that defining all slaves to each other in addition to main seriously degraded performance. They only really need the main's MAC address.
     
  3. Arghtastic

    Arghtastic Networkin' Nut Member

    WRT54GLx2, 1x3500L all running Toastman. The WRT54GLs are at v1.28.7633 .3-Toastman-IPT-ND ND VPN, and the 3500L is at v1.28.7500 MIPSR2Toastman-RT K26 USB VPN.

    Prior to about 2 weeks ago, the WRT54GLs ran alone and worked. . . .but the 2nd one always had some issues. . .it would incessantly report a virtual WWPN on the Wifi. . . .it took me two reloads and two NVRAM clears to get it to go away. Anyway, it worked. And immediately after upgrade it worked, but about 48 hours after I added the 3500L, something happened and I had to power cycle everything, including cable modem to get network back. After that, the problem child WRT54GL has been half-alive. Works fine for local network access, can't get anywhere outside of the network.
     
  4. Arghtastic

    Arghtastic Networkin' Nut Member

    I will also add the other odd thing I've noticed is that I have a lot of trouble making and receiving calls over sipgate from both an Obi202 and a Nokia VoIP Client on an ESeries since making the 3500L the main access point. The echo test works fine (from Nokia) when call it, but normal phone calls do not. . .from the Obi202 nothing works. My Cable Modem has a wifi access point I don't use on it and when I use that Wifi (from Nokia) SIPGate works fine. So it has to be the 3500L. But I don't see anything logs-wise that should be a problem.
     
  5. mvsgeek

    mvsgeek Addicted to LI Member

    A shot in the dark...I vaguely remember having a similar problem (sorry, can't recall the exact details) that was caused by having "AP Isolation" enabled on all nodes. Soon as I disabled it, all nodes were back on speaking terms.
     
  6. Arghtastic

    Arghtastic Networkin' Nut Member

    I think I got this one. reloaded with stock firmware, then DD-WRT, then back to toastman.....it's got the bizarre mac address on the WLAN again, but it seems to work
     
  7. mvsgeek

    mvsgeek Addicted to LI Member

    MAC address 00:90:4C:5F:00:2A or similar is hard coded in cfe.bin, probably just a place-holder. Anyway, glad you got this resolved. Ah, the mysterious vagaries of wireless networking!
     
  8. Arghtastic

    Arghtastic Networkin' Nut Member

    Cancel all that--people if you get to where I was at--the thing is toast. Just give up. It's half dead.
     

Share This Page