Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    IP CAM access

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 3 Posters 32 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      asyouwish57
      last edited by

      I am new to pfSense. I need some help in configuring my TP-Link IP camera. I am trying to allow them internet access so that i can view cameras when at and not at home. I do not want them to be able to access to my other interfaces. Right now, I am having to manually enter block rules on the TP-Link interface to allow access and see cameras via their app. My rules on the TP-Link interface is large. I do not have any VLAN's setup.

      TP-Link camera interface
      10.99.x.x is the static IP address
      I have block rules to prevent access to firewall, WAN, and my other interfaces.
      9a7b24b2-f630-4930-ad47-441200bc3995-Screenshot 2025-11-23 134942.png

      Manually entering IP address that are getting blocked.
      3ebffbf8-330b-47df-b0f4-86cfe8159bef-Screenshot 2025-11-23 134750.png

      I would greatly appreciate any help.

      chpalmerC 1 Reply Last reply Reply Quote 0
      • chpalmerC Offline
        chpalmer @asyouwish57
        last edited by

        @asyouwish57 Everything going into the interface is blocked by default anyways. You have to have a rule allowing traffic for it to pass.

        If you instigate however a connection from one of your other interfaces to the camera where you have allowed it there will be an open state which will let the camera pass traffic back until the state expires..

        Your first rule is backwards. though as I pointed out not really needed since it is already blocked by default..

        I do not see any kind of rules allowing the camera(s) to access DNS.. by design?

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        1 Reply Last reply Reply Quote 0
        • U Offline
          Uglybrian
          last edited by

          I dont know if I can help you , but I will try to get you going in the right direction. I am not familiar with tp-link cameras. I use nest/google so i have a idea.
          You certainly have a mess of firewall rules. Does your port 4 subnet have internet access?
          I would start with a simple rule set, get everything working. Then add your layers of restrictions.
          Here are the rules i use for my wired iot devices.

          2025-11-23_12-52.png

          you can use one block rule to other subnets . The netgate docs show how to set it up and use it for the WAN.but, you can also use it to keep every one in there own lane.
          https://docs.netgate.com/pfsense/en/latest/recipes/rfc1918-egress.html.

          I hope this helps you a little bit.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.