Release Asuswrt-Merlin 386.7 is now available for all models

Status
Not open for further replies.

visortgw

Very Senior Member
Which software are you using on Mac to make the OVPN connection?
I have been using Viscosity (Spark Labs) for years. Viscosity:
  • supports both TUN and TAP connections;
  • is well supported (and updated regularly);
  • is available for macOS and Windows; and
  • is very reasonably priced.
 

RMerlin

Asuswrt-Merlin dev
Any of you guys with WiFi or WAN issues also using Home Assistant and ASUSWRT integration? Disabling the integration appears to fix my issues for now...

@RMerlin I know there is a way to schedule a reboot of the main router, but as I'm using 2XT8's as nodes, is it possible to add a checkbox to schedule a reboot for the whole system including nodes as the button under system settings does trigger a complete reboot?
I have no control over AiMesh nodes.
 

Chuckles67

Regular Contributor
I have been using Viscosity (Spark Labs) for years. Viscosity:
  • supports both TUN and TAP connections;
  • is well supported (and updated regularly);
  • is available for macOS and Windows; and
  • is very reasonably priced.
Thanks for this.
 

Neil62

Senior Member
Any of you guys with WiFi or WAN issues also using Home Assistant and ASUSWRT integration? Disabling the integration appears to fix my issues for now...

@RMerlin I know there is a way to schedule a reboot of the main router, but as I'm using 2XT8's as nodes, is it possible to add a checkbox to schedule a reboot for the whole system including nodes as the button under system settings does trigger a complete reboot?
If you setup a schedule rebbot on the Main router it will also reboot the nodes. Or using the GUI, AiMesh > System Settings > System Reboot, will also reboot the nodes.
 

rwijnhov

Occasional Visitor
I have some weird issues with my ax6000 and 2 ac86u as nodes. With stock firmware alle devices roam nicely and all iot connects fine. With merlin on the ax6000. I get really sticky devices and they won't roam correctly. Plus some 2.4 iot devices won't connect. I did both clean install and dirty upgrade. Both same issue.
 

Martin Fishkov

Regular Contributor
Update on the speedtest:

I downgraded to 386.7_0 (the version I used speedtest with before) but no luck. There must be a problem elsewhere, maybe my internet connectiob isn't as steady as I thought.
Looking for ways to test this. I have conmon running, that looks fine:


Time ↓TargetDuration (s)Ping (ms)Jitter (ms)Line Quality (%)
2022-08-03 08:54:168.8.8.8105.5270.423100.0


As this is not related to the update I will start a new thread when I have a bit more time.

<edit>
I noticed IP addresses weren't resolved in the SSH terminal (updating amtm scripts), so I reverted to ISP DNS. Now it works, so this was probably the cause.

My (not working ) WAN DNS settings were:

ServiceDNS ServerDescription
Privacy-respecting
Quad99.9.9.11
149.112.112.11
Collects no information about users, and is governed by Swiss privacy law. Learn more


Thanks for your time</edit>
 
Last edited:

torstein

Regular Contributor
Which software are you using on Mac to make the OVPN connection?
I’m using the official OpenVPN Connect 3.3.6 app for macOS and 3.3.0 for iOS. Both are latest versions. :) I’m noticing that even after setting up a new openvpn server on the router with a new config file, my mac and iphone is slow to connect and i have to try several times for OpenVPN to establish a connection. On 386.5_2 the OpenVPN connection was instantaneous. Not so on 386.7_2.

Maybe Rmerlins recent Openvpn changes in regard to NAT and IPv6 together with the leatest OpenVPN 2.5.7 server is causing the issues?
 
Last edited:

clweb

Occasional Visitor
Update on the speedtest:

I downgraded to 386.7_0 (the version I used speedtest with before) but no luck. There must be a problem elsewhere, maybe my internet connectiob isn't as steady as I thought.
Looking for ways to test this. I have conmon running, that looks fine:


Time ↓TargetDuration (s)Ping (ms)Jitter (ms)Line Quality (%)
2022-08-03 08:54:168.8.8.8105.5270.423100.0


As this is not related to the update I will start a new thread when I have a bit more time.

<edit>
I noticed IP addresses weren't resolved in the SSH terminal (updating amtm scripts), so I reverted to ISP DNS. Now it works, so this was probably the cause.

My (not working ) WAN DNS settings were:

ServiceDNS ServerDescription
Privacy-respecting
Quad99.9.9.11
149.112.112.11
Collects no information about users, and is governed by Swiss privacy law. Learn more


Thanks for your time</edit>
I also have Quad9 as DNS server and no problem with Speedtest or something else. Router is AX58U with Merlin 386.7_2.
 

Jaime Alvarez

Regular Contributor
I’m using the official OpenVPN Connect 3.3.6 app for macOS and 3.3.0 for iOS. Both are latest versions. :) I’m noticing that even after setting up a new openvpn server on the router with a new config file, my mac and iphone is slow to connect and i have to try several times for OpenVPN to establish a connection. On 386.5_2 the OpenVPN connection was instantaneous. Not so on 386.7_2.

Maybe Rmerlins recent Openvpn changes in regard to NAT and IPv6 together with the leatest OpenVPN 2.5.7 server is causing the issues?
I'm using Tunneblick to connect to an AX86U without issues.
 

John Fitzgerald

Senior Member
saves as .cfg here, latest ff 103.0.1
What is different in your setup that it works for you?
I have not made any changes on my end and it just started saving as .txt
I can rename the file but I can't figure why I'm affected and others are not.

I use duckduckgo and ublock origin as add ins.
Windows 10, up to date.

Any insights would be helpful.
 

shabbs

Very Senior Member

BreakingDad

Very Senior Member
What is different in your setup that it works for you?
I have not made any changes on my end and it just started saving as .txt
I can rename the file but I can't figure why I'm affected and others are not.

I use duckduckgo and ublock origin as add ins.
Windows 10, up to date.

Any insights would be helpful.
Only extensions I have are ublock origin, malwarebytes and dashlane.

I have done a lot of privacy mods to firefox over a long time, but I doubt these would be anything to do with your issue.

Couple of thoughts, are you sure it's not windows making it save as .txt and not firefox? Have you tried refreshing firefox?

have you tried "saving as all files" and not as .txt

or..
  • open up the folder your config is in
  • on the top of that window, click 'view'
  • there should be an option 'file name extensions' with a check box next to it
  • click said checkbox
  • rename file filename.cfg
 

John Fitzgerald

Senior Member
Only extensions I have are ublock origin, malwarebytes and dashlane.

I have done a lot of privacy mods to firefox over a long time, but I doubt these would be anything to do with your issue.

Couple of thoughts, are you sure it's not windows making it save as .txt and not firefox? Have you tried refreshing firefox?

have you tried "saving as all files" and not as .txt

or..
  • open up the folder your config is in
  • on the top of that window, click 'view'
  • there should be an option 'file name extensions' with a check box next to it
  • click said checkbox
  • rename file filename.cfg
I did a FF Refresh and that fixed the issue, now I have to rebuild some things.

Thanks, don't know how it became corrupted.
 

BreakingDad

Very Senior Member
I did a FF Refresh and that fixed the issue, now I have to rebuild some things.

Thanks, don't know how it became corrupted.
Nice, glad you sorted it, when you have it all working as you wish, any performance or privacy tweaks etc. Save the config, so you can easily restore it after events like this.
 
Last edited:

The PyroPath

Occasional Visitor
Ok, this is driving me crazy. Disabled the asuswrt extension, but no less than 24 hours later my devices are connecting and disconnecting from WiFi. Started noticing while watching TV that the TV would display a notification again and again about WiFi being disconnected. See lots and lots of associated and disassociated messages in the log with only seconds in between. What's going on?:

Code:
Aug  3 21:10:33 wlceventd: wlceventd_proc_event(505): eth7: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:10:33 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:10:33 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:10:55 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:10:55 wlceventd: wlceventd_proc_event(505): eth7: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:10:55 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:19 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:19 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:24 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:11:24 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:11:38 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:11:38 wlceventd: wlceventd_proc_event(505): eth7: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:38 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:52 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:11:52 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:12:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 88:46:04:F5:80:3A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:12:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 88:46:04:F5:80:3A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:12:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 88:46:04:F5:80:3A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:12:59 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 88:46:04:F5:80:3A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug  3 21:13:22 wlceventd: wlceventd_proc_event(505): eth6: Auth 88:46:04:F5:80:3A, status: Successful (0)
Aug  3 21:13:22 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc 88:46:04:F5:80:3A, status: Successful (0)
Aug  3 21:13:27 wlceventd: wlceventd_proc_event(505): eth6: Auth 70:F0:88:31:71:4A, status: Successful (0)
Aug  3 21:13:27 wlceventd: wlceventd_proc_event(534): eth6: Assoc 70:F0:88:31:71:4A, status: Successful (0)
Aug  3 21:13:27 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 88:46:04:F5:80:3A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:27 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 88:46:04:F5:80:3A, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:33 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 70:F0:88:31:71:4A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:33 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 70:F0:88:31:71:4A, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:39 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:39 wlceventd: wlceventd_proc_event(505): eth7: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:39 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:42 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:42 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:42 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:43 wlceventd: wlceventd_proc_event(486): eth6: Disassoc BE:77:BA:38:88:4D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug  3 21:13:45 wlceventd: wlceventd_proc_event(505): eth6: Auth 70:F0:88:31:71:4A, status: Successful (0)
Aug  3 21:13:45 wlceventd: wlceventd_proc_event(534): eth6: Assoc 70:F0:88:31:71:4A, status: Successful (0)
Aug  3 21:13:46 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 48:5F:99:15:D9:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:13:46 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 48:5F:99:15:D9:AB, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:57 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:13:58 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:14:02 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:14:03 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:14:03 wlceventd: wlceventd_proc_event(505): eth7: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:14:03 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:14:03 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind BE:77:BA:38:88:4D, status: 0, reason: Unspecified reason (1)
Aug  3 21:14:28 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 70:F0:88:31:71:4A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Aug  3 21:14:28 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 70:F0:88:31:71:4A, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Aug  3 21:14:31 wlceventd: wlceventd_proc_event(505): eth6: Auth BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:14:31 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc BE:77:BA:38:88:4D, status: Successful (0)
Aug  3 21:14:32 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 70:F0:88:31:71:4A, status: 0, reason: Unspecified reason (1)
Aug  3 21:14:32 wlceventd: wlceventd_proc_event(505): eth7: Auth 70:F0:88:31:71:4A, status: Successful (0)
 

det721

Part of the Furniture
Logs have been showing this for years and Asus wont fix it. That said if your devices are disconnecting at will with out you doing yourself there may be another issue going on. I get tons of these to but only when something is restarted or it leaves the house and returns.
 

octopus

Part of the Furniture
Logs have been showing this for years and Asus wont fix it. That said if your devices are disconnecting at will with out you doing yourself there may be another issue going on. I get tons of these to but only when something is restarted or it leaves the house and returns.
It's nothing wrong, probably some debug message they have forget to turn off.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top