What's new
  • 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!

Accessing router SMB server from Guest network?

Stiletto364

New Around Here
My equipment:
GT-AX6000 running Merlin 3006.102.4, IP = 192.168.10.1
SMB server enabled, SMB 2.0 (see attached config)
  1. Main LAN = 192.168.10.0/24
    1. Laptop IP = 192.168.10.46
    2. Android phone = 192.168.10.101 (2.4 Ghz)
    3. Firestick 4K Max = 192.168.10.111 (5 Ghz)
  2. VLAN 52 192.168.52.xxx Intranet access enabled to Main LAN; AP Isolation disabled (see attached config)
    1. Firestick 4k Max 192.168.52.186 (5 Ghz)
    2. Android phone 192.168.52.247 (2.4 Ghz)
What's happening:
I can access the router-based SMB server with no issues from the laptop, the phone and the Firestick located on the main LAN and primary 2.4 and 5 Ghz SSIDs. Works perfectly. I can do a port scan to 192.168.10.1:445 with success. I can ping both clients on VLAN 52 from the router and the Android phone on the main LAN without problems.
However, I cannot access the router SMB server even though intranet access to the main LAN is configured (result is an error resolving the router IP address). Using the phone on VLAN 52 to launch a scan of port 445 on 192.168.10.1 fails. Attempts at pinging the router from the VLAN 52 phone also fail. The results of a brctl show performed on the router is attached, along with the SMB share config and VLAN config.

I would have expected that enabling intranet access to the main LAN on VLAN 52 would have allowed bi-directional access from main LAN <==> VLAN 52 but apparently it is one-way. Has anyone seen this before and can explain what is going on? Or even better, how to resolve the issue? I know the workaround is to move the clients requiring SMB access to the main LAN but that defeats the purpose of the VLAN intranet access capability, doesn't it?

Appreciate any insight anyone could share regarding this.
 

Attachments

  • 1753301544122.png
    1753301544122.png
    75.2 KB · Views: 7
  • SMB Config.PNG
    SMB Config.PNG
    96.5 KB · Views: 7
  • VLAN 52.PNG
    VLAN 52.PNG
    52.9 KB · Views: 7
@Stiletto364, the Guest Network Pro Profile's Access Intranet option, as you have discovered, doesn't currently work properly for some. Its something that's been commented on in a number of earlier posts on both the stock Asus 3006.102.x firmware and Asus-Merlin 3006.102.x firmware. The workaround if Access Intranet isn't working, if you want Guest Network Pro Profile clients to access the main LAN when one has configured the Guest Network Pro Use same subnet as main network to disable, is to use a firewall-start script with IPTables entries that allow the traffic to pass to/from the two networks. There are a number of past discussions on this Guest Network Pro accessing main LAN using firewall-start scripting, here are a few of them:
And see this post with an example: https://www.snbforums.com/threads/t...st-network-pro-limitations.94438/#post-952345

Edit: Fixed error
 
Last edited:
@Stiletto364, the Guest Network Pro Profile's Access Intranet option, as you have discovered, doesn't currently work properly for some. Its something that's been commented on in a number of earlier posts on both the stock Asus 3006.102.x firmware and Asus-Merlin 3006.102.x firmware. The workaround if Access Intranet isn't working, if you want Guest Network Pro Profile clients to access the main LAN when one has configured the Guest Network Pro Use same subnet as main network to enable, is to use a firewall-start script with IPTables entries that allow the traffic to pass to/from the two networks. There are a number of past discussions on this Guest Network Pro accessing main LAN using firewall-start scripting, here are a few of them:
And see this post with an example: https://www.snbforums.com/threads/t...st-network-pro-limitations.94438/#post-952345
Thanks, I checked the forums this morning before posting to see if I could solve it on my own (to no avail unfortunately). I will scour those posts you mentioned to see if I overlooked a trick or two, I appreciate you responding to me so quickly.

I already tried the following iptables entries earlier today but I am still experiencing only one-way traffic (from the main LAN to vlan 52).

iptables -I FORWARD -i br52 -s 192.168.52.0/24 -d 192.168.10.1 -j ACCEPT
iptables -I FORWARD -i br0 -s 192.168.10.1 -d 192.168.52.0/24 -j ACCEPT
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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