Disallow wireless access to web ui

Discussion in 'Tomato Firmware' started by Cold Chest, Apr 2, 2009.

  1. Cold Chest

    Cold Chest LI Guru Member

    WRT54GL running 1.23

    In Administration > Admin Acess I have "Allow Wireless Access" unchecked, but still I can access the Web UI from wirelessly connected computers.
    If it makes any difference, it's connected via WDS to a WRT54G v8 running dd-wrt.

    Also in Device List, in Interface I have 4 devices showing as "br0", yet only one is a wired client (me) and the other 3 are using wi-fi. Shouldn't they show as "eth1"?

    Thanks in advance.
  2. Toastman

    Toastman Super Moderator Staff Member Member

    Are they wirelessly connected to that particular router? If they are coming into it on ethernet they are from br0 and the router has no way to know whether they were originnaly connected by wireless.

    br0 is correct, this is the name of the interface, again, are these other machines connected to another AP? Only connections to that particular machine will show as wireless.
  3. bigclaw

    bigclaw Network Guru Member

    Yes, that makes a difference.
  4. Cold Chest

    Cold Chest LI Guru Member

    Well, one of the wireless PCs is connected to the host router, the other two through the client WDS router (at least if I check the web ui on the client router, it shows only 2 wireless connections to it, out of the total three). Yet all three of them appear as "br0" to Tomato. (btw, is there any way to check within tomato which PCs are connected to it directly or through the client router?)

    So you're saying that if they're connected to the client router, they'll appear as ethernet connections to the primary router? Doesn't make much sense to me...

    Even before I set up the secondary router, the one computer that connected directly through wi-fi appeared as "br0"... so I don't think WDS can be much of a factor.
  5. RonWessels

    RonWessels Network Guru Member

    The "Allow Wireless Access" controls whether clients connected to the access point of the local router are able to access the configuration page of that local router. What you have is a client accessing the configuration page of the router via a WDS link. Coming in over WDS is _not_ the same as coming in over the access point.

    If nothing else, the local router has no way of knowing whether clients accessing via the WDS link accessed the network via a wired interface or via wireless access on the remote (WDS) side.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice