IP address keeps getting banned even when excluded in Firewall

[volkswagner]

I have a remote location with two Yealink devices.

I have a DNS name added to the firewall as “trusted - excluded from firewall” yet
the ip still get’s banned in fail2ban asterisk-iptables.

I’m running FreePBX 14.0.13.40

I’m not sure what to do to prevent these devices from getting banned.

After adding the hostname, to firewall to I have to manually reload/restart anything?

What can I do to further troubleshoot?
What should I look for in logs?

I do see “Failed to authenticate” for the remote extension, but why is it getting banned. I have
a feeling remote network issues may be causing the failures but I’ll need to do a packet capture
to know for sure.

Should the IP still get banned for failures if it’s excluded in firewall network as trusted?

Well, I do see something interesting:
Request ‘INVITE’ from ‘sip:49.144.111.111’

It seems the phone is not sending the authname, or it’s getting lost somewhere.

Thanks!

[sorvani (Jared Busch)]

Upgrade to Edge.

Major facelift to the FreePBX Firewall

One of the goals of FreePBX 16 is a review and update for FreePBX security settings. Today, a major aspect of that work has been published to edge for FreePBX 14 and 15 Firewall module. These latest changes are mostly the work of @danardf, and you can read his blog post here: FreePBX historians (if there be such a thing) will recall that it was right around 5 years ago that the FreePBX firewall made its debut. It was the work product of @xrobau and it came shortly after the merger of Schmoo…