Wifi config on a Multitech mLinux Conduit

@kersing

Hi Jac,
I followed your instructions to load the modules. I got no error messages so I presume they loaded ok. ifconfig -a shows:

eth0 Link encap:Ethernet HWaddr 00:08:00:4A:06:33
inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:23 Base address:0xc000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1476 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1462 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:187 errors:0 dropped:0 overruns:0 frame:0
TX packets:187 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22230 (21.7 KiB) TX bytes:22230 (21.7 KiB)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

…I presume I should expect to see wlan0 in the ifconfig if it was working?

Is there a list of compatible wifi adapters for the Conduits? I couldn’t find one on the Multitech site.

You can check the output of lsmod to see if the modules were loaded and dmesg to check for any output generated by the modules.
I’m not aware of a list of compatible adapters. You could ask MultiTech on their forum…

Thanks very much Jac,
lsmod shows the modules loaded ok. Dmesg gave an interesting clue:

rtl8192cu: Chip version 0x10
rtl8192cu: MAC address: 00:13:ef:30:30:7e
rtl8192cu: Board Type 0
rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
usbcore: registered new interface driver rtl8192cu
rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
rtlwifi: Firmware rtlwifi/rtl8192cufw_TMSC.bin not available

I raised a query on the Multitech forum yesterday, and will pursue a list of compatible adapters. We won’t be the only ones keen to connect over wifi. I’ll update here and the wiki when I get an answer.

Thanks for your help, Mark

1 Like

I have a Wi-Fi adapter based on the rt2870 chip. I had a similar error, it detected the card but said it couldn’t find rt2870.bin. I downloaded this bin file from the kernel git repo, placed it in /lib/firmware/rt2870.bin and was able to connect using the same wpa_supplicant.conf and interfaces file. I suspect if you find the firmware for your device and place it in the correct location it should work.

1 Like

Hello,
I just bought a Belkin wireless USB device, with a Realtek 8192cu chipset inside.
After plugged in the Multitech mlinux conduit, I see that modules are loaded well.
It fails when trying to load the firmware files.

Snipped from dmesg:

usb 1-2.4: new high-speed USB device number 23 using atmel-ehci
usb 1-2.4: New USB device found, idVendor=050d, idProduct=1004
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: 802.11n WLAN Adapter
usb 1-2.4: Manufacturer: Realtek
usb 1-2.4: SerialNumber: 00e04c000001
rtl8192cu: Chip version 0x11
rtl8192cu: MAC address: c0:56:27:80:28:27
rtl8192cu: Board Type 0
rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
rtlwifi: Firmware rtlwifi/rtl8192cufw_TMSC.bin not available

By doing a modinfo on rtl8192cu, I got:

root@mtcdt:/lib/modules/3.12.27/kernel/drivers/net/wireless/rtlwifi# modinfo rtl8192cu | grep firmware
firmware: rtlwifi/rtl8192cufw_TMSC.bin
firmware: rtlwifi/rtl8192cufw_B.bin
firmware: rtlwifi/rtl8192cufw_A.bin
firmware: rtlwifi/rtl8192cufw.bin

I found these files at firmwares/rtlwifi at master · TI-OpenLink/firmwares · GitHub.
I followed the advice of @cmolson to create /lib/firmware and putting the 4 firmware files into it, but this did’nt help.

I am stuck now, and suspect that the solution is not so far.
If someone could help me, please.
Louis.

I found a working solution at https://www.debian-fr.org/t/installation-de-clef-usb-wifi-netgear-wna1000m/68643/5

The rtl8192cufw_TMSC.bin file has to be put at /lib/firmware/rtlwifi directory.
Note: this is working in mLinux kernel version 3.12.27

Now ifconfig -a is showing wlan0 device.

1 Like

That’s awesome, well done @Louis :slight_smile:

You’r welcome.
In addition, note that in the config file /etc/network/interfaces, the “allow-hotplug wlan0” trick does not make wlan0 interface up while booting without manual intervention.
I must use the normal way: “auto wlan0” to make it working

Hello Louis,
I’m not sure the auto wlan0 is really needed as stated in the /etc/network/interfaces :

#Wifi client
#NOTE: udev rules will bring up wlan0 automatically if a wifi device is detected
#and the wlan0 interface is defined, therefore an "auto wlan0" line is not needed.
#If "auto wlan0" is also specified, startup conflicts may result.

in my case, the auto keyword is needed.
Try to remove it, and use “allow hotplug”.
But for me, the wlan0 itf did not if-up

hi Louis,
I have also a belkin wifi dongle seen as a “rtl8192cu” in the dmesg logs; (under mLinux kernel version 3.12.27 too)
I tried to put the FW files as you suggested (in /lib/firmware/rtlwifi) but no success in showing up the WLAN0 :-/

Actually when the module is loaded ,dmesg gives a “Firmware is too big” error.

rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
rtlwifi:rtl_fw_cb():<0-0> Firmware is too big!

any hints in this ?
cheers
Rico

i guess the firmware file is not the good one, or is altered. Try to cross verify other sources of download for the fw file.
When you remove the firmware file, what is the full path written in the error in the log file ?

Hi Rico - did you solve this? I’m getting the same issue.

Mark

Hi Mark,
sorry for not having replied to your question.
I didn’t succeded in making running the wifi dongle so I kept the GW connected to Eth cable.
yet I’m still interested in getting hints :slight_smile: and from your side ? how did you solve it ?

cheers
Rico

Hi,

I tried to configure WiFi according to your method on my multitech conduit which ships with preinstalled WiFi module. But when i ran the command

ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:00:4A:37:2B
inet addr:192.168.0.101 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::208:ff:fe4a:372b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:166 errors:0 dropped:0 overruns:0 frame:0
TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14771 (14.4 KiB) TX bytes:14582 (14.2 KiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

This did not show any wifi0. Any help in this matter?

Can you try
ifconfig -a
and
lsmod
and post the output?
(Please use [code] and [/code] to enclose the output)

Thank you for the response.
The output is as below:

root@mtcdt:~# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:08:00:4A:37:2B
          inet addr:192.168.0.101  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::208:ff:fe4a:372b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3009 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1613 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:444966 (434.5 KiB)  TX bytes:211756 (206.7 KiB)
          Interrupt:23 Base address:0xc000

gre0      Link encap:UNSPEC  HWaddr 00-00-00-00-62-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1476  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

gretap0   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1462  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ip_vti0   Link encap:UNSPEC  HWaddr 00-00-00-00-62-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1364  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

tunl0     Link encap:UNSPEC  HWaddr 00-00-00-00-62-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
root@mtcdt:~# lsmod
Module                  Size  Used by
bluetooth             194621  0
rfkill                 10109  1 bluetooth
usb_f_acm               4199  1
u_serial                8936  3 usb_f_acm
g_serial                1738  0
libcomposite           26763  2 usb_f_acm,g_serial
configfs               20798  3 usb_f_acm,libcomposite
mts_io                 50871  0
vizzini                15862  2
cdc_acm                14885  0
spidev                  4904  2
atmel_mci              12966  0
spi_atmel              10487  0
atmel_usba_udc         11246  0
udc_core                6158  2 atmel_usba_udc,libcomposite
tmp102                  2732  0
pps_gpio                2351  0
pps_core                7419  1 pps_gpio
uio_pdrv_genirq         2706  0
uio                     6938  1 uio_pdrv_genirq

Thanks a lot

Additionally the output of dmesg is as below:-

root@mtcdt:~# dmesg
0x000000160000-0x000000200000 : "u-Boot Redundant Config"
0x000000200000-0x000000800000 : "uImage"
0x000000800000-0x000001000000 : "Config"
0x000001000000-0x000001800000 : "OEM Config"
0x000001800000-0x000010000000 : "Rootfs"
libphy: MACB_mii_bus: probed
macb f802c000.ethernet eth0: Cadence MACB at 0xf802c000 irq 23 (00:08:00:4a:37:2b)
macb f802c000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:00, irq=-1)
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-atmel: EHCI Atmel driver
atmel-ehci 700000.ehci: EHCI Host Controller
atmel-ehci 700000.ehci: new USB bus registered, assigned bus number 1
atmel-ehci 700000.ehci: irq 31, io mem 0x00700000
atmel-ehci 700000.ehci: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.12.27r15 ehci_hcd
usb usb1: SerialNumber: 700000.ehci
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci 600000.ohci: AT91 OHCI
at91_ohci 600000.ohci: new USB bus registered, assigned bus number 2
at91_ohci 600000.ohci: irq 31, io mem 0x00600000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: AT91 OHCI
usb usb2: Manufacturer: Linux 3.12.27r15 ohci_hcd
usb usb2: SerialNumber: at91
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
rtc (null): invalid alarm value: 1900-1-1 0:0:0
at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0
at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver.
i2c /dev entries driver
at91sam9_wdt: enabled (heartbeat=15 sec, nowayout=0)
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3964 buckets, 15856 max)
ipip: IPv4 over IPv4 tunneling driver
gre: GRE over IPv4 demultiplexor driver
ip_gre: GRE over IPv4 tunneling driver
IPv4 over IPSec tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 10
mip6: Mobile IPv6
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
l2tp_core: L2TP core driver, V2.0
Key type dns_resolver registered
at91_rtc fffffeb0.rtc: setting system clock to 2018-03-24 10:47:25 UTC (1521888445)
usb 2-3: new full-speed USB device number 2 using at91_ohci
usb 2-3: New USB device found, idVendor=04e2, idProduct=1414
usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
devtmpfs: mounted
Freeing unused kernel memory: 168K (c0574000 - c059e000)
jffs2: notice: (74) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
jffs2: notice: (74) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
udevd[85]: starting version 182
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
pps pps0: new PPS source pps.7.-1
pps pps0: Registered IRQ 32 as PPS source
tmp102 0-0048: initialized
atmel_usba_udc 500000.gadget: MMIO registers at 0xf803c000 mapped at d0928000
atmel_usba_udc 500000.gadget: FIFO at 0x00500000 mapped at e1100000
atmel_spi f0000000.spi: version: 0x212
atmel_spi f0000000.spi: Using dma0chan1 (tx) and dma0chan2 (rx) for DMA transfers
atmel_spi f0000000.spi: Atmel SPI Controller at 0xf0000000 (irq 28)
atmel_spi f0000000.spi: master is unqueued, this is deprecated
atmel_spi f0004000.spi: version: 0x212
atmel_spi f0004000.spi: Using dma1chan0 (tx) and dma1chan1 (rx) for DMA transfers
atmel_spi f0004000.spi: Atmel SPI Controller at 0xf0004000 (irq 29)
atmel_spi f0004000.spi: master is unqueued, this is deprecated
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
vizzini 2-3:1.0: This device cannot do calls on its own. It is not a modem.
vizzini 2-3:1.0: ttyXRUSB0: XR21v14x usb uart device
vizzini 2-3:1.2: This device cannot do calls on its own. It is not a modem.
vizzini 2-3:1.2: ttyXRUSB1: XR21v14x usb uart device
vizzini 2-3:1.4: This device cannot do calls on its own. It is not a modem.
vizzini 2-3:1.4: ttyXRUSB2: XR21v14x usb uart device
atmel_mci f0008000.mmc: version: 0x504
vizzini 2-3:1.6: This device cannot do calls on its own. It is not a modem.
atmel_mci f0008000.mmc: using dma0chan3 for DMA transfers
vizzini 2-3:1.6: ttyXRUSB3: XR21v14x usb uart device
atmel_mci f0008000.mmc: Atmel MCI controller at 0xf0008000 irq 22, 1 slots
usbcore: registered new interface driver vizzini
vizzini: Exar USB UART Driver for XR21V141x
[INFO] mts-io:mts_io_init:1007: init: v1.5.16
[INFO] mts-io:mts_id_eeprom_load:913: detected board MTCDT-0.1
[INFO] mts-io:mts_id_eeprom_load:921: sizeof: 512
[INFO] mts-io:mts_id_eeprom_load:922: vendor-id: Multi-Tech Systems
[INFO] mts-io:mts_id_eeprom_load:923: product-id: MTCDT-247A
[INFO] mts-io:mts_id_eeprom_load:924: device-id: 19528911
[INFO] mts-io:mts_id_eeprom_load:925: hw-version: MTCDT-0.1
[INFO] mts-io:mts_id_eeprom_load:932: mac-addr: 00:08:00:4A:37:2B
[INFO] mts-io:mts_id_eeprom_load:934: imei:
[INFO] mts-io:mts_id_eeprom_load:935: capa-gps: yes
[INFO] mts-io:mts_id_eeprom_load:936: capa-din: no
[INFO] mts-io:mts_id_eeprom_load:937: capa-dout: no
[INFO] mts-io:mts_id_eeprom_load:938: capa-adc: no
[INFO] mts-io:mts_id_eeprom_load:939: capa-wifi: yes
[INFO] mts-io:mts_id_eeprom_load:940: capa-bluetooth: yes
[INFO] mts-io:mts_id_eeprom_load:941: capa-lora: no
[INFO] mts-io:mts_id_eeprom_load:950: mac-bluetooth: 00:23:A7:C9:04:44
[INFO] mts-io:mts_id_eeprom_load:959: mac-wifi: 00:23:A7:CA:F8:30
[INFO] mts-io:mts_id_eeprom_load:966: uuid: 75EC47543675B8DB355002EA1CE14367
[INFO] mts-io:load_port:694: no accessory card inserted in port 1
[INFO] mts-io:load_port:729: accessory card 2 vendor-id: Multi-Tech Systems
[INFO] mts-io:load_port:730: accessory card 2 product-id: MTAC-LORA-H-868
[INFO] mts-io:load_port:731: accessory card 2 device-id: 19525146
[INFO] mts-io:load_port:732: accessory card 2 hw-version: MTAC-LORA-1.5
[INFO] mts-io:load_port:753: accessory card 2 eui: 00:80:00:00:A0:00:1F:D5
[INFO] mts-io:lora_setup:60: loading LORA accessory card in port 2
[INFO] mts-io:lora_setup:90: created link [lora] to [ap2], success:0
[INFO] mts-io:lora_setup:125: Substitute pins
[INFO] mts-io:lora_setup:131: LORA H: Replace name AP2_GPIO1 with name AP2_CDONE
[INFO] mts-io:lora_setup:132: LORA H: Replace pin number 84 with number 84
[INFO] mts-io:lora_setup:131: LORA H: Replace name AP2_GPIO2 with name AP2_CRESET
[INFO] mts-io:lora_setup:132: LORA H: Replace pin number 85 with number 85
[INFO] mts-io:lora_setup:189: ap_subdirs[port_index=1] = cf0c8b20 ap_subdirs[port_index=1]=bf0d6958
usb 1-2: new high-speed USB device number 2 using atmel-ehci
usb 1-2: New USB device found, idVendor=0424, idProduct=2534
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
usb 1-2.1: new high-speed USB device number 3 using atmel-ehci
[INFO] mts-io:mts_attr_store_radio_reset:289: radio is reset

usb 1-2.1: New USB device found, idVendor=0424, idProduct=2534
usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2.1:1.0: USB hub found
hub 1-2.1:1.0: 4 ports detected
usb 1-2.2: new high-speed USB device number 4 using atmel-ehci
usb 1-2.2: New USB device found, idVendor=1618, idProduct=9113
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
usb 1-2.2: Product: Wireless USB Network Module
usb 1-2.2: Manufacturer: Redpine Signals, Inc.
usb 1-2.2: SerialNumber: 000000000001
usb 1-2: USB disconnect, device number 2
usb 1-2.1: USB disconnect, device number 3
usb 1-2.2: USB disconnect, device number 4
usb 1-2: new high-speed USB device number 5 using atmel-ehci
usb 1-2: New USB device found, idVendor=0424, idProduct=2534
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
usb 1-2.1: new high-speed USB device number 6 using atmel-ehci
usb 1-2.1: New USB device found, idVendor=0424, idProduct=2534
usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2.1:1.0: USB hub found
hub 1-2.1:1.0: 4 ports detected
usb 1-2.2: new high-speed USB device number 7 using atmel-ehci
usb 1-2.2: New USB device found, idVendor=1618, idProduct=9113
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
usb 1-2.2: Product: Wireless USB Network Module
usb 1-2.2: Manufacturer: Redpine Signals, Inc.
usb 1-2.2: SerialNumber: 000000000001
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb f802c000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode

The operating system does not seem to recognize the module.
Is the WiFi module provided by MultiTech? In that case I would try the forum @ multitech.net.

Yes, the WiFi module is provided by multitech. I have opened one case at their support portal