Any way to get a global list of banned address ranges?

[ZPrime]

I guess like a reverse I: listing? I'm a big IRC freak but have never taken the time to learn the inner workings of the server-side of things. I don't know the proper terminology for a banned IP range.

I ask because I have a shell (for privacy purposes) with a provider who, after getting hit with a DDoS, decided to change coloc hosts and is now at Foonet. I've found out (the hard way) that many servers have denied access from foonet's address blocks, and I am looking for a way to just figure out which servers will work, WITHOUT having to try and access each IRCd first.

Is this possible?

[tabarnac]

I ask because I have a shell (for privacy purposes) with a provider who, after getting hit with a DDoS, decided to change coloc hosts and is now at Foonet. I've found out (the hard way) that many servers have denied access from foonet's address blocks, and I am looking for a way to just figure out which servers will work, WITHOUT having to try and access each IRCd first.

Unfortunately, there's a few incompetent IRC admins on EFnet who thinks they are professionals, but they can't finish a verifying job.

The shell providers using Foonet's IP ranges are not listed in ARIN, so some admins will just place the ban on the whole block and go on with their life, without trying to contact the responsible shell.

The only solution I know is for your shell admin to (try to) contact each IRC server admin and declare they're responsible for their own IP ranges. In the other hand, there will always be a strong foonet-hater ircop who will once again ban the ip range regardless.

As for trying each server one by one, it's a long process, but you can find a list by doing /links once connected.

[munky]

many servers kline foonet ranges because of past attempts to contact abuse@ have failed (or not produced acceptable results).

a list of servers is already online at http://www.efnet.info/?module=servers
you can use /admin [irc.server.name] to get the admin contact if needed.

as for the original question, you can /stats <k|K|d|D> to get lists of temp and perm k/d-lines on servers that allow non-opers to do these /stats (you have to do it for each server, there is no global list). many servers do not allow this, and be prepared to parse through a large list if they do.

[Pills]

There is no centralized list of banned IP#s. The reason? Every server has a different list.

Please make some more assumptions, tabarnac.

[tabarnac]

Please make some more assumptions, tabarnac.

Will do. Thanks

[seiki]

They're banned just about everywhere for originating DoS attacks, spamming, hosting abusive lusers, attacking colo customers after they move away from them, and ignoring legitimate abuse complaints..

As the others have said, there is no central list, and many servers choose to hide the local bans from users.

-seiki

[sealie]

I ask because I have a shell (for privacy purposes) with a provider who, after getting hit with a DDoS, decided to change coloc hosts and is now at Foonet. I've found out (the hard way) that many servers have denied access from foonet's address blocks, and I am looking for a way to just figure out which servers will work, WITHOUT having to try and access each IRCd first.

Unfortunately, there's a few incompetent IRC admins on EFnet who thinks they are professionals, but they can't finish a verifying job.

The shell providers using Foonet's IP ranges are not listed in ARIN, so some admins will just place the ban on the whole block and go on with their life, without trying to contact the responsible shell.

The only solution I know is for your shell admin to (try to) contact each IRC server admin and declare they're responsible for their own IP ranges. In the other hand, there will always be a strong foonet-hater ircop who will once again ban the ip range regardless.

As for trying each server one by one, it's a long process, but you can find a list by doing /links once connected.

Mental note: There is already a post regarding the banfiest on Foonet's address ranges

- sealie

[wundr]

Mental note: There is already a post regarding the banfiest on Foonet's address ranges

- sealie

Why post here about a mental note for yourself? Just make the mental note or write it down or something.

[sealie]

Did i say it was for myself? And the main point being that there is already a post about Foonet and its lack of support on the old forum.

[wundr]

Did i say it was for myself?

that's usually what a mental note is.

And the main point being that there is already a post about Foonet and its lack of support on the old forum.

in your post, you said nothing about the old forums. how were we to know that? maybe a link would have been good.
especially when you post to a thread that's been dead for more than a couple months already, it might be good to have more of a descripton about what your point is and why it's relevant enough to bring up a long-dead thread.

[sealie]

*sigh* I'll keep that in mind, Mr
I'm sure those who cared would be clued enough to find it

Good luck on your journey hunting/flaming down the rest of the "un-linked" threads on this forum.

- sealie

[wundr]

I'm sure those who cared would be clued enough to find it

So, someone would be clued enough to find something on the old forums without you even mentioning that it is ON the old forums? The way your post was worded, it sounded like you were making a note for yourself that this thread exists, not refering to another thread. I think that's how most native English speakers would read your post, since you said "mental note", which is a note to yourself. I'm sorry if this wasn't what you intended, and if I didn't understand what you meant.

Good luck on your journey hunting/flaming down the rest of the "un-linked" threads on this forum.

I think you know that wasn't the point of my post.

[munky]

ok, thats enough.

either get back on topic, or kill the thread