About the behavior when changing the IP address of vlan1 without a controller
I changed the IP address of VLAN1 on the SG3428X without using the controller.
When I did so, I can no longer communicate with the changed IP address or access the GUI.
The PC's IP address matches the segment of the changed IP address.
If I create an uplink port (tagged port) and link it up, I can communicate with the changed IP address.
I would like to know how to communicate with the changed IP address and access the GUI without linking up the uplink port.
Best Regards!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
TM00 wrote
Thank you for checking.
I will state specifically what I was unable to do.
The default IP address of the switch was 192.168.0.1/24.
This IP address is recognized as being set in VLAN1.
In this case, I was able to access the switch's web page by setting the PC's IP address to 192.168.0.10/24.
Next, I changed the VLAN1 IP address to 172.16.0.1/24, and the PC's IP address to 172.16.0.10/24.
Only the IP address was changed in the switch settings.
In this case, I was unable to access the switch's web page.
Are there any other items that need to be set when accessing the switch's web page?
Best Regards!
The steps are legit if you describe it in this way.
When you change it to 172.16.0.1, and there is no uplink or DHCP involved, and PC is 172 subnet, what does the routing look like on your PC?
What does the routing table look like on the switch?
Do you ping it okay?
This should be accessible.
- Copy Link
- Report Inappropriate Content
Thank you for pointing this out.
The 172.16.0.0 routing on the PC and SW was visible as connected, but ping was not possible.
However, when I set up routing on the PC to 172.16.0.0 with the next hop set to the switch's IP address, I was able to access the switch.
It seems that there was something wrong with the PC's routing.
I appreciate resolving the issue.
Best Regards.
- Copy Link
- Report Inappropriate Content
The switch either gets an IP from the DHCP or uses the default IP. And when you are without the uplink, it is not on a DHCP IP, and your computer is not on DHCP as well. Both are required to be set in the same subnet.
I think you have made mistakes before you try to access the web page.
- Copy Link
- Report Inappropriate Content
Thank you for checking.
I will state specifically what I was unable to do.
The default IP address of the switch was 192.168.0.1/24.
This IP address is recognized as being set in VLAN1.
In this case, I was able to access the switch's web page by setting the PC's IP address to 192.168.0.10/24.
Next, I changed the VLAN1 IP address to 172.16.0.1/24, and the PC's IP address to 172.16.0.10/24.
Only the IP address was changed in the switch settings.
In this case, I was unable to access the switch's web page.
Are there any other items that need to be set when accessing the switch's web page?
Best Regards!
- Copy Link
- Report Inappropriate Content
TM00 wrote
Thank you for checking.
I will state specifically what I was unable to do.
The default IP address of the switch was 192.168.0.1/24.
This IP address is recognized as being set in VLAN1.
In this case, I was able to access the switch's web page by setting the PC's IP address to 192.168.0.10/24.
Next, I changed the VLAN1 IP address to 172.16.0.1/24, and the PC's IP address to 172.16.0.10/24.
Only the IP address was changed in the switch settings.
In this case, I was unable to access the switch's web page.
Are there any other items that need to be set when accessing the switch's web page?
Best Regards!
The steps are legit if you describe it in this way.
When you change it to 172.16.0.1, and there is no uplink or DHCP involved, and PC is 172 subnet, what does the routing look like on your PC?
What does the routing table look like on the switch?
Do you ping it okay?
This should be accessible.
- Copy Link
- Report Inappropriate Content
Thank you for pointing this out.
The 172.16.0.0 routing on the PC and SW was visible as connected, but ping was not possible.
However, when I set up routing on the PC to 172.16.0.0 with the next hop set to the switch's IP address, I was able to access the switch.
It seems that there was something wrong with the PC's routing.
I appreciate resolving the issue.
Best Regards.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 244
Replies: 4
Voters 0
No one has voted for it yet.