Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

Calkulin

Regular Contributor
@ASUSWRT_2020

I understand its a RC firmware version, but please stop the endless queries to dns.msftncsi.com, for me, they are averaging around 2 thousand queries per day for each node. It's ridiculous, the setting under system, administration, dns query, does not work, i.e. disabled. Why? Maybe this setting is not been passed to the nodes from the main router? Stop it, please. Even my windows 10 PC does not misbehave like this.

This in not the first time I have reported this in the same forum. And month’s later it’s still an issue.


That is not new to the 386 code, so complaining like that isn't going to get you very far. But I will say I've seen that behaviour for a long time and resolved it by enabling DNS Query and blanking out the hostname and IP address sections then applying the changes. Then I unchecked DNS Query and applied again.
 

mbze430

Regular Contributor
anyone know if I change the power output on the main router does it also change the power output on the node? or the nodes are always 100%? anyway to change the node power output?

Trying to figure out a better way to roam. Because right now all my wireless device is stuck to one node. even though some of those devices is closer to the main router and the devices that is stuck to them is across the house. the router is in the basement and the node is the main floor. but they are opposite of each other at the end of the house.
 

L&LD

Part of the Furniture
No, that would not make sense for it to do that.

Move the nodes further, if possible. (Think outside the box). :)
 

L&LD

Part of the Furniture
Maybe too much Wi-Fi hour the available area?
 

Mason

New Around Here
@ASUSWRT_2020

I understand its a RC firmware version, but please stop the endless queries to dns.msftncsi.com, for me, they are averaging around 2 thousand queries per day for each node. It's ridiculous, the setting under system, administration, dns query, does not work, i.e. disabled. Why? Maybe this setting is not been passed to the nodes from the main router? Stop it, please. Even my windows 10 PC does not misbehave like this.

This in not the first time I have reported this in the same forum. And month’s later it’s still an issue.
https://www.reddit.com/r/pihole/comments/edvpkn
 

alba666

Occasional Visitor
Maybe too much Wi-Fi hour the available area?
I have my old AC88 node powered down for this reason. Only turn it on once in a blue moon when we need back patio coverage. Otherwise, I have the coverage I need with the single AX92.

Hint: Play with router location. I was able to get by with one device by getting the AX92 off the outside wall where the Xfinity coax is located. An APC UPS against a wall makes a great stand for the AX92 and a cable modem. Power and coax behind couch and it was GTG.
 

Neil62

Senior Member
@Neil62 does it behave like that after a full reset to factory defaults? Without using a saved backup config file?
Thanks for the reply but unfortunately it does, I always do a full reset, when applying new firmware.
 

Neil62

Senior Member
That is not new to the 386 code, so complaining like that isn't going to get you very far. But I will say I've seen that behaviour for a long time and resolved it by enabling DNS Query and blanking out the hostname and IP address sections then applying the changes. Then I unchecked DNS Query and applied again.
Thanks for reply but I have tried that tip, and a makes no difference, I think this setting is maybe not being passed down to the nodes. Strangely though on using using Merlins 386 latest beta firmware, its all good.
 

benganb

Occasional Visitor
Thanks for reply but I have tried that tip, and a makes no difference, I think this setting is maybe not being passed down to the nodes. Strangely though on using using Merlins 386 latest beta firmware, its all good.

Whats the difference of this 386-rc2-public-beta and Merlins beta firmware?
Iäm not happy with the stability of my system, AC86u as main with ethernet backhaul to AC68u as node.
 

Neil62

Senior Member
Whats the difference of this 386-rc2-public-beta and Merlins beta firmware?
Iäm not happy with the stability of my system, AC86u as main with ethernet backhaul to AC68u as node.
My whole setup is 100% ethernet (Cat 6). Just today (morning), I completed a total clean instal and manual rebuild, (the same process I use with an ASUS firmware install), to install Merlins 386.1 Beta 2 firmware, across the main and node routers, with the identical settings (using ASUS firmware), the problem I reported is gone. So go figure....it therefore suggests its not AiMesh related, as it is closed source code to Merlin. Thank you Merlin for your firmware...

@ASUSWRT_2020

Over to ASUS to fix the problem....
 
Last edited:

rlj2

Regular Contributor
I would clean install released Asuswrt on the 2xRT-AC86U wired AiMesh and see how that performs over several days... the longer the better. If that remains solid for your multi-day test period, then do similar to add one AC68U node. And again for the last AC68U node. And hope to narrow in on the issue.

OE
This one is confusing the hell out of me.
traceroute to google.com (216.58.192.174), 30 hops max, 60 byte packets
1 Asus (192.168.50.1) 0.912 ms 0.963 ms 0.918 ms <<<<<<<<<<<<Router
2 192.168.254.254 (192.168.254.254) 3.184 ms 3.172 ms 3.250 ms <<<<<<<<<<< Modem
3 50.121.102.1 (50.121.102.1) 2320.007 ms 2321.083 ms 2322.117 ms <<<<<<<<<<< <Gateway
4 ae13---100.car01.ftwy.in.frontiernet.net (74.42.112.109) 2329.525 ms 2331.322 ms 2330.708 ms
5 ae3---0.scr01.chcg.il.frontiernet.net (74.40.5.174) 2334.267 ms 2334.437 ms 2335.688 ms

Looking at that I would almost guarantee a modem/internet issue. BUT


traceroute to google.com (216.58.192.174), 30 hops max, 60 byte packets
1 Asus (192.168.50.1) 0.915 ms 1.181 ms 1.160 ms
2 192.168.254.254 (192.168.254.254) 2.547 ms 2.518 ms 2.505 ms
3 50.121.102.1 (50.121.102.1) 28.795 ms 31.327 ms 31.312 ms
4 ae13---100.car01.ftwy.in.frontiernet.net (74.42.112.109) 38.230 ms 37.737 ms 39.707 ms
5 ae3---0.scr01.chcg.il.frontiernet.net (74.40.5.174) 43.262 ms 43.248 ms 43.939 ms
6 ae0---0.cbr02.chcg.il.frontiernet.net (74.40.5.173) 44.055 ms 44.233 ms 44.130 ms

This is after I did nothing but walk around and shutoff the AIMESH nodes. Did not reboot main router, or modem. It also seems to happen overnight mostly. But I still cant see anything in logs. Theres nothing that runs in cru,etc
 
Last edited:

juched

Senior Member
This one is confusing the hell out of me.
traceroute to google.com (216.58.192.174), 30 hops max, 60 byte packets
1 Asus (192.168.50.1) 0.912 ms 0.963 ms 0.918 ms <<<<<<<<<<<<Router
2 192.168.254.254 (192.168.254.254) 3.184 ms 3.172 ms 3.250 ms <<<<<<<<<<< Modem
3 50.121.102.1 (50.121.102.1) 2320.007 ms 2321.083 ms 2322.117 ms <<<<<<<<<<< <Gateway
4 ae13---100.car01.ftwy.in.frontiernet.net (74.42.112.109) 2329.525 ms 2331.322 ms 2330.708 ms
5 ae3---0.scr01.chcg.il.frontiernet.net (74.40.5.174) 2334.267 ms 2334.437 ms 2335.688 ms

Looking at that I would almost guarantee a modem/internet issue. BUT


traceroute to google.com (216.58.192.174), 30 hops max, 60 byte packets
1 Asus (192.168.50.1) 0.915 ms 1.181 ms 1.160 ms
2 192.168.254.254 (192.168.254.254) 2.547 ms 2.518 ms 2.505 ms
3 50.121.102.1 (50.121.102.1) 28.795 ms 31.327 ms 31.312 ms
4 ae13---100.car01.ftwy.in.frontiernet.net (74.42.112.109) 38.230 ms 37.737 ms 39.707 ms
5 ae3---0.scr01.chcg.il.frontiernet.net (74.40.5.174) 43.262 ms 43.248 ms 43.939 ms
6 ae0---0.cbr02.chcg.il.frontiernet.net (74.40.5.173) 44.055 ms 44.233 ms 44.130 ms

This is after I did nothing but walk around and shutoff the AIMESH nodes. Did not reboot main router, or modem. It also seems to happen overnight mostly. But I still cant see anything in logs. Theres nothing that runs in cru,etc

Do you have a guest network enabled, and the option to sync it to all nodes? Try turning that to Router only and see if that stops the large delays.
 

mbze430

Regular Contributor
I have my old AC88 node powered down for this reason. Only turn it on once in a blue moon when we need back patio coverage. Otherwise, I have the coverage I need with the single AX92.

Hint: Play with router location. I was able to get by with one device by getting the AX92 off the outside wall where the Xfinity coax is located. An APC UPS against a wall makes a great stand for the AX92 and a cable modem. Power and coax behind couch and it was GTG.
My router is in the basement in my server room. So there isn't much to move around other then vertically. I have my router at the BOTTOM of the rack. Hence why there is a node at the main floor.

my basement is fully built so down there we need wifi coverage mainly for IoT devices like light switches and laundry machines, wifi frig, wifi water softeners...etc.... things that you can't wire up. Things that can is all wired.

then same goes for the main floor.
 
Last edited:

rlj2

Regular Contributor
Do you have a guest network enabled, and the option to sync it to all nodes? Try turning that to Router only and see if that stops the large delays.
no guest network.
 

MDK

Occasional Visitor
Hello,

when is this beta will be final release for AX GT11000, the AX88 has alot new firmware with more features..... ?

cheers
 

OzarkEdge

Part of the Furniture
Hello,

when is this beta will be final release for AX GT11000, the AX88 has alot new firmware with more features..... ?

cheers

When the beta test is over.

OE
 

MDK

Occasional Visitor
When the beta test is over.

OE


Thanks for the reply, thats not acurate as like i said alot of firmwares are available now for AX88 with new features..... and the GT gets none of them....

is this latest Beta ok to use on the GT11000 ? did not see major issues reported but could have missed it

cheers
 
Status
Not open for further replies.

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