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

Fix channel number when in Wireless Client mode

Discussion in 'Tomato Firmware' started by igorjrr, Mar 19, 2017.

  1. igorjrr

    igorjrr New Member Member

    Hi all,

    I'm using TomatoUSB shibby 1.28 firmware on an ASUS RT-N66U.

    My 5Ghz band is set as Wireless Client. It works well most of the time. However, sometimes it changes from channel 132 to 60 for unknown reason, even though channel 132 is still reachable. When it does that, the connection becomes very bad (unusable basically!)

    I would like to prevent the router from switching to a different channel. Channels 132 and 136 are the best.
    How can I set channels 132 (and possibly 136) as the only acceptable channels for 5Ghz band (so the router doesn't switch to another channel, like 60)? Maybe there are commands I can run to do that.

    I've already tried inside the Basic settings page, the channel 132 is selected for 5Ghz band, but when you go the Status page, it's actually using channel 60 (and then the connection is very bad).

    Thank you!
  2. cloneman

    cloneman Addicted to LI Member

    Since it's on the DFS band, perhaps its auto-switching due to the presence of a radar?

    36-48 and 149-165 are safe from autoswitching
  3. igorjrr

    igorjrr New Member Member

    The 132 and 136 are the ones that actually work :/
    So no way to prevent autoswitching?
  4. cloneman

    cloneman Addicted to LI Member

    perhaps you can periodically set the channel back to the one you want with the wl command

    This would require checking to see what channel you are one (wl channel) and then changing it if neccesary (wl channel 132). For the setting to be applied you probably have to restart the interface (wl down & wl up).

    to get info about all the wl commands, you can try wl | more

    Also of interest, the commands dfs_status , dfs_channel_forced, and radarargs . Maybe with these you can see if radar is interfering, or maybe you can force a DFS channel and ignore radar regulations :p

    Note that messing with the wl command is generally not recommended by the Tomato Developers and can have unexpected behavior, and probably requires to be redone with a startup script to work after a reboot.
  5. txnative

    txnative Networkin' Nut Member

    Since when is wireless client is working? In the past it was instructed to use the wireless ethernet bridge.
  6. cloneman

    cloneman Addicted to LI Member

    I totally missed the part about wireless client. Are you sure it's not the other router that's changing the channel with "auto"? You don't have control over that from the "client" router
  7. Monk E. Boy

    Monk E. Boy Network Guru Member

    Exactly my thought. In wireless client mode it should connect over whatever channel the router is using. If you don't want the client connecting over a particular channel you should make the change on the router, since its the one dictating the channel to use.
  8. igorjrr

    igorjrr New Member Member

    The channel 132 is still available when Status page shows it is using channel 60. I'm still able to connect to channel 132 from another device. Yes, maybe the primary router, for a period of time, changed to channel 60, but that was only temporary. My router should go back to channel 132 as soon as possible.
    What I'd like is that my router should only use channels 132 and 136 (best ones), and I even prefer it disconnects while these 2 channels are not available.
  9. Monk E. Boy

    Monk E. Boy Network Guru Member

    Auto is not based on what's available, it's based on what the router thinks is available. It determines the channel, not the client. You would be better off changing the Auto setting on the router to match what you want the channel to be. Basically Auto is not worth the headache involved, choose a channel, fix the router to that channel, then it never changes from that channel and everything works like everyone expects it to. Auto is a nebulous thing that every router implements differently.

    Also keep in mind WiFi routers can only show you other WiFi traffic. It cannot show you non-WiFi traffic. I could setup a non-WiFi wireless security system that nukes your WiFi network and you wouldn't see a sign of it in routers or clients. You need a spectrum analyzer to see non-WiFi traffic, and they're quite expensive.
  10. cloneman

    cloneman Addicted to LI Member

    I don't think its possible for a client to connect to a another router on a different channel than the router is broadcasting. If it's connected at 60, it means the other router is broadcasting on 60. Unless the other router is one of those expensive routers that has 2 5Ghz radios transmitting simultaneously. In any case, *something* is transmitting on that channel if your other router is connecting to it.
    Monk E. Boy likes this.

Share This Page