Can We Disable Linksys E3000 Guest Wireless Yet?

Discussion in 'Tomato Firmware' started by mBrane, Aug 6, 2011.

  1. mBrane

    mBrane Networkin' Nut Member

    Just upgraded Linksys E3000 to Toastman's build (7475.5 MIPSR2 NOCAT), and *still* have factory guest wireless enabled. Would *really* like to thwack that SSID!

    As of August 2011, what is the best/quickest way to handle this? Do I *really* need to revert to factory FW, run Cisco Connect, then re-upgrade to Tomato?

    Thx in advance!
  2. Toink

    Toink Network Guru Member

    Did you already clear the NVRAM (and your browser's cache) after you upgraded from stock to Toastman's firmware? I got the E3000 and I don't have the Guest wireless SSID.
  3. mBrane

    mBrane Networkin' Nut Member

    I appreciate the reply, but this has been a known issue (ie. more than just clearing NVRAM), since mainline tomato.

    If you really have an E3000, then either 1) you *did* run the Cisco Connect CD while on stock firmware, or 2) you were fully aware of this issue, and found another workaround to disable guest wireless. I'm leaning more toward option 1, but because you didn't mention it, I'm not sure what to think. <shrug>

    * I'm assuming that you have scanned (ie. are familiar with) your wireless spectrum, and confident that you're not broadcasting the default guest wireless SSID (Cisco uses a goofy "slow-cheatah" or "slimy-walrus" -type naming convention... can't miss it!). I'm not trying to be insulting, but coupled with the suggestion to clear my browser's cache (as if *that* will make the SSID go away!), again, I'm not sure what to think. <shrug>

    I fully erased NVRAM when I first went to tomato, and no one seems to be adding the ability to configure this very-cool feature of the E3000. So, something tells me that the guest wireless function is either 1) hard, or 2) under-appreciated (maybe both!).

    Anyway, because of the hassles involved with clearing NVRAM and re-setting up the router, I'm gonna hold off, until someone (hopefully) replies that is familiar with this issue.
  4. TexasFlood

    TexasFlood Network Guru Member

    I would actually love to know how to set up the guest network under Tomato. If the answer could be found by reviewing a backup config of your router that would be cool. I'd volunteer to try!
  5. Toink

    Toink Network Guru Member

    1.) Running the Cisco Connect CD never crossed my mind of doing. I personally find it useless. Since more than 12 years that I owned a Linksys router, I never once ran the CD that comes in the package.

    2.) I flashed directly to Tomato or access stock firmware via its webgui.

    Yes I do own the E3000, two of them. And I never got the "Guest" SSID in them. Unfortunately you're a "New Member" in the forum, hence you can't see my signature? - Since the upgrade of the forum, I'm not sure if it's still the way it was for noobies not to see the sigs.....

    Resetting the NVRAM is a requisite when flashing to 3rd party firmware (or even to stock firmware). That's part of the process to minimize any setup "hiccups". - But of course, you already know that.

    If you find it a "hassle" to clear the NVRAM, then perhaps you should have dug enough and found that it's a breeze restoring your previous setup.

    BTW, tone down the attitude a bit, would you? It's my intention to help you. People here are generous with helping out. But you should do your share of giving everyone even a little respect.

    I hear you. I have been wanting to know that too. Unlike the TS, I want to have the guest SSID in my E3000 - so long as it works.
  6. Toastman

    Toastman Super Moderator Staff Member Member

    Questions that would be nice to have answered by mBrane:

    1) Does the guest SSID that you are stuck with still have encryption working?
    2) Are there any NVRAM settings remaining in your config pertaining to this guest SSID and especially encryption?

    If so it might help with developers trying to actually get that feature working. I've never seen a new installation of Tomato with it still broadcasting, normally it would have to be enabled and set up with nvram entries. But if you've erased NVRAM, then it shouldn't be there.
  7. tvlz

    tvlz LI Guru Member

  8. mBrane

    mBrane Networkin' Nut Member

    As requested: NVRAM, ifconfig, and ps (attached)

    Notice wl0.1 (the guest wireless sub-interface for the factory/auto-generated "FastMoose-guest" SSID).
    * also notice that 15 sub-interfaces and MACs have been pre-allocated on wl0, which is encouraging

    Also, notice that "wl status" does not see this interface (again, I can see the beacon when I scan my spectrum):

    root@e3000:/tmp/home/root# wl status
    SSID: "MyNon-FastMooseSSID"
    Mode: Managed RSSI: 0 dBm noise: -85 dBm Channel: 1
    BSSID: xx:xx:xx:xx:xx:xx Capability: ESS ShortSlot
    Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
    802.11N Capable:
    Chanspec: 2.4GHz channel 1 20MHz (0x2b01)
    Control channel: 1
    802.11N Capabilities:
    Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ]


    Attached Files:

  9. Toastman

    Toastman Super Moderator Staff Member Member

    Thanks !!!!
  10. mBrane

    mBrane Networkin' Nut Member

    Additional notes:
    - how to disable the guest wireless SSID looks pretty straightforward (ie. wl0.1_bss_enabled=0)
    UPDATE: no, that did *not* work as expected! I did an "nvram commit," but maybe I need to reboot? Will try that...
    UPDATE2: OK, it took a reboot to knock down the guest SSID.

    - guest wireless is *not* functional with this config (ie. no IP address received after associating)
    - guest wireless has no security enabled (ie. it's open)

    At this point, I'm really intrigued by the possibilities with guest wireless. BTW, I noticed that the VLAN build seems to be a (much) lower version than the latest non-VLAN build. Does this mean that it lacks some of the current capabilities? Please advise. Thx!
  11. tvlz

    tvlz LI Guru Member

    Use "wl -i wl0.1 status" for the guest wireless sub-interface
  12. Toastman

    Toastman Super Moderator Staff Member Member

    No, the VLAN-GUI branch is just a different series, [44xx] it was built on top of the standard version (7479)
  13. mBrane

    mBrane Networkin' Nut Member

    It looks like the VLAN builds are 1.28.4402 (I didn't see a VLAN build under the 7479 directory). Help?
  14. Toastman

    Toastman Super Moderator Staff Member Member

  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