RT-AX88U 384.10 firmware issues

[Phil Outram]

Hi

I have a couple of problems with my RT-AX88U running firmware version 384.10:

1) After several days of uptime (between 4 and 6) the WAN becomes disconnected and there is no internet access. I have a draytek vigor 130 modem connected to a vdsl ppoe service. Rebooting the modem resolves the fault, which then occurs again after a few days. This does not occur with either the stock firmware or another router connected to the same modem.

2) After several days the router no longer obtains any updated AI protection definition updates. Performing a manual check on the definitions reports that it is the latest version, however if you reboot the router then it will update to a later version.

Does anyone else experience the same issues?

 

[RMerlin]

If rebooting the modem fixes it, then this is either a modem or an ISP issue.

 

[Phil Outram]

Thanks for the response. However I am not sure this is entirely correct because as mentioned in my original post above, it does not occur with the stock ASUS firmware or another router using the same modem.

The AI protection problem is only resolved by a reboot of the router, and not if just the modem is rebooted.

 

[L&LD]

Thanks for the response. However I am not sure this is entirely correct because as mentioned in my original post above, it does not occur with the stock ASUS firmware or another router using the same modem.

The AI protection problem is only resolved by a reboot of the router, and not if just the modem is rebooted.

Have you unplugged the ac from your router and modem (and not just from the wall socket) and left it off at least a full 10 minutes but preferably 60 minutes or so? After this wait, plug in your modem and wait 5 minutes or more for it to fully boot up. Then plug in your router.

This little 'reset' between your equipment and the ISP may be all that is needed. Give it a try.

 

[Hozz]

Hi

I have a couple of problems with my RT-AX88U running firmware version 384.10:

1) After several days of uptime (between 4 and 6) the WAN becomes disconnected and there is no internet access. I have a draytek vigor 130 modem connected to a vdsl ppoe service. Rebooting the modem resolves the fault, which then occurs again after a few days. This does not occur with either the stock firmware or another router connected to the same modem.

2) After several days the router no longer obtains any updated AI protection definition updates. Performing a manual check on the definitions reports that it is the latest version, however if you reboot the router then it will update to a later version.

Does anyone else experience the same issues?

I use a Vigor 130 with an Asus RT-AC86U.
I find the Vigor 130 pretty rock solid in terms of connection though I think the upload speeds are possibly a bit slower than a BT Homehub 6.
On the other hand the BT Homehub regularly disconnected.
Incidentally there are other firmwares available for the Vigor 130 see attached, though you will have to email support@draytek.co.uk to get them.

 

[Phil Outram]

I've discovered the cause of the problem.

There appears to be an issue with the vpn client policy based routing. I have a nord vpn client set up with a policy to route all traffic from just one specific machine on my network over it with everything else going out via the normal connection.

If for any reason the nord vpn stops responding to dns requests then I lose internet access for all devices not just the one the policy is set to route over it.

I know the policy is working correctly when nord vpn is working as looking up my external IP reveals my regular static IP from every device except for the one device being routed over the vpn.

This appears to be a bug so I've disabled the vpn client on the router and will switch to using the nord vpn app instead for now.

 

[Martineau]

I've discovered the cause of the problem.

There appears to be an issue with the vpn client policy based routing. I have a nord vpn client set up with a policy to route all traffic from just one specific machine on my network over it with everything else going out via the normal connection.

If for any reason the nord vpn stops responding to dns requests then I lose internet access for all devices not just the one the policy is set to route over it.

I know the policy is working correctly when nord vpn is working as looking up my external IP reveals my regular static IP from every device except for the one device being routed over the vpn.

This appears to be a bug so I've disabled the vpn client on the router and will switch to using the nord vpn app instead for now.

Have you tested "Accept DNS Configuration=Exclusive" ? …. it may not be appropriate in your case, but hopefully would explain why the DNS issue occurs.

 

[Xentrk]

I've discovered the cause of the problem.

There appears to be an issue with the vpn client policy based routing. I have a nord vpn client set up with a policy to route all traffic from just one specific machine on my network over it with everything else going out via the normal connection.

If for any reason the nord vpn stops responding to dns requests then I lose internet access for all devices not just the one the policy is set to route over it.

I know the policy is working correctly when nord vpn is working as looking up my external IP reveals my regular static IP from every device except for the one device being routed over the vpn.

This appears to be a bug so I've disabled the vpn client on the router and will switch to using the nord vpn app instead for now.

That’s not a bug. It’s a feature.

This may provide some additional info.

https://www.snbforums.com/threads/r...10-is-now-available.55742/page-15#post-476198

Check the Block traffic if tunnel goes down setting too.

 

[Phil Outram]

How is this a 'feature'?

Only one client is set via policy to route over the vpn, therefore if the vpn goes down only that client should be effected, not every single client on my internal lan including the router itself.

 

[skeal]

How is this a 'feature'?

Only one client is set via policy to route over the vpn, therefore if the vpn goes down only that client should be effected, not every single client on my internal lan including the router itself.

What gets blocked when the vpn goes down is the clients governed by policy routing not the whole network, unless defined that way.

 

[Phil Outram]

What gets blocked when the vpn goes down is the clients governed by policy routing not the whole network, unless defined that way.

That is what is supposed to happen, but it is not what actually happens. As per my post above, when the vpn goes down I lose internet access on all my devices, and not just the one that is set to route over the vpn.

To be clear, only ONE pc on my network is set to route over the vpn via the policy based rules, yet when the vpn goes down ALL devices lose connection.

 

[skeal]

That is what is supposed to happen, but it is not what actually happens. As per my post above, when the vpn goes down I lose internet access on all my devices, and not just the one that is set to route over the vpn.

To be clear, only ONE pc on my network is set to route over the vpn via the policy based rules, yet when the vpn goes down ALL devices lose connection.

I would recommend a factory reset. Per @L&LD has a link on his signature that is called M&M full reset. Try it should sort you out. I use the same router as you ad have this setting working for ever now.

 

[Xentrk]

How is this a 'feature'?

Only one client is set via policy to route over the vpn, therefore if the vpn goes down only that client should be effected, not every single client on my internal lan including the router itself.

I think I know what the issue is. If you are using Policy Rules, make sure you specify the router's IP address in the list of clients and route it to the WAN. Make it the first entry in the list to the firmware assigns it a higher priority than the LAN client rules. To see how this works, type the command ip rule in an SSH session.

Source: https://x3mtek.com/torguard-openvpn-2-4-client-setup-for-asuswrt-merlin-firmware/