QSDK cannot use Luci to setup the wifi

[ifIloveu99]

I’m a beginner in openwrt and qsdk.
I want to use Luci to set up my network, but the interface looks like this:

After looking at some Luci js files, I found that it retrieves information through ubus.
However, the output of ubus call network.wireless status is like this:

root@OpenWrt:~# ubus call network.wireless status
{

}

and the output of ubus call luci-rpc getWirelessDevices is like this:

root@OpenWrt:~# ubus call luci-rpc getWirelessDevices
{

}

The output of iwinfo shows the SSID as unknown.

ath0      ESSID: unknown
          Access Point: 04:F0:21:C5:91:08
          Mode: Master  Channel: 1 (2.412 GHz)  HT Mode: NOHT
          Center Channel 1: 1 2: unknown
          Tx-Power: 50 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: -104 dBm
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11ax/b/g/n
          Hardware: embedded [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy1

ath1      ESSID: unknown
          Access Point: 06:F0:21:C5:91:09
          Mode: Master  Channel: 36 (5.180 GHz)  HT Mode: NOHT
          Center Channel 1: 36 2: unknown
          Tx-Power: 50 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: -103 dBm
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11ac/ax/n
          Hardware: embedded [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy2

mld-wifi0 ESSID: unknown
          Access Point: 00:00:00:00:00:00
          Mode: Master  Channel: unknown (unknown)  HT Mode: NOHT
          Center Channel 1: unknown 2: unknown
          Tx-Power: 0 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: unknown
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11ac/ax/b/g/n
          Hardware: unknown [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: mld-phy0

wifi0     ESSID: unknown
          Access Point: 04:F0:21:C5:91:08
          Mode: Master  Channel: 1 (2.412 GHz)  HT Mode: NOHT
          Center Channel 1: 1 2: unknown
          Tx-Power: 0 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: -104 dBm
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11ax/b/g/n
          Hardware: embedded [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy1

wifi1     ESSID: unknown
          Access Point: 04:F0:21:C5:91:09
          Mode: Master  Channel: 36 (5.180 GHz)  HT Mode: NOHT
          Center Channel 1: 36 2: unknown
          Tx-Power: 0 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: -103 dBm
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11ac/ax/n
          Hardware: embedded [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy2

Does anyone know where the problem?

[brada4]

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

[ifIloveu99]

Can anyone help me please?

[frollic]

Ask the people who gave you the QSDK.

[jdwl1o1]

To give you a more complete explanation, 'QSDK' is not Openwrt and does not function in the same way - as you have identified yourself.

We don't know what Qualcomm has done or how they intend their customers to use it. As you're using the Qualcomm SDK then your account manager / Qualcomm support will need to assist you in building your firmware.

[Hostle]

can you provide the following...

post the output of the following command ... this file likely doesn't exist, but check anyway

ls /etc/board.json && cat /etc/board.json

if it does happend to exist and you recieve output, replace any mac with xx for first mac .. yy for second ..etc.

this file should exist, post the contents, please use code tags.

cat /etc/board.d/0*_network

[ifIloveu99]

Hi Hostle,
This is the output:

root@OpenWrt:~# ls /etc/board.json && cat /etc/board.json
/etc/board.json
{
        "model": {
                "id": "qcom,ipq5332-ap-mi01.3-c2",
                "name": "Qualcomm Technologies, Inc. IPQ5332/AP-MI01.3-C2"
        },
        "network": {
                "lan": {
                        "ports": [
                                "eth0",
                                "eth1"
                        ],
                        "protocol": "static"
                },
                "wan": {
                        "protocol": "dhcp"
                }
        },
        "switch": {
                "switch1": {
                        "enable": false,
                        "reset": true
                }
        },
        "board_name": "qcom,ipq5332-ap-mi01.3-c2",
        "uboot-envtool": "true",
        "wififw_name": "ipq5332_qcn6432_squashfs.img"
}

root@OpenWrt:~# cat /etc/board.d/0*_network

[ -e /etc/config/network ] && exit 0

touch /etc/config/network

CFG=/etc/board.json

. /lib/functions/uci-defaults.sh

ipq53xx_setup_interfaces()
{
        local board="$1"

        case "$board" in
        qcom,ipq5332-ap-emulation |\
        qcom,ipq5332-db-mi01.1 |\
        qcom,ipq5332-db-mi02.1 |\
        qcom,ipq5332-db-mi03.1)
                ucidef_set_interfaces_lan_wan "eth0 eth1"
                        ;;
        qcom,ipq5332-ap-mi01.2 |\
        qcom,ipq5332-ap-mi01.2-c2 |\
        qcom,ipq5332-ap-mi01.2-qcn9160-c1 |\
        qcom,ipq5332-ap-mi01.3 |\
        qcom,ipq5332-ap-mi01.3-c2 |\
        qcom,ipq5332-ap-mi01.3-c3 |\
        qcom,ipq5332-ap-mi01.4 |\
        qcom,ipq5332-ap-mi01.6 |\
        qcom,ipq5332-ap-mi01.7 |\
        qcom,ipq5332-ap-mi01.9 |\
        qcom,ipq5332-ap-mi01.12 |\
        qcom,ipq5332-ap-mi01.13 |\
        qcom,ipq5332-ap-mi01.14 |\
        qcom,ipq5332-ap-mi03.1 |\
        qcom,ipq5332-ap-mi04.1 |\
        qcom,ipq5332-ap-mi04.1-c2 |\
        qcom,ipq5332-ap-mi04.3)
                ucidef_set_interfaces_lan_wan "eth0 eth1"
                ucidef_add_switch "switch1"
                ucidef_add_switch_attr "switch1" "enable" false
                        ;;
                *)
                echo "Unsupported hardware. Network interfaces not intialized"
                ;;
        esac
}

board_config_update
board=$(board_name)
ipq53xx_setup_interfaces $board
board_config_flush

exit 0

Is it not defined the wireless interface？

[Hostle]

thanks, I'll take a look at it .

@ifIloveu99

Is it not defined the wireless interface？

No its in there ..

 qcom,ipq5332-ap-mi01.3-c2 |\

ucidef_set_interfaces_lan_wan "eth0 eth1"

the above should be ...

ucidef_set_interfaces_lan_wan "eth0" "eth1"

this seems a bit odd

 "lan": {
                        "ports": [
                                "eth0",
                                "eth1"
                        ],
                        "protocol": "static"
                },

eth0 & eth1 are labeled as ports in board.json ... also missing setup_macs() functions in 01_network. Let me poke around and see what else i can spot. What actual device is this ?

[ifIloveu99]

This is Qualcomm's ipq5322 development board. It can use scripts to build up wifi, but it cannot be configured on luci.
it is more difficult to use.

thank you for your help.

[Hostle]

Are you able to build images for it, or are you just adding custom script to a prebuilt image ?

If you can build images it makes it easier to add modifications. If you're using a prebuilt image, you'll need to extract it using binwalk, add the mods, and then repackage the image and reflash, for the reason that the mods necessary will not be retained after reboot

but before we get to that, let start by dumping the routers partitions and see if the problem is easy to spot. can you post a bootlog or the output of the following cmd

cat /proc/mtd

you' ll need to dump each partitioin to file, then scp it from the router. See post here for the procedure

IPQ5018: GLiNET B3000 info

excellent. everything is right there. just grab each partition then scp them to safety. cat /proc/mtd dump each part found in above cmd dd if=/dev/mtdblockX of=/tmp/backup/mtdX scp from device scp /tmp/backup <user>@<host> or from host scp root@192.168.1.1:/tmp/backup ./backup am sure you know, just for completion for anyone else who may find this thread

Once you have completed this, use file.bin or you preferred fileshare, and send me the link, I'll go through it and see if i can't help get it working with luci

[ifIloveu99]

This is the output.

root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00040000 "0:TRAINING"
mtd1: 00040000 00040000 "0:LICENSE"
mtd2: 05380000 00040000 "rootfs"
mtd3: 05380000 00040000 "rootfs_1"
mtd4: 00080000 00001000 "0:SBL1"
mtd5: 00010000 00001000 "0:MIBIB"
mtd6: 00010000 00001000 "0:BOOTCONFIG"
mtd7: 00170000 00001000 "0:QSEE"
mtd8: 00010000 00001000 "0:DEVCFG"
mtd9: 00020000 00001000 "0:TME"
mtd10: 00010000 00001000 "0:CDT"
mtd11: 00010000 00001000 "0:APPSBLENV"
mtd12: 00090000 00001000 "0:APPSBL"
mtd13: 00010000 00001000 "0:BOOTCONFIG1"
mtd14: 00100000 00001000 "0:ART"
mtd15: 005a8000 0003e000 "wifi_fw"
mtd16: 004ab784 0003e000 "kernel"
mtd17: 0160a000 0003e000 "ubi_rootfs"
mtd18: 01e08000 0003e000 "rootfs_data"

ok，i will try it