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

    PFSENSE and L3 SWITCH

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    16 Posts 4 Posters 2.6k 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.
    • marcellocM
      marcelloc
      last edited by

      This is up to you. If you do not need to filter traffic between vlans, you can leave switch setup unchanged.

      If you want that pfsense filter traffic between all vlans, then configure each vlan on it, remove routing vlans on switch(sometimes just removing switch ip on vlan does the trick) and set all vlans gateways to pfsense firewall.

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • C
        cjiwonder
        last edited by

        I am not familiar with L3 and VLAN configurations, already L3 config done by the old employee. I wish to place pfsense for proxy, content filtering and NATing purpose only. pls guide me to configure without touching L3 switch setup.

        1 Reply Last reply Reply Quote 0
        • R
          robi
          last edited by

          Well if you want to keep routing on the switch between the VLANs, and you only want to do proxy, content filtering and NATing of the internet traffic, you could put a pfSense leg in each VLAN, and set up a static route in the switch saying that all traffic except the local VLANs should go in pfSense.

          1 Reply Last reply Reply Quote 0
          • C
            cjiwonder
            last edited by

            Bro, Thanks for your reply.

            I have no idea about pfsense leg and static route.

            I would be much thankful if you could explain me step by step.

            1 Reply Last reply Reply Quote 0
            • H
              heper
              last edited by

              i'm not trying to discourage you BUT:
              If you don't know how the switch works or how it is configured, then don't try to implement other complicated things
              take your time to learn how to configure the switch, get comfortable with VLANs / Routing / …

              then in a couple of weeks time, perhaps you can think about adding another device.

              Doing something wreckless now, will guarantee a big FAIL

              1 Reply Last reply Reply Quote 0
              • R
                robi
                last edited by

                If you have some time to spend, try learning from courses like ICND1 and ICND2. Although these are Cisco-specific, they train very well the basics of routing and switching, and their logic apply to other manufacturer network equimpent too - since these are standards.

                1 Reply Last reply Reply Quote 0
                • C
                  cjiwonder
                  last edited by

                  Bro, I am working in an Institution only and trying this setup for learning purpose only so there is no productivity loss if anything happend.

                  So pls help me.

                  1 Reply Last reply Reply Quote 0
                  • H
                    heper
                    last edited by

                    you can't do what you want todo without touching the switch ….  no point in doing anything before you master the switch

                    1 Reply Last reply Reply Quote 0
                    • R
                      robi
                      last edited by

                      @WONDER:

                      Bro, I am working in an Institution only and trying this setup for learning purpose only so there is no productivity loss if anything happend.

                      I thougt so. Read some chapters from these books to learn the basics, you'll know what we're talking about. It's not that difficult to understand the logic behind it.

                      1 Reply Last reply Reply Quote 0
                      • C
                        cjiwonder
                        last edited by

                        I didn't understand this magic.

                        If I add 192.168.2.1 as VIP and delete the same VIP then I can ping my pfsense IP 192.168.1.11 from VLAN 2 i.e 192.168.2.x same way for all VLANs. But if I restart pfsense it is not pinging, again I have to add VIP and delete the same VIP.

                        Any idea?

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