Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 15 Oct 2015 12:59 PM by  Timothy Starkweather
wifi and access point in 5.4GHZ band
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Timothy Starkweather
New Member
New Member
Posts:2


--
15 Oct 2015 11:57 AM

    Currently, when the driver is loaded, I get the following:

    [ 3226.948638] Loading modules backported from Linux version v3.17.1-0-g9db8a8b
    [ 3226.956054] Backport generated by backports.git v3.17.1-1-0-g2ced168
    [ 3227.318511] cfg80211: Calling CRDA to update world regulatory domain


    Then, when I do "iw list" it shows that there is no beacon available in the 5GHZ ranges:

                    Frequencies:
                            * 5040 MHz [8] (disabled)
                            * 5060 MHz [12] (disabled)
                            * 5080 MHz [16] (disabled)
                            * 5170 MHz [34] (disabled)
                            * 5180 MHz [36] (20.0 dBm) (passive scanning, no IBSS)
                            * 5190 MHz [38] (20.0 dBm) (passive scanning, no IBSS)
                            * 5200 MHz [40] (20.0 dBm) (passive scanning, no IBSS)
                            * 5210 MHz [42] (20.0 dBm) (passive scanning, no IBSS)
                            * 5220 MHz [44] (20.0 dBm) (passive scanning, no IBSS)
                            * 5230 MHz [46] (20.0 dBm) (passive scanning, no IBSS)
                            * 5240 MHz [48] (20.0 dBm) (passive scanning, no IBSS)
                            * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5600 MHz [120] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5620 MHz [124] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5640 MHz [128] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                              DFS state: usable (for 29 sec)
                            * 5745 MHz [149] (disabled)
                            * 5765 MHz [153] (disabled)
                            * 5785 MHz [157] (disabled)
                            * 5805 MHz [161] (disabled)
                            * 5825 MHz [165] (disabled)


    If I update the country code to US when running hostapd, it does not enable IBSS on these channels.  Is this an issue with the wifi chip eeprom or with the driver?  I'd like to able to set up an access point in this band to avoid interference with other networks.  Is there a way to do this?\

    Thanks in advance,

    ---Tim

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    15 Oct 2015 12:27 PM
    GWe didn't ever certify the DFS bands on the Torpedo + Wireless, so any bands that require RADAR scanning isn't FCC approved. That includes the channels from 52-144 (or 5.260GHz to 5.720GHz).

    It appears as if you're using the Wireless backports patch based on the driver version you're using. If you upgrade to the latest BSP, 2.4-4, we have a slightly newer driver, and we've modified the regulatory database to allow you to be an access point in the 5.0 and 5.8GHz bands.

    Channels 36, 40, 48 are available in the 5GHz band and 149, 153, 157, 161 and 165 are available in the 5.8GHz band as of release 2.4-4.

    adam
    Timothy Starkweather
    New Member
    New Member
    Posts:2


    --
    15 Oct 2015 12:59 PM
    Adam\-
    Thanks for the fast response! I'll try that out.

    Regards,
    ---Tim
    You are not authorized to post a reply.