Release [Beta] Asuswrt-Merlin 384.19 beta is now available

[skeal]

Rock solid ready for prime time on my AX88U! Great work @RMerlin

 

[dave14305]

Beta2 doesn't seem to be on OneDrive, only SourceForge.

 

[RMerlin]

Just updated to Beta2 and almost everything working..... But not this, maby some more $VPN_UNIT code.

May  5 07:05:23 (vpnrouting.sh): 1387 Starting routing policy configuration for client <===>
logger -st "($(basename "$0"))" $$ "Starting routing policy configuration for client $VPN_UNIT"

@RMerlin thank you for new beta!

Leftover (and broken) debug logging it seems. I removed it.

 

[RMerlin]

Beta2 doesn't seem to be on OneDrive, only SourceForge.

Looks like Asustor's new Onedrive sync client is broken. It's only like the second time they break it in the past 12 months, and each time it's taken then 3+ months to fix their crap...

 

[taffeys]

Earlier today flashed both machines to 384.19_beta2 and still the same yellow flashing icon for the AC3100. Just now dirty flashed the AC3100 to ASUS 3.0.0.4.385_20630-ged5e4c3 . No more yellow flashing icon and no "Your router is running low on free JFFS storage..." warning. Something's not right.

 

[RMerlin]

Something's not right.

What makes you say that?

 

[Xentrk]

Just updated to Beta2 and almost everything working..... But not this, maby some more $VPN_UNIT code.

May  5 07:05:23 (vpnrouting.sh): 1387 Starting routing policy configuration for client <===>
logger -st "($(basename "$0"))" $$ "Starting routing policy configuration for client $VPN_UNIT"

@RMerlin thank you for new beta!

My mistake. I see @RMerlin fixed it already.

 

[Svenskmat]

RT-AC5300 Dirty upgrade from Beta1 to Beta2 - smooth upgrade everything is working great

 

[Tex Texan]

RT-AX88U owner here

Earlier today flashed both machines to 384.19_beta2 and still the same yellow flashing icon for the AC3100. Just now dirty flashed the AC3100 to ASUS 3.0.0.4.385_20630-ged5e4c3 . No more yellow flashing icon and no "Your router is running low on free JFFS storage..." warning. Something's not right.

384.19_Beta1 was the first time I'd ever got the JFFS storage error message on my RT-AX88U, having used both official and Merlin firmware previously. Let's see how Beta2 goes!

 

[New2This]

Just clear your browser cache or force a reload.

Thanks, Did the trick

 

[RMerlin]

384.19_Beta1 was the first time I'd ever got the JFFS storage error message on my RT-AX88U, having used both official and Merlin firmware previously.

JFFS low space notification is a new feature of 384.19.

 

[octopus]

Leftover (and broken) debug logging it seems. I removed it.

There is some more of them

/usr/bin/logger -t "openvpn-routing" "Configuring policy rules for client $VPN_UNIT"

my_logger "Completed routing policy configuration for client $VPN_UNIT"

my_logger "Refreshing policy rules for client $VPN_UNIT"

 

[RMerlin]

There is some more of them

/usr/bin/logger -t "openvpn-routing" "Configuring policy rules for client $VPN_UNIT"

my_logger "Completed routing policy configuration for client $VPN_UNIT"

my_logger "Refreshing policy rules for client $VPN_UNIT"

There is nothing wrong with those calls.

Aug 10 01:59:00 openvpn-routing: Starting routing policy configuration for client 2
Aug 10 01:59:00 openvpn-routing: Configuring policy rules for client 2
Aug 10 01:59:00 openvpn-routing: Creating VPN routing table (mode 2)
Aug 10 01:59:01 openvpn-routing: Removing route for 0.0.0.0/1 to tun12 from main routing table
Aug 10 01:59:01 openvpn-routing: Removing route for 128.0.0.0/1 to tun12 from main routing table
Aug 10 01:59:01 openvpn-routing: Adding route for 192.168.50.232 to  through VPN client 2
Aug 10 01:59:01 openvpn-routing: Adding route for 192.168.50.132 to  through VPN client 2
Aug 10 01:59:01 openvpn-routing: Completed routing policy configuration for client 2

The bug in the first log call that I removed was that it was referencing VPN_UNIT before any of the instance variables were set up.. All other calls happen afterward, therefore they work fine.

 

[octopus]

There is nothing wrong with those calls.

Aug 10 01:59:00 openvpn-routing: Starting routing policy configuration for client 2
Aug 10 01:59:00 openvpn-routing: Configuring policy rules for client 2
Aug 10 01:59:00 openvpn-routing: Creating VPN routing table (mode 2)
Aug 10 01:59:01 openvpn-routing: Removing route for 0.0.0.0/1 to tun12 from main routing table
Aug 10 01:59:01 openvpn-routing: Removing route for 128.0.0.0/1 to tun12 from main routing table
Aug 10 01:59:01 openvpn-routing: Adding route for 192.168.50.232 to  through VPN client 2
Aug 10 01:59:01 openvpn-routing: Adding route for 192.168.50.132 to  through VPN client 2
Aug 10 01:59:01 openvpn-routing: Completed routing policy configuration for client 2

The bug in the first log call that I removed was that it was referencing VPN_UNIT before any of the instance variables were set up.. All other calls happen afterward, therefore they work fine.

Thanks !

 

[heysoundude]

What makes you say that?

I choose to believe he was being sarcastic.

 

[heslo]

Updated perfectly on my RT88U; dirty flash from 384.18

 

[laracroftonline]

upgrade went smoothly, will report in a few hours how it's running!

 

[SheikhSheikha]

update from beta1, smooth walk in the park!

 

[mbze430]

I am still getting drops on the AX88U with my August Connect bridge.... every few days it will just drop off if I reboot the AX88U it will then reconnect. Other devices seems to be fine...strangest thing

 

[taffeys]

What makes you say that?