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

    Separating VOIP Phones vs Other Network Traffic

    L2/Switching/VLANs
    3
    5
    616
    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.
    • M
      MarkElder
      last edited by MarkElder

      Hello,

      I have a new pfSense install that is up and working. However, I'm still making adjustments and tweaking my settings.

      I have 7 computers and 4 VOIP phones (Cisco 7960s). I have two 8 port switches chained together on the Lan side of my pfSense router. I put a 4 port Nic in my pfSense box and I am considering dedicating one of the Nic ports to the phones.

      My phones are connected to a Cloud VOIP service (Mitel)

      If I split my routers I can put all the computers on one switch connected to the Lan Port. I can take on of the extra ports and call it Phone and use the second switch to connect all the phones.

      If I do that I'm not sure how to configure pfSense. I'm also wondering if there is really any benefit or if I am just wasting my time.

      I have a separate Windows server that is handling DHCP and DNS. I was originally thinking I could keep the phone traffic separate from the rest of the Lan, but I don't see a way to run the DHCP server for one interface. I think I can bridge the Lan and Phone port on the Nic so the phones can still see my DHCP server, but then have I given up any potential benefits of keeping the two separate?

      Thanks,

      Mark

      1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott
        last edited by

        A common way is to use a VLAN for the phones and then you can use the 2nd port on the phone for connecting a computer. There really isn't much advantage to using separate switches, unless you have a PoE switch for the phones.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • M
          MarkElder
          last edited by

          I already have two drops per office running back to my switches, and also already have two 8 port switches. Does setting up a VLAN have advantages over keeping the switches separate? I'm a software developer, not a network expert. Being naive I see an extra Nic port on the pfSense box and thought maybe I should put it to use.

          chpalmerC 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott
            last edited by JKnott

            The advantage of VLANs is keeping the phone and computer traffic logically separate. That may or may not be important in your network. For example, with VLANs, you could give the phone traffic higher priority. With hosted PBX, you may find the provider wants a separate Internet connection for the phones. VLANs could be used to support this. As I mentioned, you may want to have a PoE switch for the phones, which is not needed for computers.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            1 Reply Last reply Reply Quote 0
            • chpalmerC
              chpalmer @MarkElder
              last edited by

              @markelder said in Separating VOIP Phones vs Other Network Traffic:

              I see an extra Nic port on the pfSense box and thought maybe I should put it to use.

              Yes you can do that.

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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