Beta Asuswrt-Merlin 386.4 beta is now available

[JGrana]

Quick question about the same. Will the same ssh key also work with the nodes?
My main router has ssh enabled and also has ssh keys. I am able to ssh into the router without typing any passwords.
Essentially, if I ssh into the node (using the node specific ip address), will the same ssh keys work.
I tried that and the node asks for the password; rather than logging using the ssh keys?

Hmm, not sure if the main node shares the key(s).

 

[DJones]

Hm… what you said about enabling ssh on the main router doesn’t seem to give me ssh for the node. Under wireless log it said the node doesn’t have a IP address, but when clicking usb applications under the aimesh node I can see it connects to 192.168.1.x which is the same ip i get for the node when in media bridge mode. But when I put this in putty with ssh and my main router port it doesn’t give me access to the node when I allow passwords or ssh keys.

Also attempting to login using 192.168.1.x nodes ip using a web browser just redirects me to my main routers ip.

So idk.. I don’t need access to ssh for my main router, but the node using aimesh.

So going back to my main topic having access to the administration tab and maybe system logs, and network tools would be helpful for router nodes using aimesh.

 

[dbell]

Hm… what you said about enabling ssh on the main router doesn’t seem to give me ssh for the node. Under wireless log it said the node doesn’t have a IP address, but when clicking usb applications under the aimesh node I can see it connects to 192.168.1.x which is the same ip i get for the node when in media bridge mode. But when I put this in putty with ssh and my main router port it doesn’t give me access to the node when I allow passwords or ssh keys.

Also attempting to login using 192.168.1.x nodes ip using a web browser just redirects me to my main routers ip.

So idk.. I don’t need access to ssh for my main router, but the node using aimesh.

So going back to my main topic having access to the administration tab and maybe system logs, and network tools would be helpful for router nodes using aimesh.

Unless you have a manually assigned IP address for the node in the DHCP server settings on the router, the node is going to get different IP addresses from DHCP. Look at the AiMesh node in the router GUI and see what IP address is listed in the Uplink section of the Network tab.

You should be able to SSH to that IP address and log in with admin user / password e.g ssh admin@192.168.xxx.2. You'd then need to put the SSH key in the .ssh/authorized_keys file on the node to allow login without password. You might need to script that update if it gets wiped out after each restart, since it is in /tmp/home/root/.ssh/authorized_keys

Here is the first entry in my DHCP manual assignment list so I know the node is always .2 while the router is .1:

 

[DJones]

Unless you have a manually assigned IP address for the node in the DHCP server settings on the router, the node is going to get different IP addresses from DHCP. Look at the AiMesh node in the router GUI and see what IP address is listed in the Uplink section of the Network tab.

View attachment 38131

You should be able to SSH to that IP address and log in with admin user / password e.g ssh admin@192.168.xxx.2. You'd then need to put the SSH key in the .ssh/authorized_keys file on the node to allow login without password. You might need to script that update if it gets wiped out after each restart, since it is in /tmp/home/root/.ssh/authorized_keys

Here is the first entry in my DHCP manual assignment list so I know the node is always .2 while the router is .1:

View attachment 38132

Okay so I’m seeing the correct ip address from where your showing. Hm.. maybe a issue with the port because I don’t even get to the login prompt just refuses connection.

 

[dbell]

Okay so I’m seeing the correct ip address from where your showing. Hm.. maybe a issue with the port because I don’t even get to the login prompt just refuses connection.

ok and you have the ssh service enabled in the Admin | System section of the router gui ? Side note looks like you can put auth keys here but no idea if that is shared with node or still needs manual update.

 

[dbell]

Okay so I’m seeing the correct ip address from where your showing. Hm.. maybe a issue with the port because I don’t even get to the login prompt just refuses connection.

What command are you using to connect ?

 

[DJones]

What command are you using to connect ?

On main router enable lan ssh, chose allow password login. (Tried with ssh key also) apply settings. I open putty on windows. Choose ssh set my custom port number to what is listed on my main router. Set IP address of node. Attempt connection on putty get connection refused. Does it need ssh port forwarding enabled?

Maybe SSH has to be enabled when the aimesh node is added.

 

[unsynaps]

I noticed some GUI page not loaded properly after dirty update. Anyone see something like this before? After click back and try a few more times it get displayed properly.

View attachment 38094

Clear your browser cache,

 

[CHiLL72]

I had this just recently. WAN would drop for no reason on the RT-AX88U, rebooting the router it would recover. Replaced the ethernet cable between WAN port and Cable modem, all fixed.

I will try and replace the ethernet cable again, although I already tried that. Thanks.

 

[octopus]

I have run beta3 for (2 days 13 hour(s) 29 minute(s) 22 seconds) and my wifi aimesh node on 2,4Ghz dissapered.

That happends with all latest alpha and beta firmware.

Seems disassociated and not connecting again, have to reboot aimesh node to get it back on 2,4 Ghz, it's after ~60 hour uptime.

Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated

I have also discovered some time 1 hour difference, see log: look at <<<=== TIME HERE in code tag
Same time my wifi 2,4Ghz dissapear

Dec 31 13:06:23 roamast: determine candidate node [3C:7C:3F:xx:xx:xx](rssi: -43dbm) for client [A0:D8:07:xx:xx:xx](rssi: -54dbm) to roam
Dec 31 13:06:23 roamast: Roam a client [A0:D8:07:xx:xx:xx], status [0]
Dec 31 13:06:24 roamast: [EXAP]Deauth old sta in 1 0: A0:D8:07:xx:xx:xx
Dec 31 13:06:24 roamast: eth7: disconnect weak signal strength station [a0:d8:07:xx:xx:xx]
Dec 31 13:06:24 roamast: eth7: remove client [a0:d8:07:xx:xx:xx] from monitor list
Dec 31 13:06:24 hostapd: eth7: STA a0:d8:07:xx:xx:xx IEEE 802.11: disassociated
Dec 31 13:20:44 hostapd: wl1.2: STA 88:3d:24:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: wl1.2: STA 14:2d:27:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:45 hostapd: eth7: STA 38:0b:40:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:47 custom_script: Running /jffs/scripts/dhcpc-event (args: renew)
Dec 31 13:20:47 (dhcpc-event): 15901 dhcpc-event Parms = renew <<<=== TIME HERE
Dec 31 12:22:56 kernel: CFG80211-ERROR) wl_event_handler : No wdev corresponding to bssidx: 0x0 found! Ignoring event. <<<=== TIME HERE
Dec 31 12:22:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1 <<<=== TIME HERE
Dec 31 13:22:56 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:56 kernel: device wds1.0.1 left promiscuous mode
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3fxx:xx:xx IEEE 802.11: disassociated <<<=== wifi 2,4Ghz dissapear

@RMerlin

 

[maxbraketorque]

All ok with 386.4b3 on a new AX68U running a simple setup (single wifi router, only enabled features are ASUS DDNS and OVPN) connecting to the internet via PPPoE. Smart Connect is enabled with a single SSID and manual channel selection.

 

[ColinTaylor]

I have run beta3 for (2 days 13 hour(s) 29 minute(s) 22 seconds) and my wifi aimesh node on 2,4Ghz dissapered.

That happends with all latest alpha and beta firmware.

Seems disassociated and not connecting again, have to reboot aimesh node to get it back on 2,4 Ghz, it's after ~60 hour uptime.

View attachment 38135

Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated

I have also discovered some time 1 hour difference, see log: look at <<<=== TIME HERE in code tag
Same time my wifi 2,4Ghz dissapear

Dec 31 13:06:23 roamast: determine candidate node [3C:7C:3F:xx:xx:xx](rssi: -43dbm) for client [A0:D8:07:xx:xx:xx](rssi: -54dbm) to roam
Dec 31 13:06:23 roamast: Roam a client [A0:D8:07:xx:xx:xx], status [0]
Dec 31 13:06:24 roamast: [EXAP]Deauth old sta in 1 0: A0:D8:07:xx:xx:xx
Dec 31 13:06:24 roamast: eth7: disconnect weak signal strength station [a0:d8:07:xx:xx:xx]
Dec 31 13:06:24 roamast: eth7: remove client [a0:d8:07:xx:xx:xx] from monitor list
Dec 31 13:06:24 hostapd: eth7: STA a0:d8:07:xx:xx:xx IEEE 802.11: disassociated
Dec 31 13:20:44 hostapd: wl1.2: STA 88:3d:24:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: wl1.2: STA 14:2d:27:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:45 hostapd: eth7: STA 38:0b:40:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:47 custom_script: Running /jffs/scripts/dhcpc-event (args: renew)
Dec 31 13:20:47 (dhcpc-event): 15901 dhcpc-event Parms = renew <<<=== TIME HERE
Dec 31 12:22:56 kernel: CFG80211-ERROR) wl_event_handler : No wdev corresponding to bssidx: 0x0 found! Ignoring event. <<<=== TIME HERE
Dec 31 12:22:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1 <<<=== TIME HERE
Dec 31 13:22:56 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:56 kernel: device wds1.0.1 left promiscuous mode
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3fxx:xx:xx IEEE 802.11: disassociated <<<=== wifi 2,4Ghz dissapear

@RMerlin

Can you try disabling WDS or is that required for AiMesh to work?

 

[Deleted member 77025]

I have run beta3 for (2 days 13 hour(s) 29 minute(s) 22 seconds) and my wifi aimesh node on 2,4Ghz dissapered.

That happends with all latest alpha and beta firmware.

Seems disassociated and not connecting again, have to reboot aimesh node to get it back on 2,4 Ghz, it's after ~60 hour uptime.

View attachment 38135

Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated

I have also discovered some time 1 hour difference, see log: look at <<<=== TIME HERE in code tag
Same time my wifi 2,4Ghz dissapear

Dec 31 13:06:23 roamast: determine candidate node [3C:7C:3F:xx:xx:xx](rssi: -43dbm) for client [A0:D8:07:xx:xx:xx](rssi: -54dbm) to roam
Dec 31 13:06:23 roamast: Roam a client [A0:D8:07:xx:xx:xx], status [0]
Dec 31 13:06:24 roamast: [EXAP]Deauth old sta in 1 0: A0:D8:07:xx:xx:xx
Dec 31 13:06:24 roamast: eth7: disconnect weak signal strength station [a0:d8:07:xx:xx:xx]
Dec 31 13:06:24 roamast: eth7: remove client [a0:d8:07:xx:xx:xx] from monitor list
Dec 31 13:06:24 hostapd: eth7: STA a0:d8:07:xx:xx:xx IEEE 802.11: disassociated
Dec 31 13:20:44 hostapd: wl1.2: STA 88:3d:24:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: wl1.2: STA 14:2d:27:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:44 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:45 hostapd: eth7: STA 38:0b:40:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 31 13:20:47 custom_script: Running /jffs/scripts/dhcpc-event (args: renew)
Dec 31 13:20:47 (dhcpc-event): 15901 dhcpc-event Parms = renew <<<=== TIME HERE
Dec 31 12:22:56 kernel: CFG80211-ERROR) wl_event_handler : No wdev corresponding to bssidx: 0x0 found! Ignoring event. <<<=== TIME HERE
Dec 31 12:22:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1 <<<=== TIME HERE
Dec 31 13:22:56 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx IEEE 802.11: disassociated
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:56 kernel: device wds1.0.1 left promiscuous mode
Dec 31 12:22:56 kernel: br0: port 10(wds1.0.1) entered disabled state
Dec 31 12:22:57 kernel: wl0: random key value: 87EC7F8BF14742463AF102DE19CF62702FE40E2C37830AAB340E0192611C412C
Dec 31 12:22:57 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
Dec 31 12:22:57 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 31 12:22:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 12:22:57 kernel: device wds0.0.1 left promiscuous mode
Dec 31 12:22:57 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 31 13:22:57 hostapd: eth6: STA 3c:7c:3fxx:xx:xx IEEE 802.11: disassociated <<<=== wifi 2,4Ghz dissapear

@RMerlin

time diff. had this one too but after a reset or reboot it was gone.
appeared from beta1 to beta2 with dirty flash for me.
think it has maybe also something todo with dns like from your provider and some others like cloudflare or google ?



anyone know why the vpn makes a tls soft reset every hour on beta3 ?

Dec 31 17:17:12 ovpn-client1[14922]: TLS: soft reset sec=3600/3600 bytes=394527076/-1 pkts=361654/0
Dec 31 18:17:12 ovpn-client1[14922]: TLS: soft reset sec=3600/3600 bytes=401877076/-1 pkts=399584/0

edit:

current problem from openvpn 2.5 wich can be ignored (save).

most stable beta i have seen after a dirty flash

 

[octopus]

Can you try disabling WDS or is that required for AiMesh to work?

I have WDS off in GUI not needed to get Aimesh working.
Maby it's using it anyway in other process.

 

[bits]

Rt-ax86u
In beta 2 Wan ipv6 failed. No external IP was ever set
Log had ddns and letsencrypt failure and also
Firewall: apply rules error(4619)

Beta 3 Wan ipv6 works fine.

 

[eibgrad]

anyone know why the vpn makes a tls soft reset every hour on beta3 ?

Dec 31 17:17:12 ovpn-client1[14922]: TLS: soft reset sec=3600/3600 bytes=394527076/-1 pkts=361654/0
Dec 31 18:17:12 ovpn-client1[14922]: TLS: soft reset sec=3600/3600 bytes=401877076/-1 pkts=399584/0

edit:

current problem from openvpn 2.5 wich can be ignored (save).

This is normal. By default, OpenVPN rotates/changes the session key every 3600 secs (1 hr) for the purposes of perfect forward secrecy. The time period can be changed (or disabled completely) using the reneg-sec directive.

 

[octopus]

Can you try disabling WDS or is that required for AiMesh to work?

Seems that what I have seen it's kernel dragging time 1 hour after.

Jan  1 16:20:44 hostapd: wl1.2: STA 88:3d:24:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: wl1.2: STA 14:2d:27:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: eth7: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: eth6: STA 3c:7c:3f:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: eth7: STA a0:d8:07:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: eth7: STA 38:0b:40:xx:xx:xx WPA: group key handshake completed (RSN)
Jan  1 16:20:44 hostapd: eth7: STA 04:8c:9a:xx:xx:xx WPA: group key handshake completed (RSN)

Jan  1 15:41:53 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Jan  1 15:41:53 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Jan  1 15:41:53 kernel: br0: port 5(eth5) entered disabled state
Jan  1 15:41:58 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Jan  1 15:41:58 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex
Jan  1 15:41:58 kernel: br0: port 5(eth5) entered forwarding state
Jan  1 15:41:58 kernel: br0: port 5(eth5) entered forwarding state
Jan  1 15:42:06 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Jan  1 15:42:06 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
Jan  1 15:42:06 kernel: br0: port 5(eth5) entered disabled state
Jan  1 15:42:10 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Jan  1 15:42:10 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 2500 mbps full duplex

@RMerlin

 

[5stringdeath]

Just reporting in that beta3 DDNS using my Google DDNS is now working again, and I use native IPV6 via my FiOS

 

[Deleted member 22229]

Merlin are you going with the final release today ? If yes then i wont bother with the last beta.

 

[Kabouter Plop]

Would be cool to run pihole directly from router, i know if i can manage to deploy docker on my armv8 64 nas then there should be no reason ax88u cannot either other then storage limitation perhaps, altho would probably not any heavy containers that use a lot of memory