Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Pf 2.1 voip OOMA configuration

    Scheduled Pinned Locked Moved Firewalling
    2 Posts 2 Posters 1.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.
    • R Offline
      rebuilder
      last edited by

      Beginner here.

      I have just recently installed 2.1 and am using four NIC cards. The first is for connection to the cable modem, the second is for the LAN, the third is used for all wireless connections(OPT1)  and I would like to use the fourth (OPT2) for dedicated connection to my voip system (OOMA).

      The problem is that OOMA has a lengthily list of ports that it needs  access through the firewall to operate normally. These are:

      UDP 53, 123, 514, 1194, 3386, 3480, 10000-30000
      TCP  110, 53, 443

      I'd like to know the best way to configure my fourth NIC card (now set up as 192.168.3.1 known to pfsense 2.1 as OPT2) to achieve the connection.

      One other point is that the OOMA works fine if I plug it into the switch connected to my LAN port.

      Any help/direction would be appreciated.

      1 Reply Last reply Reply Quote 0
      • M Offline
        markn62
        last edited by

        Presume you have the default NAT setup.  Inbound is typically not blocked provided you have a "pass all" Lan rule.  I would venture to say most if not all in the port list are references to inbound traffic and a non-issue.  Most of what remains will already be setup to handle port 53 dns, 110 pop, 514 syslog etc.  Port 1194 may have to be forwarded if there is some sort of security negotiation initiated external to your network.

        I would start by adding an OPT2 rule to pass all to all. Test the device to work, then remove the rule.  If removing the rule breaks comm then forward 1194, then 3386, then 3480 until it works again.  If it doesn't work with the pass all rule then you have a more subtle problem to resolve.  Some VoIP don't like PF scrubbing enabled in System, Advanced, Firewall.

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