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

    Installing pfSense with a layer 3 switch

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    69 Posts 6 Posters 27.4k 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.
    • O
      oletuv
      last edited by

      @johnpoz:

      Silly questions do not irritate me that is for sure, what can get frustrating is the same questions over and over and over and over again..  Without searching for the information yourself before asking ;)

      But even whne the questions are "silly" I still answer them or point to where they are answered… So ask away your questions..  That is what we are here for.

      Thank you very much, sir. I really appreciate the great effort and help expert users like yourself and Derelict provide in the community forum.

      Coxhaus and myself are both old farts. I´m 70 and retarded .. sorry retired  ;D and unlike Coxhaus who I believe worked professionally with Cisco stuff in the old days, I just started with setting up a home network based on separate components (SG300-10, SG200-08, Cisco WAP371, Linksys LRT214) a few months ago. It´s the LRT214 I´m planning to replace with a pfSense firewall.

      I´m moving in to a new 90 m2 apartment in a couple of months where I´ll put my home network in production. For sure I would do just fine with a small consumer router (Asus, Netgear etc.) or even the ISP provided one. I´m doing all this for fun, it´s an excellent pensionist exercise.  :)

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

        Consumer router?  Whats the fun in that ;) hehehe and they all pretty much suck anyway..

        With the use of pfsense, some smart switches and a real AP your on your way to very stable and robust network with lots of room for learning and play..

        More than happy to help anyone learn no matter the age, I myself am no spring chicken anymore at 51..  Been in IT for 30+ years..  Before there was even tcp/ip hehehe.. We use to use ipx/spx, remember changing from old thinnet/thicknet cable to UTP… Rocking cat 3 ;) what a project that was..  Having to add the tcp stack to the windows 3.1 boxes running on 486 with math co processor installed...  We were on the bleeding edge of tech heheeh ;)

        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
        • C
          coxhaus
          last edited by

          oletuv after you get your pfsense setup with your Cisco layer 3 switch you will want to supply NTP from pfsense to your switch for time.  It seems to work real well.

          1 Reply Last reply Reply Quote 0
          • O
            oletuv
            last edited by

            @coxhaus:

            oletuv after you get your pfsense setup with your Cisco layer 3 switch you will want to supply NTP from pfsense to your switch for time.  It seems to work real well.

            Hi Cox,

            Nice to see you on the forums again!

            Thanks for the tip. I think I´ll setup a pfSense box in a couple of months, after moving in to my new apartment. :)

            Ole

            1 Reply Last reply Reply Quote 0
            • D
              divsys
              last edited by

              Before there was even tcp/ip hehehe.. We use to use ipx/spx, remember changing from old thinnet/thicknet cable to UTP… Rocking cat 3 ;) what a project that was..  Having to add the tcp stack to the windows 3.1 boxes running on 486 with math co processor installed...

              Oh gawd, the days of "expensive" ISA NIC cards with undocumented IRQ dependencies - plug in a local LPT printer and the network goes down (shudder)….

              -jfp

              1 Reply Last reply Reply Quote 0
              • K
                kpa
                last edited by

                You can not write network prefixes using shortcuts like that, you have to spell them out fully. Try 192.168.0.0/16 in the destination network field and it should work.

                1 Reply Last reply Reply Quote 0
                • O
                  oletuv
                  last edited by

                  @johnpoz:

                  Also you don't need a /24 as a transit, you could just use a /30 - if you made it say 172.16.0/30 you could then just use a simple summary route 192.168/16 route to your networks on your L3 switch.  Then no matter what 192.168 vlan you add to that switch you never have to touch your routes again.

                  When trying to add a 192.168/16 summary route I´m getting an "A valid IPv4 or IPv6 destination network must be specified." error.

                  I´m using the latest 2.3.2-DEVELOPMENT (amd64) version.

                  ![Summary route .png_thumb](/public/imported_attachments/1/Summary route .png_thumb)
                  ![Summary route .png](/public/imported_attachments/1/Summary route .png)

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

                    Try 192.168.0.0 with a /16 netmask not 192.168

                    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
                    • O
                      oletuv
                      last edited by

                      @Derelict:

                      Try 192.168.0.0 with a /16 netmask not 192.168

                      Thanks, working now.

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