My network still feels the same as before, no changes in segmentation.
My network still feels the same as before, no changes in segmentation.
I maintain all my IoT gadgets on my Guest WiFi, which operates at 192.168.3.x, while my trusted devices are on 192.168.0.x. My JellyFin Media server was previously reachable locally but isn’t accessible from the Guest Network. Recently, I attempted to screen cast to a FireStick 4K and it failed. I realized the problem stems from the Guest WiFi, which is why it couldn’t connect to the server. Despite port forwarding the HTTPS port, it still tried to reach the wrong network. My subnet mask is 255.255.255.0. Connecting devices on different subnets shouldn’t be possible, yet they are now struggling. This issue has occurred before when I switched networks automatically, disrupting my JellyFin app. It’s not a major concern, but I’m concerned about security—especially with many IoT devices and some unreliable smart bulbs. Would anyone know what might be causing this? Perhaps using a separate router for all IoT devices would help, though adding another device to the UPS network isn’t ideal. My subnetting has worked well for about three years, but I’m unsure when it started failing. The problem surfaced only in the past week.
If you r JellyFin server was on the guest network instead of your trusted network, does that mean that you use the same password key for both ? A device cannot get access to a network unless it has credentials for that network. So, unless someone entered the credentials for the guest network (or used WPS or something similar) your server should not be able to join that network. On another level, there is usually a parameter to keep the guest devices from accessing your trusted network. It is worth a shot to look at that parameter to confirm that your IoT devices are in fact isolated from the rest of the network. On a final note, there may be a bug in the router's firmware and guest networks work improperly and have access to all networked devices. This is rare but not impossible. Check the manufacturer's website and see if there are known issues and if you run the latest firmware. Have a nice day !
Devices across various subnets can exchange information. This is the role of a router. Routers direct data packets between distinct networks. Even when devices from separate networks exist within the same layer-2 broadcast area, a router is necessary for them to interact at the layer-3 level. Because each host checks the destination layer-3 address against its own layer-3 address and mask to determine network membership, a router facilitates this process. If the target host belongs to another network, packets are sent as layer-2 frames to the router's configured gateway.
Changing the devices to different VLANs might resolve the problem depending on the cause.
That's confusing... you can set up two VLANs using the same IP range, but combining them in a single private network isn't allowed. You'll need separate firewalls or routers, plus two management interfaces since most don't support duplicates. It really depends on their placement—routers usually reject it as their own network, while switches without limits can handle it. If the VLANs aren't routed, you can share the same IP range. Just a note, it's not the most efficient setup, but it works.
Edit: In this case, it doesn't really matter, though. VLANs act as packages that reduce switch broadcasts to specific ports with static settings or forward to other switches that have VLAN trunking enabled. Unmanaged switches only support one VLAN and don't handle these packages.