What's new

RT-AC68U devices connected via AiMess showing incorrect device type icon

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Adrian Knight

Regular Contributor
Devices connected via an AiMess node showing incorrect device type icon (all showing as a repeater) in the client list and client status.

Current Version : 3.0.0.4.384_21045

UPDATE: I think that it maybe worth describing our setup, because the issue seems to be far more worse then 1st thought ...

90% of our network clients are bound via machine address (LAN / DHCP Server) even the AiMess nodes, I like the router at 254 and the AiMess nodes 253, 252 etc ...

We have a pool of 20 clients for our shop customers.

The devices connected via the AiMess nodes are having the device type icon updated in the DHCP settings, but this is only for devices which are using the default icon, wired and wireless VOIP devices are using our custom device type icon correctly, we use a custom device type icon for VOIP devices because the ASUS-WRT does not detect VOIP devices correctly.
 
Last edited:
Devices connected via an AiMess node showing incorrect device type icon (all showing as a repeater) in the client list and client status.

Current Version : 3.0.0.4.384_21045

Probably the least of the AiMess problems. :)

OE
 
I am new here, is this an official reply or just one you think they will say?

There are no official ASUS statements here. ASUS only collects user feedback here for their own purposes. You can trust they know their icons are not tidy.

OE
 
I am new here, is this an official reply or just one you think they will say?
just my personal opinion and what I saw in the past how lost you have been in their official asus-forum with not anyone ever seen from asus there, pure customer try to help others!
And here it is sayed to be a private forum with no advice of asus (but some strange things doesnt let me believe this independency).
At least here are some reading from asus and that let us hope things get better.
 
just my personal opinion and what I saw in the past how lost you have been in their official asus-forum with not anyone ever seen from asus there, pure customer try to help others!
And here it is sayed to be a private forum with no advice of asus (but some strange things doesnt let me believe this independency).
At least here are some reading from asus and that let us hope things get better.

That's ok then or I would have said, why don't you just go fully open source and stop using propriety bin blobs and allow descent coders like rmerlin to improve your platform.
 
Oh I see, Merlin supports AiMesh now :confused:
And there are so many open source for RT-AC86U :(

Please first think before writing ...
Most time I had Merlins, but all my problems are stock and merlin same!

yes Merlin adds some nice features, but he cannot solve one asus problem because of closed binarys.
 
Oh I see, Merlin supports AiMesh now :confused:
And there are so many open source for RT-AC86U :(

Please first think before writing ...
Most time I had Merlins, but all my problems are stock and merlin same!

yes Merlin adds some nice features, but he cannot solve one asus problem because of closed binarys.

That is exactly my point, if it was FULLY open source without propriety bin blobs, then rmerlin would stand a better chance to fix issues which affect the stock firmware, then Assus could steal them and add to stock.
 
That is exactly my point, if it was FULLY open source without propriety bin blobs, then rmerlin would stand a better chance to fix issues which affect the stock firmware, then Assus could steal them and add to stock.

sorry, than I completely misunderstood ...
 
Devices connected via an AiMess node showing incorrect device type icon (all showing as a repeater) in the client list and client status
Not with my system. I have correct device type icons for all my clients (10 to 15).
 
The only incorrect device types I've ever seen are those connecting to my Guest SSIDs. They all show as wired. I don't remember if that was the case before AiMesh, but no big deal and I'm sure it is a low priority.
 
Last edited:
Mr. Knight. I am going to step out on my shaky limb and comment on your deliberate wrong handed use of "AiMess" in lieu of the correct "AiMesh."
If you really feel that Asus is so bad that you need to run the company down, return them and get your money back or I'll trade your Asus Routers for a Netgear Orbi RBK50 system. Then you will have something to complain about!
 
If you can provide some information, such as screenshot ..etc, Maybe you can get some help from someone.
 
If you can provide some information, such as screenshot ..etc, Maybe you can get some help from someone.

Thank you for your attention, please see screen shot. If you need any further info other than what is posted in the OP and this screen shot, please let me know.

Screenshot 2018-06-04 08.57.03.png


Devices TECHNO-LAPTOP and GearS3-9246 connected via AiMess Master, device techno-voip connected to MASTER via wired, rest of the devices connected via AiMess node, device Galaxy-Tab-S2 customer device assigned from DHCP pool.
 
Last edited:

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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