Fail2Ban sends an e-mail when it bans an IP, and I saw last night at 5:21pm it banned 208.115.231.210 after "120 attempts against Asterisk".

This morning I noticed via iptables that that same IP is still banned, and I see via Wireshark that despite getting no response, that same IP is still sending around 100 SIP registration attempts a second. That's data I'm paying for!

I seem to get hit with one of these persistent buggers about once a month, and the attack can go on for as long as 48 hours and consume multiple GBs of data.

Is this just one of the realities of having an externally accessible Asterisk box?

Fail2Ban sends an e-mail when it bans an IP, and I saw last night at 5:21pm it banned 208.115.231.210 after "120 attempts against Asterisk".

This morning I noticed via iptables that that same IP is still banned, and I see via Wireshark that despite getting no response, that same IP is still sending around 100 SIP registration attempts a second. That's data I'm paying for!

I seem to get hit with one of these persistent buggers about once a month, and the attack can go on for as long as 48 hours and consume multiple GBs of data.

Is this just one of the realities of having an externally accessible Asterisk box?

All you can do is work with your provider to see if they will null route the attempts. If you have a residential connection this will be much harder than a business connection with SLA.

Haha not if they are Orcon, flat out refused to null route one of our internal IPs are DDoS to it were taking out our entire rack. Took them 3 months of us begging to finally look at a fix which was a 1gbps port upgrade which solved the issues overnight.