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

    Allowing Inbound Traffic from Specific IP Addresses

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 1.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.
    • Z
      zMaliz
      last edited by

      Hi

      I'm trying to allow an internal device to register a SIP Trunk.

      On my old router all I had to do was allow port 5060 from IP 146.101.248.200 to my Servers IP Address 192.168.1.20
      I could then see the system send messages out and receive replies back.

      I had multiple rules set up, routing different SIP trunks providers to different network devices.

      I've just set my pfSense up and now I'm trying to get the SIP trunk working.
      In WAN I've added a rule that I thought would allow 146.101.248.200 to route to 192.168.1.20, but it doesn't seem to work.

      Can any one advise what I've setup wrong ?
      WAN.jpg
      WAN.jpg_thumb
      LAN.jpg
      LAN.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • chrismacmahonC
        chrismacmahon
        last edited by

        Did you set your wan rule as a wan rule or as a port forward (Firewall, Nat, Port forward).

        Need help fast? Our support is available 24/7 https://www.netgate.com/support/

        Do Not PM For Help!

        1 Reply Last reply Reply Quote 0
        • Z
          zMaliz
          last edited by

          Hi.

          I originally set it as a WAN rule, then read it should be done as a port forward which would create the WAN Rule so I deleted it and recreated it as a NAT / Port Forward and the WAN rule appeared.

          I've tried several options and I'm not getting any inbound from port 5060 to my server.

          Any ideas ?
          Thanks

          1 Reply Last reply Reply Quote 0
          • Z
            zMaliz
            last edited by

            Hi

            This is sorted..

            Years back I'd setup IPTABLES rules on the servers to block specific traffic.
            I'd forgotten about that and it was those settings that were causing the issue.

            I now have 4 SIP trunk from different providers registered and routing to the correct devices.
            Everything seems to be working fine..

            Thanks

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