You spin lies as badly as a U.S. politician. Your expertise was invaluable but you were a pompous a*hole about it. No sense of a community effort trying to push this through and deflecting about the question in the prior post about “your patch” and testing. @RolandoMagico moved to an MR8300 - he does not have a device to test.
I have a device and at this point in time, I’m the only one who tested the updated code and the binary build on a an MR6350. I also submitted a second PR after:
Reaching out to @RolandoMagico by email and being told that he did not plan to submit.
Actually testing the code.
I sure you did not review my PR, submitted by email and rejected due to @RolandoMagico existing PR, but I referenced this thread and specifically credited @rwl408, @RolandoMagico and even you. It contained “your patch” verbatim after I had reviewed it, compiled it and tested the binary.
I was amazed to see that after my PR, “busy”@RolandoMagico suddenly found time to start working on his PR - never mind that he told me, in the email and elsewhere, that he no longer had the device and the time to work on it.
Several years ago, I participated in the forum and submitted two devices to the project; Trendnet TEW-810 and the Linksys EA7300v2. I migrated ISP’s and confirmation emails to login were rejected by my ISP. With help from the forum moderators, I managed to regain forum access after several years.
I may be out of step with the forum ethos, but I have never seen so many arrogant, out-of-context, off-topic, knee jerk replies without a moderator stepping in.
I just wonder why you all try to use some 22.03 build from unknown source, or random MR8300 builds, when is actually hosting a verifiable build of 23.05 (as he includes the source patch used to create it!) on his GitHub account.
I confirmed that the custom 23.05 build by @RolandoMagico is working OK & able to serve as an Intermediate firmware should Snapshot build / 24.10.y release build come out later.
I was amazed to see that after my PR, “busy”@RolandoMagico suddenly found time to start working on his PR - never mind that he told me, in the email and elsewhere, that he no longer had the device and the time to work on it.
I received email notification on the Github update too. However, maybe when @robimarko posted an update yesterday to ping @RolandoMagico to rebase and commit, the timing was after the reply to your email.
Given the opportunity to close the long pending issue, I am sure @RolandoMagico wanted to finish it asap. The fact that another enquiry came up afterward was probably frustrating. In any case, let’s hope no more surprises going forward.
The weekend came and went, and at the time of this post, there has been no action after @RolandoMagico asked the project to merge the submitted patch and pushing it again. I think it would be helpful to the community to update the install procedure to OEM forced flash of the custom OEM 23.05 build with a link to the URL.
I will add the OEM forced flash to my submission but won’t send unless contacted by the project. I’m sending an email to the project suggesting they set a time limit for @RolandoMagico PR.
This is tantamount to sitting on the communal toilet and not leaving. The delay has had consequences for others. My Dad, a former Navy Pilot, had a saying: “Sometimes you got to go or get off the pot.”
Not sure if it works that way. But setting up a new MR6350 Wiki page is not a bad idea. We can borrow many common info from the page of either MR8300 or EA6350 v3.
I can try to create & setup the new Wiki page if you want.
I think it would be helpful but would not invest your time until it’s committed. I’m also not sure it’s entirely my call but I support accurate, concise information. I’ll share what I’ve done so far. Probably easiest to paste the *.txt file once after it’s committed.
I pasted my mr6350_openwrt_bootlog.txt into 2 PM’s - the log line count exceed the line limit. With an eye toward saving server space, I’ll delete the posts either when they show up on the wiki or if you let me know you can’t use them.
Good news! Official support has just been merged to Main Snapshot branch. Thanks to @RolandoMagico and others who have contributed to make it happen! I updated the Draft Wiki page accordingly.
Watch out for Linksys MR6350 build in Snapshot branch in the next few days.
Wow! I step away for just a few weeks for personal reasons, and when I come back, I find all this great news! I am sincerely grateful to EVERYONE who helped make this happen. Among them, one of the most important is @RolandoMagico.
Can you try to flash the official snapshot images [via firmware selector portal] and re-produce the problem on it?
Now that both OpenWRT system & add-on packages are from official sources any support issue can be debugged in the same environment as the developers are using.
There is actually no problem. luci-app-advanced-reboot needs to add a *json entry of the device in build code to support this new dual-boot device and requests the output of 3 files from a running device. I took care of it and was just trying to avoid having someone else repeating what has already been done.
Without flow offloading, the speed would be reduced a bit.
If you do not use SQM or QoS, then I say go and turn on Hardware flow offloading.
If you only use MR6350 as WiFi AP only, then it does not matter as it’s not a NAT device.
