I have configured a new Surf SOHO MK3 router with firmware version 7 to have several VLANs. I have assigned various SSIDs to respective VLANs. Everything works fine.
The main workstation ethernet connection shows up under Status → Client List as assigned to the Untagged LAN and is not assigned to a VLAN. I want to assign it to a specific VLAN.
There probably is a setting to do this. Suggestions? Thanks.
My SOHO MK3 device is using firmware version 7.1.0. I can define the Ethernet LAN settings under “Port Settings”
Thanks. That’s precisely what I was looking for. I changed ports to type: Access, and assigned to a specific VLAN that I had created.
However, that caused another problem: I could not connect and log in to the router via a LAN port that was configured to type: Access and assigned to a specific VLAN. I could log in ok via a LAN port that was configured to type: Access and assigned to the Untagged LAN.
Does this make sense? If not, what settings might I look at? Thanks!
The port settings have nothing related to the router WebAdmin access.
You are accessing the router using untag VLAN IP when you connecting to VLAN access port ? Do you tried before access the router via the VLAN IP address ?
Yes, I tried logging in to the router before and after the LAN post settings. Here is an experiment I did to confirm the problem:
LAN port 1: port type: trunk, VLAN: any
can log in ok
LAN port 2: port type: trunk, VLAN: untagged
can log in ok
LAN port 3: port type: access, VLAN: untagged
can log in ok
LAN port 4: port type: access, VLAN: specific VLAN
can NOT log in ok
Settings for my specific VLAN include:
Specific IP address that is different from the router IP address
Inter-VLAN routing: off
Captive Portal: off
Perhaps the VLAN IP address is the problem? Any other suggestions? Thanks!
DHCP server: enable
Please help us to isolate the problem:
When you connect to LAN port 4, do your PC able to obtain IP address ? If yes, what is the IP address for your PC ? Do you able to ping to the gateway IP address for the VLAN ?
When you connect to LAN port 4, you are using accessing the SOHO device via untagged VLAN IP or specific VLAN IP ?
Hi: Let me simplify the problem by focusing on two LAN ports:
LAN port 1: port type: access, VLAN: untagged LAN
I can connect to the router. Status → client list shows that my computer is connected with an IP address assigned to the Untagged LAN.
LAN port 4: port type: access, VLAN: my VLAN
I can not connect to the router via port 4. The VLAN assigned to port 4 has a different
network IP than the port assigned to port 1. The VLAN port is within the port range that I assigned to my VLAN.
The router IP address is a unique address within the IP range I assigned to the untagged LAN.
Thanks for you help,
Fred
Here are some basics for Vlan stuff…
So, I assume that you are trying to access the admin panel from a device plugged into the “Access VLan 51” interface. Here are my assumptions – plug in your actual values…
Lan Name - Router IP - Subnet Mask
Untagged (Main) LAN - 192.168.1.1 255.255.255.0
VLan51 - 10.0.0.1 255.255.255.0
When you are on VLan51, you should get an address like 10.0.0.2 and you should be able to get to the router by typing in 10.0.0.1 in the URL field of your browser.
Let me know if that helps you at all…
Hey, thanks for the clarification.
In my case, I have specified a router IP of something like
10.199.3.3
and the IP range for the untagged VLAN is
10.199.3.21 to 10.199.3.250
The above is mapped onto LAN port 1. I can connect and log in to the router ok on this port.
I have a VLAN with the IP range
10.199.4.21 to 10.199.4.250
The above is mapped onto LAN port 2. I can NOT connect and log in to the router ok on this port.
My assumption is that on port 2, I should still connect with the specified router IP of
10.199.3.3
So let me ask, is my assumption incorrect? Would a different router IP be required to coincide with IP assignments on port 2?
Also, my intent was to have LAN ports mapped onto a VLAN. The use of VLANs for AP communications makes sense. Does it make sense for LAN ports?
Thanks,
Go to System → Admin Security
At the bottom of the page find “LAN Connection Access Settings”
This controls who can get to the web interface of the router
Its a great safety feature as it can keep visitors and IoT devices from ever touching the admin interface of the router.
Do you have simple network diagram (Make sure IP address info is included) for the setup that you would like to achieve ? Sometimes wording may not fully tell the story this why different answer given here 
Michael234: good suggestion, thanks.
sitloongs: a network diagram is attached. Thanks for taking a look at it.
Can you explain your issue base on the diagram ? or the problem solved base on suggestion from @Michael234 ?
Sorry - my post was incomplete. The first diagram I posted is my desired configuration. With that configuration, I can’t log on to the router at the IP address listed in the router box in the diagram.
I am including a second diagram with this post. This is my current configuration. In this configuration, I can log on to the router at the IP address listed in the router box in the diagram (10.41.3.7) but only with port 1, which is an untagged LAN.
With the second diagram, I can not log in to ports 2-4 using the IP address listed in the router box in the diagram (10.41.3.7). However, I can log in to ports 2-4 using IP address 10.41.4.7.
It appears that I simply did not understand the following setting:
A key setting is:
Settings → Dashboard → LAN interface → Router IP Address: 10.41.3.7.
It appears that VLAN IP addresses take precedence over this Router IP Address. In other words, if I connect to a port assigned to the VLAN, I must connect with the VLAN’s IP address, and not the specified Router IP address.Is this the case?
Thanks for your help.
