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

    One interface with multiple VLANs

    Scheduled Pinned Locked Moved Hardware
    7 Posts 4 Posters 4.5k 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.
    • J
      josempinto
      last edited by

      I am sorry for this question:

      I have configured various HP procurve switches; I know what are VLNs and trucking and how to configure it on HP procurve switch.
      Now, on configuring PFSense, I saw the fallowing message:

      If you do not have at least two REAL network interface cards
              or one interface with multiple VLANs then pfSense WILL NOT
              function correctly.

      My question is: can anyone point me to directly to one or more brands and models of network interface cards with multiple VLANs, working and tested with pfSense.

      Which is the better?

      Thanks in advance.

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

        The general recommendation for nics is intel. They don't stress the cpu as much and have support for advanced options like vlans.

        See http://www.freebsd.org/cgi/man.cgi?query=vlan&sektion=4&apropos=0&manpath=FreeBSD+6.2-RELEASE for a complete list of supported devices.

        1 Reply Last reply Reply Quote 0
        • T
          thinair
          last edited by

          I've used a 3com Etherlink XL nic when I tried a single nic.  I was able to attain 43Mb/s between VLANS on an Intel Celeron 500MHz with 128MB of RAM.

          Example: http://forum.pfsense.org/index.php/topic,61.0.html

          As previously mentioned I'd also definately recommend an Intel nic.

          Nelson Papel

          1 Reply Last reply Reply Quote 0
          • J
            josempinto
            last edited by

            @thinair:

            I've used a 3com Etherlink XL nic when I tried a single nic.  I was able to attain 43Mb/s between VLANS on an Intel Celeron 500MHz with 128MB of RAM.

            Example: http://forum.pfsense.org/index.php/topic,61.0.html

            As previously mentioned I'd also definately recommend an Intel nic.

            Very Good, and Very Nice work, and it’s explanation!!!

            Not all days we find someone with time and Preseverence To do a so complete and explainfull drawing along with it’s explanation.

            But, I am sorry going a little backwards and I have some more, Might basic, might essential, might even existential question.

            To avoid Crossposting, I am going to continue, and post the question here:

            http://forum.pfsense.org/index.php/topic,61.0.html

            1 Reply Last reply Reply Quote 0
            • J
              josempinto
              last edited by

              @thinair:

              I've used a 3com Etherlink XL nic when I tried a single nic.  I was able to attain 43Mb/s between VLANS on an Intel Celeron 500MHz with 128MB of RAM.

              Example: http://forum.pfsense.org/index.php/topic,61.0.html

              As previously mentioned I'd also definately recommend an Intel nic.

              Ops!!! It seams that the topic as closed, so I will continue here:

              But, I am sorry going a little backwards, and I have some more, Might basic, might essential, might even existential question.

              That Is:

              Ass we all know PFSense refuses to install with less then 2 network cards plugged in.
              (I can repeat this again, in English, as PFSense does, Joke!)
              So, I ask, at witch point of the network card detection process, what we should do, what key (even secret) to press, witch option to chose, or whatever else, we should do to, to be able to install PFSense on a system with one physical network card plugged in???
              Or, alternatively, should we plug-in two network cards  to have PFSense installed on the hard disk, and later on, re-run the network card detection process, but again, and in this later case Again, I ask:  at witch point of the network card detection process, what we should do, what key (even secret) to press, which option to chose, or whatever else, we should do to be able to have PFSense running and not complaining???

              < hoba> redirected me to a page/document,  where we are told to To compile the driver into the kernel And to place some lines in the
                  kernel configuration file or alternatively to load a driver as a module at boot time ….  , but again a lot of questions arise: Is this already done on PFsense, if not how to do that? And so on… (A lot of questions!!!). And Were, and how we assign virtual network tags/ID’s to PFSense networks and/or virtual network interface? And so on… (As you see, A lot of questions!!!)

              Thanks for any help

              Regards

              1 Reply Last reply Reply Quote 0
              • P
                Perry
                last edited by

                This old wink video might help you out.
                http://www.hotlinkfiles.com/files/99466_h4vnm/vlan_setup_part1.swf

                /Perry
                doc.pfsense.org

                1 Reply Last reply Reply Quote 0
                • J
                  josempinto
                  last edited by

                  @Perry:

                  This old wink video might help you out.
                  http://www.hotlinkfiles.com/files/99466_h4vnm/vlan_setup_part1.swf

                  After this video, I only have the following words:

                  -Thank you all!!!
                  -Thank you the PFSense team for doing a so powerful, rich of futures, and easy to configure, and to set-up firewall!
                  -Thank you all the supporters!
                  -Thank you < thinair> for the time and Preseverence To do a so complete and explainfull drawing along with it’s explanation!
                  -Thank you < Perry > for your reply with the video!

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