Switch to router

Aug 29, 2018
1
0
10
Switch is on the same subnet as gateway/router. The main router does not use DHCP. I use static on everything. The switch has it's IP address in the correct range and it's gateway is set to that of the routers IP.

If I plug directly into the switch I can manage it via web utility. If I go in the office on a PC plugged directly into the gateway/router I can't log into the switch when I put it's IP Addess in Internet Explorer.


The switch is plugged directly into the router. Why can't I manage it from a device plugged directly into the router?
 
Solution
If the switch is layer3 and has it's own gateway you don't want to have a conflict with your routers gateway.
Each gateway on the switch would be in it's own subnet.
The router wouldn't need a dhcp server. just a gateway on the lan side.

(WAN-> LAN GW)router-> (VLAN GW 1,2,3,4,5,etc)switch each VLAN has it's own subnet. route rules would pass packets from one gateway to another.

if you don't need VLANs don't use them. get rid of any ip conflicts.
Aug 29, 2018
2
0
10
If you have a cheap unmanaged 5p switch, to connect your switch and office to *ONE* port of the router, you probably can manage the router.

It's a lot of things you doesn't give info about, like VLAN tagging in the router and so on. Or what hardware you have. So it's virtually impossible to give a correct answer to your question "out of nothing".

You probably have the router isolating traffic between ports. Therefore the suggestion of a cheap switch in between.
 
If the switch is layer3 and has it's own gateway you don't want to have a conflict with your routers gateway.
Each gateway on the switch would be in it's own subnet.
The router wouldn't need a dhcp server. just a gateway on the lan side.

(WAN-> LAN GW)router-> (VLAN GW 1,2,3,4,5,etc)switch each VLAN has it's own subnet. route rules would pass packets from one gateway to another.

if you don't need VLANs don't use them. get rid of any ip conflicts.
 
Solution