What's new

[ 386.4 alpha Build(s) ] Testing available build(s)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Repeated starts every minute that seems to not find itself. :)
Code:
Nov 16 11:55:00 rc_service: service 10253:notify_rc restart_wgc
Nov 16 11:55:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:56:00 rc_service: service 10438:notify_rc restart_wgc
Nov 16 11:56:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:57:00 rc_service: service 10628:notify_rc restart_wgc
Nov 16 11:57:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:58:00 rc_service: service 10813:notify_rc restart_wgc
Nov 16 11:58:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:59:00 rc_service: service 10998:notify_rc restart_wgc
Nov 16 11:59:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:00:00 rc_service: service 11185:notify_rc restart_wgc
Nov 16 12:00:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:01:00 rc_service: service 11738:notify_rc restart_wgc
Nov 16 12:01:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:02:00 rc_service: service 11924:notify_rc restart_wgc
Nov 16 12:02:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:03:00 rc_service: service 12109:notify_rc restart_wgc
Nov 16 12:03:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:04:00 rc_service: service 12294:notify_rc restart_wgc
Nov 16 12:04:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:05:00 rc_service: service 12479:notify_rc restart_wgc
Nov 16 12:05:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:06:00 rc_service: service 12670:notify_rc restart_wgc
Nov 16 12:06:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:07:00 rc_service: service 12867:notify_rc restart_wgc
Nov 16 12:07:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)

RT-AX88U_386.4_alpha2-g952c6bdecc
 
Updated my router from alpha2 da82 to alpha2 decc build but when clicking upload on the firmware update page to update the node the url is constructed with http instead of https and the :8443 port is missing and thus fails to connect - had to copy url and manually change to https: and append :8443 then it works. I don't recall an issue with updating the node to da82 build, so wondering if this is a regression ?

1637085290170.png
 
The RT-AX56U, Alpha 1 and 2, do not see the "Download Master" already installed on the HDD. The installation also doesn't work, it counts up to 99 percent and nothing happens. Returning to 386.3_2 "Download Master" it works again.
 
Repeated starts every minute that seems to not find itself. :)
Code:
Nov 16 11:55:00 rc_service: service 10253:notify_rc restart_wgc
Nov 16 11:55:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:56:00 rc_service: service 10438:notify_rc restart_wgc
Nov 16 11:56:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:57:00 rc_service: service 10628:notify_rc restart_wgc
Nov 16 11:57:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:58:00 rc_service: service 10813:notify_rc restart_wgc
Nov 16 11:58:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 11:59:00 rc_service: service 10998:notify_rc restart_wgc
Nov 16 11:59:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:00:00 rc_service: service 11185:notify_rc restart_wgc
Nov 16 12:00:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:01:00 rc_service: service 11738:notify_rc restart_wgc
Nov 16 12:01:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:02:00 rc_service: service 11924:notify_rc restart_wgc
Nov 16 12:02:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:03:00 rc_service: service 12109:notify_rc restart_wgc
Nov 16 12:03:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:04:00 rc_service: service 12294:notify_rc restart_wgc
Nov 16 12:04:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:05:00 rc_service: service 12479:notify_rc restart_wgc
Nov 16 12:05:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:06:00 rc_service: service 12670:notify_rc restart_wgc
Nov 16 12:06:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)
Nov 16 12:07:00 rc_service: service 12867:notify_rc restart_wgc
Nov 16 12:07:00 custom_script: Running /jffs/scripts/service-event (args: restart wgc)

RT-AX88U_386.4_alpha2-g952c6bdecc
Seeing this on my AX86U router but not on the AX86U node. Seems to have stopped after another router restart.
 
Repeated starts every minute that seems to not find itself.
Probably means that in the past you ran an Asus beta that had Wireguard enabled, and those nvram variables are still there. You will have to sort that out, either through a factory default reset, or by clearing the wgc related variables in nvram (there`s probably a wgc_enable or something like that, you will have to check yourself).
 
Probably means that in the past you ran an Asus beta that had Wireguard enabled, and those nvram variables are still there. You will have to sort that out, either through a factory default reset, or by clearing the wgc related variables in nvram (there`s probably a wgc_enable or something like that, you will have to check yourself).
No Asus beta that had wireguard enabled ever loaded with this router only yours.
 
I see these - I can't remember the last stock version that was on this router.

1637109408821.png


@bluepoint - see if setting it to zero helps: nvram set wgc_enable=0
 
I see these - I can't remember the last stock version that was on this router.

View attachment 37392

@bluepoint - see if setting it to zero helps: nvram set wgc_enable=0
It already is just like yours.
Code:
ASUSWRT-Merlin RT-AX88U 386.4_alpha2-g952c6bdecc Tue Nov 16 04:41:20 UTC 2021
xxxx@RT-AX88U-XXXX:/tmp/home/root# nvram getall | grep wgc
size: 76095 bytes (54977 left)
wgc_addr=
wgc_aips=
wgc_alive=25
wgc_dns=
wgc_enable=0
wgc_ep_addr=
wgc_ep_port=
wgc_nat=1
wgc_ppub=
wgc_priv=
wgc_psk=
wgc_unit=1
 
I, too, have the wgc nvram settings and log entries. Lucky for me, my usb_mount script logs a 'cru l' command to verify my socks5 proxy starts/stops. It shows an entry of:

*/1 * * * * service restart_wgc #WireGuard#

which one can eliminate from the command line with:

cru d WireGuard

stopping the every minute check.
 
It already is just like yours.
Code:
ASUSWRT-Merlin RT-AX88U 386.4_alpha2-g952c6bdecc Tue Nov 16 04:41:20 UTC 2021
xxxx@RT-AX88U-XXXX:/tmp/home/root# nvram getall | grep wgc
size: 76095 bytes (54977 left)
wgc_addr=
wgc_aips=
wgc_alive=25
wgc_dns=
wgc_enable=0
wgc_ep_addr=
wgc_ep_port=
wgc_nat=1
wgc_ppub=
wgc_priv=
wgc_psk=
wgc_unit=1
@gerardr @dbell
Do you have diversion and ntpmerlin addons? It doesn't seems to affect many with this wgc bug so maybe there is something common amongst us?
 
I, too, have the wgc nvram settings and log entries. Lucky for me, my usb_mount script logs a 'cru l' command to verify my socks5 proxy starts/stops. It shows an entry of:

*/1 * * * * service restart_wgc #WireGuard#

which one can eliminate from the command line with:

cru d WireGuard

stopping the every minute check.

And rebooting brings the check back.
 
And rebooting brings the check back.
Was this done from a dirty upgrade? I wonder if the latest alpha requires a factory reset to initialize (properly) these new nvram settings.
 
And rebooting brings the check back.
Hmm ... I have an RT-AX3000 (RT-AX58U firmware), and once I removed the cron entry, it did not come back, so I had concluded it was a first-run issue. Sorry it appears to be more complicated.
 
@gerardr @dbell
Do you have diversion and ntpmerlin addons? It doesn't seems to affect many with this wgc bug so maybe there is something common amongst us?
No add-ons. I'm running the RT-AX58U firmware on an RT-AX3000, and have never even setup a VPN, so I'm not sure how I got the 'wgc_XXX' variables in my nvram. Since it was asked in other posts, this was a dirty upgrade from alpha2-ga85421da82 to alpha2-g952c6bdecc. I don't remember this issue being in the alpha1 or the 2nd alpha2. I did avoid loading the 1st apha2 firmware, having delayed enough for the 2nd one to post.
 
Did a dirty flash to to the newest alpha from the previous one on an AX88U/AX68U node with no issues since yesterday 11/16. I'm not running much on the main router. No VPN servers/clients as I'm running those on my Opnsense box.
 
Merlin may already be on it locally, but it looks like this function results in the cron job being setup if time is not synced yet.


I'm not looking or touching the Wireguard code until it comes out of beta with Asus, which means not until the RC3 (386_5xxxx) release next year.
 
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