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

    Port-Fowarding question with Layer 3 switch as router

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 496 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.
    • R
      raind0wn388
      last edited by

      Hello All,

      So I have my Layer 3 switch doing all the routing for my VLANs. I have setup a /30 transit network to connect my Layer 3 Switch to the pfsense box. I also have static routes in place. I can browse the Internet, cool.

      But question is, how does port-forwarding work in this setup? Would I just do a normal port-forward in this case, or do I just need a firewall rule to allow the traffic I want from the internet to the servers?

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        I take it pfsense is natting the traffic for your downstream networks.. Or are these downstream networks public and routed to your pfsense?

        If your natting at pfsense then you would have to forward at pfsense, if your routing public then just need a firewall rule to allow it.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          Yeah. No difference. Just port forward to the inside address. As long as the target host's reply traffic makes it back to pfSense it will work.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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