You had it right with the VLANS initially but you need to understand the /30 establishes a network between the devices BUT ONLY for those IPs.
The switch will only know about 10.0.0.0/30 not any other network because its a switch and has no default route.
If for example you are on a different IP range lets say 10.0.1.0/24 and connected to the router, the router knows how to get packets from 10.0.1.0/24 to the switch (10.0.0.2) but the switch has no idea what to do with 10.0.1.0/24 packets.
Generally the switch will need a static route of any other network that wants to access it back to the router on 10.0.0.1 or even send everything (0.0.0.0/0 next-hop 10.0.0.1) back to the router to start with until the penny drops.
If that is all too hard for you because you fail at understanding use a /24 instead of a /30 and put the device you want to access the switch with in the same network range =====> router 10.0.0.1 ... switch 10.0.0.2 and PC to play with switch 10.0.0.3![:-)]( "Smile")
The switch will only know about 10.0.0.0/30 not any other network because its a switch and has no default route.
If for example you are on a different IP range lets say 10.0.1.0/24 and connected to the router, the router knows how to get packets from 10.0.1.0/24 to the switch (10.0.0.2) but the switch has no idea what to do with 10.0.1.0/24 packets.
Generally the switch will need a static route of any other network that wants to access it back to the router on 10.0.0.1 or even send everything (0.0.0.0/0 next-hop 10.0.0.1) back to the router to start with until the penny drops.
If that is all too hard for you because you fail at understanding use a /24 instead of a /30 and put the device you want to access the switch with in the same network range =====> router 10.0.0.1 ... switch 10.0.0.2 and PC to play with switch 10.0.0.3
Statistics: Posted by LdB — Sat Dec 30, 2023 4:17 pm