HI
>>>Set up VLAN 10 with 192.168.2.x, change the subnet of VLAN 1 to 192.168.3.x, and then change the subnet of VLAN 10 to >>>192.168.1.x ... ?
1. Yes. This is what you will need to do, if you want to move "192.168.1.x" subnet from "vlan1" to "vlan10"
2. you have a lan-pc connected in vlan1 (meaning its untagged) with a ipaddr say 192.168.1.100 and you have accessed the GUI from this pc (assuming that the vlan1 lan-interface ipaddr of router is 192.168.1.1)
a) So if this lan-pc is a windows, then i dont know how, but it should be also configured with a secondary-alias ipaddr of 192.168.3.100/24 (no need to configure default-gw ipadd here for this subnet)
- and then you access the GUI using 192.168.1.1, and then change the ipaddress of vlan1 to 192.168.3.1...and apply.. you will loose connectivity....
- and on this lan-pc, first confirm that you can ping to 192.168.3.1, and then open a new browser window, and access the GUI using the ipaddr 192.168.3.1 (click on accept in browser for any cert-related/secure connectivity messags...etc)
- now you change the subnet of vlan10 from 192.168.2.x to 192.168.1.x...and then do a apply and now also do a permanent save, and i would also recommend a reboot just once of this router...although it is not compulsory or required as such.
OR, the better way (in my opinion and how i would prefer):
3.. Use a Linux Lan-PC, and configure the interface connected to the R34X router as below in cli:
- say its a eth0 interface:
ifconfig eth0 192.168.1.100 netmask 255.255.255.0 up
- check with ping to 192.168.1.1
- next configure the below alias interface/address too on the same eth0 interface
ifconfig eth0:3 192.168.3.100/24 up
OR
ifconfig eth0:3 192.168.3.100 netmask 255.255.255.0 up
- and then you access the GUI using 192.168.1.1, and then change the ipaddress of vlan1 to 192.168.3.1...and apply.. you will loose connectivity....
- and on this lan-pc, first confirm that you can ping to 192.168.3.1, and then open a new browser window, and access the GUI using the ipaddr 192.168.3.1 (click on accept in browser for any cert-related/secure connectivity messags...etc)
- now you change the subnet of vlan10 from 192.168.2.x to 192.168.1.x...and then do a apply and now also do a permanent save, and i would also recommend a reboot just once of this router...although it is not compulsory or required as such.
4. OR in the very worst case, if you dont want to go thru all the steps for creating/configuring alias addresses, etc, etc
a) Assuming that you have enabled/configured/activated the wanX interface on the router
b) from the lan PC in vlan1 with ipaddr 192.168.1.100, access the GUI and in Firewall-settings:
- disable/uncheck "Block Ping...from wan"
- enable "Remote Management access" and don't change anything else...simply click on apply
c) Now from a host in the wan-side of router, first check whether you can ping to the router's wan-ipaddress
- if yes, then open the router's GUI and first create a vlan10 with the subnet 192.168.2.x
- then change the vlan1 subnet/ipaddr to 192.168.3.1/24 (or whichever subnet you had wanted on vlan1)...apply
- then, again, change the vlan10 subnet to 192.168.1.x...apply
- logout
d) Now change the ipaddr of your lan-pc from 192.168.1.100 to 192.168.3.100
- and check with ping to 192.168.3.1...if yes, then do the below steps:
- login to GUI, and in Firewall-settings, "disable Remote Management access.." AND also "enable - Block Ping from wan"
e) Now you do a apply and a permanent save again and do a reboot of the router once - not really neccessaary...but it does help in proper re-initialization of the routers services, if any
