Battlezone Forums

Removed irrelevant info

Removed irrelevant info

Updated list. Tweaked any ranges operated by RIPE network. Reduced the scope to those listed on RIPE network's website for each IP. The Arin.net CIDRs were much more broad. For example, 79.0.0.0/8 became 79.141.161.0/24.

There were about 5 different IPs operated by RIPE network, http://www.ripe.net/.

Basically how I determine the CIDR.

1. Go to www.arin.net
2. Enter a player's IP
3. The CIDR is listed there, if the specified organization isn't RIPE Network, I use the provided CIDR.
4. If the listed organization is RIPE Network, I go to http://www.ripe.net/
5. I again enter the player's IP.
6. I use the route, listed on the bottom of the page

Added an additional IP. Also went over the previous entries and made minor adjustments to make the info more consistent.

Enclosed actual IPs in "".
Added Arin.net URL = followed by the actual URL
Enclsoed the Arin.net CIDRS, only applicable to RIPE Network IPs in ""
Enclosed the customer/organization in ""

12-26-2013 @ 7:41 P.M.

* Added Vearie's (Suffering_Clown's) IP to the whitelist.
* B!t[hZone][ shares the same subnet as GSH. Documented in the whiteist.
* NostalgicRCB shares the same subnet as GreenHeart. Documented in the whitelist.

12-26-2013 @ 10:44 P.M.

* Added znsw's IP and info to the whitelist.
* Added IP info for Anonymous

Perhaps a stupid question ..
How does this whitelist IPs by adding them to the banlist? To me it would seem you just block all of those IPs.

You add the IPs to your whitelist. You ban "0.0.0.0/32" in your ban list then add the following to your whitelist.

The whitelist overrides your banlist.

IOW, the later patches include a whitelist and so my question was a stupid one?
Thanks for the explanation.

The whitelist is backwards, IMO. Everything else I've ever worked with has rejectsions taking precedence over allows, windows file access and sharing, firewall policies, etc. So the behavior is backwards to me.

My strategy for the whitelist has been to get a player's IP then from there, get the CIDR, subnet, for the player's ISP. From there I unblock the player at the ISP level, in case their IPs change.

If a problematic player joins from said ISP, the only way to block them is through windows firewall due to there being no override for the whitelist.

This approach blocks everyone but those on the whitelist. Its probably not what most players would want to do.
The other approach would be to just blacklist the ISP (and VPN ranges) used by a problem player and then use the whitelist to allow welcome players from those ranges in, if you know who they are.
That way you still allow most unknown players in, but just have to keep banning your persistent problem players until they get fed up with getting new vpn addresses just to deliberately enter games where they have already made themselves unwelcome. This could take some time, as some of our griefers seems very determined to continue entering games where they know themselves to be unwelcome.
A similar technique could be used with peerblock, it has the advantage of being able to be updated without actually ending a bz2 session.

True. This list would probably be more helpful to Vas as he's been a prime target for the griefers.

He's also convinced that some 50% of the beta team is also against him.

True. I know He and N1 went at it for a while, but didn't get involved.

N1 waded in in my defence after he started having a go at me. He's also convinced GSH is against him.

Short: Serious persecution complex, and not the kind brought on by persistent griefing.

12-28-2013 @ 9:51 A.M.

Added IPs belonging to the following players' ISPs. Data provided by arin.net. Two ranges were added for manslayer as his ISP appears to have two subnets for the same range of IPs.

mort
Manslayer
DogePark
Feared_1
Wolfen

Updated list 12-28-2013 @ 10:20 P.M.
Added the following players' ISPs to the whitelist, for those that choose to use it.
Sokol
Captain_Henway
Sinbad
Wannab
XxHAMADEHxX
Nielk1
Red_Devil

Added the following.

Muffin
Kebbz
Mr Scout