Ezurio is actively working with our vendor to patch the kr00k vulnerability on Ezurio products. Unfortunately, at this time a firmware fix has not been provided for the BCM4329 (used in the 40 Series products). Based on an understanding that this vulnerability has a severity level of “low” by NIST, it is recommended that customers use TLS data encryption whenever possible as TLS tunneled data is not at risk for the kr00k vulnerability.

For more information on the vulnerability, please visit:

https://nvd.nist.gov/vuln/detail/CVE-2019-15126
https://www.eset.com/int/kr00k/

By default, it will show annoSUMMIT as outer ID to protect the ID not showing in public. If really need to show the real ID in outer ID, then need to add semicolon (;) at the end of ID configuration to make it happen.

The responsibility for providing the QDID for a host system is with the provider of the stack that is used on that system. If for instance the host system uses a module that requires the Bluetooth stack to run on that system (e.g. Lairds Sterling-LWB in a Linux platform) the QDID must be provided by the stack vendor who's stack is running on that Linux platform. Challenges might occur when an open-source, community based stack is used. If a module with integrated stack us used (e.g. Lairds BL652) the QDID is provided by the module vendor.  

Yes, we can position our WB as a system on module.  Technically speaking, the WB is a SoM, but we historically haven?t marketed it as such. Our Wireless Bridges are suitable for instance as the main processing unit for a headless (no screen) IoT product. The WBs have everything needed for a SoM except graphics/screen capabilities.   

All this can be controlled through standard Linux commands/programs like ?iw?, ?hostapd?, ?wpa_supplicant?, ?wpa_cli?, etc.

The ECCN for the radios listed, which comprise the "Summit" line of Wi-Fi radios, is 5A002.

We highly do not recommend conformal coating the radio module. If you plan on encapsulating the radio module in a potting compound or conformal coating, you must assure that the compound in liquid or solid form does not enter under the shield where there are sensitive RF components. Some of the capacitive and inductance values are as low (pF and nH) and could be sensitive to contacting materials such as potting compounds. There are potting compounds and conformal coatings which have very good dielectric constants and are suitable for 2.4 GHz potting applications, however, when you apply any of these, they were not accounted for in the circuit design and might reduce performance of the device (or all together cause it not to function).  You should run tests on their particular potting compound and evaluate radio's performance and range.  Also, it's worth mentioning that applying any compound, conformal coating or potting directly to the module WILL void the warranty. If your application requires 100% sealing of the radio module, there is a way to do this very successfully without impacting the module performance. Simply place the module on your PCB. Place a plastic cover over the module (like a hat), make the cover large enough to cover the whole module. Apply glue around the bottom perimeter of the cover where it sits on the PCB. This allows the module to function in free air-space while there is a complete seal around it. This information is only for reference and we recommend you should conduct your own testing with your prototype of your end application to find the best suitable fit for your design.  

Ezurio provides 3D files (STEP) files for most but not all of it's modules.  Based on the nature of the information in the files, in most cases Laird requires a login to access these files as well as layout files and software/firmware downloads.  As such, for most modules, the 3D files are found under the Software Downloads tab of the product page.  The page offers a credentials request link for customers who need credentials.  In most cases, the credentials are provided via return email within about 10 minutes. Please contact support if you have any additional questions or have any issues accessing our downloads.

We only recommend reflowing our modules once as it can damage the module and void the warranty.

Ezurio provides layout files PADS and PADS ASCII formats. The ASCII files will import to Altium (and Protel varients) as well as Cadence (Orcad and Allegro) CAD packages. As far as we know, there is no way to import to Eagle CAD. Please be sure to use the .asc file for PCB and the .txt file for the schematic when importing to Altium. Ezurio uses ORCAD for schematics (Gerbers). 

The recommended cleanser is "hydrocarbon cleaning oil", which can be used to clean the RF shield and PCB. We do not recommend the use of alcohol as it doesn't work as well and could leave residue on the boards.  

mandatory/optional input for EAP type   EAP credentials Mandatory input Optional input LEAP User name, user password   EAP FAST User name, user password PAC file, FAC password PEAP MSCHAP User name, user password CA cert PEAP GTC User name, user password CA cert EAP TLS User name, user cert CA cert EAP TTLS User name, user password CA cert PEAP TLS User name, user cert CA cert   Note 1: this settings should be read in user perspective but not for actual implementation. For example, when a user does not input PAC file, it will use auto PAC provisioning. If a user inputs it, it will do a manual PAC provisioning. Note 2: user password is not used for TLS but only user cert is used instead.    

EAP-TLS is a tunnel authentication. outer identity: this is the User-Name in the RADIUS packet and visible to all intermediate parties inner identity: this is the actual user identification. It is only visible to the user himself and the Identity Provider The user cert is issued to a user identified by the username, so the username has to be configured so we know which user cert we should be using for the authentication. By default, the username is also used during authentication as the outer identity which gets sent in the identity response packet.

To change the loglevel in run time, you can echo the number to /proc/sys/kernel/printk. However, this setting is in RAM and won't be kept in next boot. # echo 8 > /proc/sys/kernel/printk To keep this setting, you need to set it in bootargs in boot loader configuration. Such as add an extra setting "loglevel=4" as below. bootargs='mem=32M console=ttyS0,115200 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs loglevel=4 rootflags=bulk_read,chk_data_crc rw'

There are two reasons to send out null packets with p bit enabled. 1. Its RSSI has crossed over the Roam Trigger and the client radio is supposed to start scanning for a new AP. 2. The client radio is running one of our power-save modes (Fast or Max) and is going to sleep for a brief (e.g. 20 ms) period and is telling the AP so it will buffer traffic for it while it sleeps. After a radio has slept for some period of time (defined as the interval between DTIM periods) it is supposed to wake up and indicate to the AP that it is awake by sending a null packet with the P-bit turned off. The radio should only wake if it has traffic to send or it sees from the DTIM in the AP?s beacons that the AP has traffic to send to it.

The following channels require DFS in Korea KCC/KC domain. Channel Frequency MHz 52 5260 56 5280 60 5300 64 5320 100 5500 104 5520 108 5540 112 5560 116 5580 120 5600 124 5620

Here are the instructions to switch partitions from u-boot: #To revert to kernel-a and rootfs-a: setenv bootargs 'console=ttyS0,115200 loglevel=4 rw noinitrd mem=64M rootfstype=ubifs root=ubi0:rootfs ubi.mtd=6' setenv bootcmd 'nand read 0x22000000 0x000E0000 0x00280000; run _mtd; bootm' saveenv #To revert to kernel-b and rootfs-b: setenv bootargs 'console=ttyS0,115200 loglevel=4 rw noinitrd mem=64M rootfstype=ubifs root=ubi0:rootfs ubi.mtd=7' setenv bootcmd 'nand read 0x22000000 0x00360000 0x00280000; run _mtd; bootm' saveenv note: setenv your ubi.mtd might be different depending on kernel version.

A list of our radios and supported connector types can be found here: WiFi + Bluetooth Modules

With EAP-MS-CHAPv2, the data sent in tunnel will be encapsulated as EAP-MESSAGE AVP (attribute-value pair). In the case of MS-CHAPv2, there is no such extra encapsulation it is just the MS-CHAPv2 message.

The attached document is the list current channels for the KCC domain as of 2015. In document, red means DFS required.

Q: I was told that the the module is able to receive BT and WLAN packets in the same time and it is able to address the packet in the right way. But I do not understand if it is possible, using the SRU (in test mode), to set the receiving mode for the BT and the WLAN in the same time. Could you help me?

A: Here are considerations you can take.

• 40NBT supports 802.11a/b/g/n dual band radio but not simultaneous dual-band operation.
• 40NBT supports simultaneous BT/WLAN receive with single antenna.
• Aux and Main port can receive a signal at a time (played by a switch) So, only case that can receive signal at the same in the below table is BT 2.4Ghz + WLAN 2.4Ghz on Aux port.

Standard: indicates PMK Caching: This means that the 802.1x authentication can be skipped on an access point that a client has already authenticated to once before. Only the 4-way handshake needs to happen. This is useful for a client that needs to reconnect to an access point that it roamed away from previously, due to signal loss etc. However, if a client has not roamed to a particular access point during its current working session, it must then authenticate to that specific access point using 802.1x. PMK Caching is the method defined in the 802.11x (WPA/WPA2) specification. Opportunistic Key Caching: With this method, a client device can skip the 802.1x authentication with an access point after a full authentication,and only needs to perform the 4 way handshake when roaming to access points that are centrally managed by the same WLC in an LWAPP or other controller-based infrastructure. This means that the client doesn't need to authenticate with access points that it wants to roam to, as long as the client has authenticated successfully to at least one of the access points in the same zone as the access point that handled the previous successful authentication. In this case, the PMK identifier has been cached at a central location, like the WLC (or wireless switch.) With OKC, the client must support this method for it to be used, even if the infrastructure has been configured with OKC enabled.

CCKM is supported with all EAP types Laird supports?LEAP, EAP-FAST, PEAP-MSCHAPv2, PEAP-GTC, PEAP-TLS, EAP-TLS and EAP-TTLS. ACS supports all of the EAP types except EAP-TTLS. However, supporting CCKM is not dependent on using ACS as the RADIUS server. Laird can do CCKM with any RADIUS server since CCKM support is in the wireless infrastructure.

The WB40NBT uses WiFi/BT Coexistence on the module. This disconnection is normal as the antennas on the device are saturated from the scanning and discovery process. WiFi will reestablish a connection when the Bluetooth scanning is complete. This happens because the BT portion of the radio requests access to the RF portion of the radio.  The request will have a priority associated with it depending on the type of request (tx, rx, scan, etc.).The WLAN portion will then either grant or deny access to the RF based on what it is currently doing and taking into account the priority of the BT request.

Q: Do you have any C / C++ examples of how to set up an SPP service and exchange data across it using the Laird BT SDK? For example a simple "Chat" example? What I want to do is set up an SPP connection between the Laird module (running on our system acting as a server) and an Android tablet / phone acting as a client. I want to be able to send / receive data over this SPP link.

A: The Bluetooth SDK does not handle the SPP data directly. The SPP data is piped through a Virtual Serial Port that is installed on the system when the stack starts. Also, by default the stack has an SPP Service running when it starts. Typically when the SPP Service is installed it is running on COM Port #7 (this is the default number that the SPP service uses). You will have to.

1. Have the tablet discover and pair with your Laird module (on your system acting as a server).
2. The tablet should do a search for services and will find the Laird module has an SPP service available.
3. The tablet will then connect on your service. From there, you will have to open a COM port using Microsofts API call of CreateFile(). Something similar to the effect of CreateFile("COM7:", GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL ); Here is an example for opening the COM port. You must make sure that your tablet supports SPP as well. If SPP isn't supported then your tablet will not be able to discover your Laird Modules' SPP service.