<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY LINK="#0000ff">
Depending on your scope of service, I personally have found that maintaining static blocklists just creates a heap of support problems, but instead deny traffic outside ARIN allocated IP's and allow customers to turn on international use individually which has severely cut down our fraud, since chasing it statically is just a game of whack-a-mole. <BR>
<BR>
Though this topic does raise a question I have been kicking around for a while, has anyone here tried implementing a SIP equivalent of URPF on your border controllers or proxies on the peering side, so if you cannot determine a route back to the calling number you drop the call to IVR or reject? Obviously implementing UPRF at L3 has saved me tons of headaches in other facets, but certainly a L5 solution could alleviate a potential ton of spam calls that come through normal PSTN connections. Thoughts?<BR>
<BR>
On Sat, 2010-04-17 at 22:14 -0700, Ujjval Karihaloo wrote:
<BLOCKQUOTE TYPE=CITE>
We have seen a lot Unauthorized attempts from Mid-East, China recently. I wanted to see if there is a blacklist of IPs that is maintained or we as Service Providers should maintain. Maybe a wild idea but worth a shot. I would like to identify whole subnets from even sending traffic to our networks.<BR>
<BR>
<BR>
<BR>
Here is the IPs we have blocked recently…<BR>
<BR>
<BR>
<BR>
188.161.142.151<BR>
<BR>
188.161.135.62<BR>
<BR>
85.114.97.106<BR>
<BR>
113.105.152.137<BR>
<BR>
121.14.149.148<BR>
<BR>
113.105.152.131<BR>
<BR>
113.105.152.135<BR>
<BR>
188.161.130.5<BR>
<BR>
121.14.149.148<BR>
<BR>
188.161.135.62<BR>
<BR>
188.161.155.180<BR>
<BR>
188.225.184.117<BR>
<BR>
95.35.189.89<BR>
<BR>
188.161.241.77<BR>
<BR>
95.35.211.88<BR>
<BR>
188.225.193.97<BR>
<BR>
<BR>
<BR>
Shut the buggers out!<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
_______________________________________________
VoiceOps mailing list
<A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
<A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>