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

WRT54GS + Tomato v1.17 no windows network browse

Discussion in 'Tomato Firmware' started by mikep55, Jun 9, 2008.

  1. mikep55

    mikep55 Addicted to LI Member

    I am running a WRT54GS V2.0 with Tomato v1.17. I have just added a wireless winXP client and have discovered that I am now having problems with windows network browsing. I found the threads which suggested disabling loopback of port forwarding and now the wireless client can see the rest of the network shares but there is still a problem that the wired clients cannot see the wireless clients shares. The problem seems to be that the wired side of the router does not forward the netbios broadcast packets to the wireless side.

    I have also tried running the router with the dd-wrt v24 firmware and have the same problems.

    When I revert back to a DLink di-624 wireless router, everything works perfectly. I have now tried 2 differing WRT54GS routers running both Tomato and dd-wrt, and no combination works properly.

    So, my question is, is there a setup configuration item that I am missing which enables full wireless/wired remote browsing in both directions with the WRT54GS? Is there a magic formula that I am missing?
     
  2. Kiwi8

    Kiwi8 LI Guru Member

    Check that u have not enabled "AP Isolation" under Advanced -> Wireless.
     
  3. mikep55

    mikep55 Addicted to LI Member

    Nope. AP Isolation is disabled.
     
  4. HennieM

    HennieM Network Guru Member

    My Advanced > Firewall > NAT Loopback on Tomato 1.19 is set to "Forwarded only", and I have no such problems.

    The Wired switch and the wireless interface are bridged together in most setups, so unless you explicitly filter netbios (tcp/udp ports 137, 138, 139), or broadcasting in general, you should not have problems. I suggest you ssh or telnet in, and check your firewall ules. If you find a problem, see which settings you can turn off/on in the web interface.
     
  5. mikep55

    mikep55 Addicted to LI Member

    Yes, I am set to "Forwarded only" also and the wired and wireless are bridged in my setup as well. I am not knowingly filtering netbios across the bridge anyway. All interfaces are set to enable both broadcast and multicast.

    In my case I have several win98 clients which need to access the wireless XP client and they use the netbios broadcasts which are not going across the wired to wireless bridge. These seem to be what are failing.
     
  6. mikep55

    mikep55 Addicted to LI Member

    PROBLEM RESOLVED, though not yet understood.

    I read with interest the thread "Why is QoS throttling transfers within my LAN?" as it seems to have a similar issue with the wan to wireless bridge. So I decided to try and disable QoS and see what happened. With QoS disabled, everything works perfectly. The wireless side now sees the broadcast packets. So I again enabled the QoS and everything STILL worked perfectly.

    So, with QoS still enabled I then rebooted the router and again network browsing of the wireless client was dead. So I again disabled QoS and once again everything started working perfectly. Then I enabled QoS and everything continues to work.

    So, there seems to be a problem with QoS starting up at boot time which interferes with propogating a broadcast packet from the wan side to the wireless side which gets corrected if QoS is stopped and restarted.

    Does anyone have any idea how QoS might be involved in this and why it would cause this type of broadcast interference?
     

Share This Page