🌟 Support for RT-AX58U V2 🌟 #550
Comments
|
looking for pre-alpha testers. |
|
Pre-alpha available here <REMOVED_ BROKEN_IMAGE> |
|
I just got a RT-AX3000, and it's a V2. :( I was hoping to get it working with Merlin, but I guess it's not ready yet. That being said, I'd be willing to be an alpha tester. |
|
I flashed the image before you removed the link and bricked my router 😅. I was able to flash back a stock firmware, so I'm ready for testing future builds! |
|
@Souler those are soft bricks something you can quickly recover.. :D |
How do I download the alpha firmware? |
|
Hi @Stellar1616 the alpha is not out yet. There was a pre-alpha but it was not booting. |
|
New pre-alpha image available Link to image: |
|
Link is broken
Neil
Sent with Spark
…On 24 Mar 2024 at 14:51 +0800, Antonio Aloisio ***@***.***>, wrote:
New pre-alpha image available
Version: pre-alpha-2
Risk: HIGH - This image has not been tested so worst case scenario your router won't start anymore and ASUS restoration tool is required. So before flashing this make sure you have a copy of the latest stock firmware.
Link to image:
https://github.com/gnuton/asuswrt-merlin.ng/actions/runs/8403778904/artifacts/1352759145
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
@neil1962 -_- the link works for me. Are you logged in github when downloading? |
|
The pre-alpha seems to boot. So it should work now. |
|
It says at the top that the stable has been released, but I'm not showing the V2 listed as a supported model on https://www.asuswrt-merlin.net/about and on the download page on source forge, I'm only showing an entry for RT-AX58U, doesn't specify a hardware version https://sourceforge.net/projects/asuswrt-merlin/files/RT-AX58U/ |
It's a GNUton build, available from here - |
|
I was pleased to find support for the AX58U V2 model and all seemed well but I cannot get the VPN tunnel to block devices when it goes down. I have checked the VPN director and all seems okay. I can connect to my VPN but when I disconnect it, my devices revert to WAN which is why I wanted to use the kill switch. Any idea why this is occurring? Thanks Aidan |
|
I tried thanks for the big effort man |
|
Hi, I'm really happy that this router is supported, however, it has the exact same damn bug as the original Asus code, which is that you cannot disable Roaming Assistant. The setting in the GUI does not work, as soon as a wifi client reaches -68 -69 -70 RSSI, it gives the device a swift cold hard kick off the wifi. Being as this is the only router and I don't have multiple of these, as assumed by Asus and their AiMesh (reason this feature exists), so the client device keeps attempting to reconnect. The device usually initially will report to the router it has -40 or -50 RSSI (smart bulbs with no antennas). Router reassess the RSSI within several seconds and gives another hard kick. Over and over and over. IF I enable Roaming Assistant (Professional tab of wifi) for 2.4Ghz and give it a value of -90 (max) or anything else that I wish, save the settings, and then reboot (or unplug), the result is the same. The roaming assistant MUST be using a hard coded default variable number of -70 somewhere. I know next to nothing about this programming language or I'd trying to help find it. Further, I found a settings page called "Roaming Block List" (should be called Roaming Exclusions List but ok lost in translation....) which promises to exclude devices from the roamast script that kicks devices off the network to encourage them to roam to a closer AP. This setting..... does not work. Not even after pulling the power and reconnecting. Of course not, because Asus is incompetent (as someone else said) Again, this is a bug in the original Asus code, and it exists also in this firmware. I was hoping you all caught it and fixed it. This is severely impacting my network and it explains everything that is wrong with my smart home devices, including my doorbell camera. I only have two devices outside, but naturally they will have a weaker signal that is unfortunately in the -70s, and that's normal. I don't have a ethernet connected apartment, or I would buy another router and do as Asus wants. I really don't like it when companies force things on us that we don't won't. In the rush for "AiMesh" and Ai everything, Asus was in too big of a hurry and didn't link the actually systemd script variables that runs the wifi roaming assistant to the user GUI, or whatever it is (assuming this is Linux). This has taken me hours upon hours to diagnose over many days (thanks Asus) and I'm hoping this team can help me fix the problem until Asus does. I also have suggestions regarding the roaming assistant:
EDIT! 100% Confirmed: Upon DISABLING Roaming Assistant and then watching the log, it shows the wifi restarting, devices reauthenticating, then, Roamast starts up and starts selecting it's victims: "Aug 24 07:05:11 roamast: ROAMING Start... God damn you Asus and your bugs! . |
|
Another Bug: Checking the lights in question, YUP ANOTHER GD BUG by Asus. Trying to control that light which was connected less than an hour ago (remember I just rebooted the wifi and also power cycled the router so many times in the last 2 hours), Google says "Sorry it looks like Dining Light 2 isn't available right now" God fuck. I never want my router to kick off a device because it's sleeping or otherwise inactive. WTF Asus. I don't want these Mesh features. I want a normal fucking router that leaves my devices alone and lets them be. |
*This thread is about supporting RT-AX58U V2.
If you see this issue here is because I have decided to support this model.
So, feel free to ask questions here about this topic.
I will keep the status updated.
Status:
The text was updated successfully, but these errors were encountered: