[384.18_Alpha Builds] Testing all variants

[archiel]

@archiel use command

nvram show | grep -E 'territory_code|ccode|regrev|regulation|wl[0-9]_country|wl[0-9]_reg_mode|:max|wl[0-9]_chlist' | sort

This works where the router has a country code (AX88U)

admin@RT-AX88U-5050:/tmp/home/root# nvram show | grep -E 'territory_code|ccode|regrev|regulation|wl[0-9]_country|wl[0-9]
_reg_mode|:max|wl[0-9]_chlist' | sort
size: 69554 bytes (61518 left)
1:ccode=DE
1:maxp2ga0=0x6E
1:maxp2ga1=0x6E
1:maxp2ga2=0x6E
1:maxp2ga3=0x6E
1:regrev=963
2:ccode=DE
2:maxp5gb0a0=110
2:maxp5gb0a1=110
2:maxp5gb0a2=110
2:maxp5gb0a3=110
2:maxp5gb1a0=110
2:maxp5gb1a1=110
2:maxp5gb1a2=110
2:maxp5gb1a3=110
2:maxp5gb2a0=110
2:maxp5gb2a1=110
2:maxp5gb2a2=110
2:maxp5gb2a3=110
2:maxp5gb3a0=110
2:maxp5gb3a1=110
2:maxp5gb3a2=110
2:maxp5gb3a3=110
2:maxp5gb4a0=110
2:maxp5gb4a1=110
2:maxp5gb4a2=110
2:maxp5gb4a3=110
2:regrev=963
territory_code=UK/01
wl0_chlist=1 2 3 4 5 6 7 8 9 10 11 12 13
wl0_country_code=DE
wl0_country_rev=963
wl0_reg_mode=d
wl1_chlist=36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
wl1_country_code=DE
wl1_country_rev=963
wl1_reg_mode=h

but not where the country code is 'unknown' (AX58U)

admin@RT-AX58U-70F0:/tmp/home/root# nvram show | grep -E 'territory_code|ccode|regrev|regulation|wl[0-9]_country|wl[0-9]
_reg_mode|:max|wl[0-9]_chlist' | sort
size: 65094 bytes (65978 left)
0:ccode=E0
0:maxp2ga0=90
0:maxp2ga1=90
0:regrev=742
1:ccode=E0
1:maxp5gb0a0=110
1:maxp5gb0a1=110
1:maxp5gb0a2=110
1:maxp5gb0a3=110
1:maxp5gb1a0=110
1:maxp5gb1a1=110
1:maxp5gb1a2=110
1:maxp5gb1a3=110
1:maxp5gb2a0=110
1:maxp5gb2a1=110
1:maxp5gb2a2=110
1:maxp5gb2a3=110
1:maxp5gb3a0=110
1:maxp5gb3a1=110
1:maxp5gb3a2=110
1:maxp5gb3a3=110
1:maxp5gb4a0=110
1:maxp5gb4a1=110
1:maxp5gb4a2=110
1:maxp5gb4a3=110
1:regrev=742
territory_code=EU/01
wl0_country_code=E0
wl0_country_rev=742
wl0_reg_mode=off
wl1_country_code=E0
wl1_country_rev=742
wl1_reg_mode=h

 

[Ozymandias]

fwiw on AX56U (where I also have the 'unknown' country code)

nvram show | grep -E 'territory_code|ccode|regrev|regulation|wl[0-9]_country|wl[0-9]_reg_mode|maxp|wl[0-9]_chlist' | sort

sb/0/ccode=ALL
sb/0/maxp2ga0=0x72
sb/0/maxp2ga1=0x72
sb/0/regrev=0
sb/1/ccode=ALL
sb/1/maxp5gb0a0=0x72
sb/1/maxp5gb0a1=0x72
sb/1/maxp5gb1a0=0x72
sb/1/maxp5gb1a1=0x72
sb/1/maxp5gb2a0=0x72
sb/1/maxp5gb2a1=0x72
sb/1/maxp5gb3a0=0x72
sb/1/maxp5gb3a1=0x72
sb/1/maxp5gb4a0=0x72
sb/1/maxp5gb4a1=0x72
sb/1/regrev=0
territory_code=UK/01
wl0_chlist=1 2 3 4 5 6 7 8 9 10 11 12 13
wl0_country_code=E0
wl0_country_rev=741
wl0_reg_mode=d
wl1_chlist=36 40 44 48 52 56 60 64 100 104 108 112 116 132 136 140
wl1_country_code=E0
wl1_country_rev=741
wl1_reg_mode=h

 

[L&LD]

@archiel was the RT-AX58U fully reset prior to 'pointing' to it from the main router and adding it as an AiMesh node?

 

[archiel]

@archiel was the RT-AX58U fully reset prior to 'pointing' to it from the main router and adding it as an AiMesh node?

As far I as remember -

• Arrived brand new 30 March
• installed 384.15, nothing else
• setup basic config: network connection, wifi ssid, clients, etc.
• very disappointed with wifi range (compared to AC87U)
• next day (31 March) ordered AX88U
• on delivery (6 April) setup basic configuration for AX88U then changed AX58U from Router Mode to AiMesh Node - this then started the automatic reset.
• only changes to AX58U since then - updates to 384.16, then 384.17

 

[jackiechun]

This may be a silly question, but does 384.18 Alpha include the possibility of enabling DHCP "Continuous" mode on AC86U as referenced in this post? https://www.snbforums.com/threads/a...ot-function-properly.61907/page-2#post-573192

"The Continuous Mode module should have been included in the latest firmware 3.0.0.4.384.81792" and I see that the version used in this is 384_81846.

I believe the answer is yes but just wanted to confirm. Thanks!

 

[madfusker]

I couldn't ever isolate the disconnects and that information is quite helpful, thanks! Hopefully this comes soon and it can be incorporated. I have taken mine off the default aggressive mode for now to see if it helps.

 

[Alaska99]

My RT-AX88U reboot wifi 2 or 3 times by days. I already do a factory reset but same things.
I check the log after the last wifi drop and I found this.

Jun 10 20:05:38 kernel: WLC_SCB_AUTHORIZE sta_flags_mask not set
Jun 10 20:05:43 kernel: 08:12:A5:16:9C:8E already exist in UDB, can't add it
Jun 10 20:05:43 kernel: CC:F7:35:D2:97:27 already exist in UDB, can't add it
Jun 10 20:05:43 kernel: 00:13:21:C6:F7:98 already exist in UDB, can't add it
Jun 10 20:05:43 kernel: 68:B3:5E:56:D3:69 already exist in UDB, can't add it
Jun 10 20:05:43 kernel: 5C:41:5A:94:63:21 already exist in UDB, can't add it
Jun 10 20:05:43 kernel: 68:9A:87:AA:5C:C9 already exist in UDB, can't add it
Jun 10 20:05:43 rc_service: amas_lib 1272:notify_rc restart_firewall
Jun 10 20:05:43 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Jun 10 20:06:01 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted

I don't understand this log but maybe someone here can spot something wrong?

Thanks.

 

[L&LD]

As far I as remember -

• Arrived brand new 30 March
• installed 384.15, nothing else
• setup basic config: network connection, wifi ssid, clients, etc.
• very disappointed with wifi range (compared to AC87U)
• next day (31 March) ordered AX88U
• on delivery (6 April) setup basic configuration for AX88U then changed AX58U from Router Mode to AiMesh Node - this then started the automatic reset.
• only changes to AX58U since then - updates to 384.16, then 384.17

archiel, to me, it seems both your routers are not set up properly then.

After flashing RMerlin firmware, you need to do a full reset to factory defaults.

The proper way to use AiMesh node is to do a full reset on the router you want as an AiMesh node and then don't touch it further at all.

On the main router, 'point' to the router you want as an AiMesh node and wait while it configures and reboots it.

To put your routers back to a good/known state, follow the suggestions in the M&M Config and ideally the Nuclear Reset guides found in the link in my signature below.

 

[morfy]

Hello. I keep a 790 netgear attached via USB. Everything works perfectly, but every now and then from error and I have to restart everything.
Jun 11 08:35:30 WAN_Connection: ISP's DHCP did not function properly.
Jun 11 08:35:30 DualWAN: skip single wan wan_led_control - WANRED off
Jun 11 08:35:30 nat: apply redirect rules
Jun 11 08:35:35 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 3
Jun 11 08:35:36 kernel: rndis_host 2-2: 1.0: eth2: register 'rndis_host' at usb-0000: 00: 0b.1-2, RNDIS device, 00: a0: c6: 00: 00: 00
Jun 11 08:35:36 hotplug: add net eth2.
Jun 11 08:35:36 hotplug: set net eth2.
Jun 11 08:35:39 WAN_Connection: Ethernet link up.
Jun 11 08:35:44 wan: finish adding multi routes

What can it depend on ???? ASUSAC87U + netgear 790 + Versione firmware:384.13_8

 

[archiel]

archiel, to me, it seems both your routers are not set up properly then.

After flashing RMerlin firmware, you need to do a full reset to factory defaults.

The proper way to use AiMesh node is to do a full reset on the router you want as an AiMesh node and then don't touch it further at all.

On the main router, 'point' to the router you want as an AiMesh node and wait while it configures and reboots it.

To put your routers back to a good/known state, follow the suggestions in the M&M Config and ideally the Nuclear Reset guides found in the link in my signature below.

I am a little confused

Both routers seem to be working happily and quite stable, but I could take a few hours out to reconfigure the AX88U over the weekend. My query was really about whether there was a way to see what channels are available on the AiMesh Node given the E0/742 response.

AX58U: As far as I remember when I switched to AiMesh Node, there was a message says that this would now reset all the settings - are you saying that it needs a further reset after that? Also you have said "then don't touch it further at all." - what about updates to firmware - should I ignore these?

AX88U: This arrived with Asus firmware/factory defaults and was then immediately flashed to Merlin. The only step missing is that I did not then re-reset to factory default before starting to configure - given that the router is quite happy and stable, is doing a factory reset now and then reconfiguring likely to improve anything?

 

[GHammer]

Here's the info from my US based/bought AX58U

ASUSWRT-Merlin RT-AX58U 384.18_alpha1-g6368a955e8 Fri May 29 04:00:36 UTC 2020
nvram show | grep -E 'territory_code|ccode|regrev|regulation|wl[0-9]_country|wl[0-9]_reg_mode|:max|wl[0-9]_chlist' | sort
size: 66202 bytes (64870 left)
0:ccode=ALL
0:maxp2ga0=114
0:maxp2ga1=114
0:regrev=0
1:ccode=ALL
1:maxp5gb0a0=110
1:maxp5gb0a1=110
1:maxp5gb0a2=110
1:maxp5gb0a3=110
1:maxp5gb1a0=110
1:maxp5gb1a1=110
1:maxp5gb1a2=110
1:maxp5gb1a3=110
1:maxp5gb2a0=110
1:maxp5gb2a1=110
1:maxp5gb2a2=110
1:maxp5gb2a3=110
1:maxp5gb3a0=110
1:maxp5gb3a1=110
1:maxp5gb3a2=110
1:maxp5gb3a3=110
1:maxp5gb4a0=110
1:maxp5gb4a1=110
1:maxp5gb4a2=110
1:maxp5gb4a3=110
1:regrev=0
territory_code=US/01
wl0_chlist=1 2 3 4 5 6 7 8 9 10 11
wl0_country_code=US
wl0_country_rev=768
wl0_reg_mode=d
wl1_chlist=36 40 44 48 52 56 60 64 149 153 157 161 165
wl1_country_code=US
wl1_country_rev=768
wl1_reg_mode=h

 

[prosperot]

I can set a country code in nvram but after a reboot this is reset to E0, any way around this?

 

[MDM]

I can set a country code in nvram but after a reboot this is reset to E0, any way around this?

That's basically hacking, don't ask for it here...

 

[prosperot]

That's basically hacking, don't ask for it here...

Well I just want to set my router to its proper country code instead of E0. But if that is considered hacking, then I guess the whole discussion on country codes could be considered ' hacking'.

Just forget the question and lets go back to topic: 384.18 alpha...

 

[bigcid10]

Is there anyway to stop the dyndns service from hammering by router every 30 sec ?
Thank you

 

[MarkyPancake]

I can set a country code in nvram but after a reboot this is reset to E0, any way around this?

I think the country is hard coded at the bootloader level, and is not designed to be tampered with, so the device operates correctly for its intended territory.

 

[dave14305]

Is there anyway to stop the dyndns service from hammering by router every 30 sec ?
Thank you
View attachment 24041

You can post the output from the command below to get some hints (it removes user and password). I'm guessing the DDNS update isn't finishing successfully and setting the nvram ddns_updated. Run this before and after one of the 30 second updates.

nvram show 2>/dev/null | grep -E "^ddns_" | grep -vE "passwd|username" | sort

 

[L&LD]

I am a little confused

Both routers seem to be working happily and quite stable, but I could take a few hours out to reconfigure the AX88U over the weekend. My query was really about whether there was a way to see what channels are available on the AiMesh Node given the E0/742 response.

AX58U: As far as I remember when I switched to AiMesh Node, there was a message says that this would now reset all the settings - are you saying that it needs a further reset after that? Also you have said "then don't touch it further at all." - what about updates to firmware - should I ignore these?

AX88U: This arrived with Asus firmware/factory defaults and was then immediately flashed to Merlin. The only step missing is that I did not then re-reset to factory default before starting to configure - given that the router is quite happy and stable, is doing a factory reset now and then reconfiguring likely to improve anything?

If they're working happily and as you need, then keep enjoying them.

AX58U: Of course firmware updates should be done as they become available. But did you change it to an AiMesh node from the Administration tab or did you just 'point' to it from the main router, after having performed a full reset? The latter is what gives the most stable performance in my experience.

A full reset would include (in this order);

1. Flash the firmware you want to use on the router to be used as an AiMesh node (and flash it even if it is the same version that is currently installed).
2. Format the JFFS partition on the next reboot. Make sure you hit 'Apply' at the bottom of the page. Reboot the router 3 times in the next 15 minutes.
3. Perform a full reset to factory defaults via the GUI, including checking the 'Initialize all settings' checkbox.
4. At this point, do not touch or access the router at all except via the main router's GUI to add it as an AiMesh node by 'pointing' to it by clicking the Search button.

AX88U: Yes, you missed an important step (I would not leave a router like this for a customer). In your case, as long as the router/network is behaving, leave it as is.

But know this is the first thing you need to address if random bugs and glitches start showing up at any time in the future.

Many things change within the firmware when you flash RMerlin's version (or, reflash the stock firmware back from RMerlin firmware). A full reset is needed to ensure that the firmware installed is properly configured with its expected defaults. Right now it is not, even if it seems to be working fine for you so far.

HTH.

 

[Vexira]

This may be a silly question, but does 384.18 Alpha include the possibility of enabling DHCP "Continuous" mode on AC86U as referenced in this post? https://www.snbforums.com/threads/a...ot-function-properly.61907/page-2#post-573192

"The Continuous Mode module should have been included in the latest firmware 3.0.0.4.384.81792" and I see that the version used in this is 384_81846.

I believe the answer is yes but just wanted to confirm. Thanks!

I would say it's model dependant your best off checking the log of comits on github to see what has been add or changed.

It's not yet available on my AX88U mabye on another model perhaps.

 

[Thermaltake]

Asus still didn't release .385 code ?