[Dev] Asuswrt-Merlin 388.1 development

[Tech9]

That's unfortunate

You already have everything included in 388 in Asuswrt-Merlin 386 plus extras.

 

[XIII]

I got the confirmation that AC models will not be moved to 388 - only AX models will be.

Time to start looking for a replacement for my AC86u then…

(Not in a hurry, but a good Black Friday deal could help)

 

[Rajjco]

My Wireguard Client keeps stopping randomly on it's own When checking the status it says stopped.

Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Checking if WireGuard® VPN Peer KILL-Switch is required.....
Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Restarting WireGuard® to reinstate RPDB/firewall rules
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting WireGuard® VPN Peer stop (wg21 wgc1)
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting termination of WireGuard® VPN 'server' Peer ('wg21')
Oct 31 10:42:41 GT-AX11000-CF50 wg_manager-serverwg21: WireGuard® VPN 'server' Peer (wg21) on 10.50.1.1:51820 Terminated
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Requesting WireGuard® VPN Peer start (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Initialising Wireguard® VPN 'server' Peer (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialising WireGuard® VPN 'Server' Peer (wg21) on 10.50.1.1:51820
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialisation complete.

 

[PR3MIUM]

Noticed some Wireguard issues here too in my logs, even while not using Wireguard and just using OpenVPN
Did a reset this morning of my 3x RT-AX88U because of some connection drop-outs, previouse alpha didnt had this issue.

May  5 07:08:28 wlceventd: wlceventd_proc_event(486): eth6: Disassoc xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May  5 07:08:28 hostapd: eth6: STA xx:xx:xx:xx:xx IEEE 802.11: disassociated
May  5 07:09:00 rc_service: service 2542:notify_rc restart_wgc
May  5 07:09:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:09:24 dnsmasq-dhcp[1918]: DHCPREQUEST(br0) 192.xxx.xxx.xxx xx:xx:xx:xx:xx
May  5 07:09:24 dnsmasq-dhcp[1918]: DHCPACK(br0) 192.xxx.xxx.xxx xx:xx:xx:xx:xx DESKTOP-XXX
May  5 07:10:00 rc_service: service 2741:notify_rc restart_wgc
May  5 07:10:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:11:00 rc_service: service 2935:notify_rc restart_wgc
May  5 07:11:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:12:00 rc_service: service 3130:notify_rc restart_wgc
May  5 07:12:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:13:00 rc_service: service 3322:notify_rc restart_wgc
May  5 07:13:05 WireGuard: NTP time not sync in -1 seconds
Oct 31 09:07:44 ntpd: Initial clock set
Oct 31 09:07:44 rc_service: ntpd_synced 3430:notify_rc restart_diskmon
Oct 31 09:07:44 disk_monitor: Finish
Oct 31 09:07:44 disk_monitor: be idle

 

[PR3MIUM]

Time to start looking for a replacement for my AC86u then…

(Not in a hurry, but a good Black Friday deal could help)

Getting a Corona Bonus from my work this month, so maybe buying 2x GT-AXE16000

 

[gpmc]

I got the confirmation that AC models will not be moved to 388 - only AX models will be.

The whole AX family (i.e. including RT-AX58U and above) or only a subset of them?

 

[skeal]

My Wireguard Client keeps stopping randomly on it's own When checking the status it says stopped.

Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Checking if WireGuard® VPN Peer KILL-Switch is required.....
Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Restarting WireGuard® to reinstate RPDB/firewall rules
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting WireGuard® VPN Peer stop (wg21 wgc1)
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting termination of WireGuard® VPN 'server' Peer ('wg21')
Oct 31 10:42:41 GT-AX11000-CF50 wg_manager-serverwg21: WireGuard® VPN 'server' Peer (wg21) on 10.50.1.1:51820 Terminated
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Requesting WireGuard® VPN Peer start (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Initialising Wireguard® VPN 'server' Peer (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialising WireGuard® VPN 'Server' Peer (wg21) on 10.50.1.1:51820
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialisation complete.

Where are you pulling these logs from? This firmware version if I'm not mistaken doesn't use Wireguard Manager so these logs do not apply here.

 

[skeal]

Noticed some Wireguard issues here too in my logs, even while not using Wireguard and just using OpenVPN
Did a reset this morning of my 3x RT-AX88U because of some connection drop-outs, previouse alpha didnt had this issue.

May  5 07:08:28 wlceventd: wlceventd_proc_event(486): eth6: Disassoc xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May  5 07:08:28 hostapd: eth6: STA xx:xx:xx:xx:xx IEEE 802.11: disassociated
May  5 07:09:00 rc_service: service 2542:notify_rc restart_wgc
May  5 07:09:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:09:24 dnsmasq-dhcp[1918]: DHCPREQUEST(br0) 192.xxx.xxx.xxx xx:xx:xx:xx:xx
May  5 07:09:24 dnsmasq-dhcp[1918]: DHCPACK(br0) 192.xxx.xxx.xxx xx:xx:xx:xx:xx DESKTOP-XXX
May  5 07:10:00 rc_service: service 2741:notify_rc restart_wgc
May  5 07:10:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:11:00 rc_service: service 2935:notify_rc restart_wgc
May  5 07:11:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:12:00 rc_service: service 3130:notify_rc restart_wgc
May  5 07:12:05 WireGuard: NTP time not sync in -1 seconds
May  5 07:13:00 rc_service: service 3322:notify_rc restart_wgc
May  5 07:13:05 WireGuard: NTP time not sync in -1 seconds
Oct 31 09:07:44 ntpd: Initial clock set
Oct 31 09:07:44 rc_service: ntpd_synced 3430:notify_rc restart_diskmon
Oct 31 09:07:44 disk_monitor: Finish
Oct 31 09:07:44 disk_monitor: be idle

These entries pertain to Wireguard being started before the NTP service has had a chance to sync time. Notice the May 5 date. This would be normal.

 

[Martin Fishkov]

You already have everything included in 388 in Asuswrt-Merlin 386 plus extras.

Any idea how lang that will keep us up to date? I mean, at some point I'd have to replace my AC68U (reluctantly).
On a side note: That sparked a short search for a list of currently recommended 'best of breed' Asus routers, but so far no cigar.. ANy thoughts on a suitable replacement for my rock-steady AC68U?

 

[Rajjco]

Where are you pulling these logs from? This firmware version if I'm not mistaken doesn't use Wireguard Manager so these logs do not apply here.

From System Messages flashed directly from 386.7_2

Not sure if wg_manager is running from jff partition since ssh is broken right now and can't login to router.

 

[ZebMcKayhan]

My Wireguard Client keeps stopping randomly on it's own When checking the status it says stopped.

Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Checking if WireGuard® VPN Peer KILL-Switch is required.....
Oct 31 10:42:00 GT-AX11000-CF50 (wg_firewall): 32248 Restarting WireGuard® to reinstate RPDB/firewall rules
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting WireGuard® VPN Peer stop (wg21 wgc1)
Oct 31 10:42:00 GT-AX11000-CF50 (wg_manager.sh): 32271 v4.18 Requesting termination of WireGuard® VPN 'server' Peer ('wg21')
Oct 31 10:42:41 GT-AX11000-CF50 wg_manager-serverwg21: WireGuard® VPN 'server' Peer (wg21) on 10.50.1.1:51820 Terminated
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Requesting WireGuard® VPN Peer start (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 (wg_manager.sh): 2806 v4.18 Initialising Wireguard® VPN 'server' Peer (wg21)
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialising WireGuard® VPN 'Server' Peer (wg21) on 10.50.1.1:51820
Oct 31 10:42:42 GT-AX11000-CF50 wg_manager-serverwg21: Initialisation complete.

These logs are from Wireguard Manager Addon script. if you are having issue with an addon, please post in the appropriate addon thread, i.e.:
https://www.snbforums.com/threads/session-manager-4th-thread.81187/

Or if you are migrating from Wireguard Manager, make sure ALL your peers are stopped in Wireguard Manager to avoid any port collisions and such.

ps: Your WGM peers could be stopped (and disabled) from the addon GUI if you cant reach SSH.

 

[skeal]

From System Messages flashed directly from 386.7_2

Not sure if wg_manager is running from jff partition since ssh is broken right now and can't login to router.

It is trying to run that's for sure. You will want to remove the wireguard_manager.sh script as the current firmware implantation doesn't require it in any way.

 

[skeal]

For the people that used the Wireguard solutions offered before this new firmware; please undo the changes from this addon before using the firmware's implementation, for best results.

 

[Rajjco]

For the people that used the Wireguard solutions offered before this new firmware; please undo the changes from this addon before using the firmware's implementation, for best results.

Yep did a factory reset and removed all addons now working properly. Will be running stock 388 Alpha now.

 

[STRUZZIN]

There is a issue with my 58U Nodes.
One Node is in our shop on a different Electric line.
If the House goes down or Main turned off the node(s) have to be restarted to connect up.

 

[skeal]

There is a issue with my 58U Nodes.
One Node is in our shop on a different Electric line.
If the House goes down or Main turned off the node(s) have to be restarted to connect up.

This is because the master would need to be running before the node can connect. If they are the same router, they very well could have similar boot time length, so restoring power at the same time wouldn't work. IMO.
I use AIMesh as well and because my node is an AC68U and my master is an AX88U the boot time length is way faster for my master the AX88U, so this never happens to me.

 

[skeal]

There is a issue with my 58U Nodes.
One Node is in our shop on a different Electric line.
If the House goes down or Main turned off the node(s) have to be restarted to connect up.

A JFFS script delaying something on the node could assist this issue, however, I leave the complex stuff too the experts on this forum.

 

[Elmer]

I got the confirmation that AC models will not be moved to 388 - only AX models will be.

I have an AX88 with three (much) older AC units being used for AImesh. Will this code split have any affect on mixing AX and AC units in an AImesh scenario?

 

[Suzib6sw]

There is a issue with my 58U Nodes.
One Node is in our shop on a different Electric line.
If the House goes down or Main turned off the node(s) have to be restarted to connect up. For.

I use 3 ax58u. 1 main and 2 nodes. All on this latest alpha. One node is ethernet backhaul, the other is wifi. If i power the main down, the nodes will reconnect once the main is back up. Ethernet 1st. I do have them both set to manual for the backhaul and both selected to refer to the main rather than "optimized " but thats just because my layout makes that the logical choice. The reconnect can take 5 mins one the main is back up.

 

[RMerlin]

The whole AX family (i.e. including RT-AX58U and above) or only a subset of them?

I don't know.

I have an AX88 with three (much) older AC units being used for AImesh. Will this code split have any affect on mixing AX and AC units in an AImesh scenario?

It shouldn't, AiMesh does not require identical firmware versions.