ok, thanks for verifying…firmware selects driver kmod…only wonder about the leds error…should only depend on kmod-gpio-pca953x which is selected in my test
1 Like
Now i tested an noname SFP to rg45 module. And it can`t work. Ai write that i need install some modules. Afer install the modules it write that it need some more modules… it is AI circle.
ethtool -m eth1
Cannot get module EEPROM information: Not supported
root@BPI:~# ethtool -m eth1
Cannot get module EEPROM information: Not supported
root@BPI:~# dmesg | grep -i sfp
[ 2.741224] FIT: flat_dt sub-image 0x00631000..0x006311a4 "fdt-mt7988a-bananapi-bpi-r4-pro-4e-wan-sfp" (ARM64 OpenWrt bananapi_bpi-r4-pro-4e device tree overlay mt7988a-bananapi-bpi-r4-pro-4e-wan-sfp)
[ 29.913629] platform sfp1: deferred probe pending: (reason unknown)
[ 29.919902] platform sfp2: deferred probe pending: (reason unknown)
root@BPI:~#
About kmod-gpio-pca953x - it has no install. Will test it now.
have you changed the bootconf_extra?
i have updated code and image (phy overlay now also renamed to wan-phy)
1 Like
Yes
root@BPI:~# fw_printenv bootconf_extra
bootconf_extra=mt7988a-bananapi-bpi-r4-pro-cn13#mt7988a-bananapi-bpi-r4-pro-cn14#mt7988a-bananapi-bpi-r4-pro-4e-wan-sfp
root@BPI:~#
mhm, thats strange…i can see the eeprom…have you correctly inserted it?
i’m missing the phy-driver in my current system, but basicly i can read it
root@OpenWrt:~# ethtool -m eth1
Offset Values
------ ------
0x0000: 03 04 07 10 00 00 00 00 00 00 00 06 67 00 00 00
0x0010: 08 02 00 1e 4f 45 4d 20 20 20 20 20 20 20 20 20
0x0020: 20 20 20 20 00 00 00 00 53 46 50 2d 31 30 47 2d
0x0030: 54 20 20 20 20 20 20 20 31 20 20 20 03 52 00 39
0x0040: 00 1a 00 00 32 35 30 36 30 32 30 30 39 33 20 20
0x0050: 20 20 20 20 32 35 30 35 33 30 20 20 68 f0 03 9f
0x0060: 9f 00 11 84 93 c6 2a 5e 19 cd c2 fd 42 c8 4a f3
0x0070: 20 cd 1a 00 00 00 00 00 00 00 00 00 22 7f 3c 18
0x0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0100: 5f 00 ce 00 5a 00 d3 00 8c a0 75 30 88 b8 79 18
0x0110: 1d 4c 01 f4 19 64 03 e8 4d f0 06 30 3d e8 06 f2
0x0120: 2b d4 00 c7 27 10 00 df 00 00 00 00 00 00 00 00
0x0130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0140: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00
0x0150: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 f1
0x0160: 1e 5b 82 b3 00 00 00 00 00 00 00 00 00 00 82 00
0x0170: 05 40 00 00 05 40 00 00 00 00 00 ff ff ff ff 00
0x0180: 43 4f 55 49 41 38 4e 43 41 41 31 30 2d 32 34 31
0x0190: 35 2d 30 33 56 30 33 20 01 00 46 00 00 00 00 c6
0x01a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x01b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 aa aa
0x01c0: 53 46 50 2d 31 30 47 2d 53 52 20 20 20 20 20 20
0x01d0: 20 20 20 20 33 32 00 00 00 00 00 00 00 00 00 35
0x01e0: 1e 28 2e 2e 31 34 29 36 00 00 00 00 00 00 00 00
0x01f0: 00 00 00 00 00 66 00 00 ff ff ff ff 00 00 00 00
root@OpenWrt:~# ip a a 192.168.0.19/24 dev eth1
root@OpenWrt:~# ip link set eth1 up
[ 57.333846] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/usxgmii link mode
root@OpenWrt:~# [ 58.189866] mtk_soc_eth 15100000.ethernet eth1: PHY i2c:sfp2:11 (id 0x00000000) has no driver loaded
[ 58.199050] mtk_soc_eth 15100000.ethernet eth1: Drivers which handle known common cases: CONFIG_BCM84881_PHY, CONFIG_MARVELL_PHY
[ 58.210685] sfp sfp2: sfp_add_phy failed: -EINVAL
WTF? It can insert not correct?
I think that it can broken sfp module?!
I don`t have exp with sfp modules.
It must snap in…last 2mm takes a bit more pressure,but still be careful to insert correctly (not rotated)…
added phy driver, now my wan-sfp looks like this:
root@OpenWrt:~# ip link set eth1 up
[ 29.862428] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/usxgmii link mode
root@OpenWrt:~# [ 30.745482] hwmon hwmon7: temp1_input not attached to any thermal zone
[ 31.845387] mtk_soc_eth 15100000.ethernet eth1: PHY [i2c:sfp2:11] driver [Aquantia AQR113C] (irq=POLL)
[ 31.925288] mtk_soc_eth 15100000.ethernet eth1: switched to inband/10gbase-r link mode
root@OpenWrt:~# ip [ 36.291047] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
root@OpenWrt:~# ip a a 192.168.0.19/24 dev eth1
root@OpenWrt:~# ping 192.168.0.21
PING 192.168.0.21 (192.168.0.21): 56 data bytes
64 bytes from 192.168.0.21: seq=0 ttl=64 time=0.404 ms
64 bytes from 192.168.0.21: seq=1 ttl=64 time=0.245 ms
^C
--- 192.168.0.21 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.245/0.324/0.404 ms
not sure, why ethtool -m only shows hex values, but it is same when using the sfp-lan
root@OpenWrt:~# ethtool -m sfp-lan
Offset Values
------ ------
0x0000: 03 04 07 10 00 00 00 00 00 00 00 06 67 00 00 00
0x0010: 08 02 00 1e 4f 45 4d 20 20 20 20 20 20 20 20 20
0x0020: 20 20 20 20 00 00 00 00 53 46 50 2d 31 30 47 2d
0x0030: 54 20 20 20 20 20 20 20 31 20 20 20 03 52 00 39
0x0040: 00 1a 00 00 32 35 30 36 30 32 30 30 39 33 20 20
0x0050: 20 20 20 20 32 35 30 35 33 30 20 20 68 f0 03 9f
0x0060: 9f 00 11 84 93 c6 2a 5e 19 cd c2 fd 42 c8 4a f3
0x0070: 20 cd 1a 00 00 00 00 00 00 00 00 00 22 7f 3c 18
0x0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0100: 5f 00 ce 00 5a 00 d3 00 8c a0 75 30 88 b8 79 18
0x0110: 1d 4c 01 f4 19 64 03 e8 4d f0 06 30 3d e8 06 f2
0x0120: 2b d4 00 c7 27 10 00 df 00 00 00 00 00 00 00 00
0x0130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0140: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00
0x0150: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 f1
0x0160: 21 96 82 ca 00 00 00 00 00 00 00 00 00 00 82 00
0x0170: 05 40 00 00 05 40 00 00 00 00 00 ff ff ff ff 00
0x0180: 43 4f 55 49 41 38 4e 43 41 41 31 30 2d 32 34 31
0x0190: 35 2d 30 33 56 30 33 20 01 00 46 00 00 00 00 c6
0x01a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x01b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 aa aa
0x01c0: 53 46 50 2d 31 30 47 2d 53 52 20 20 20 20 20 20
0x01d0: 20 20 20 20 33 32 00 00 00 00 00 00 00 00 00 35
0x01e0: 1e 28 2e 2e 31 34 29 36 00 00 00 00 00 00 00 00
0x01f0: 00 00 00 00 00 66 00 00 ff ff ff ff 00 00 00 00
root@OpenWrt:~# ip link set sfp-lan up
[ 45.849424] mxl862xx mdio-bus:10 sfp-lan: configuring for inband/usxgmii link mode
root@OpenWrt:~# [ 46.755387] hwmon hwmon7: temp1_input not attached to any thermal zone
[ 47.875283] mxl862xx mdio-bus:10 sfp-lan: PHY [i2c:sfp1:11] driver [Aquantia AQR113C] (irq=POLL)
[ 47.915199] mxl862xx mdio-bus:10 sfp-lan: switched to inband/10gbase-r link mode
[ 52.247049] mxl862xx mdio-bus:10 sfp-lan: Link is Up - 1Gbps/Full - flow control rx/tx
root@OpenWrt:~# ip a a 192.168.0.19/24 dev sfp-lan
root@OpenWrt:~# ping 192.168.0.21
PING 192.168.0.21 (192.168.0.21): 56 data bytes
64 bytes from 192.168.0.21: seq=0 ttl=64 time=0.395 ms
64 bytes from 192.168.0.21: seq=1 ttl=64 time=0.217 ms
^C
--- 192.168.0.21 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.217/0.306/0.395 ms
btw. i do not have the red-led deferred message i see in your log
It has key. Can Key closed if the module not set in correct position?
For fix the error:
[ 29.919991] platform gpio-leds: deferred probe pending: leds-gpio: Failed to get GPIO '/gpio-leds/sys-led-red'
Need install:
CONFIG_SFP=y
CONFIG_PHYLINK=y
CONFIG_MDIO_I2C=y
CONFIG_I2C_MT65XX=y
CONFIG_I2C_MUX=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_CHARDEV=y
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
Can do it use the command:
cat << 'EOF' >> target/linux/mediatek/filogic/config-6.18
CONFIG_SFP=y
CONFIG_PHYLINK=y
CONFIG_MDIO_I2C=y
CONFIG_I2C_MT65XX=y
CONFIG_I2C_MUX=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_CHARDEV=y
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
EOF
the gpio_pca953x should be already selected by filogic.mk
btw. created a PR for 4E variant:
lets see what AI-pipelines tell us 
1 Like
After install the modules:
root@BPI:~# ethtool -m eth1
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x07 (LC)
Transceiver codes : 0x00 0x00 0x00 0x01 0x00 0x00 0x0c 0x00 0x00
Transceiver type : FC: Multimode, 50um (M5)
Encoding : 0x01 (8B/10B)
BR Nominal : 1300MBd
Rate identifier : 0x00 (unspecified)
Length (SMF) : 0km
Length (OM2) : 550m
Length (OM1) : 550m
Length (Copper or Active cable) : 0m
Length (OM3) : 0m
Laser wavelength : 850nm
Vendor name : PACBTECH
Vendor OUI : 00:00:00
Vendor PN : PAC-GLC-T
Vendor rev : A
Option values : 0x00 0x1a
Option : TX_DISABLE implemented
BR margin max : 0%
BR margin min : 0%
Vendor SN : PA26054221
Date code : 260527
Optical diagnostics support : Yes
Laser bias current : 28.994 mA
Laser output power : 0.2508 mW / -6.01 dBm
Receiver signal average optical power : 0.3258 mW / -4.87 dBm
Module temperature : 19.77 degrees C / 67.59 degrees F
Module voltage : 3.3120 V
Alarm/warning flags implemented : Yes
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser output power high alarm : Off
Laser output power low alarm : Off
Laser output power high warning : Off
Laser output power low warning : Off
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Laser rx power high alarm : Off
Laser rx power low alarm : Off
Laser rx power high warning : Off
Laser rx power low warning : Off
Laser bias current high alarm threshold : 90.000 mA
Laser bias current low alarm threshold : 1.000 mA
Laser bias current high warning threshold : 80.000 mA
Laser bias current low warning threshold : 3.000 mA
Laser output power high alarm threshold : 0.7943 mW / -1.00 dBm
Laser output power low alarm threshold : 0.0794 mW / -11.00 dBm
Laser output power high warning threshold : 0.6310 mW / -2.00 dBm
Laser output power low warning threshold : 0.1000 mW / -10.00 dBm
Module temperature high alarm threshold : 90.00 degrees C / 194.00 degrees F
Module temperature low alarm threshold : -45.00 degrees C / -49.00 degrees F
Module temperature high warning threshold : 85.00 degrees C / 185.00 degrees F
Module temperature low warning threshold : -40.00 degrees C / -40.00 degrees F
Module voltage high alarm threshold : 3.6300 V
Module voltage low alarm threshold : 2.9700 V
Module voltage high warning threshold : 3.4700 V
Module voltage low warning threshold : 3.1300 V
Laser rx power high alarm threshold : 0.6310 mW / -2.00 dBm
Laser rx power low alarm threshold : 0.0013 mW / -28.86 dBm
Laser rx power high warning threshold : 0.5012 mW / -3.00 dBm
Laser rx power low warning threshold : 0.0020 mW / -26.99 dBm
root@BPI:~#
GOOD NEWS! I hope that it will be merged very fastly. Thx for great works!
I have an questions: When openwrt will merged on mainline - wifi7/be14 modules willbe include in the firmware? Or it can easy install? Or i need building manual the firmware?
What have you done differently to get the sfp recognized? Just not completely inserted like i guessed?
What do you mean with mainline? Mainline linux? Openwrt is not merged to mainline…this is a separate process. Mainline linux misses the usxgmii pcs which is on hold because of framework needs clearance.
Wifi/be14 should work when you add the packages. Have not yet assembled my card as i’m still working on base support.
I rebuilt the firmware:
CONFIG_SFP=y
CONFIG_PHYLINK=y
CONFIG_MDIO_I2C=y
CONFIG_I2C_MT65XX=y
CONFIG_I2C_MUX=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_CHARDEV=y
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
I mean openwrt.
Good. If it works like in openwrt from you repo - it good. I hope with time it will be support more futures!
I think this, Add BPI-R4 pro 4e variant by frank-w · Pull Request #24897 · openwrt/openwrt · GitHub, suggestion by AI is correct.
If I wanted to include a custom /etc/config/network like BPI-R4PRO-4E-OPENWRT-V24.10.0-Master-Devel/target/linux/mediatek/filogic/base-files/etc/config/network at d876c3d6d541d0d162c250e235d36992b9009bcd · BPI-SINOVOIP/BPI-R4PRO-4E-OPENWRT-V24.10.0-Master-Devel · GitHub, how would I go about doing it? Instead of doing:
bananapi,bpi-r4-pro-4e)
ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4 lan5 lan6" "wan"
I would like to use a supplied file for /etc/config/network without mandating that on all boards. Is that possible?
I think that it can change use https://firmware-selector.openwrt.org/
#### Script to run on first boot (uci-defaults)
Regarding wifi:
Have not tested it yet,but it should and it is not board specific…mt7996 is supported by mt76 repo which is pulled into openwrt and also mainline linux.
Regarding network config: i guess i need to change the line in network-script. I only have seen comments regarding git headers yet
1 Like
Sorry about the log post. Testing out @frank-w’s branch, I can confirm that the board (Pro 4E) works but with some configuration.
Summary
- Please add
openwrt,netdev-name = "wan";totarget/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patchor label what is in the latter to something. - WiFi does not work by default unless you apply my
/etc/config/wireless. /etc/config/networkneeds to be adjusted a bit.
Changes applied
$ git diff
diff --git a/target/linux/mediatek/filogic/base-files/etc/board.d/02_network b/target/linux/mediatek/filogic/base-files/etc/board.d/02_network
index a2d1d11389..88a02a732f 100644
--- a/target/linux/mediatek/filogic/base-files/etc/board.d/02_network
+++ b/target/linux/mediatek/filogic/base-files/etc/board.d/02_network
@@ -122,7 +122,7 @@ mediatek_setup_interfaces()
ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4" "wan sfp-wan"
;;
bananapi,bpi-r4-pro-4e)
- ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4 lan5 lan6" "wan"
+ ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4 lan5 lan6 sfp-lan" "wan sfp-wan"
;;
bananapi,bpi-r4-pro-8x)
ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4 lan5 lan6" "wan"
diff --git a/target/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patch b/target/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patch
index 2d8ac2a317..6c7bac0109 100644
--- a/target/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patch
+++ b/target/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patch
@@ -48,7 +48,7 @@
+};
--- /dev/null
+++ b/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-4e-wan-sfp.dtso
-@@ -0,0 +1,20 @@
+@@ -0,0 +1,21 @@
+// SPDX-License-Identifier: (GPL-2.0 OR MIT)
+/*
+ * Author: Wilfried Teiken <[email protected]>
@@ -67,6 +67,7 @@
+ managed = "in-band-status";
+ phy-mode = "usxgmii";
+ sfp = <&sfp2>;
++ openwrt,netdev-name = "sfp-wan";
+ status = "okay";
+};
--- a/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-4e.dts
/etc/config/network
The generated /etc/config/network with the above patch applied is then:
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid '000494dab254666e570cb0faad64fe9835b0'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'lan5'
list ports 'lan6'
list ports 'sfp-lan'
config interface 'lan'
option device 'br-lan'
option proto 'static'
list ipaddr '192.168.1.1/24'
config device
option name 'br-wan'
option type 'bridge'
list ports 'wan'
list ports 'sfp-wan'
config interface 'wan'
option device 'br-wan'
option proto 'dhcp'
config interface 'docker'
option device 'docker0'
option proto 'none'
option auto '0'
config device
option type 'bridge'
option name 'docker0'
The incorrect part is:
config device
option name 'br-wan'
option type 'bridge'
list ports 'wan'
list ports 'sfp-wan'
It should not have list ports 'wan' but the other RJ-45 port used for WAN when the mt7988a-bananapi-bpi-r4-pro-4e-wan-phy overlay is applied. I don’t have a setup so I cannot test. I suspect, target/linux/mediatek/patches-6.18/970-arm64-dts-mediatek-mt7988a-add-support-for-bpi-r4-pro-4e.patch, is just missing openwrt,netdev-name = "wan";, or whatever you want to call it.
/etc/config/wireless broken
The default /etc/config/wireless does not work:
config wifi-device 'radio0'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '0'
option band '2g'
option channel '1'
option htmode 'EHT20'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
option disabled '1'
config wifi-device 'radio1'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '1'
option band '5g'
option channel '36'
option htmode 'EHT80'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
option disabled '1'
config wifi-device 'radio2'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '2'
option band '6g'
option channel 'auto'
option htmode 'EHT80'
option country '00'
config wifi-iface 'default_radio2'
option device 'radio2'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'owe'
option disabled '1'
/etc/config/wireless working
```sh
config wifi-device 'radio0'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '0'
option band '2g'
option channel '1'
option htmode 'EHT40'
option country 'GB'
option disabled '0'
option rnr '1'
option tx_burst '0.0'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid '12-Rochford-Close_E6-1QR_2G'
option encryption 'none'
option mbo '0'
config wifi-device 'radio1'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '1'
option band '5g'
option channel '36'
option htmode 'EHT160'
option country 'GB'
option disabled '0'
option rnr '1'
option background_radar '1'
option tx_burst '0.0'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid '12-Rochford-Close_E6-1QR_5G'
option encryption 'none'
option mbo '0'
config wifi-device 'radio2'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option radio '2'
option band '6g'
option channel '37'
option htmode 'EHT320'
option country 'GB'
option disabled '0'
option mbssid '1'
option tx_burst '0.0'
config wifi-iface 'default_radio2'
option device 'radio2'
option network 'lan'
option mode 'ap'
option ssid '12-Rochford-Close_E6-1QR_6G'
option encryption 'sae'
option mbo '1'
option key '1234567890'
option sae_pwe '2'
option ieee80211w '2'
1 Like
Do you think that is ideal? So everyone will need to hunt down and find a valid /etc/config/network before being able to use the router?
I forgot to upload my .config. Here it is. Run make defconfig before running make.
.config (346.2 KB)
thanks, have added your changes, but imho it would be better to have it called only wan in the board dts instead of naming it in overlay…so only 1 of 2 possible names are available…not sure if openwrt reacts always correctly if one interface is missing
edit: have updated my tree to have only “wan” as interface name independ of which overlay is applied and so more similar to 8x
I think that you want an custom config, sorry.