Beta Asuswrt-Merlin 386.3 beta is now available

[visortgw]

were do I find "Redirect Internet Traffic"?

On the VPN Client page, just above Custom Configuration.

 

[John Adler]

On the VPN Client page, just above Custom Configuration.

today is not my day...
I cannot see it...
sorry...

 

[dave14305]

today is not my day...
I cannot see it...
sorry...

Keep scrolling down.

 

[shabbs]

today is not my day...
I cannot see it...
sorry...

Scroll down near the bottom...

 

[Clark Griswald]

Just Keep Scrolling
Just keep Scrolling

 

[Deleted member 22229]

Beta 1 and 2 ran great on my AC3100 and AX58U. So where is Beta 3 ?

 

[John Adler]

Scroll down near the bottom...

Many, many thanks !
have a nice evening !
it worked out perfect !

 

[The Pook]

anyone know if 386.3_x fixed the issue with EEE randomly turning off?

I can force it back on through SSH on 386.2_4 but it always randomly turns back off. CPU temp difference is nearly 25C (low 70s vs mid 90s)

 

[L&LD]

What router are you talking about? What is EEE? What do your tests conclude about the random issue?

 

[shabbs]

EEE: https://en.wikipedia.org/wiki/Energy-Efficient_Ethernet

 

[L&LD]

Doesn't seem that important inside most homes (with such few Ethernet runs).

 

[Deleted member 22229]

Doesn't seem that important inside most homes (with such few Ethernet runs).

Thats not the point the poster is looking to reduce the temp issue. I think Asus changed something with EEE to make the router run cooler and that change seems to revert itself.

 

[The Pook]

What router are you talking about? What is EEE? What do your tests conclude about the random issue?

RT-AC86U.

Not sure what tests I'm supposed to perform (lol), the issue is pretty straight forward. I turn EEE on, it stays on for a bit, then turns off. I can turn it back on but it always eventually turns back off.

I typically don't SSH into my router on a routine so I dunno how long it stays on before it turns off, but it's at least a couple hours.

EEE is supposed to turn off when you enable QoS/fq_codel but I'm not using either. It should stay on, AFAIK.

Thats not the point the poster is looking to reduce the temp issue. I think Asus changed something with EEE to make the router run cooler and that change seems to revert itself.

pretty much. not a huge deal because I'm not throttling but it's a pretty significant increase in temperature for no reason.

 

[L&LD]

If the router is acting 'weird', time for a reset. If it continues to be weird afterward, the hardware is highly suspect (if the testing/setup is properly executed).

Fully Reset Router and Network

Best Practice Update/Setup Router/AiMesh Node(s) 2021

About L&LD

 

[The Pook]

already been done. happens on the factory firmware too. it's just a bug and/or because of some other setting conflicting with it that I'm unaware of, I'm just assuming the former.

 

[bakgwei]

Quick question: My goal is to have some redundancy on my VPN - if VPN-Server 1 goes down, the system will switch to VPN2, then VPN3. If all three servers are not reachable, the kill switch is supposed to kick in. My current setup is seen below. My questions would be, and any help is much appreciated:

1) Would these setting alow me the desired VPN redundancy?
2) Would VPN2 and VPN3 need to be set to ON? Or could I leave them OFF ("Stop Client"), and the router would switch them ON automatically if VPN1 goes down and it is looking to enforce policy rule no 2?
3) If they have to be switched ON for the redundant setup to work: Are the constantly connected to the VPN (as the status is "Connected")? My VPN provider only allows six connected devices - so having three connections from my router would be a shame.

 

[RMerlin]

Beta 3 has been uploaded. Changes since beta 2:

b450eefd91 Updated documentation
352ab973d5 inadyn: handle Freedns authentication errors as such; improve error logging
dbfafff825 openvpn: only set error state in nvram on fatal config errors
c157287738 libovpn: only enforce DNS exclusive for a client if the rule has no remote IP specified
8a80d88fa1 Bump revision to beta 3
2c88c8ee59 rc: remove code handling cleanup of old 1.xxx TrendMicro signatures
7a37a1eaed libovpn: add log message when creating RPDB rule for OVPN_RGW_ALL mode

 

[shabbs]

BOOM!

 

[JohnD5000]

Beta 3 has been uploaded. Changes since beta 2:

b450eefd91 Updated documentation
352ab973d5 inadyn: handle Freedns authentication errors as such; improve error logging
dbfafff825 openvpn: only set error state in nvram on fatal config errors
c157287738 libovpn: only enforce DNS exclusive for a client if the rule has no remote IP specified
8a80d88fa1 Bump revision to beta 3
2c88c8ee59 rc: remove code handling cleanup of old 1.xxx TrendMicro signatures
7a37a1eaed libovpn: add log message when creating RPDB rule for OVPN_RGW_ALL mode

Quick testing on Beta3 (dirty upgrade)
dbfafff825 openvpn: only set error state in nvram on fatal config errors
seems to have fixed my VPN issue we discussed and seems to be working as expected now.

 

[HappyJuicy]

Quick question: My goal is to have some redundancy on my VPN - if VPN-Server 1 goes down, the system will switch to VPN2, then VPN3. If all three servers are not reachable, the kill switch is supposed to kick in. My current setup is seen below. My questions would be, and any help is much appreciated:

1) Would these setting alow me the desired VPN redundancy?
2) Would VPN2 and VPN3 need to be set to ON? Or could I leave them OFF ("Stop Client"), and the router would switch them ON automatically if VPN1 goes down and it is looking to enforce policy rule no 2?
3) If they have to be switched ON for the redundant setup to work: Are the constantly connected to the VPN (as the status is "Connected")? My VPN provider only allows six connected devices - so having three connections from my router would be a shame.

View attachment 35086

1) yes
2) yes
3) yes

It seem to be configured fine, but with the old firmwares with such setting, I could not excluse a device or website from the chain.
I want also to know why. I have just installed the firmware now. I have not tested anything yet.

BTW I see the kill switch is configured to the last active client only, it is well configurated!