Beta Asuswrt-Merlin 388.1 Beta is available for select models

[abir1909]

I added wgserver-start, wgserver-stop, wgclient-start and wgclient-stop (with the unit number passed as argument).

This is in addition to the already existing postconf/custom config files.

Custom config:
wgclient<UNIT>
wgserver<UNIT>
wgserver_peer (for generated client config file)

Postconf:
wgclient<UNIT>.postconf
wgserver<UNIT>.postconf
wgserver_peer.postconf (for generated client config file)

I assume this is to use with SSH? whats the exact command to start wireguard client 1 to start? i am trying to run the command on ios shortcuts. i tried "Service wgclient1-start" nothing happended.
thx

 

[octopus]

Have you tried, "service wgclient1_start"

 

[RMerlin]

Just a little fail. Have been running the built-in wifi scanner (Wireless>Wifi Radar) and when I tried to download the database I was sent to the login page.after logging in I tried to download the database again and the same thing happened. I don't even know if it's relevant but in the logs:

I've encountered that issue in the past, but most of the related code is closed source, so I could never get to the root cause of it.

I assume this is to use with SSH? whats the exact command to start wireguard client 1 to start? i am trying to run the command on ios shortcuts. i tried "Service wgclient1-start" nothing happended.

Try service start_wgc1 or service start_wgc 1 ( i haven't tried it).

 

[Trent Hubbert]

Installed Beta3 today and 8 hours later need to reboot router.

Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable
Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable
Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable
Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable
Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable
Nov 22 20:38:26 dnsmasq[2004]: failed to send packet: Resource temporarily unavailable

any idea what is causing this? No addins installed.

AX86S

 

[Plak]

Beta 3 installed on axe16000. Running latest asus stock firmware 3.0.0.4.388_21617-g1288c22 on AI mesh node axe16000. Reset back to factory settings. Took some time to get everything setup and back online. So far running great first day.

 

[evo17paul]

Successfully upgraded from beta1 to beta1 and then beta3 this morning (didn't want to jump betas just in case)

Thanks for the good work Rmerlin

 

[abir1909]

I've encountered that issue in the past, but most of the related code is closed source, so I could never get to the root cause of it.




Try service start_wgc1 or service start_wgc 1 ( i haven't tried it).

Unfortunately none of the 3 options above works.
just FYI for the open VPN I am using “service start_vpnclient1” and it works!

 

[octopus]

Unfortunately none of the 3 options above works.
just FYI for the open VPN I am using “service start_vpnclient1” and it works!

It should be.

service start_wgc(unit)
service stop_wgc(unit)
service restart_wgc(unit)

Usage: service <action_service>

 

[GMcD79]

Recently performed a clean install on my RT-AX86U. Everything has been running great, although I noticed one small inconsistency between the Ports Section on the main page and the SysInfo page. The main page tells me my HIVE Hub is only connected at 10mb, whereas the sysinfo page shows the correct speed of 100mb.

Not earth shattering, but thought I’d mention it.

Thanks

 

[Ser9ei]

In case wg client is enable, all dns requests are go through the wg vpn.
As I see, /tmp/etc/wg/dns1.sh script create automatic and there are iptables rules to redirect dns requests.
RMerlin, could you please add functionality in the web interface to disable redirect of dns request?

 

[skeal]

In case wg client is enable, all dns requests are go through the wg vpn.
As I see, /tmp/etc/wg/dns1.sh script create automatic and there are iptables rules to redirect dns requests.
RMerlin, could you please add functionality in the web interface to disable redirect of dns request?

You can do this by using DNS director.

 

[abir1909]

It should be.

Usage: service <action_service>

Did you actually test it?
I tried again with different ssh client and still showing off.

 

[RMerlin]

RMerlin, could you please add functionality in the web interface to disable redirect of dns request?

Clear the DNS field on the WGC client config page.

 

[visortgw]

Beta 3 installed on axe16000. Running latest asus stock firmware 3.0.0.4.388_21617-g1288c22 on AI mesh node axe16000. Reset back to factory settings. Took some time to get everything setup and back online. So far running great first day.

Have you tried pushing guest network 1 WITH INTRANET DISABLED to AiMesh node? If not, could you please?

 

[dbell]

Have you tried pushing guest network 1 WITH INTRANET DISABLED to AiMesh node? If not, could you please?

I am running with this config on my pair of AX86u's. I had been running with intranet enabled due to an issue (either routing or not being able to lease a dhcp address) so the devices could not connect to the internet but that seems to be resolved now. All of my IoT devices (e.g. Ring, Nest, LG washer/dryer type stuff) are connected to that guest network (some on router and some on node) and all are online.

 

[visortgw]

I am running with this config on my pair of AX86u's. I had been running with intranet enabled due to an issue (either routing or not being able to lease a dhcp address) so the devices could not connect to the internet but that seems to be resolved now. All of my IoT devices (e.g. Ring, Nest, LG washer/dryer type stuff) are connected to that guest network (some on router and some on node) and all are online.

I have working GT-AX6000 as well. The issue appears to be specifically with GT-AXE16000 as primary router for both Merlin and Asus builds -- VLAN tags are not being passed to AiMesh nodes. I am awaiting response from Adus tech support escalation.

 

[unsynaps]

Woo! Router supports ECC once more.

 

[Treadler]

Same here, using the site you suggested.

I always have the IPv4 firewall enabled.
Its disabling the ”Enable IPv4 inbound firewall rules” that turned everything from ‘refused’ to ‘stealth’.

Now, for the first time ever, I’m seeing occasional dropped IPv6 packets in syslog.

 

[blackfireball5]

I just had the strangest thing happen. Out of nowhere a bunch of programs on my computer stopped being connected to the internet. However, I was still able to play the video game I was in (Overwatch 2). But programs like Chrome, Discord, Teamviewer, etc all stopped connecting to the internet. Then when I checked my phone, I noticed I wasn't connected to the wifi. I could see my SSID's, but when I tried to connect to them, nothing would happen. It wouldn't fail, or error, I would tap itm it would say connecting, then it would stop and nothing would happen.

I have never seen it where some programs on my ethernet wired computer could access the internet normally, but others completely couldn't.

I was able to access my router and modem fine. Ran diagnostics on modem (normal) and speed test from router (normal).

This was super unusual and I can't explain what caused it.

I rebooted the router from GUI and that fixed everything.

My log was just doing this over and over repeatedly during this time:

Nov 23 23:18:59 wlceventd: wlceventd_proc_event(469): eth10: Deauth_ind 2C:AA:8E:0C:26:C4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 23 23:18:59 wlceventd: wlceventd_proc_event(486): eth10: Disassoc 2C:AA:8E:0C:26:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 23 23:18:59 hostapd: eth10: STA 2c:aa:8e:0c:26:c4 IEEE 802.11: disassociated
Nov 23 23:18:59 hostapd: eth10: STA 2c:aa:8e:0c:26:c4 IEEE 802.11: disassociated
Nov 23 23:19:10 wlceventd: wlceventd_proc_event(505): eth10: Auth 2C:AA:8E:0B:F0:5E, status: Successful (0)
Nov 23 23:19:10 wlceventd: wlceventd_proc_event(534): eth10: Assoc 2C:AA:8E:0B:F0:5E, status: Successful (0)
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0b:f0:5e IEEE 802.11: associated
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0b:f0:5e RADIUS: starting accounting session 3B932C2AC5C40033
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0b:f0:5e WPA: pairwise key handshake completed (RSN)
Nov 23 23:19:10 wlceventd: wlceventd_proc_event(505): eth10: Auth 2C:AA:8E:0C:26:C4, status: Successful (0)
Nov 23 23:19:10 wlceventd: wlceventd_proc_event(534): eth10: Assoc 2C:AA:8E:0C:26:C4, status: Successful (0)
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0c:26:c4 IEEE 802.11: associated
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0c:26:c4 RADIUS: starting accounting session 8F56A27A7EEA9D3D
Nov 23 23:19:10 hostapd: eth10: STA 2c:aa:8e:0c:26:c4 WPA: pairwise key handshake completed (RSN)
Nov 23 23:19:16 wlceventd: wlceventd_proc_event(469): eth10: Deauth_ind 2C:AA:8E:0C:2D:FD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 23 23:19:16 wlceventd: wlceventd_proc_event(486): eth10: Disassoc 2C:AA:8E:0C:2D:FD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 23 23:19:16 hostapd: eth10: STA 2c:aa:8e:0c:2d:fd IEEE 802.11: disassociated
Nov 23 23:19:16 hostapd: eth10: STA 2c:aa:8e:0c:2d:fd IEEE 802.11: disassociated
Nov 23 23:19:17 wlceventd: wlceventd_proc_event(469): eth10: Deauth_ind 2C:AA:8E:A7:10:77, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 23 23:19:17 wlceventd: wlceventd_proc_event(486): eth10: Disassoc 2C:AA:8E:A7:10:77, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 23 23:19:17 hostapd: eth10: STA 2c:aa:8e:a7:10:77 IEEE 802.11: disassociated
Nov 23 23:19:17 hostapd: eth10: STA 2c:aa:8e:a7:10:77 IEEE 802.11: disassociated
Nov 23 23:19:27 wlceventd: wlceventd_proc_event(505): eth10: Auth 2C:AA:8E:0C:2D:FD, status: Successful (0)
Nov 23 23:19:27 wlceventd: wlceventd_proc_event(534): eth10: Assoc 2C:AA:8E:0C:2D:FD, status: Successful (0)
Nov 23 23:19:27 hostapd: eth10: STA 2c:aa:8e:0c:2d:fd IEEE 802.11: associated
Nov 23 23:19:27 hostapd: eth10: STA 2c:aa:8e:0c:2d:fd RADIUS: starting accounting session ED06BDCCA22F3742
Nov 23 23:19:27 hostapd: eth10: STA 2c:aa:8e:0c:2d:fd WPA: pairwise key handshake completed (RSN)
Nov 23 23:19:28 wlceventd: wlceventd_proc_event(505): eth10: Auth 2C:AA:8E:A7:10:77, status: Successful (0)
Nov 23 23:19:28 wlceventd: wlceventd_proc_event(534): eth10: Assoc 2C:AA:8E:A7:10:77, status: Successful (0)
Nov 23 23:19:28 hostapd: eth10: STA 2c:aa:8e:a7:10:77 IEEE 802.11: associated
Nov 23 23:19:28 hostapd: eth10: STA 2c:aa:8e:a7:10:77 RADIUS: starting accounting session 1A4B4A19F6167897
Nov 23 23:19:28 hostapd: eth10: STA 2c:aa:8e:a7:10:77 WPA: pairwise key handshake completed (RSN)

 

[blackfireball5]

From what I can tell, all the mac addresses listed that are being repeatedly deauthenticated are Wyze cams / smart outlets connected to my 2.4ghz network.