Omega2: WiFi Client with Lede Image

luz

For me, station mode works fine (and definitely did not before these commits from yesterday). I did not try iw wlan0 scan yet, but just set my SSID and key in /etc/config/wireless. I'll try scan this evening and let you know.

luz

@Nikolay-Hristov [Update] iw wlan0 scan works fine, and ap mode works as well. Not a single unexpected message in dmesg.

However, in my setup I had rearranged /etc/config/network and /etc/config/wireless a bit as I didn't want the standard router setup, but a pure client. I also have removed odhcpd and dnsmasq packages because I absolutely don't want the Omega to ever become DHCP server and mess up my LAN.
I don't think that this should affect the mt76 driver level stability at all. But still, for reference, here's my config:

/etc/config/network:

config interface 'loopback'
  option ifname 'lo'
  option proto 'static'
  option ipaddr '127.0.0.1'
  option netmask '255.0.0.0'

config globals 'globals'
  option ula_prefix 'fd1d:48c4:7633::/48'

# station mode WiFi
config interface 'wlan'
  option proto 'dhcp'
  option hostname 'pixelboard-WiFi'
  option enabled '1'

# Ethernet
config interface 'lan'
  option ifname 'eth0'
  option proto 'dhcp'
  option hostname 'pixelboard-LAN'
  option enabled '1'

# AP mode WiFi
config interface 'wlanap'
  option proto 'static'
  option ipaddr '192.168.44.1'
  option netmask '255.255.255.0'
  option enabled '1'

/etc/config/wireless:

config wifi-device 'radio0'
  option type 'mac80211'
  option channel '11'
  option hwmode '11g'
  option path 'platform/10300000.wmac'
  option htmode 'HT20'
  option disabled '0'

config wifi-iface 'ap_radio0'
  option device 'radio0'
  option network 'wlanap'
  option mode 'ap'
  option ssid 'PIXELBOARD'
  option encryption 'none'
  option disabled '0'

config wifi-iface 'cli_radio0'
  option device 'radio0'
  option mode 'sta'
  option network 'wlan'
  option ssid 'MYSSID'
  option encryption 'psk2'
  option key 'MYPASSWORD'

The only problem I currently have is that disconnecting ethernet does not automatically remove the route for eth0, so if eth0 and wlan0 go to the same subnet, wlan answer packets might get routed to the disconnected eth0.

Gerhard Bertelsmann

@luz Many thx for your updates. Great News. However I didn't get it working so far albeit I hadn't much time to check my setup. I going to take your Settings (network&wireless) and see how it goes ...

Nikolay Hristov

I've tested it more and I can say - yes, there is a significant improve in stability on open source driver. I still have some problems but it is a good step in the right direction. Will test it more and then report here.

Nikolay Hristov

I am still getting kernel call traces with the latest driver and batman-adv.. so not stable yet

[ 481.264177] ---[ end trace 9f93126277e705d5 ]---
[ 481.273327] ------------[ cut here ]------------
[ 481.282527] WARNING: CPU: 0 PID: 6 at /home/geroy/dev/lede-project/lede/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7688/batman-adv-2017.0/net/batman-adv/bat_v.c:630 batadv_algo_dump
[ 481.320572] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mmc_spi iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_
[ 481.528850] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G W 4.4.61 #0
[ 481.543547] Workqueue: bat_events batadv_orig_node_put [batman_adv]
[ 481.555960] Stack : 00000001 00000001 87670000 8004ae38 87c2dbac 8039ed63 8033a64c 00000006
[ 481.555960] 8036331c 87c49ccc 803a0000 80048da4 87670000 8004ae38 8033fb4c 803a0000
[ 481.555960] 00000003 87c49ccc 803a0000 80038db4 87670000 87c49d04 00000128 00000000
[ 481.555960] 8039de50 00000000 87655cb4 87f56c00 87f56e00 5f746162 6e657665 00007374
[ 481.555960] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 481.555960] ...
[ 481.626428] Call Trace:
[ 481.631296] [<8004ae38>] vprintk_default+0x24/0x30
[ 481.640819] [<80048da4>] printk+0x2c/0x38
[ 481.648761] [<8004ae38>] vprintk_default+0x24/0x30
[ 481.658280] [<80038db4>] print_worker_info+0x148/0x174
[ 481.668525] [<87655cb4>] batadv_orig_node_put+0x6dc/0x718 [batman_adv]
[ 481.681500] [<80025418>] warn_slowpath_common+0xa0/0xd0
[ 481.691873] [<8014dbd8>] dump_stack+0x14/0x28
[ 481.700517] [<8001486c>] show_stack+0x50/0x84
[ 481.709137] [<80025418>] warn_slowpath_common+0xa0/0xd0
[ 481.719531] [<87644098>] batadv_algo_dump+0x3e30/0x5204 [batman_adv]
[ 481.732159] [<800254d0>] warn_slowpath_null+0x18/0x24
[ 481.742188] [<8020c7d4>] netdev_pick_tx+0x48/0xd4
[ 481.751546] [<87644098>] batadv_algo_dump+0x3e30/0x5204 [batman_adv]
[ 481.764204] [<87656d40>] batadv_update_route+0xd4/0x1e4 [batman_adv]
[ 481.776866] [<87654954>] batadv_neigh_node_put+0x110/0x190 [batman_adv]
[ 481.790025] [<876548a8>] batadv_neigh_node_put+0x64/0x190 [batman_adv]
[ 481.803053] [<87655b68>] batadv_orig_node_put+0x590/0x718 [batman_adv]
[ 481.816063] [<87652ef4>] batadv_vlan_ap_isola_get+0xee8/0xf50 [batman_adv]
[ 481.829795] [<87655ccc>] batadv_orig_node_put+0x6f4/0x718 [batman_adv]
[ 481.842783] [<80036ccc>] process_one_work+0x1f8/0x334
[ 481.852887] [<80037ae0>] worker_thread+0x2b0/0x404
[ 481.862407] [<80037830>] worker_thread+0x0/0x404
[ 481.871585] [<80037830>] worker_thread+0x0/0x404
[ 481.880743] [<8003be98>] kthread+0xd8/0xec
[ 481.888894] [<8003bdc0>] kthread+0x0/0xec
[ 481.896861] [<80004478>] ret_from_kernel_thread+0x14/0x1c
[ 481.907562]
[ 481.910512] ---[ end trace 9f93126277e705d6 ]---

luz

indeed.

But then, batman is already quite advanced WiFi usage.

Still, could be worth posting the trace to LEDE forum.

Cezane

I'm directly interested solving this problem. However, the open source driver may take a while until it gets fully reliable. I would still focus on integrating the proprietary driver.

The interesting part is that the Linkit Smart OpenWrt image does include the proprietary wifi binary. I'm trying now to build a stripped image and have it put in Omega2. There are still some build errors (like renaming the wifi binary from *.44 to *.45 as the kernel version goes).

https://docs.labs.mediatek.com/resource/linkit-smart-7688/en/tutorials/firmware-and-bootloader/build-the-firmware-from-source-codes

Nikolay Hristov

@Cezane just to say, not sure but I think I've read somewhere that propriety driver does not support ad-hoc mode. Is that true?

Cezane

It seems to me that there are two different proprietary drivers. I can deduce this from two different types of configuration that I've encountered, with Omega and with LinkIt Smart. I'm personally interested in having a reliable AP and Sta at the same time. The driver from LinkIt can support AP, Sta and AP+Sta. Haven't found anything related to ad-hoc mode...

dr_jkl

Yay! With the LEDE image, my Omega2+ connects to my Mikrotik router. Finally I can start developing on this months after receiving it.

onion.io devs: Please fix your wireless drivers so I can come back to your images. I shouldn't have to use the LEDE images just to get wifi out of the box. You've got a great product here but it's hindered by this problem.

Leonardo Costa

Hello,
any news about the topic? With a LEDE project firmware built from scratch with mt76 drivers i have a quite stable wifi 'sta' connection, but i still get disassociations sometimes. Anyone building the proprietary drivers with good results?

Douglas Kryder

onion admin stated several weeks ago that they were developing a completely new wifi driver that would be ready by the end of august. so it's close, hopefully, for onion devs to release the new driver. however, there have been no updates that i'm aware of since the original announcement.

luz

For those building their own images: mt76 open wifi driver has significantly improved again in OpenWrt 18.0.6.2.