[Beta 384/NG] Asuswrt-merlin 384.4 Beta is now available

[thelonelycoder]

cfg_server crashed according to this. Unfortunately, it's closed source - it handles config synchronisation between AiMesh nodes, and the service runs even if AiMesh isn't in use...

I see... Is that also the reason why the networkmap had that translation fault?
Can't say what or when it started, the syslog was flooded with these messages.
I only noticed because @bigeyes0x0 dnscrypt script failed to start and I was looking for clues in the syslog.

 

[dvohwinkel]

I think you are misunderstanding what I am asking for (or I did a crappy job of wording my question). I want it to pick the band for the device like it is designed, which it does well. What I am asking for is control over the channel/frequency that it assigns to each band. 11 is free in my area, but the router insists on using 1 or 6 or 7 for 2.4. All I am asking for is the ability to just tell it that I want it to use channel 11 for 2.4. I still want it to do what it does, I just want to be able to have some control over the frequency is uses. I don't think that is an unreasonable request. I have always found the automatic frequency choices that Asus routers make to be a little silly.

Just like AndreiV said.. you turn off "Smart Connect" which is under Advanced Settings->Wireless and select the channel you want.

 

[maxbraketorque]

I think you are misunderstanding what I am asking for (or I did a crappy job of wording my question). I want it to pick the band for the device like it is designed, which it does well. What I am asking for is control over the channel/frequency that it assigns to each band. 11 is free in my area, but the router insists on using 1 or 6 or 7 for 2.4. All I am asking for is the ability to just tell it that I want it to use channel 11 for 2.4. I still want it to do what it does, I just want to be able to have some control over the frequency is uses. I don't think that is an unreasonable request. I have always found the automatic frequency choices that Asus routers make to be a little silly.

I agree with this as well. I'm amazed how much within-band channel hoping occurs with Smart Connect enabled. It seems totally arbitrary, especially in the 5 GHz bands where there are no other routers in range. What's perhaps more surprising is when Smart Connect selects a channel in the 2.4 GHz band that has a bunch of neighbor routers piled into it. I think it would be great to have manual channel selection for the bands, and then let Smart Connect do its job of switching between bands.

 

[WET]

I modified Samba protocol support to SMBv2 only as recommended. Do the below log entries mean I have a client that is using SMBv1?

Mar 1 07:11:34 smbd[16597]: [2018/03/01 07:11:34.311402, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:11:34 smbd[16597]: No protocol supported !
Mar 1 07:11:34 smbd[16598]: [2018/03/01 07:11:34.907910, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:11:34 smbd[16598]: No protocol supported !
Mar 1 07:16:59 smbd[16719]: [2018/03/01 07:16:59.292098, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:16:59 smbd[16719]: No protocol supported !
Mar 1 07:17:01 smbd[16720]: [2018/03/01 07:17:01.088696, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:17:01 smbd[16720]: No protocol supported !
Mar 1 07:17:01 smbd[16721]: [2018/03/01 07:17:01.544306, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:17:01 smbd[16721]: No protocol supported !
Mar 1 07:17:01 smbd[16722]: [2018/03/01 07:17:01.890964, 0] smbd/negprot.c:706(reply_negprot)
Mar 1 07:17:01 smbd[16722]: No protocol supported !

 

[RMerlin]

I see... Is that also the reason why the networkmap had that translation fault?

No idea. I guess it's always possible that an nvram manipulation operation caused cfg_server to crash, preventing in turn networkmap from accessing data... Can't say since I don't know the details of what cfg_server does, neither how the new networkmap works.

Do the below log entries mean I have a client that is using SMBv1?

Probably, as it does indicate that something tried to use an unsupported protocol. Don't forget to restart all your clients - Windows clients will not renegotiate the protocol if the server changes, they will just be unable to connect until you restart the computer itself or the Workstation service.

 

[unsynaps]

This is normal, the network browse ability is only supported on SMB1 and was removed from SMB2 and later releases (M$ wants you to use active directory or other complicated solutions). So, with >=SMB2 you need to know the hostname of the machine doing the sharing at least in order to find the share.

Mother fffff. No wonder my reloaded Fall Creators computers dont show up browsing anymore.

 

[JMB64]

384.4 Beta for AC86U is missing the SNMP tab under Administration Tab. Not sure if this is Asus or Merlin. 384.3 has it.

 

[john9527]

384.4 Beta for AC86U is missing the SNMP tab under Administration Tab. Not sure if this is Asus or Merlin. 384.3 has it.

Removed for the AC86, since there are kernel incompatibilities
https://github.com/RMerl/asuswrt-merlin.ng/commit/736d04b8cc7542d15f467eda149a64db60b72fa4

 

[JMB64]

Removed for the AC86, since there are kernel incompatibilities
https://github.com/RMerl/asuswrt-merlin.ng/commit/736d04b8cc7542d15f467eda149a64db60b72fa4

Any chance of it being put back in with a later release? I use an SNMP app to track throughput when I don't have the Asus UI open.

 

[AndreiV]

I think you are misunderstanding what I am asking for (or I did a crappy job of wording my question). I want it to pick the band for the device like it is designed, which it does well. What I am asking for is control over the channel/frequency that it assigns to each band. 11 is free in my area, but the router insists on using 1 or 6 or 7 for 2.4. All I am asking for is the ability to just tell it that I want it to use channel 11 for 2.4. I still want it to do what it does, I just want to be able to have some control over the frequency is uses. I don't think that is an unreasonable request. I have always found the automatic frequency choices that Asus routers make to be a little silly.

No, I understood you perfectly well. You either use the automated system ,"Smart Connect" or you make manual settings. Smart Connect is a closed source proprietary Asus component , if you want new features you need to speak to Asus direct.

 

[Broken Hope]

2.4 Ghz radio busted on AC86U with this build.
Done settings restore, reboot, power cycle.

Mar  1 03:06:01 kernel: br0: port 5(eth6) entered listening state
Mar  1 03:06:01 kernel: br0: port 5(eth6) entered listening state
Mar  1 03:06:01 kernel: acsd[2741]: unhandled level 2 translation fault (11) at 0x03e4a4cb, esr 0x92000006
Mar  1 03:06:01 kernel: pgd = ffffffc016644000
Mar  1 03:06:01 kernel: [03e4a4cb] *pgd=00000000161c2003, *pud=00000000161c2003, *pmd=0000000000000000
Mar  1 03:06:01 kernel: CPU: 1 PID: 2741 Comm: acsd Tainted: P           O    4.1.27 #2
Mar  1 03:06:01 kernel: Hardware name: Broadcom-v8A (DT)
Mar  1 03:06:01 kernel: task: ffffffc0167d0ac0 ti: ffffffc0169f8000 task.ti: ffffffc0169f8000
Mar  1 03:06:01 kernel: PC is at 0xf746c768
Mar  1 03:06:01 kernel: LR is at 0x40b68
Mar  1 03:06:01 kernel: pc : [<00000000f746c768>] lr : [<0000000000040b68>] pstate: 20080010
Mar  1 03:06:01 kernel: sp : 00000000ffe332fc
Mar  1 03:06:01 kernel: x12: 0000000000000100
Mar  1 03:06:01 kernel: x11: 00000000ffe33438 x10: 0000000000061e90
Mar  1 03:06:01 kernel: x9 : 00000000f7641ce0 x8 : 0000000000000000
Mar  1 03:06:01 kernel: x7 : 00000000ffffffed x6 : 0000000000061ad4
Mar  1 03:06:01 kernel: x5 : 00000000ffe33420 x4 : 00000000005f1c00
Mar  1 03:06:01 kernel: x3 : 0000000000000000 x2 : 000000008f40fc00
Mar  1 03:06:01 kernel: x1 : 0000000000000000 x0 : 0000000003e4a4cf
Mar  1 03:06:03 kernel: br0: port 5(eth6) entered learning state
Mar  1 03:06:05 kernel: br0: topology change detected, propagating
Mar  1 03:06:05 kernel: br0: port 5(eth6) entered forwarding state

My 2.4GHz radio is fine on my 86U on this build.

Have noticed something which I can't remember if it was there on previous builds, but on the Wireless log where it says Mode: it states AP, I'm using mine in router mode so not sure why it's not stating as such.

 

[Alfsu]

Noticed these repetitive log entry after update, with SMBv2 selected:

Mar  2 01:46:37 smbd[17028]:   Invalid SMB packet: first request: 0x000D
Mar  2 01:47:38 smbd[17069]: [2018/03/02 01:47:38.328549,  0] smbd/smb2_server.c:248(smbd_smb2_request_create)
Mar  2 01:47:38 smbd[17069]:   Invalid SMB packet: first request: 0x000D
Mar  2 01:48:39 smbd[17089]: [2018/03/02 01:48:39.080673,  0] smbd/smb2_server.c:248(smbd_smb2_request_create)
Mar  2 01:48:39 smbd[17089]:   Invalid SMB packet: first request: 0x000D
Mar  2 01:49:39 smbd[17106]: [2018/03/02 01:49:39.830965,  0] smbd/smb2_server.c:248(smbd_smb2_request_create)
Mar  2 01:49:39 smbd[17106]:   Invalid SMB packet: first request: 0x000D
Mar  2 01:50:40 smbd[17123]: [2018/03/02 01:50:40.980749,  0] smbd/smb2_server.c:248(smbd_smb2_request_create)
Mar  2 01:50:40 smbd[17123]:   Invalid SMB packet: first request: 0x000D

Log entry stops if setting SMBv1 + SMBv2

A folder in the router's USB drive (128GB memory stick) is mounted on a computer running Debian 9 (arch 64), via fstab.

These log messages were absent under 384.3 with SMB set to v2.

Will continue testing.

Sent from my ONEPLUS A3000 using Tapatalk

 

[john9527]

Log entry stops if setting SMBv1 + SMBv2

A folder in the router's USB drive (128GB memory stick) is mounted on a computer running Debian 9 (arch 64), via fstab.

These log messages were absent under 384.3 with SMB set to v2.

SMBv1+SMBv2 in 384.4 is equivalent to the SMBv2=Yes setting in the older releases (it added SMBv2 but did not disable SMBv1). You have a client that is attempting to use SMBv1.

 

[Nigel Jones]

Update to my RT-AC3200 issue - it occurred again with the current *STOCK* firmware.
I've now done a full factory reset (with limited manual reconfig) directly on the current merlin beta 384.4b1 & will try with that...

 

[Maghook]

Feb 14 01:01:17 Samba_Server: daemon is started
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 3
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:19 lldpd[805]: custom TLV op replace oui f8:32:e4 subtype 2
Feb 14 01:01:34 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Feb 14 01:01:34 kernel: br0: port 1(eth0) entered disabled state
Feb 14 01:01:34 kernel: ===> Activate Deep Green Mode
Feb 14 01:01:36 ntp: start NTP update
Feb 14 01:01:37 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Feb 14 01:01:37 kernel: br0: port 1(eth0) entered forwarding state
Feb 14 01:01:37 kernel: br0: port 1(eth0) entered forwarding state
Feb 14 01:01:37 kernel: <=== Deactivate Deep Green Mode
Feb 14 01:01:56 ntp: start NTP update
Feb 14 01:02:14 ntp: start NTP update
Mar  1 15:03:49 rc_service: ntp 1116:notify_rc restart_diskmon
Mar  1 15:03:49 disk_monitor: Finish
Mar  1 15:03:49 disk_monitor: be idle
Mar  1 15:04:34 crond[786]: time disparity of 548042 minutes detected
Mar  1 16:42:27 kernel: br0: received packet on eth6 with own address as source address
Mar  1 16:42:28 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 16:51:36 kernel: jffs2: warning: (757) jffs2_sum_write_data: Not enough space for summary, padsize = -1089
Mar  1 16:51:37 kernel: br0: received packet on eth6 with own address as source address
Mar  1 17:09:08 kernel: br0: received packet on eth6 with own address as source address
Mar  1 17:09:08 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:15:28 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:31:18 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:32:51 kernel: br0: received packet on eth6 with own address as source address
Mar  1 17:32:53 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:37:18 roamast: eth6: add client [8c:f5:a3:1c:23:xx] to monitor list
Mar  1 17:39:58 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:52:48 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  1 17:54:09 kernel: br0: received packet on eth5 with own address as source address
Mar  1 21:31:33 roamast: eth6: add client [8c:f5:a3:1c:23:xx] to monitor list
Mar  1 23:03:49 disk_monitor: Got SIGALRM...
Mar  2 06:41:43 roamast: eth6: add client [f8:32:e4:b4:f8:xx] to monitor list
Mar  2 06:41:58 roamast: eth6: add client [1c:91:48:8d:33:xx] to monitor list
Mar  2 08:22:52 kernel: br0: received packet on eth5 with own address as source address
Mar  2 09:28:53 roamast: eth6: add client [1c:91:48:8d:33:xx] to monitor list
Mar  2 09:42:13 kernel: br0: received packet on eth6 with own address as source address
Mar  2 09:42:18 roamast: eth6: add client [8c:8e:f2:e5:d7:xx] to monitor list

kernel: br0: received packet on eth with own address as source address

This old issue still does not seem to be resolved by ASUS.
Getting these at least with all .384-based releases on RT-AC86u (ap mode).

 

[dlandon]

The router seems to be giving out the wrong IPv6 gateway address.

 

[skeal]

I have a ac3100 using 384.4 beta_1. I noticed 2 log entries that puzzle me. Last night while asleep my routers wireless service retsarted no know reason:

Mar  2 02:00:31 rc_service: rc 14254:notify_rc restart_wrs
Mar  2 02:00:48 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Mar  2 02:00:48 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Mar  2 02:00:48 kernel: ioctl_iqos_op_config() fail!
Mar  2 02:00:48 kernel: ERR[qos_start:3344] QoS is already started!
Mar  2 02:00:48 kernel: ioctl_iqos_op_switch(1) fail!

The second one happened earlier in the day, I have no clue:

Mar  1 17:49:50 rc_service: httpd 429:notify_rc reset_vp_db

Is this stuff closed source? Are these logs normal at this point?
EDIT: My up time is almost 3 days if that counts as good information.

 

[LostFreq]

@RMerlin
A few years ago you bumped the sshd_authkeys field size from 2999 to 3499 characters in Advanced_System_Content.asp. But release/src/router/shared/defaults.c contains this line:

{ "sshd_authkeys", "", CKN_STR2999, CKN_TYPE_DEFAULT, CKN_ACC_LEVEL_DEFAULT, CKN_ENC_DEFAULT, 0 },

is that not a problem?

 

[RMerlin]

Any chance of it being put back in with a later release? I use an SNMP app to track throughput when I don't have the Asus UI open.

Unlikely, as I was unable to resolve the compatibility issue, which is probably related to the new switch used by this model.

 

[RMerlin]

@RMerlin
A few years ago you bumped the sshd_authkeys field size from 2999 to 3499 characters in Advanced_System_Content.asp. But release/src/router/shared/defaults.c contains this line:

{ "sshd_authkeys", "", CKN_STR2999, CKN_TYPE_DEFAULT, CKN_ACC_LEVEL_DEFAULT, CKN_ENC_DEFAULT, 0 },

is that not a problem?

If I increase it, the new length will be rejected by the RT-AC86U due to its hardcoded values within the wlc module.