I didn't try US on that's but GB was giving 5dbm and 8dbm
In my case, BDF FCC with country code removed works fine for US and GB.
For GB the reported power is a bit low but as it turns out on the OEM software it looks the same:
~ # iwconfig ath1
ath1 IEEE 802.11axa ESSID:"_VelopSetupxxx"
Mode:Master Frequency:5.22 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate:2.4019Gb/s Tx-Power:16dBm
RTS thr:off Fragment thr:off
Encryption key:* Security mode:restricted
Power Management:off
Link Quality=0/94 Signal level=-93 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
~ # iwconfig ath0
ath0 IEEE 802.11axg ESSID:"_VelopSetupxxx"
Mode:Master Frequency:2.447 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate:573.5 Mb/s Tx-Power:15 dBm
RTS thr:off Fragment thr:off
Encryption key:* Security mode:restricted
Power Management:off
Link Quality=0/94 Signal level=-102 dBm Noise level=-102 dBm
Rx invalid nwid:131 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
iwinfo
phy0-ap0 ESSID: "xxx"
Access Point: 80:69:1A:xx:xx:xx
Mode: Master Channel: 60 (5.300 GHz) HT Mode: HE80
Center Channel 1: 58 2: unknown
Tx-Power: 19 dBm Link Quality: unknown/70
Signal: unknown Noise: -108 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
phy1-ap0 ESSID: "xxx"
Access Point: 80:69:1A:xx:xx:xx
Mode: Master Channel: 13 (2.472 GHz) HT Mode: HE20
Center Channel 1: 13 2: unknown
Tx-Power: 20 dBm Link Quality: 66/70
Signal: -44 dBm Noise: -108 dBm
Bit Rate: 60.0 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ax/b/g/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
phy2-ap0 ESSID: "xxx"
Access Point: 80:69:1A:xx:xx:xx
Mode: Master Channel: 108 (5.540 GHz) HT Mode: HE80
Center Channel 1: 106 2: unknown
Tx-Power: 27 dBm Link Quality: 50/70
Signal: -60 dBm Noise: -108 dBm
Bit Rate: 6.0 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy2
It seems to be working very well in terms of raw performance but it is early to tell about stability.
Hi all! Congrats and thanks for the job done. I been following this thread for weeks now.
Try to help debug v1 here.
I've flashed two units of MX4200v1 with the bin images shared by SpectreDev some days ago:
04277f5cf18ff4950c726a2a76923a62 openwrt-ipq807x-generic-linksys_mx4200v1-squashfs-factory.bin
d6536b606cb1d2b910d7eb337b5ff472 openwrt-ipq807x-generic-linksys_mx4200v1-squashfs-sysupgrade.bin
Since then, I've had both units up and running, as daily drivers.
wrt1 has an uptime of 3d 20h, while wrt2 1d almost.
I can dump logs and outputs here if you need help debugging v1.
So far my setup is:
wrt1 has the wan, 1Gbps fiber with a ONT, speedtestcpp reports at max 950+ Mbps performance.
wrt1 is serving the Wifi as follows (all country code set as ES, for Spain):
- phy0, ax, channel auto (60 now), 80Mhz. Currently, one client is being wrt2 explained below.
- phy1, n, channel 8 (fixed), 40Mhz. Currently 29 clients.
- phy2, ax, channel 124 (fixed), 80Mhz. Currently 6 clients.
wrt2 is a client wlan to wrt1-phy0 with this link:
576.4 Mbit/s, 80 MHz, HE-MCS 5, HE-NSS 2
432.3 Mbit/s, 80 MHz, HE-MCS 4, HE-NSS 2
Then, using the switch, I connected two computers to it.
Considering they are my daily drivers, I'll be reluctant to flash wrt1, but I can be more experimental in wrt2. I assume it will be a manner of sysupgrades back and forth, isn't it?
I'll be keeping an eye on this forum several times per day.
1 Like
And this is EU BDF with the country set to GB?
Yes, the BDF that you shared with us earlier today with country set to GB
Can you set the country to US and show what iwinfo returns on the same BDF file?
I just checked and none of the BDF files other than Linksys have any country set:
0x0034 0x0458 0x0500 0x05a8
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Asus-RT-AX89X.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Buffalo-WXR-5950AX12.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=CMCC-RM2-6.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Compex-WPQ873.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Dynalink-DL-WRX36.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Edgecore-EAP102.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Edimax-CAX1800.bin
0x833a 0x833a 0x833a 0x833a bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Linksys-MX4200v1.bin
0x833a 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Linksys-MX4200v2.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Netgear-RAX120v2.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Netgear-SXK80.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Netgear-WAX218.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Netgear-WAX620.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Netgear-WAX630.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=prpl-Haze.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=QNAP-301w.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Redmi-AX6.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Wallys-DR8072V01.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Xiaomi-AX3600.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Xiaomi-AX9000.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Yuncore-AX880.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=ZTE-MF269.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=Zyxel-NBG7815.bin
0x0000 0x0000 0x0000 0x0000 bus=ahb,qmi-chip-id=0,qmi-board-id=624,variant=Arcadyan-AW1000.bin
I've installed the new images via the OpenWrt Firmware Selector and am also having issues with 5GHz radio0 as well as radio2 showing up as Generic unknown. Is this likely to be due to the BDF files?
I've got one MX4200V1 and one MX4200V2 and they are both behaving the same with regards to the radios.
Some genius at Linksys thought it would be smart to country lock it and then have kernel overlaying rootfs lol
Hmmm weird, I didn't get such issues
I've sysupgrade-ed from quite an old install 
But I wouldn't have thought that would matter? Unless some config has been carried over which has broken things?
Is there any useful info I can provide?
Run iwinfo command and post here
When doing sysupgrade, we switch to the second partition with a separate rootfs_data: Adding OpenWrt support for Linksys MX5300 - #25 by lytr
The next sysupgrade will allow you to return to the current rootfs_data partition.
I'm thinking about adding an option that would allow sysupgrade on the same partition: Adding OpenWrt support for Linksys MX5300 - #35 by lytr
You get that because the current BDF doesn't create radio2 however your configuration has it from when the previous BDF did.
1 Like
How's FCC bdf going for you, if it works well for you I'll open a pull request to switch V2 to FCC
I used it for about 24h and it worked well after it settled yesterday. Currently I am using the EU BDF that lytr shared with us this morning and it seems to me that it consistently reaches faster transfer rates. I also had a fair share of hiccups with this one in the beginning so I rebooted from Luci like I did yesterday and it also seems to have settled. I don't know if I am imagining things or it's true that the first boot is a bit temperamental but things sort themselves out with a bit of use.
If I am honest with you, right now I don't know if I would recommend to use the FCC or the EU BDF.
yeah the BDF can be tempermental, issue with using EU one is that not everyone is going to read the flashing guide and they may not set their country to US
Yeah, it's a tricky one. I'd eventually would build my own if the EU performs better but we went with FCC for mainstream. I wonder if getting hold of the new firmware for CF which is numbered 2.0.7.213542 would help.
yeah we could try