[Beta 380] Asuswrt-Merlin 380.69 Beta is now available

[Sanna1967]

Looks like the System Status - Ethernet Ports has stop working on 380.69_beta1

https://www.snbforums.com/threads/beta-380-asuswrt-merlin-380-69-beta-is-now-available.42660/#post-363382

 

[Martin_D]

https://www.snbforums.com/threads/beta-380-asuswrt-merlin-380-69-beta-is-now-available.42660/#post-363382

Sorry didn't see that

 

[RMerlin]

wo concurrent active VPN clients 1 & 2 both with 'Accept DNS Configuration=Exclusive'

I just tested it, and I couldn't reproduce it here. Can you detail the steps you used? This is what I did here:

1) Configured VPN Client 1, started it with 1 policy rule client
2) Configured VPN client 2, started it with 1 policy rule client
3) Enabled DNSFilter, added one client set to OpenDNS
4) Checked output of the nat table - both DNSVPN1 and 2 were still there, along with their respective clients.

Restarting DNSFIlter involves restarting dnsmasq and the firewall, so check these two to make sure you don't have any custom script interfering. Also, make sure you have both VPN client's Firewall set to "Automatic".

 

[elnash]

Hi, I've been testing beta 380.69 on an 87u asus and I've had Teredo problems on an xbox one x. I had to return to 380.68_4 and everything returned to normal, do you know merlin to what can this be? sorry for my English since I have done with the google translator, I hope you understand.

 

[Martineau]

Also, make sure you have both VPN client's Firewall set to "Automatic".

Yes they are both set to Automatic.

Restarting DNSFIlter involves restarting dnsmasq and the firewall, so check these two to make sure you don't have any custom script interfering.

I do have custom scripts called from firewall-start/nat-start but they only append rules to the existing DNSVPNx chains........ there has never been any delete code for the DNSVPNx chains in any of my scripts.

However, on saturday morning I did have a brief test of the v382_Alpha on the RT-AC68U and ended up having to edit some scripts having encountered v382 issues.

e.g. check the version number

FIRMWARE=$(echo $(nvram get buildno) | awk 'BEGIN { FS = "." } {printf("%03d%02d",$1,$2)}')

if [ "$FIRMWARE" -lt 38063 ];then
  <do something>    # If firmware version <380.63 then <do something>
fi

if [ "$FIRMWARE" -ge 38201 ];then
  < file / etc /ethers no longer created but
         / etc /dnsmasq.conf now populated with multiple 'dhcp-host=' statements instead.
        Duplicates due to legacy dnsmasq.conf.add entries prevents DNSMASQ starting :-(
fi

I then installed v380.69Beta and factory reset and restored NVRAM using @john9527's utility but clearly retained the modified scripts to accommodate my v382.2 fixes.

It could be possible that I may have broken something, so I'll probably have to wait until the weekend to see if a clean v380.90 reinstall with only v380.68 scripts resolves it.

 

[RMerlin]

if [ "$FIRMWARE" -lt 38063 ];then

That won't work because 3821 < 38063. You have to compare major and minor versions separately, i.e. 380 vs 382 and 63 vs 1.

 

[shooter40sw]

So far so good for me, tested VPN no issues at the time with the beta