What's new

Wireguard (Asus) cannot acces USB drive remotely.

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hardly a routing problem, the usb file share (samba) uses the same routing table as other local services. Perhaps access restriction in firewall....

Indeed, you are right. The following entries appear in the log
Apr 6 10:21:08 smbd[32420]: [2023/04/06 10:21:08.412078, 0] lib/access.c:338(allow_access)
Apr 6 10:21:08 smbd[32420]: Denied connection from 10.6.0.2 (10.6.0.2)
Apr 6 10:21:15 smbd[32432]: [2023/04/06 10:21:15.998882, 0] lib/access.c:338(allow_access)
Apr 6 10:21:15 smbd[32432]: Denied connection from 10.6.0.2 (10.6.0.2)

10.6.0.1 is the subnet on which (in my configuration) WireGuard is running. The connection reaches the router but is unfortunately blocked. I will wait with the installation of Asuswrt-Merlin for the stable version, because as I can see, it is a beta so far.
 
I also, for the past few days I have been trying to find the cause of this problem that WireGuard cannot access resources (USB drive in the router) via Samba. As you wrote, through OpenVPN everything works as it should. I have described the problem via a feedback channel on the Router, I suspect no one there reads it but it was all I could do.

Perhaps it's a coincidence that they added this capability in the last update 3.0.0.4.388.23285, or maybe they read what I wrote to them through the Feedback channel in the router :)

-Allowed WireGuard Server clients to access the Samba server.
 
Last edited:
Apparently this issue still exist as of July 2023. There is another thread about this and the end result was getting in via SSH and then reconfiguring the firewall. I don't understand why ASUS would let this "bug" go as-is.

I am on 388.2_2 Merlin
 
I don't understand why ASUS would let this "bug" go as-is.

I am on 388.2_2 Merlin
You seem to be confusing Asus' firmware with Merlin's. Post #22 said it was fixed in firmware 388.23285 (see the release notes). Merlin's firmware 388.2_2 is based on an earlier release, 388_22525.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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