Release [Fork] Asuswrt-Merlin 374.43 LTS releases (V44EA)

djphilosophy

Occasional Visitor
I have an RT-N66U running this latest version (V44EA) in AP mode. I remember setting the IP to 192.168.101.2 (router on 101.1), and the primary router shows the N66U at this address. Everything works fine, except ... I can no longer access the admin page at the assigned IP address.

I've tried:
  • Connecting both via http and https
  • Connecting directly via LAN port
  • Disconnecting WAN cable, setting PC manual IP to 192.168.0.3 assuming N66U at 192.168.0.1
  • Same as above with 192.168.1.3 to 192.168.1.1
What's strange is I could swear I remember accessing the admin page after putting it into AP mode when first setting it up a few weeks ago. I know I can just reset the router to regain access, but obviously I'm trying to avoid that given everything is working - plus this has me wondering if this is a bug or by design.

Is there a way to access the admin page while in AP mode? A default IP address it takes if it isn't assigned one?
 

djphilosophy

Occasional Visitor
@djphilosophy Download the ASUS Device Discovery utility and see if that can find it.

Thanks for the reply. It finds it at 192.168.101.2 as well. If I click configure there it attempts to load the webpage, which gives the error "refused to connect" (same as before - should have mentioned that).

Worth adding that I've attempted access on both Linux and now Windows (after running the Device Discovery app just now), so it's not an OS/firewall issue.

Edit: Also tried unplugging the WAN cable, rebooting and running Device Discovery again. Same IP, still no access.
 
Last edited:

ColinTaylor

Part of the Furniture
Thanks for the reply. It finds it at 192.168.101.2 as well. If I click configure there it attempts to load the webpage, which gives the error "refused to connect" (same as before - should have mentioned that).

Worth adding that I've attempted access on both Linux and now Windows (after running the Device Discovery app just now), so it's not an OS/firewall issue.
You didn't setup any access control by IP for the web interface did you?

The obvious question: have you rebooted it?

Did you ever enable Telnet or SSH access on it? If so try connecting with that.

Otherwise I think by now I would have just factory reset it and be done with it. :)

EDIT: Did you remember to include the default port on the HTTPS connection attempt? e.g. https://192.168.101.2:8443/
 
Last edited:

djphilosophy

Occasional Visitor
Otherwise I think by now I would have just factory reset it and be done with it. :)
I had faith that someone smarter than me would think of why I can't access it when we know it's there. :)

EDIT: Did you remember to include the default port on the HTTPS connection attempt? e.g. https://192.168.101.2:8443/
That was it! Adding port 8443. HTTP access was disabled - which I've now changed so it won't happen again - and port 443 is reserved for Cloud Disk, which I'm guessing wasn't loading because it's in AP mode.

Thank you very much for your help! :)
 

bright357

New Around Here
@john9527,Can you add RT-AC56S firmware support in the next new firmware release? RT-AC56S (single core) same as RT-AC56U(dual core).

Thank you very much!
 

arovik

New Around Here
Hi. Im currently on 3.0.0.4.382_52287 for AC66U. Does that mean that this fork is based on a very much older asus firmware than the newest?
 

thelonelycoder

Part of the Furniture

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top