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

    PFsense has blocked our phone system (Internal IP).

    General pfSense Questions
    6
    13
    2.3k
    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
      jai23155
      last edited by

      Hi all, our PFsesne firewall has blocked our internal phone system's IP (192.168.10.39). Whenever we plug the phone system into LAN with Firewall plugged in phone system goes dead. Disconnect the firewall from LAN then phones will work. Change the IP address of the phone system then it works fine but when change it back to 192.168.10.39 then it goes dead again. Is there way of finding out where can I change these settings? I don't want this to happen with new IP address.
      FYI - I am 200% sure it's not the phone system's problem. Thanks for helping out.

      1 Reply Last reply Reply Quote 0
      • S
        smither
        last edited by

        Could it be that "Block private networks" is enabled in the LAN interface settings?

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

          An obvious question, but one that needs asking: Have you set the IP address of your phone system to the same address as the firewall? The conflict would certainly prevent the system from working.

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

            PFsense is in different VLAN (10.xxx.xxx.1) and phone system is 192.168.10.39. Strangely enough, the system has worked ok for more than 6months and all this happened on Thursday last week.
            This is the only messaged logged around the time the issue happened "inetd[1529]: warning: can't get client address: Connection reset by peer"

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

              Someone changed something.  Pfsense doesn't block phones.
              Especially easy to determine because it was working before and suddenly for no reason (you have figured out) it has stopped.
              Look for whatever someone changed recently either in the pfsense, switches, or phone system.

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

                Cannot think of any changes unless our Cisco switch automatically blocks something.

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

                  Firmware updates on the phones, switches or pfsense?

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

                    @jai23155:

                    Hi all, our PFsesne firewall has blocked our internal phone system's IP (192.168.10.39). Whenever we plug the phone system into LAN with Firewall plugged in phone system goes dead. Disconnect the firewall from LAN then phones will work. Change the IP address of the phone system then it works fine but when change it back to 192.168.10.39 then it goes dead again. Is there way of finding out where can I change these settings? I don't want this to happen with new IP address.
                    FYI - I am 200% sure it's not the phone system's problem. Thanks for helping out.

                    You've left out quite a bit of information. For instance, you say you change the IP address of the phone system and it works. What do you change it to? If you disconnect the firewall from the LAN then the phones work - but if so how are they routing to the phone system if the firewall is down? If changing the IP address of the phone system makes the phones work, then why not keep the change?

                    You're assuming we know more information than you're presenting here. Can you perhaps post a diagram of your network layout so someone can understand a bit better the scenario you're describing?

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

                      No changes at all.

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

                        @muswellhillbilly:

                        @jai23155:

                        Hi all, our PFsesne firewall has blocked our internal phone system's IP (192.168.10.39). Whenever we plug the phone system into LAN with Firewall plugged in phone system goes dead. Disconnect the firewall from LAN then phones will work. Change the IP address of the phone system then it works fine but when change it back to 192.168.10.39 then it goes dead again. Is there way of finding out where can I change these settings? I don't want this to happen with new IP address.
                        FYI - I am 200% sure it's not the phone system's problem. Thanks for helping out.

                        You've left out quite a bit of information. For instance, you say you change the IP address of the phone system and it works. What do you change it to? If you disconnect the firewall from the LAN then the phones work - but if so how are they routing to the phone system if the firewall is down? If changing the IP address of the phone system makes the phones work, then why not keep the change?

                        You're assuming we know more information than you're presenting here. Can you perhaps post a diagram of your network layout so someone can understand a bit better the scenario you're describing?

                        IP address of the phone system is changed to 192.168.10.45 same subnet but different IP. Phone system is IP based for internal connection only. For external calls it runs off through ISDN.
                        Yes, changes are kept, system is working but I am trying to find what caused this in first place. Did I explain ok? let me know if you need more info.

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

                          Are you using DHCP to assign that address to the phone system?

                          Is it possible that you have another MAC address "assigned" that IP address in the DHCP server?

                          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
                          • DerelictD
                            Derelict LAYER 8 Netgate
                            last edited by

                            @jai23155:

                            No changes at all.

                            Dude.  Something changed or it would be working.  Sounds like a duplicate IP address, perhaps.

                            Diagram your network and post it with all the relevant VLANs, IP addresses, switches, DHCP servers/scopes, etc.

                            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
                            • J
                              jai23155
                              last edited by

                              Hi Derelict,
                              Here is a quick drawing of our network (sorry! poor visio skills).

                              On other note, the problem with phone system happened earlier on few occasions but it used to sort itself out within few mins, before we run any diagnostics. This time around it's dead.

                              Thanks
                              Jai

                              ![Current network.jpg](/public/imported_attachments/1/Current network.jpg)
                              ![Current network.jpg_thumb](/public/imported_attachments/1/Current network.jpg_thumb)

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