Device Information:

• Model: Archer BE230

• Connection Type: WireGuard VPN

• USB Storage: NTFS/FAT32 (Tested and working locally)

Description of the Issue: I am reporting a specific failure regarding the Samba (SMB) service on the Archer BE230. While the WireGuard VPN tunnel is established and working correctly for other services, the USB Storage sharing (SMB) is completely unreachable from VPN clients, despite it working perfectly for local LAN clients.

Detailed Observations & Tests Performed:

1. VPN Connectivity: The WireGuard tunnel is healthy. From a remote client (Windows and Android), I can successfully access the Router’s Web Management interface and perform RDP (Remote Desktop) sessions to other PCs in the LAN.

2. Service Comparison: * FTP Service: Works perfectly via VPN (both using LAN IP and VPN Gateway IP).

   • Samba (SMB) Service: Fails via VPN. It does not respond to the LAN IP address (\\192.168.x.x) or the VPN Gateway IP (\\10.x.x.x).

3. Local Performance: When connected directly to the router's Wi-Fi/LAN, the SMB share works without any issues.

4. Client-Side Tests: Tested on Windows 11 and Android (using various file explorers). MTU settings were adjusted to 1280 with no success. Accessing via IP address (instead of hostname) also fails
    

Technical Suspicion: I strongly suspect that the latest firmware update has introduced a regression or a restrictive firewall policy. It appears the Samba daemon is only binding to the LAN interface and ignoring requests originating from the VPN subnet, or the internal firewall is dropping port 445 traffic specifically for the router's local-host services when coming from the WireGuard interface.
 

Requested Action: Please verify if there is a known issue with SMB routing over VPN for the BE230 or if a beta firmware is available to resolve this subnet-filtering issue. I need the Samba service to be accessible from VPN clients as it was previously.