# MM8108 EU Europe Support **URL:** \ **Category:** General\ **Created:** [September 25, 2026, 11:24pm UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059 "2026-09-25T23:24:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![TechGuy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.morsemicro.com/techguy/32/694_2.png) [@TechGuy](https://community.morsemicro.com/u/TechGuy)\ **Post date:** [September 25, 2026, 11:24pm UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/1 "2026-09-25T23:24:10Z")
Hello, We are working with a Gateworks M.2 Card with the MM8108 module on it (GW16167) and were having issues with getting the software to run when configured for EU country code. Error: ```auto root@noble-venice:~# hostapd_s1g ./hostapd_s1g_wpa3.conf -B Invalid s1g config of oper class, country code and channel s1g mapped ht channel 38 2 errors found in configuration file './hostapd_s1g_wpa3.conf' Failed to set up interface with ./hostapd_s1g_wpa3.conf Failed to initialize interface ``` It appeared the op\_class to be used was 68 for 1mhz and 69 for 2mhz, but this gave us the error. Doing lots of digging, it appears the correct op\_class is 66 for 1mhz and 67 for 2mhz. Is this correct? Where is this documented in the Morse Micro documentation? Any cementing data would be helpful. Thank you. ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [September 29, 2026, 12:59am UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/2 "2026-09-29T00:59:22Z")
Hi @TechGuy I’ll see if we can get the regulatory database lifted from our devices and onto the website where it is more accessible - especially now that we have a better CMS. The old one was a little…underwhelming. If you have a HaLowLink1 or 2 handy, there is a page under Help → Regulatory Information that has a list of all of the channels and their respective regulatory rules. ![image](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/2X/1/1f5850a9836b11426b4d1400f9f560f085a321d9.png) This information is carried through a csv in the Morse Micro OpenWrt package feed. See for example, [morse-feed/essentials/morse-regdb/artefacts/repo\_channels.csv at fb4e676cd0697955340e31e095575ea8d6d70934 · MorseMicro/morse-feed · GitHub](https://github.com/MorseMicro/morse-feed/blob/fb4e676cd0697955340e31e095575ea8d6d70934/essentials/morse-regdb/artefacts/repo_channels.csv) ---
**Author:** ![ldennis](https://avatars.discourse-cdn.com/v4/letter/l/3ab097/32.png) [@ldennis](https://community.morsemicro.com/u/ldennis)\ **Post date:** [September 29, 2026, 2:50am UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/3 "2026-09-29T02:50:32Z")
> [@TechGuy](#): > > It appeared the op\_class to be used was 68 for 1mhz and 69 for 2mhz, but this gave us the error. For reference, this is the op class used for the channel sets like US. As you found, and Arien linked, the EU op-class is 66/67 ---
**Author:** ![TechGuy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.morsemicro.com/techguy/32/694_2.png) [@TechGuy](https://community.morsemicro.com/u/TechGuy)\ **Post date:** [September 29, 2026, 4:20pm UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/4 "2026-09-29T16:20:20Z")
Thank you for the reply, this is very helpful. We are not using the HaLowLink1 or 2 and their help section. We are looking for more generic documentation about the chipset and radio and not something specific to the ‘dev kit’. The GitHub is VERY helpful, just hunting through code is not the typical way we look for documentation. We look forward to seeing more documentation in a more general fashion, thank you for letting us know this effort is currently underway. ---
**Author:** ![ldennis](https://avatars.discourse-cdn.com/v4/letter/l/3ab097/32.png) [@ldennis](https://community.morsemicro.com/u/ldennis)\ **Post date:** [October 2, 2026, 1:45am UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/5 "2026-10-02T01:45:42Z")
The op classes come from the 802.11-2024 Wi-Fi standard, no specific dev-kit behaviour there 🙂 See [IEEE SA - IEEE 802.11-2024](https://standards.ieee.org/ieee/802.11/10548/) Annex E, Table E-5—S1G operating classes, page 5664. | S1G Operating Class | Global Operating class | Channel starting Frequency (GHz) | Channel Spacing MHz | | --- | --- | --- | --- | | 1 (United States and its territories) | 68 | 0.902 | 1 | | 2 (United States and its territories) | 69 | 0.902 | 2 | | … | | | | | 6 (Europe) | 66 | 0.863 | 1 | | 7 (Europe) | 67 | 0.863 | 1 | With that said, we do have some Morse Micro documentation that’s a little easier to consume, see: > **[EU - Morse Micro IoT SDK: BCF regulatory channel support](https://morsemicro.github.io/mm-iot-sdk/framework/doc/html/BCF_REGDOM_SUPPORT.html#autotoc_md83)** > > 1 MHzChannel 1 Centre: 863.5 MHz Bandwidth: 1 MHz S1G Op Class: 6 Global Op Class: 66 Tx Power: 16.13 dBm EIRP AP Duty: 10% / STA Duty: 2.8%1Channel 3 Centre: 864.5 MHz Bandwidth: 1 MHz S1G Op Class: 6 Global Op Class: 66 Tx Power: 16.13 dBm EIRP AP... You’ll need to hover over the channel to get the extra info like op-class: ![image](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/2X/f/f27e1bec3f052bb677ffb7d5f69b241e37630866.png) ---
**Author:** ![TechGuy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.morsemicro.com/techguy/32/694_2.png) [@TechGuy](https://community.morsemicro.com/u/TechGuy)\ **Post date:** [October 2, 2026, 10:45pm UTC](https://community.morsemicro.com/t/mm8108-eu-europe-support/2059/6 "2026-10-02T22:45:17Z")
This is VERY Very helpful! Thank you!