Messages

Correct, the problem was with the machine connected to the VLAN rather than the VLAN or router setup. I guess the giveaway was that I was able to connect to the interface itself which should not be possible if the path was actually blocked by firewall rules.

Hi, thanks for the tip! I think I missed something very stupid as I believe there is some extra setup needed for pings to go through to Windows machines. When I booted up Linux on the machine in the CAMERA VLAN, I was able to ping it from the TRUSTED VLAN:

In my network, I have a couple of VLANs, but there seem to be some issues with communication between the different VLANs. For context:

• VLAN parents are all LAN. I'll be focusing mostly on TRUSTED (192.168.10.X) and CAMERA (192.168.30.X) VLANs
• TRUSTED has these firewall rules. The important one is the one that is connecting to CAMERA's net.You cannot view this attachment.
• CAMERA has these firewall rules.
  You cannot view this attachment.
  Note that once I figure out everything, I will be removing access to internet and other rules. These extra rules are merely for debugging purposes. Also note the rule that connects to the TRUSTED net.
• From a computer in the TRUSTED VLAN, I am able to ping the CAMERA interface itself (192.168.30.1), but no computer that is connected to the CAMERA VLAN. You cannot view this attachment.
• Interestingly enough, from a computer in the CAMERA VLAN, I am able to ping a computer in the TRUSTED VLAN despite the firewall rules simply being mirrors of each other.
  You cannot view this attachment.

I have looked into the actual interfaces themselves (CAMERA vs TRUSTED), but don't see anything different with the setup. Any ideas on why this is happening? My end goal is simply to allow TRUSTED to view CAMERA devices when I eventually install some security cameras.