RT-AC68U - 384.12 - 0 Clients in Network Map?

[AztecPyramid]

For some reason, I can't see any clients when I log into the admin page Network Map.

0 Clients. Firmware Version: 384.12

Has anyone experienced this?

Thanks,

 

[RMerlin]

Do you have a real, genuine RT-AC68U? if not, please read the sticky posts in this forum.

 

[AztecPyramid]

Do you have a real, genuine RT-AC68U? if not, please read the sticky posts in this forum.

I don't, I have a t mobile one. It's just that it always works great. Thanks

 

[Salles]

I don't, I have a t mobile one. It's just that it always works great. Thanks

The network map behaves strangely sometimes for supported devices. This is an issue that only Asus can fix.

For unsupported devices I have no idea. Please read the FAQ before posting.
https://www.snbforums.com/threads/the-tm-ac1900-is-not-supported.48056/

 

[JemTheWire]

Doesn’t now. [emoji3]

 

[Striker317]

For some reason, I can't see any clients when I log into the admin page Network Map.

0 Clients. Firmware Version: 384.12

Has anyone experienced this?

Thanks,

Since you didn’t read the pinned post, here’s the link

THE TM-AC1900 IS NOT SUPPORTED
https://www.snbforums.com/threads/the-tm-ac1900-is-not-supported.48056/

If you read the pinned post and ignored it, I’m not apologizing for accusing you of not reading it.

 

[AztecPyramid]

@Striker317 , I did not read it. I wonder why it is that the ac1900 is not supported. Why the hate?

 

[skeal]

@Striker317 , I did not read it. I wonder why it is that the ac1900 is not supported. Why the hate?

Because it is illegal. The router is not an Asus product despite the hardware. It was designed for the ISP specifically with no further support intended or promised.

 

[AztecPyramid]

Illegal? Sounds dramatic. Who broke the law?

 

[skeal]

Illegal? Sounds dramatic. Who broke the law?

Anyone who hacks the router you have to run this firmware, is breaking the law.

 

[dave14305]

The wording of the sticky posts says the TM-AC1900 is not supported, without mentioning illegality.

The illegal sticky refers to forks running on non-Asus hardware. Not sure if the TM-AC1900 technically falls in that camp. I assume it’s aimed at the NETGEAR Vortex crowd, primarily.

Either way, it’s a no-go on this forum.

 

[RMerlin]

That model is cheaper for a reason - it isn't covered by the licence for Trend Micro's engine. Running an unlicensed proprietary engine on it is the part that's illegal, and Asus have taken steps to prevent people from breaking the licensing agreement, by actively preventing flashing a non-authorized firmware.

 

[Holanos]

That model is cheaper for a reason - it isn't covered by the licence for Trend Micro's engine. Running an unlicensed proprietary engine on it is the part that's illegal, and Asus have taken steps to prevent people from breaking the licensing agreement, by actively preventing flashing a non-authorized firmware.

Ahhh.. I see and understand now. I had the router second hand and didn't know that it was flashed so I updated the firmware. Any way for me to revert back to an earlier version by any chance? I thought I had a non-t-mobile one because I only looked in the config gui, not the actual router (someone on this site helped me identify the difference...and yup... )

 

[ColinTaylor]

Any way for me to revert back to an earlier version by any chance?

I see from your other post that you have been able to revert your firmware. Just mentioning that here so people don't waste their time responding to this post.

 

[AztecPyramid]

Hello,

If anyone still has this issue, I just wanted to let everyone know that after all this time I fixed this by:

1. Backing up my configuration file
2. Flashing the router with the latest ASUS firmware
3. Restoring the router with the "initialize all the settings ..." flag checked.
4. Flashing the router with the latest AsusWrt-Merlin version: 3.84.17
5. Restoring my settings file

That did it for me. Now I am able to see all the connected devices once again and enjoying the full capabilities of this awesome Asuswrt-Merlin firmware. By the way, that is the only thing that broke for some reason. The rest of the functionality was intact, thank you,

 

[jpthsd]

Hello,

If anyone still has this issue, I just wanted to let everyone know that after all this time I fixed this by:

1. Backing up my configuration file
2. Flashing the router with the latest ASUS firmware
3. Restoring the router with the "initialize all the settings ..." flag checked.
4. Flashing the router with the latest AsusWrt-Merlin version: 3.84.17
5. Restoring my settings file

That did it for me, thank you,

I don't think anyone might answer you last post here, I am new here but try to answer to you if benefit you . Basically you if you restore the settings file from previous, sometimes later it will come back and haunt your router for sure. As being said, the TM-AC1900 is not supported by Asusrwt Merlin period. if you insist to do what you were trying to do, no one would stop you but no support I guess

My 2c!

 

[AztecPyramid]

Doesn’t now. [emoji3]

well, it does now. I fixed it.

 

[jimtale]

well, it does now. I fixed it.

How did you restore to stock firmware, with Asus FW restoration tool ? The reason I ask is because I uploaded stock firmware and it wouldn't upgrade, still stayed on Merline 384.18. Thanks !

 

[AztecPyramid]

How did you restore to stock firmware, with Asus FW restoration tool ? The reason I ask is because I uploaded stock firmware and it wouldn't upgrade, still stayed on Merline 384.18. Thanks !

I just updated it with the latest stock firmware by uploading the file. Nothing special.