I've got 2540ea6 up and running. For some reason default gw for lan interface was not set after upgrade.
That is exactly my scenario. Thanks for pointing that out.
I have been running @qosmio ’s NSS branch for the past 24hrs without any issues (minus needing to revert to an older VLAN config style that is apparently a known issue on NSS builds). Should the NSS branch suffer from the same issue? If so I’ll revert the commit you linked and try again
1 Like
Here's some pictures of a serial port cable install. I just finished doing this for my devices. Again, it's a JST PH 6 pin. I am dangling it out of one of the bottom vents and then it tucks into another, nice and hidden until I need it. Then I can just pull it out with a little pick/hook.
4 Likes
its a generic issue in ath11k. not related to nss. you will see the same issue in non nss builds. if you revert the patch it told it will be fixed but still has the issue with bss transition from 2.4 to 5 ghz in roaming scenarios. a fix for that is tested by me in my dd-wrt builds and looks stable so far and as i said i will work with qosmio to make a openwrt patch for it . i also sended a comment for the original bad patch to the upstream maintainers but never got a reply for weeks now. typical upstream ignorance
6 Likes
@asd111333 -
i concede your point about the NAND wear.
however - my mx4300 will not reboot to other partition with power cycles and is effectively bricked after flashing the build to both partitions.
So won't the cycle count reset block the power cycle x3 method to rebood to the other partition?
It won't. The boot counter is reset only if OpenWrt have successfully boot.
1 Like
ok. that suggests both partitions are bonked.
my device status is a mystery then. i'll post logs after i get serial access.
thx
Thanks, @BrainSlayer. I'll wait for your + qosmio's patch for openwrt in that case. I'm more likely to use BSS transitions from 2.4 to 5 than have my clients manually changing BSSIDs right now. I likely hit the crash so often last week as I was stress testing the different APs / BSSIDs.
I'd also be happy to try out your changes if you'd be willing to share the dd-wrt patch.
I've got at least one crash, don't see anything in the logs, let me know if there is anything I can setup for future crashes.
Also, anybody has problems connecting to WiFi? I keep having fairly frequent problems with connecting to WiFi, both from Mac and Androids. It will connect after switching b/w SSID several times. Symptoms are either self-IP (I see IP advertised by DHCP server), or ..nothing (just disconnect from WiFi, the same - I see IP advertised by DHCP server), or sometimes it looks like WiFi is rebooting.
i did a pull request with the patch on qosmios github, but its just compile tested since i manually had to merge it to the openwrt tree. but if there is any bug left its would be just a small thing which would be easy to fix
4 Likes
So, at the moment I'm pretty sure that connection issues are not specific to my network config - I've installed OpenWrt 23.05.4 r24012-d8dd03c46f on RBR50, did the same config and it works fine. Then I've reset MX4300 to defaults and reconfigured it from scratch, exactly the same - and again see frequent issues connecting to WiFi. I'm on r0-2540ea6.
I just set up an mx4300 as an access point on r0-2540ea6 and have my wifi camera's connected to it on the 2.4ghz radio. Been fine for 8 hours so far as well as other random devices connecting to the 5ghz radios.
@asd111333, @lytr -
an update to my birck after flashing asd111133's image to both partitions -
i got serial access on my mx4300 and found both partitions borked. it was changing boot_part as expected - that was not the issue
lytr's image flashed to both partitions and all set again.
i did notice that both builds have the serial console turned off once openwrt is fully booted; i'm not sure if that desired or not, but can inhibit some torubleshooting
i'm thinking that when i forced-flashed asd333111's build to alt_kernel and rebooted to boot_part 2, that the errantly-entered code somehow corrupted the first image?
anyway - i'm glad we are on a path to support and appreciate the help
Got two of the MX4300. Installed OpenWRT on both and successfully formed a mesh. Set up 802.11s mesh point on radio2 and set it to the same channel on both (namely 161 in my case). Both nodes working fine.
Which radio is the 2x2 5Ghz and which one is the 4x4? What’s the difference between radio0 and radio2? Should I be setting them both to the same SSID?
Much thanks to the OpenWRT developers for making this hardware useful!
2 Likes
these mx4300 devices seemingly have great hardware. i got 4 of these with intention to replace my 3 AC AP's in my big old chicken-wire-walled house. but wireless has been a disappointnment:
I couldnt get radio2 working at all. i set up the 3 radios first with the same SSID, then with separate, to see if I could force a connection to radio2. no go.
compared to my AC accesspoints, both 2.4 and 5G rnage is limited.
as others have noted, frequent band switching attempts resulting in disconnects.
i've set up DAWN to manage the wireless connections, but the jury is still ut about efficacy.
FWIW - i've got wpad-mbedtls running so full capabilities should be there. i havent tried mesh since i couldt get radio2 to work. i've got WPA2/persona/SAE encryption on all radios, and 802.11r active.
any hints?
thx
Both 5ghz radios need to be set at certain channels and cannot support 160 mhz width or they'll both disable themselves is the behavior I saw.
2 Likes
Which build did you used?
radio0 is 2x2 lower channels.
radio1 is 2.4G
radio2 is 4x4 higher channels.
Your mesh back haul should be on radio2.
Would you mind sharing your .config for the mx4300 build with NSS and mesh support?
Hey man, thanks for clarifying which radio does what; that totally makes sense.
I'm using the following build: https://github.com/testuser7/openwrt/releases/tag/qualcommax-2540ea6
for radio0 and radio2, should I set it to the same SSID or use different SSIDs?
@qosmio I can't find the .config seed file linked above. could you please post again? I assume your branch has additional fixes compared to the build posted by @lytr. Reason I am chasing this is because Mesh for me is quite unstable and I can only get the Mesh to work on channel 161 and it's been flakey (with @lytr's build posted above). I was about to rebuild from your branch (since you mentioned you have 5 of these in a mesh working flawlessly) but looking for the .config seed file so I don't have to reinvent the wheel. thanks much.