Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Firewall and the relative direction data goes

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 2 Posters 810 Views
    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.
    • B Offline
      Bonobo
      last edited by

      This might seem like a easy question to you guys but I can't figure out the terminology used in the firewall rules.
      What exactly is outbound and inbound? What are they relative to? After a bit of testing they do not refer to the pfsense device in general meaning inbound being "coming from the WAN side and being routed to the LAN" and outbound being "coming from the LAN side and routed to the WAN side"
      I've read
      https://doc.pfsense.org/index.php/Firewall_Rule_Basics
      But that doesn't explain it either.
      I suspect the rules are relative to the interface they're being configured on.
      All my rules are based on NAT port forwarding by linking them but I want to do some more specific rules. And without knowing this seemingly basic thing I can't do that.
      I would really appreciate the help.

      1 Reply Last reply Reply Quote 0
      • KOMK Offline
        KOM
        last edited by

        Inbound means the interface receives data; outbound means it transmits.  When your users are making a request over the Internet they are communicating inbound on LAN, outbound on WAN.

        mod4_fig6.png
        mod4_fig6.png_thumb

        1 Reply Last reply Reply Quote 0
        • B Offline
          Bonobo
          last edited by

          Thanks, that picture is exactly what I was looking for!

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