ai-mesh compatibility issue between ac3100(20379) & AC68U(20624)

[indark]

To start, it's not a TM-AC1900 convert

my setup is ac3100 as main router, first gen ac68u as node.

ac3100 firmware version 384_20379, ac68u uses 384.20308 n 384.20624

here are things I have tried out so far.
1. try to establish ai-mesh with ac68u on 384.20624
reset both router many time and tried
it is unable to find potential ai-mesh node .

2. try to establish ai-mesh with ac68u on 384.20308 then update the firmware via aimesh
it's effortless to find ac68u and establish the ai-mesh
However, here comes the fun part,
After I push the update via firmware updating menu
the node is now listed offline
if I navigate to the firmware update menu, it will instantly trigger the firmware is upgrading dialogue just like what happen couple firmware back.

when I navigate to syslog, I get the kernel: dump console message

Mar 29 08:06:59 kernel: DUMP CONSOLE: F: tid 4 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047500.929 wl1.0: wlc_send_bar: seq 0x152 tid 4
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047504.094 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047513.418 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 4 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047523.657 wl1.0: wlc_send_bar: seq 0x154 tid 4
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047531.319 wl1.0: wlc_send_bar: seq 0x7c tid 1
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047532.298 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 4 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047541.430 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 1 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047554.134 wl1.0: wlc_send_bar: seq 0x158 tid 4
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047560.102 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 4 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047566.350 wl1.0: wlc_send_bar: seq 0x52 tid 2
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047568.562 wl1.0: wlc_send_bar: seq 0x164 tid 4
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047578.760 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047578.760 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 4 initiator 0 reason 39
Mar 29 08:06:59 kernel: DUMP CONSOLE: 047580.437 wl1.0: wlc_send_bar: seq 0x81 tid 1
Mar 29 08:06:59 kernel: dhdpcie_checkdied: msgtrace address : 0x00000000
Mar 29 08:06:59 kernel: console address  : 0x003FFCF0
Mar 29 08:06:59 kernel: Assrt not built in dongle
Mar 29 08:06:59 kernel: TRAP type 0x4 @ epc 0x2657a8, cpsr 0x68000193, spsr 0x68000033, sp 0x2ac7c4, lp 0x24f789, rpc 0x2657a8
Mar 29 08:06:59 kernel: Trap offset 0x2ac76c, r0 0x3e4678, r1 0x0, r2 0x0, r3 0x339c00, r4 0xb9d8f205, r5 0x3bdba4, r6 0x3b9828, r7 0x2ac880

I released the node but it seems that it's not properly reset as I am unable to find it via wifi.
have to physically reset it

now back to mediabridge mode
------------------------------------------------------------------------------------------------------------
update:
interesting result that I actually get it to work now.

sum up on the test I have done so far.
1 ac3100 @ 20379, ac68u @ 20624 (tried couple times, repeatable)
unable to find ac68u and it takes forever for spinning circle on search for nodes.

2. ac3100 @ 20379, ac68u @ 20308 (tried couple times, repeatable)
find the node and established without issue.

3. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried once)
via the firmware upgrade button, it updates, but the node will show offline and have kernel dump.
and it trigger infinite loop on the firmware is updating dialogue when navigate to the firmware page

4. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried few times)
instead of using the firmware upgrade button, I decided to manually upload the firmwae to ac68u only.
surprising enough that everything works normally, no issue with ai-mesh, no infinite firmware updating page nor the kernel dump.
View attachment 12531
also noticed that I have signature version @ 2062 this time instead of 2060.

For now, I will leave it as is to see if I encounter any more issue next few days.

 

[Sammy2]

So, in short, you're experiencing issues with the upgraded f/w on a native RT-AC68U?

I have this set up with an RT-AC3100, native RT-AC68U and two converted TM-AC1900's and it is working.

I haven't upgraded any f/w.



Sent from my SM-G930P using Tapatalk

 

[indark]

nah, i think it's more like the compatibility between older ai-mesh code with new ai-mesh code

and it is fine to get ai-mesh working by simply revert the firmware back to 20308.

and
asus's reply on amazon regardin people with issue on TM-AC1900

it's not really trojan attack when you are trying to load it on something that's not supported.
TM-AC1900 is T-mobile branded with T-mobile custom firmware that should be supported by T-mobile.
people who bought TM-AC1900 should be aware of the risk they are taking when trying to mod the router.

 

[Sammy2]

Shouldn't the f/w work with other routers though? There's been no update to the f/w for my RT-AC3100 and I have an RT-AC68U that I bought in 2013 for 200 some odd bucks. The f/w was updated for improved AiMesh functioning so to speak for this router yet it seems that that is really not the case at all. Your's is not the only report of issues with AiMesh on this router but it is the closest to my set up in that I have the RT-AC3100 as the main router. Currently, I have upgraded non of the firmware. As usually, I don't jump on f/w updates right when they're released and have learned over the years to go check before messing with a perfectly working system.. There's some issues with AiMesh on even my native router with it dropping clients so I may go back to another topology of Wired AP's and Wireless Repeaters anyhow and see how that works out.

 

[Sammy2]

@indark
Did you do a reset of the node to see if it comes back on line? This seems to be yet one more reason not to update the f/w for me as I have the same setup as you for the most part.

 

[indark]

it's always better to wait few days before you apply updates as there is always risk with changes.
it's not much of hassle for me as I like to play with it and it's simply resolved by loading previous firmware.

as long as it's working and no security issue, you dont need to update.
and the security supposed to be handled by main ai-mesh router.

So far I haven't find any real benefit to use ai-mesh over mediabridge for my setup.
It's more or less a fun project to try on with extra coverage to my yards ;p

I did reset the node, and as long as it's 20308, it can be found and connect to ai-mesh.
And if aimesh is setup with 20308 then upgrade to 20624, I can see that the node is trying but fail to establish the link
So I think there is some compatibility issue with newer ai-mesh code.

 

[Sammy2]

I find it interesting that your OEM router will not show up as an AiMesh node with this f/w.

Like you say, if it works and there's no security threat, why worry.. That said, I'm still testing out how well the AiMesh works. So far pretty good but for whatever reason, the TV and Ceton Echo connected via Ethernet to the OEM router in AiMesh mode keeps dropping the signal (actually it doesn't show it is connected to the AiMesh Node but rather shows up in the Main Router as a wired device which is misleading at best) so I'm not sure it is working all that well.. I may make this a Media Bridge at this location with one of the TM units and then use this OEM in AiMesh at another location. The other TM unit can also be a media bridge for that matter as that is what it is doing basically now in AiMesh mode.

 

[Sammy2]

nah, i think it's more like the compatibility between older ai-mesh code with new ai-mesh code

and it is fine to get ai-mesh working by simply revert the firmware back to 20308.

and
asus's reply on amazon regardin people with issue on TM-AC1900
View attachment 12521
it's not really trojan attack when you are trying to load it on something that's not supported.
TM-AC1900 is T-mobile branded with T-mobile custom firmware that should be supported by T-mobile.
people who bought TM-AC1900 should be aware of the risk they are taking when trying to mod the router.

I searched amazon for that review but couldn't find it. Is there a way to link it?

Thanks.

 

[indark]

I find it interesting that your OEM router will not show up as an AiMesh node with this f/w.
Like you say, if it works and there's no security threat, why worry.. That said, I'm still testing out how well the AiMesh works. So far pretty good but for whatever reason, the TV and Ceton Echo connected via Ethernet to the OEM router in AiMesh mode keeps dropping the signal (actually it doesn't show it is connected to the AiMesh Node but rather shows up in the Main Router as a wired device which is misleading at best) so I'm not sure it is working all that well.. I may make this a Media Bridge at this location with one of the TM units and then use this OEM in AiMesh at another location. The other TM unit can also be a media bridge for that matter as that is what it is doing basically now in AiMesh mode.

It's more of minor bug that they need to fix due to the wide range devices and I guess some fragmentation in the ai-mesh firmware.
the combination of the devices is just crazy so it's understandable that Asus tighten the support on what they actually can and want to support.
the patch notes says improve ai-mesh compatibility, so i assumed something changes.
It is probably how router handshake the connection
mesh node setup will stay when update from 20308 to 20624; can see it's trying to establish connection but fail.

if you need the range, repeater mode can do that, maybe some lower speed?
But for me, ac3100 is more than enough cover my 3 stroeis and part of my yards, so media bridge for my ps4

it's unfortunate that I can not link the specific review from amazon,
it's one of the 3 stars review,

It was my conclusion back when ac68u still costly and hacking TM-1900AC was tempting.
So I never bother to take the chance.
And now there are alternative like refurb ac1900 or new ac66u b1, why bother with something that's not new nor ever supported by Asus.

 

[Sammy2]

Newegg had refub RT-AC68U's for $95 the other day..

 

[indark]

Newegg had refub RT-AC68U's for $95 the other day..

https://www.newegg.com/Product/Product.aspx?Item=N82E16833320329
asus certifed refurb RT-AC1900 is 75 + tax (depends on your state) with free shipping

ac66u b1, however, as someone pointed out, not officially list, so I cant be sure even if it does have aimesh on my uncle's comupter

 

[Sammy2]

BTW, they have a refurbished RT-AC1900P for $75 . Does that do AiMesh and what's the difference between it and a RT-AC68U?

 

[indark]

BTW, they have a refurbished RT-AC1900P for $75 . Does that do AiMesh and what's the difference between it and a RT-AC68U?

It should as it's an actual asus product and listed under the official page. it's basically hardware difference, say hardware revision?
here is people created for quick reference
https://www.snbforums.com/threads/rt-ac68u-rt-ac68p-rt-ac1900-rt-ac1900p.35759/

 

[Sammy2]

Read the review too. Basically the same thing. I may just grab one or two of these..

 

[indark]

Read the review too. Basically the same thing. I may just grab one or two of these..

i am actually gonna wait and see what new RT-AX series router have to bring to the table before I replace my 68u ;p
it's gonna be a long wait though

but anyway, back to original topic, I decided to reset my main aimesh router (ac3100) without remove the node (ac68u) after firmware update(20308 to 20624)
I see the SSID from factory reset ac3100 - ASUS_30, ASUS_30_5G ( i think that's the name) and also the boardcast of the SSID that I uses
assuming it's from ac68u,

I did not have much time to test if a reboot on ac68u will fix the issue, only tried to reboot ac3100.
I will try more things tonight when families dont need network.

 

[Sammy2]

i am actually gonna wait and see what new RT-AX series router have to bring to the table before I replace my 68u ;p
it's gonna be a long wait though

but anyway, back to original topic, I decided to reset my main aimesh router (ac3100) without remove the node (ac68u) after firmware update(20308 to 20624)
I see the SSID from factory reset ac3100 - ASUS_30, ASUS_30_5G ( i think that's the name) and also the boardcast of the SSID that I uses
assuming it's from ac68u,

I did not have much time to test if a reboot on ac68u will fix the issue, only tried to reboot ac3100.
I will try more things tonight when families dont need network.

So you have 4 different SSID's now and it is in AiMesh mode?

usually when I do a reset, I restore my settings from a saved file as I probably have 15 to 20 ports for various things to "talk" to the internet in addition to having static IP's for most devices. Re-doing that all is a pain. When I went from a single RT-AC68U to AiMesh with the RT-AC3100 as the main, I kept my same SSDI's so I didn't have to reconfigure a bunch of devices either.

Agree on the family thing. I'm always having to do this in the early morning..

 

[indark]

interesting result that I actually get it to work now.

sum up on the test I have done so far.
1 ac3100 @ 20379, ac68u @ 20624 (tried couple times, repeatable)
unable to find ac68u and it takes forever for spinning circle on search for nodes.

2. ac3100 @ 20379, ac68u @ 20308 (tried couple times, repeatable)
find the node and established without issue.

3. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried once)
via the firmware upgrade button, it updates, but the node will show offline and have kernel dump.
and it trigger infinite loop on the firmware is updating dialogue when navigate to the firmware page

4. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried once)
instead of using the firmware upgrade button, I decided to manually upload the firmwae to ac68u only.
surprising enough that everything works normally, no issue with ai-mesh, no infinite firmware updating page nor the kernel dump.

also noticed that I have signature version @ 2062 this time instead of 2060.

For now, I will leave it as is to see if I encounter any more issue next few days.

 

[bbunge]

https://www.newegg.com/Product/Product.aspx?Item=N82E16833320329
asus certifed refurb RT-AC1900 is 75 + tax (depends on your state) with free shipping

ac66u b1, however, as someone pointed out, not officially list, so I cant be sure even if it does have aimesh on my uncle's comupter

RT-AC66U-B1 does support Aimesh. Mine runs the latest firmware just fine!

Sent from my P01M using Tapatalk

 

[Sammy2]

To get this straight, the only way the f/w update allowed your RT-AC68U yo be seen as a node is if you took it off line, reset it, plugged it into a pc or laptop with an Ethernet cable, went to the GUI, updated the f/w from there then told it to be am AiMesh node?

Just trying to understand how you did this manually.

Thanks

Sent from my SM-G930P using Tapatalk

 

[Sammy2]

interesting result that I actually get it to work now.

sum up on the test I have done so far.
1 ac3100 @ 20379, ac68u @ 20624 (tried couple times, repeatable)
unable to find ac68u and it takes forever for spinning circle on search for nodes.

2. ac3100 @ 20379, ac68u @ 20308 (tried couple times, repeatable)
find the node and established without issue.

3. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried once)
via the firmware upgrade button, it updates, but the node will show offline and have kernel dump.
and it trigger infinite loop on the firmware is updating dialogue when navigate to the firmware page

4. ac3100 @ 20379, ac68u @ 20624 after establish ai-mesh with 20308 (tried once)
instead of using the firmware upgrade button, I decided to manually upload the firmwae to ac68u only.
surprising enough that everything works normally, no issue with ai-mesh, no infinite firmware updating page nor the kernel dump.
View attachment 12531
also noticed that I have signature version @ 2062 this time instead of 2060.

For now, I will leave it as is to see if I encounter any more issue next few days.

To get this straight, the only way the f/w update allowed your RT-AC68U yo be seen as a node is if you took it off line, reset it, plugged it into a pc or laptop with an Ethernet cable, went to the GUI, updated the f/w from there then told it to be am AiMesh node?

Just trying to understand how you did this manually.

Thanks

Sent from my SM-G930P using Tapatalk