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

tofu 10 problem

Discussion in 'HyperWRT Firmware' started by billy_rud, Nov 29, 2005.

  1. billy_rud

    billy_rud Network Guru Member

    Hello, i have a WRT54G V 2.2. I recently upgraded from tofu 9. The problem im having is none of my wireless clients can access the internet. Wireless Web Access is enabled. Also the DHCP leases over wireless do not show up in the device list.
    EDIT: it works fine without WEP, but once i enable WEP on all devices it doesn't work. WRT54G is in AP mode.
  2. danielhaden

    danielhaden Network Guru Member

    It is expected that none of your wireless devices will access a router that is running in WET mode.

    WET mode is wireless ethernet bridge. This sits at a distant network and serves wired clients. You can also use it to give a game station, Linux box, Windows 98, TIVO a wireless card. It does not serve clients because it is a client.

    In my own testing of WET mode, I find that TOFU 9 works much better.
  3. billy_rud

    billy_rud Network Guru Member

    Whoops, i ment i was running wireless security with WEP.
  4. danielhaden

    danielhaden Network Guru Member

    There are some odd issues with Tofu10 and authentication is not the least of them. It does work with WPA.

    I'd suggest to "sit this one out" and return to Tofu9. A second release of Tofu10 is coming up soon, and it should work better. I have not tested it yet.

    However, Tofu9 exibited zero functional problems except for a non-working STA:Client Mode selection. WET mode can be used as a substitute if you need this functionality.

    Tofu9 worked much better in AP mode, WDS mode, WDS AP mode, and WET mode than Tofu10.
    There's an additional forum on hyperwrt.org that may contain some more information for you.
  5. tofu

    tofu Network Guru Member

    Try putting the WEP key in anything but index 1. I avoided forcing the wep key to index 1 (internally) if it was index 1 already, but that may have caused more problems.

Share This Page