Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-11504

Failed registartions not blocked

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 13
    • Fix Version/s: None
    • Component/s: Fail2Ban, Firewall
    • Labels:
      None
    • ToDo:
    • Distro Version:
      10.13.66-7
    • Distro:
      FreePBX Distro

      Description

      Hello,

      Monitoring form the CLI, we continually see hundred of failed registration attempts from the same IP, every 15 seconds or so.

      Neither the Firewall or Fail2Ban are blocking these, and we have been manually monitoring and blocking IP's.

      Fail2Ban is running with a ban time: -1, max retry: 3 and find time: 604800.
      However, it has only ever banned 1 single IP (via SSH) since the last distro update just over a month ago.

      ie:

      [2016-02-06 13:46:07] NOTICE[29600]: chan_sip.c:27921 handle_request_register: Registration from '"780" <sip:780@XXX.XX.XXX.XX:5060>' failed for '151.22.164.138:5063' - Wrong password
      [2016-02-06 13:46:21] NOTICE[29600]: chan_sip.c:27921 handle_request_register: Registration from '"2001" <sip:2001@XXX.XX.XXX.XX:5060>' failed for '151.22.164.138:5081' - Wrong password
      [2016-02-06 13:46:35] NOTICE[29600]: chan_sip.c:27921 handle_request_register: Registration from '"2000" <sip:2000@XXX.XX.XXX.XX:5060>' failed for '151.22.164.138:1047' - Wrong password

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                xrobau Rob Thomas
                Reporter:
                voipmuch D Hunter
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.