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

Tomato and Buffalo WLI-TX4-G54HP, Routing Problems

Discussion in 'Tomato Firmware' started by gkverne, Jun 30, 2007.

  1. gkverne

    gkverne LI Guru Member

    I use a WRT54GL as my router, and a Buffalo WLI-TX4-G54HP as an Ethernet adapter for my Xbox. I've used stock Linksys firmware (no problems), Thibor 15c (no problems), and Tomato (problems). Basically, when I use Tomato (no matter what settings I choose in the Routing configuration page), I can access the internet with my Xbox (and anything else behind the Buffalo), but I can't access SMB shares on the network. I've tried different Buffalo firmwares and configurations, but I've started to think that the issue may be with Tomato. I love absolutely everything else about Tomato, so I'm hoping that I can resolve this and flash back to it. If anyone has any ideas or potential solutions, I'd love to hear them... I've tried enabling RIPv1 and v2 and Spanning-Tree, I haven't tried WDS (but that shouldn't be the issue anyway), and I'm out of ideas. So just to be clear, with Tomato, I'm able to get net access behind the Buffalo, but no access to any other computer using the WRT's LAN.
     
  2. azeari

    azeari LI Guru Member

    hmmm.. what exactly do you mean by using the buffalo as the ethernet adapter for your xbox?

    also, it'll help to see a sample route you've setup
     
  3. gkverne

    gkverne LI Guru Member

    The Buffalo WLI-TX4 is Buffalo's "Ethernet Converter" (http://www.buffalotech.com/products...eless-g-mimo-performance-ethernet-converter/). Basically, it's a WHR minus the WAN port and using different firmware. I plug an Ethernet cable from my Xbox into the WLI-TX4, the WLI-TX4 establishes a connection with my WRT54GL, and the Xbox can access the network. The problem crops up with DD-WRT and Tomato (not Thibor)... With Tomato, the Xbox (and anything else using the WLI-TX4) can access the internet, but not the network (SMB shares, etc).

    Also, I'm not sure how to map a sample route, but basically the (hardware) route from the Xbox to the other networked PCs is Xbox --> WLI-TX4 --> WRT54GL --> (Wireless) PC.
     
  4. azeari

    azeari LI Guru Member

    Well what you could try here is to map a route from your WLI-TX4's subnet(i.e.192.168.2.0) to your WRT's(i.e.192.168.1.0)

    In this case, it should look something like this
    Route to 192.168.1.0
    Gateway 192.168.1.1(assuming the WRT's IP is as such)
    Subnet 255.255.255.0

    I'm in school now so can't really visualize how the routing interface looks like exactly ;) i'll update it if necessary when i get home

    Edit: Route refers to destination, metric should be 0, and e interface.. i'm guessing should be WAN. not sure abt that though (=
     
  5. gkverne

    gkverne LI Guru Member

    I'll have to give static routes a shot... Thanks a bunch for your suggestions! I've never been brave enough to sample static routes, but I'll dig up with IPs and plug them in. What confused me about this situation, however, was the ability of devices behind the TX4 to access the internet, but not other devices on the WRT54GL's wireless.
     
  6. unix_guy

    unix_guy LI Guru Member

    The WLI-TX4 is an Ethernet bridge: it doesn't have its own network. (Don't be confused by the configuration IP address.) Whatever wireless AP it connects to, all the wired devices plugged into it are on the network that the wireless AP is on. So forget about routing.

    What version of Tomato are you using?
    Do you have any PCs connected to the WRT54GL via Ethernet?
    If so, can the Xbox communicate with them?
    If not, could you temporarily connect a PC via Ethernet and try it?
     
  7. gkverne

    gkverne LI Guru Member

    1. I'm using Tomato 1.07
    2. I've got one PC connected to the WRT via Ethernet.
    3. Devices behind the WLI can't see any of the devices behind the WRT. I've tried with the Xbox and with a laptop, both can access the internet without issue, but neither can access any networked PCs on the WRT side.

    Also, for your reference, I can see the WLI and any device behind it when I use Tomato's "Device List". The WLI shows up (as you would expect it to) without a DHCP lease. The device behind the WLI shows up with the same MAC address but a DHCP lease.

    Thanks again for everyone's help and time, hopefully I won't have to go back to Thibor because of this (not that Thibor isn't an excellent firmware)!
     
  8. unix_guy

    unix_guy LI Guru Member

    If all of your PCs were wireless I thought the problem might be that "AP Isolation" was turned on, but that's not it.

    FYI, I'm using Tomato 1.07 on a Buffalo WHR-HP-G54, one wired PC, one wireless laptop, and they can both talk to each other.

    If you didn't do so after you first flashed Tomato, try resetting the WRT54GL to factory (Tomato factory, in this case) defaults by depressing the reset button until the power LED starts to flash. You'll have to reenter all of your setup changes after doing this.
     
  9. gkverne

    gkverne LI Guru Member

    Yeah, I don't think that the problem is AP Isolation either, there are no problems with any of the WRT-connected devices. Also, I always factory-reset (NVRAM-wipe if applicable) when I change firmwares. I'm thinking that the trouble arises from some difference in the way that Tomato (and DD-WRT, of course) handles the devices connected behind the WLI-TX4...
     
  10. unix_guy

    unix_guy LI Guru Member

    I have a WLI-TX4. It is normally connected to the WAN port on my router to pick up my community wireless Internet access.

    I just very nearly duplicated your setup by turning off my laptop's wireless, connecting my laptop's Ethernet port to the WLI-TX4 and connecting the WLI-TX4 radio to the wireless AP in my router. Of course, I had no Internet access while doing this (router WAN port disconnected). Laptop-through-WLI-TX4-to-router's wireless AP and desktop-through-Ethernet-to-router were able to talk to each other.

    One difference: You changed your WLI-TX4's MAC address setting from default to "first connected device". Mine is still at default, so my Tomato doesn't see two devices w/ the same MAC address, like yours does. It's worth trying setting your WLI-TX4 back to default MAC address.
     
  11. gkverne

    gkverne LI Guru Member

    Hmm... I must have been mistaken when I was talking about the Device List page in Tomato... I left everything on the WLI-TX4 at default except for the SSID selection page (the front page when you access the WLI-TX4's web server). So I guess that means that my WLI-TX4 is set to "first connected". I'm actually going to try monkeying some more this evening, and then I'm going to chuck the WLI in favor of a new WHR-G125.
     
  12. unix_guy

    unix_guy LI Guru Member

    As long as you realize that Tomato won't run on the WHR-G125 (newer Broadcom chipset). There is a beta version of DD-WRT for the WHR-G125, though.
     
  13. gkverne

    gkverne LI Guru Member

    unix_guy:

    Thanks for your attention and help! I've got a status update for you...

    I unboxed my WHR-G125 and TFTP'd DD-WRT (special v24 beta for the G125) to it. I did a factory-default reset just to be safe, configured everything so that the G125 acts as a client bridge for the Xbox, and then let it go to work. So far, so good. I fired up XBMC and it has no trouble communicating with other computers on the WRT54GL/Tomato end.

    Sooooo... I'm guessing that the problem lies somewhere within the WLI-TX4...

    Somewhere DEEP within the WLI-TX4. ARP table problems (the Xbox appears to use a new MAC address every boot)? Something else? Bad juju? I'm at a loss.
     
  14. unix_guy

    unix_guy LI Guru Member

    I'm glad to hear you're up and running.
    Too bad we couldn't figure out what was wrong with your original setup, though.
     
  15. gkverne

    gkverne LI Guru Member

    Thanks again for all your help unix_guy! I'm a little disappointed that I couldn't figure out the problem either, but so far, so good with the new setup. I've now got the Buffalo WHR-G125 (DD-WRT) running without any problems at all, the WRT54GL (Tomato) running as the router/gateway, and I've even got the WLI-TX4 running as a replacement for a PCI card gone bad. Now if I can only figure out why the Xbox was giving the TX4 problems...
     
  16. unix_guy

    unix_guy LI Guru Member

    You're welcome!
    I'm glad it all worked out.
     

Share This Page