Long-range ban?
Fish and I have been discussing semiseriously banning the 38.*.*.* range from the board for hosting our banned user, being evidently riddled with proxies and generally having a poor reputation.
Before we do so, though I want to make sure that none of our regulars regularly fall into that net. Hence, I request you all check your IPs and see if they're registered to the same ISP, or ARE 38.x.x.x.
Even if none are, I'm not entirely sure that were going to block all that. This is preliminary.
-Q
Before we do so, though I want to make sure that none of our regulars regularly fall into that net. Hence, I request you all check your IPs and see if they're registered to the same ISP, or ARE 38.x.x.x.
Even if none are, I'm not entirely sure that were going to block all that. This is preliminary.
-Q
Comments
Check Here
Thump
:badgrin:
I'm having doubts about it, but this was more of a negative determination (I hope that's the right phrase): If noone was on that network, we MIGHT proceed, but if a major contributor was, that would completely sink the idea.
In other words, we are NOT going to ban this range just because noone's on it.
-Q
-Kirk
You sure? That netblock is registered for an american company.
Thats weird, i swear i remmber having a 38, maybe it was 83 or something lol.
No. 192.168.0.1 and 192.168.0.3.
192.168.*.* is private, that's not your 'real' IP.
http://www.whatismyip.com/
AOL = dynamic IP.
-Q
For those that don't know, typing ipconfig in the command prompt isn't going to give you your public IP address... I have a feeling thats what some people did.
ipconfig would only give your public address if you were directly connected to the modem.