RT-BE88U VLAN IP Address Not What I Assigned

[Basspig]

I've set up a VLAN (no Wi-Fi) for the purpose of feeding a multiple port switch to supply PCs on a different subnet as follows:

I've assigned that VLAN to the SFP port:

I'm expecting the PC connected to the switch that is connected to this trunk port to have the IP address 192.168.10.1.

What IPCONFIG actually shows is  192.168.0.1 as the gateway and an IP of  192.168.0.173, instead of 192.168.10.173.

Why doesn't the router respect the VLAN IP address I've assigned?

[jzchen]

If that is the DHCP server settings, (I don't use VLANs and can't see anything beyond that snippet), then isn't the 192.168.10.1 the IP to access the router?

[Basspig]

I thought the gateway address was the router UI access. I thought LAN IP was the IP assigned to the VLAN. Doesn't seem to be the case.

I was hoping to eliminate a second router (old Linksys WRT3200ACM) and put all the static 192.168.1.xxx devices on a VLAN trunk fed switch with 16 ports. The idea was to have those devices which are set for static IPs to connect to the 2.5gb 16 port switch, whose uplink connects to the SFP port on the Asus router, and is assigned as VLAN with that IP address.

[jzchen]

To be honest I just recall how I set up the router's main DHCP server, and translate that to this.  There, you assign a LAN IP and subnet.  It then automatically provides an IP range...

I think I may be able to help a little.  So if you change the subnet you can get a lot more IPs:

It seems you set up the router's IP as 192.168.0.1?  You may change the Subnet to 255.255.254.0 .  Then check, the DHCP server will automatically set a range to 192.168.0.2 - 192.168.1.254.  You can change the 192.168.0.2 to 192.168.0.101.  Then manually assign from 192.168.0.2 to 192.168.0.100.  (You'd have about 98 static IPs, although I think the limit is 64 through the Web GUI)....

[Basspig]

I'm a bit confused when you mention set a range to 192.168.0.2 - 192.168.1.254. I thought changing the mask to lower number reduces the number of IP addresses. But how does it increase it to another subnet?

To be clear, my intent is to create a VLAN port on a different subnet that will be a trunk to the switch that is attached to the SFP port. I want that subnet to be 192.168.1.1xx range, like my second router that I'm eliminating is currently on.

Somehow, messing with VLANs did something to make the wi-fi filter the internet. My IoT devices stopped working the next morning. Couldn't turn on the a/c, security cameras were inaccessible, etc. Turned out any device or phone/tablet connected to that SSID could not access any sites but google and social media. Speedtest, isitdownrightnow and other test sites took too long to respond. Rebooting didn't fix it, so I had to re load the config file to get it working normally. This router is somewhat glitchy.

[Basspig]

I thought I replied to this yesterday, but the reply is gone.. so I'll summarize:

I don't understand how changing the subnet mask to 254.0 is going to make the VLAN node have a 192.168.1.1xx IP address when the router is on 192.168.0.1.

I'm attempting to replace my slower inner tier router with a 2.5 gbs switch, but I want to keep that network on the 192.168.1.1xx IP range, and I thought VLANs could make a subnet of my choice that could be assigned to SFP port as a trunk line to the new switch.

Have I misunderstood the implementation of VLANs in this router?

[jzchen]

I'm afraid I know next to nothing about VLANs.

In the past someone came on the forums about VLAN issues, and I tried to replicate it, and failed.

More recently I learned about how the Subnet mask affects the IP range.  In order for the router to service 192.168.0.xxx and 192.268.1.yyy you need to change the 255.255.255.0 to 255.255.254.0.  Then you may be able to create the VLAN with IPs 192.168.1.yyy as you wish...

EDIT-  In that past experience I was trying to create a VLAN with a different 3rd triplet, and the person with the problem didn't share with me changing the Subnet was how to do it....

[jzchen]

So if 255.255.254.0 gives xxx.yyy.1.zzz

255.255.253.0 would also allow xxx.yyy.2.zzz

255.255.252.0 - 3

255.255.251.0 - 4

255.255.250.0 - 5

...

255.255.245.0 - should allow your 192.168.10.zzz that your OP notes

(If I didn't goof up the math).

[jzchen]

In the past it would just say invalid trying to create a VLAN with a different 3rd triplet, and I didn't understand that the subnet was why...

[Basspig]

I tried an experiment with this tonight.

So I set the router's mask to 255,255.254.0 (so far no problems.

Then I made a guest network (no wi-fi) and assigned it to the SFP port on the LAN menu. Connected that SFP port to a Cisco switch and plugged a laptop into the switch.

I set up the laptop for 192.168.2.150 static IP in Windows ipv4 settings.

IPCONFIG confirms that the PC is on that address. Problem is, I had a warning setting default gateway to 192.168.0.1, which is the router's gateway. I saw the PC could not connect to internet. So I changed gateway to 192.168.2.1 and ignored the warning from Windows. However, I still could not reach the internet.

Only setting it to 192.168.0.xxx and gateway 192.168.0.1 got me internet access.