Jump to content

User talk:Tobias10

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Range block

[edit]
This user's unblock request has been reviewed by an administrator, who declined the request. Other administrators may also review this block, but should not override the decision without good reason (see the blocking policy).

Tobias10 (block logactive blocksglobal blockscontribsdeleted contribsfilter logcreation logchange block settingsunblockcheckuser (log))


Request reason:

I set up an account earlier today at university. I am now at home, logged into to the VPN system, but can't login due to a range block, clearly because I am trying to use a shared IP address (i presume). Would someone please allow my account to operate, to avoid being affected by this 'range block' - think that was what is was called. I am happy for someone to monitor the account when i edit if they have any concerns. Hope this wont be a problem, thanks

Decline reason:

Procedural decline. You'll need to provide us with more information, particularly the IP address you're using, by copying the appropriate part of the message you see when you try to edit and pasting it to this page. ​—DoRD (talk)​ 18:56, 19 March 2012 (UTC)[reply]


If you want to make any further unblock requests, please read the guide to appealing blocks first, then use the {{unblock}} template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired. Do not remove this unblock review while you are blocked.

This user's unblock request has been reviewed by an administrator, who declined the request. Other administrators may also review this block, but should not override the decision without good reason (see the blocking policy).

Tobias10 (block logactive blocksglobal blockscontribsdeleted contribsfilter logcreation logchange block settingsunblockcheckuser (log))


Request reason:

same as above, the IP of my VPN address i would like to use is 129.215.4.0/24, thanks again

Decline reason:

Unblock request is coming from the same person for whom the rangeblock was intended for. As such, this account is now directly blocked as a sock puppet. Per recent egregious abuse of unblock request, talk page access has been revoked. --MuZemike 21:27, 19 March 2012 (UTC)[reply]


If you want to make any further unblock requests, please read the guide to appealing blocks first, then use the {{unblock}} template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired. Do not remove this unblock review while you are blocked.

.

Hmm, I thought maybe it was blocked as an open proxy, but according to this, the range was blocked on 11 March, presumably due to an IP hopping sockpuppet. Is that whole range dedicated to the VPN, or just one IP address? I'll ask the blocking admin if s/he can shed some light. ~Amatulić (talk) 19:55, 19 March 2012 (UTC)[reply]

I think it's blocked the whole VPN, as if I try it on my friends login it doesn't appear to work either. I now have an account as I created it from a university computer with therefore a different IP and thought I could then just use that to log in, and just want to use that. Im not asking account creation to be lifted, or to be able to edit as an IP user. Otherwise I would only be able to edit away from my main computer (Tobias10 (talk) 20:07, 19 March 2012 (UTC)).[reply]
Understood — and your account is not blocked. But my question was whether the VPN system at your university uses the entire /24 range (256 IP addresses from 129.215.4.0 to 129.215.4.255) or just a few IP addresses in it? If the VPN system is using just one or just a few IP addresses, then holes could be poked in the larger block. ~Amatulić (talk) 21:00, 19 March 2012 (UTC)[reply]

Im not really sure, it appears that the client and server addresses are slightly different, if that's any help, but not sure whether it uses the full range(Tobias10 (talk) 21:18, 19 March 2012 (UTC)).[reply]