Posts made by huntc

@santi29051 We changed the ssid to "Cuprous-<mac>". Does that help? Nothing else should have changed. Also, can you get in via the serial console and see what interfaces are up? Both the AP and ethernet should be up.

@santi29051 Yep - replied in that other thread of yours.

In case there's any interest, we've also managed to get OpenWrt 23.05 working for us - WiFi, GPIO (char mode), WireGuard, and more. We took some inspiration from the work here and figured a few things out ourselves. Here's our fork and the changes we've made: https://github.com/openwrt/openwrt/compare/openwrt-23.05...cuprous-au:openwrt:openwrt-23.05. We also publish the images we'll be using for our production environment there.

Please note that our image is not as feature-full as the Onion one, but it should illustrate how you can start from the OpenWrt stable branch, perhaps towards building something for production.

@santi29051 You'll need a version of OpenWrt that includes WireGuard. We've got some pre-built packages of OpenWrt that we're using for the Omega2S+ here: https://github.com/cuprous-au/openwrt/releases.

Check out our diffs to the main 23.05 branch to see what's changed.

Thanks to both of you. I'm left not understanding whether there is something to be done... FYI I'm also using the Onion dev board with the Omega2S+.

@crispyoz Interesting. Thanks. Will do.

I began suspecting that I may have a h/w failure somehow. So, I then tried another Omega2S+ and all appears well. I can apply the Onion config to my custom 22.03 image as per my first post here. Thanks for the engagement. I hope that my config here may help others too.

I should also mention that the above occurs without applying the Onion config. I'm doing a basic wifi enabling on the 22.03 distro.

I'm also assuming that it shouldn't matter whether there's an actual antenna connected... I don't have a spare at the mo. I can't see why that should affect things though.

OK, I've managed to restore my custom image. TBH I was still having difficulty with the Onion distro also...

So, back to my custom image, which is pretty close to the 22.03 distro. If I set -x within the /sbin/wifi script then after enabling WiFi and a bit of execution, we get:

+ '[' '!' -f /lib/netifd/wireless/mac80211.sh ]
root@OpenWrt:/# [  260.011156] br-lan: port 2(phy0-ap0) entered blocking state
[  260.016854] br-lan: port 2(phy0-ap0) entered disabled state
[  260.022992] device phy0-ap0 entered promiscuous mode
[  260.050570] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[  260.057548] br-lan: port 2(phy0-ap0) entered blocking state
[  260.063294] br-lan: port 2(phy0-ap0) entered forwarding state

...and then it hangs.

@crispyoz I've installed the Omega 22.03 distro again and the WiFi appears to be ok. Perhaps there's something in the kernel or other config that is missing/different from the 22.03 branch...? I'll re-install my distro and try and debug the wifi script as you suggest.

@crispyoz Using the Onion beta now too... Hangs entirely... i.e. same outcome. Hmm.

Another input: If I use the image provided by the image builder for 22.03 then I get the same result i.e. the wifi command causes the system to hang. I thought this'd be an interesting angle just in case I'd something awry when building the image from scratch. I also did a sysupgrade -n to blast away any spurious config.

I'll try the beta image of 22.03 from Onion now and report back...

@crispyoz Thanks for replying. If I use wifi to apply the settings then it hangs.

Having then rebooted and disabled wifi before it tries to bring the interface up lets me get back in i.e.:

uci set wireless.@wifi-device[0].disabled="1"
uci commit wireless
wifi

So now with the network disabled, here are your commands and their output:

root@OpenWrt:/# wifi status
{
        "radio0": {
                "up": false,
                "pending": false,
                "autostart": true,
                "disabled": true,
                "retry_setup_failed": false,
                "config": {
                        "path": "platform/10300000.wmac",
                        "channel": "auto",
                        "band": "2g",
                        "htmode": "HT40",
                        "disabled": true
                },
                "interfaces": [
                        {
                                "section": "default_radio0",
                                "config": {
                                        "mode": "ap",
                                        "ssid": "Cuprous-dc82",
                                        "encryption": "psk2",
                                        "ifname": "ra0",
                                        "key": "12345678",
                                        "network": [
                                                "wlan"
                                        ],
                                        "mode": "ap"
                                },
                                "vlans": [

                                ],
                                "stations": [

                                ]
                        }
                ]
        }
}
root@OpenWrt:/# uci show network
network.loopback=interface
network.loopback.device='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fda1:7d87:bc2f::/48'
network.@device[0]=device
network.@device[0].name='br-lan'
network.@device[0].type='bridge'
network.lan=interface
network.lan.device='br-lan'
network.lan.proto='static'
network.lan.ipaddr='192.168.4.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='0'
network.wan=interface
network.wan.proto='dhcp'
network.wan.device='eth0'
network.wan.hostname='Cuprous-dc82'
network.wlan=interface
network.wlan.device='ra0'
network.wlan.proto='static'
network.wlan.ipaddr='192.168.3.1'
network.wlan.netmask='255.255.255.0'
network.wlan.ip6assign='60'
network.wwan=interface
network.wwan.proto='dhcp'
network.wwan.device='apcli0'
network.wwan.hostname='Cuprous-dc82'
root@OpenWrt:/# uci -s show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='platform/10300000.wmac'
wireless.radio0.channel='auto'
wireless.radio0.band='2g'
wireless.radio0.htmode='HT40'
wireless.radio0.disabled='1'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='wlan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='Cuprous-dc82'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.ifname='ra0'
wireless.default_radio0.key='12345678'
wireless.client=wifi-iface
wireless.client.device='radio0'
wireless.client.network='wwan'
wireless.client.mode='sta'
wireless.client.ssid='MySSID'
wireless.client.key='MyKey'
wireless.client.encryption='psk2'
wireless.client.ifname='apcli0'
wireless.client.disabled='1'

@crispyoz said in Original Image openwrt-22.03.3-ramips:

<snip - working wifi config>

Hopefully related to this thread, I've been looking at applying the latest of what I can glean from Onion's 22.03 branch and applying it to a fresh 22.03 build, but I'm seeing that the WiFi hangs having typed the wifi command. It could be my specific build of the image, but I've taken the OpenWrt 22.03 branch and note that the WiFi works out of the box with the resultant image.

Here's the Onion config; is there more to this than below (it doesn't appear to be fundamentally that different to the example provided)?

	set network.lan.ipaddr='192.168.4.1'

	del_list network.@device[0].ports='eth0'
	set network.wan='interface'
	set network.wan.proto='dhcp'
	set network.wan.device='eth0'
	set network.wan.hostname="${HOSTNAME}"

	set network.wlan='interface'
	set network.wlan.device='ra0'
	set network.wlan.proto='static'
	set network.wlan.ipaddr='192.168.3.1'
	set network.wlan.netmask='255.255.255.0'
	set network.wlan.ip6assign='60'

	set network.wwan='interface'
	set network.wwan.proto='dhcp'
	set network.wwan.device='apcli0'
	set network.wwan.hostname="${HOSTNAME}"

	commit network

	set wireless.@wifi-device[0].disabled='0'
	set wireless.@wifi-device[0].channel='auto'
	set wireless.@wifi-device[0].htmode='HT40'
	set wireless.@wifi-iface[0].ifname='ra0'
	set wireless.@wifi-iface[0].network='wlan'
	set wireless.@wifi-iface[0].ssid="${HOSTNAME}"
	set wireless.@wifi-iface[0].encryption='psk2'
	set wireless.@wifi-iface[0].key='12345678'

	set wireless.client=wifi-iface
	set wireless.client.device='radio0'
	set wireless.client.network='wwan'
	set wireless.client.mode='sta'
	set wireless.client.ssid=MySSID
 	set wireless.client.key=MyKey
	set wireless.client.encryption=psk2
	set wireless.client.ifname=apcli0
	set wireless.client.disabled=1

	commit wireless

	add_list firewall.@zone[0].network='wlan'

	del_list firewall.@zone[1].network='wan6'
	add_list firewall.@zone[1].network='wwan'
	set firewall.@zone[1].mtu_fix='1'
	set firewall.@zone[1].input='ACCEPT'
	set firewall.@zone[1].forward='ACCEPT'

	commit firewall

	set dhcp.wlan='dhcp'
	set dhcp.wlan.interface='wlan'
	set dhcp.wlan.start='100'
	set dhcp.wlan.limit='150'
	set dhcp.wlan.leasetime='12h'
	set dhcp.wlan.dhcpv4='server'
	set dhcp.wlan.dhcpv6='server'
	set dhcp.wlan.ra='server'
	set dhcp.wlan.ra_slaac='1'
	add_list dhcp.wlan.ra_flags='managed-config'
	add_list dhcp.wlan.ra_flags='other-config'
	commit dhcp

Hey there. Now that I'm quite familiar with my Omega2s+, I've re-embarked on customising our OS image directly from the stable OpenWRT 22.03 branch. We're doing this mainly from a security and control perspective as we can see production looming. I realise there's a 22.03 branch directly from Onion, but we end up having to disable features. I'd rather add features as necessary.

My main question at this point is based on observing the logs at boot time. I notice the following:

Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.386866] WARNING: CPU: 0 PID: 1 at drivers/mtd/spi-nor/core.c:2862 spi_nor_init+0x17c/0x184
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.395721] enabling reset hack; may not recover from unexpected reboots
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.402525] Modules linked in:
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.405631] CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.114 #0
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.411655] Stack : 00000000 00000000 80c23974 80860000 806a0000 805fb6b8 80c39300 8069fe23
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.420187]         808633b4 00000001 809b7e90 80061ad8 805f4e8c 00000001 80c23930 2e702557
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.428718]         00000000 00000000 805fb6b8 80c237c8 ffffefff 00000000 00000000 ffffffea
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.437234]         00000000 80c237d4 00000049 806a6298 80860000 00000009 00000000 8036adbc
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.445756]         00000009 809b7e90 80640000 80e4f800 00000018 8032ddc8 00000000 80860000
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.454285]         ...
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.456773] Call Trace:
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.459261] [<8000702c>] show_stack+0x28/0xf0
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.463714] [<800261b4>] __warn+0x9c/0x124
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.467895] [<800262c8>] warn_slowpath_fmt+0x8c/0xac
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.472943] [<8036adbc>] spi_nor_init+0x17c/0x184
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.477728] [<8036b650>] spi_nor_scan+0x7a4/0xba0
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.482524] [<8036c390>] spi_nor_probe+0x94/0x310
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.487312] [<8033ed18>] really_probe.part.0+0xac/0x354
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.492649] [<8033f24c>] driver_probe_device+0x4c/0x154
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.497977] [<8033f8a4>] __device_attach_driver+0xd0/0x15c
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.503556] [<8033c990>] bus_for_each_drv+0x70/0xb0
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.508526] [<8033f5c8>] __device_attach+0xe0/0x180
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.513487] [<8033dc64>] bus_probe_device+0xa0/0xbc
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.518456] [<8033a408>] device_add+0x3e4/0x8e0
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.523062] [<80376b84>] __spi_add_device+0x80/0x160
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.528140] [<80376cc4>] spi_add_device+0x60/0x9c
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.532925] [<80377630>] spi_register_controller+0x7bc/0xaf4
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.538688] [<8037a0a8>] mt7621_spi_probe+0x168/0x220
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.543831] [<803414ac>] platform_probe+0x50/0xa4
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.548633] [<8033ed18>] really_probe.part.0+0xac/0x354
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.553946] [<8033f24c>] driver_probe_device+0x4c/0x154
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.559268] [<8033f9dc>] __driver_attach+0xac/0x1ac
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.564229] [<8033c8e4>] bus_for_each_dev+0x68/0xa4
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.569198] [<8033df38>] bus_add_driver+0x150/0x238
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.574158] [<803401dc>] driver_register+0x98/0x154
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.579129] [<80000638>] do_one_initcall+0x50/0x1b4
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.584086] [<8072e0d4>] kernel_init_freeable+0x1d0/0x26c
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.589591] [<80564058>] kernel_init+0x20/0x108
Sat Jun  3 09:42:30 2023 kern.warn kernel: [    0.594217] [<80002478>] ret_from_kernel_thread+0x14/0x1c

While it shows as a warning, I wonder if there's something for us to attend to here. Any ideas? I've not found much info re. the warning message elsewhere.

Configuration info:

• For Target System, selected MediaTek Ralink MIPS
• For Subtarget, selected MT76x8 based boards
• For Target Profile, Onion Omega2+

Thanks.

@crispyoz Thanks - yes, but I note that the wifi reload doesn't have the drammatic pause effect where the network goes offline for a while. Re-phrasing my question, is wifi reload sufficient for updating Warp's driver with the ssid and credentials?

@crispyoz Thanks! Another case for going with the standard OpenWrt distro it seems!

So, the wifi reload approach won't get us there I assume?

Hi there,

Is there a way we can configure the station interface and apply our settings (ssid, password etc) without restarting the AP?

We've built a program that provides a nice UI to our customers for selecting the Omega's station interface, apcli0. We use the same commands as the wifisetup script, including invoking the OpenWrt wifi script to restart radio0. What we find is that the radio is entirely restarted, including the AP (ra0). This is unfortunate as our UI is connected to the AP, which then loses connectivity for several seconds.

There is the wifi reload command, but I'm unsure whether this is sufficient. The OpenWrt documentation is quite lacking on what reload actually does.

Had there been two radio interfaces, say radio0 for the station and radio1 for the AP, then wifi up radio0 would have worked I guess. Unfortunately for us, radio0 hosts both the station and AP interfaces, and this is making the user experience not-so-great.

Thanks for any help.

@Lazar-Demin said in ️ Beta OpenWRT 22.03 firmware available! Your feedback is needed ️:

@huntc Thanks for the feedback. Yeah, it's a tough balancing act - staying close to the latest developments while maintaining the value-add customizations.
Can you elaborate on what you mean by "blessed by Onion" wrt the OpenWRT distribution?

I went down the standard distro path before and it was mentioned on this forum that the main repo isn't supported by Onion. So, it'd be great if that wasn't the case!

When you mention moving away from MIPS, what's the biggest driver behind that? Is it more horsepower or more support or something else?

We've had to jump through a few hoops having to target MIPS32 and Rust, but it is working for us now. We're quite interested in the more energy-efficient architectures though. Energy efficiency is important to us.

@Lazar-Demin said in ️ Beta OpenWRT 22.03 firmware available! Your feedback is needed ️:

But we're open to hearing feedback and changing our stance on this.

Thanks. Appreciate the insight. My understanding was that these OpenWRT distributions weren't blessed by Onion. If they are, or they are going forward, then we're very happy with that.

Have you had a chance to try out Onion's v0.3.3 firmware for the Omega2/2+? Did you find any value in the additional utilities that were added?

We are using v0.3.3-b256 now and I think we've always used v0.3.3, although please note that we're not yet in production (nearly!). I think that the only utility we're using is the Onion wifi-scan ubus call. Our strategy is to not diverge from the OpenWrt base if practical, although the wifi scan did make things quite a bit easier. That said, we'd probably move to do things the OpenWrt way in the future.

If we were to focus our efforts elsewhere, which areas would you rather see us putting effort into?

We may be a bit different from your other customers. We are more focused on the hardware offering than any customisation of OpenWrt. Continuing to support the main branch of OpenWrt is the most important thing for us.

Moving away from MIPS32 would also be attractive, although I appreciate the logistics of that. Supporting mainstream targets such as an Arm or Risc-V platform would be very attractive.