Deus Ex Alpha

Hmm... seems I am banned from the DXAG server and I haven't been on it today. I'm 56k, and get a new ip address every time I sign on. I don't recall ever being banned from there at any time. May have banned my ip range.

Update: Nobody did ban my range to get rid of dogny. He took it off. Now me a dogny can fly free. *skips in a meadow*

Nobody has banned whole 4.* range :O
Try again.

Give em' hell Nobody!

Resolved Loasmeister?

I am still banned. What I dooo??!!! lmao.

play a different server

¤[ß2S]¤je$u$ wrote:play a different server

not helpful.

But funny

I hope my ip range is never banned

If you ban players with dynamic IP addresses then use whois tools to narrow the IP range (and to not catch innocents as well). In the Nephthys documentation there's some explanation.

Basically, start with one of these links (online whois services): http://www.ripe.net/whois?form_type=advanced&alt_database=ALL or http://ww2.arin.net/whois/. Both will refer to other whois services if necessary.

One of the results of those whois queries is a range which is assigned to the provider responsible for the given IP address.

But some providers have very large pools of dynamic IP addresses, so don't ban the entire pool. Look at your IP/name logs to get a proper range used by the player in question.

Zora

But what if the person he wants to ban has a dynamic IP, that as only static part has 4. so the IP can be 4.255.***.*** but also 4.200.***.***

Sure, then you have to ban 4.200.0.0 ... 4.255.255.255. But I don't recognized a player with that huge range yet. Also, I don't think a single ISP has the entire 4 range.

And still it's better to ban 4.200 ... 4.255 instead of all 4.x.x.x.

Some players have multiple ranges (e.g. with my old ISP I got a dynamic IP out of 217.80.x.x or 84.70.x.x). So don't ban a single huge range but ban multiple small ranges in those cases. In most cases, a range isn't larger than x.x.0.0 .. x.x.255.255 (65536 addresses).

Zora

well.. in most cases, players with a dynamic IP have the first 2 blocks static
of course there are exceptions..

the problem is.. if i wanted to ban 4.200.x.x till 4.255.x.x then i had to make 56 entries, which already wouldn't work because the banlist can just carry 50 entries

~[A]Noodles~ wrote:well.. in most cases, players with a dynamic IP have the first 2 blocks static
of course there are exceptions..

the problem is.. if i wanted to ban 4.200.x.x till 4.255.x.x then i had to make 56 entries, which already wouldn't work because the banlist can just carry 50 entries

I think the ban list is bigger with nephthys?

i don't know.. is it?

Nephthys has its own ban list. It can be as huge as you want. Although every ban list entry more will take more cpu power on player joins (to look through and be sure the player isn't banned). Ban lists with about 300 entries shouldn't be a problem on average machines though.

However, you don't need to block 56 contiguous blocks. If you are *sure* the range to ban is contiguous then make the range as large as you are convinced to. Even 0.0.0.0 ... 127.255.255.255 will work with Nephthys (although I think this makes your server empty ). Nephthys also can handle "odd" ranges like 4.200.143.28 ... 4.201.15.123 (although this isn't a reasonable range).

What I wanted to say is: If your block is larger than 65536 entries (i.e. one or both of the first 2 numbers vary) you should take a closer look because you might accidentally block innocent players (which you like to have as guests at your server). With my experience most blocks are even smaller than 65536 entries (every rule has its exception though).

Zora

alright
I guess it's time for me to RTFM

~[A]Noodles~ wrote:I guess it's time for me to RTFM

6 words, 1 letter, and one abbreviation I never thought you would say in one sentence =O

Still, reading manuals pays dividends. (Unless they're patronizing manuals, in which case, you're better off doing it yourself, and only install the driver software/minimal additional software needed to make it run.