User talk:ST47: Difference between revisions
Line 104: | Line 104: | ||
:{{re|Dennis Brown}} Looking at each of the constituent /24s, they are all proxy or cloud hosting services. In order, hostinger, packethub, and two by heficed. I think they're all eligible to stay blocked, and I note that the full /22 is also blocked globally. [[User:ST47|ST47]] ([[User talk:ST47#top|talk]]) 22:12, 13 January 2024 (UTC) |
:{{re|Dennis Brown}} Looking at each of the constituent /24s, they are all proxy or cloud hosting services. In order, hostinger, packethub, and two by heficed. I think they're all eligible to stay blocked, and I note that the full /22 is also blocked globally. [[User:ST47|ST47]] ([[User talk:ST47#top|talk]]) 22:12, 13 January 2024 (UTC) |
||
::That was my thing, I noticed that ISP is on a /24, not a /22, so there seems to be some collateral damage with a /22 block. I have no issue with the /24 being blocked, but I don't quite understand why the /22 is needed. Maybe it is just my misunderstanding (always possible), but it seems the ISP you are trying to block is only /24. The *.*.93.*/24 that the user is using isn't HOSTINGER-HOSTING (*.*.92.*/24), it is a different ISP altogether, TEFINCOMSA-AS-AP. Both are using /24 only. Again, maybe you did this on purpose and I just don't understand, but it *seems* that the /22 is walking outside of HOSTINGER's range, which is only a /24. Are we sure TEFINCOMSA is a relay? 02:57, 14 January 2024 (UTC) |
::That was my thing, I noticed that ISP is on a /24, not a /22, so there seems to be some collateral damage with a /22 block. I have no issue with the /24 being blocked, but I don't quite understand why the /22 is needed. Maybe it is just my misunderstanding (always possible), but it seems the ISP you are trying to block is only /24. The *.*.93.*/24 that the user is using isn't HOSTINGER-HOSTING (*.*.92.*/24), it is a different ISP altogether, TEFINCOMSA-AS-AP. Both are using /24 only. Again, maybe you did this on purpose and I just don't understand, but it *seems* that the /22 is walking outside of HOSTINGER's range, which is only a /24. Are we sure TEFINCOMSA is a relay? 02:57, 14 January 2024 (UTC) |
||
:::{{re|Dennis Brown}} [https://whois-referral.toolforge.org/gateway.py?lookup=true&ip=194.195.93.0 the 93 range is Packethub which is a cloud service provider closely associated with public vpn services]. google shows that tefincom is also closely associated with nordvpn. [[User:ST47|ST47]] ([[User talk:ST47#top|talk]]) 04:10, 15 January 2024 (UTC) |
|||
== ''The Signpost'': 10 January 2024 == |
== ''The Signpost'': 10 January 2024 == |
Revision as of 04:10, 15 January 2024
12.172.251.102
Hi--I think this is a proxy? Maybe there's a range you can block. These edits are from a longterm disruptor, a really childish one. Thanks in advance! Drmies (talk) 13:34, 16 November 2023 (UTC)
Bumping thread for 60 days. — Mdaniels5757 (talk • contribs) 14:40, 2 December 2023 (UTC)
Administrators' newsletter – January 2024
News and updates for administrators from the past month (December 2023).
- Following the 2023 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Aoidh, Cabayi, Firefly, HJ Mitchell, Maxim, Sdrqaz, ToBeFree, Z1720.
- Following a motion, the Arbitration Committee rescinded the restrictions on the page name move discussions for the two Ireland pages that were enacted in June 2009.
- The arbitration case Industrial agriculture has been closed.
- The New Pages Patrol backlog drive is happening in January 2024 to reduce the backlog of articles in the new pages feed. Currently, there is a backlog of over 13,000 unreviewed articles awaiting review. Sign up here to participate!
My IP is not in 103.212.224.0/22
I Have a Different IP ArtemisandLouie (talk) 07:16, 5 January 2024 (UTC)
range block
[1] UTRS ticket [2] is the reference. Shouldn't that /22 block be a /24 block? The /22 seems to be walking into a range that is not a webhost. I haven't reserved that ticket in case you want to handle it. Dennis Brown 2¢ 07:32, 12 January 2024 (UTC)
- @Dennis Brown: Looking at each of the constituent /24s, they are all proxy or cloud hosting services. In order, hostinger, packethub, and two by heficed. I think they're all eligible to stay blocked, and I note that the full /22 is also blocked globally. ST47 (talk) 22:12, 13 January 2024 (UTC)
- That was my thing, I noticed that ISP is on a /24, not a /22, so there seems to be some collateral damage with a /22 block. I have no issue with the /24 being blocked, but I don't quite understand why the /22 is needed. Maybe it is just my misunderstanding (always possible), but it seems the ISP you are trying to block is only /24. The *.*.93.*/24 that the user is using isn't HOSTINGER-HOSTING (*.*.92.*/24), it is a different ISP altogether, TEFINCOMSA-AS-AP. Both are using /24 only. Again, maybe you did this on purpose and I just don't understand, but it *seems* that the /22 is walking outside of HOSTINGER's range, which is only a /24. Are we sure TEFINCOMSA is a relay? 02:57, 14 January 2024 (UTC)
- @Dennis Brown: the 93 range is Packethub which is a cloud service provider closely associated with public vpn services. google shows that tefincom is also closely associated with nordvpn. ST47 (talk) 04:10, 15 January 2024 (UTC)
- That was my thing, I noticed that ISP is on a /24, not a /22, so there seems to be some collateral damage with a /22 block. I have no issue with the /24 being blocked, but I don't quite understand why the /22 is needed. Maybe it is just my misunderstanding (always possible), but it seems the ISP you are trying to block is only /24. The *.*.93.*/24 that the user is using isn't HOSTINGER-HOSTING (*.*.92.*/24), it is a different ISP altogether, TEFINCOMSA-AS-AP. Both are using /24 only. Again, maybe you did this on purpose and I just don't understand, but it *seems* that the /22 is walking outside of HOSTINGER's range, which is only a /24. Are we sure TEFINCOMSA is a relay? 02:57, 14 January 2024 (UTC)
The Signpost: 10 January 2024
- From the editor: NINETEEN MORE YEARS! NINETEEN MORE YEARS!
- Special report: Public Domain Day 2024
- Technology report: Wikipedia: A Multigenerational Pursuit
- News and notes: In other news ... see ya in court!
- WikiProject report: WikiProjects Israel and Palestine
- Obituary: Anthony Bradbury
- Traffic report: The most viewed articles of 2023
- Comix: Conflict resolution
Hello. Thanks for blocking users related to 'DENOSIO'.
As someone who has contributed to many visa policies and map production over the past 2 years, I have recently been focusing on defending and cleaning up the suddenly increasing number of successors to "DENOSIO."
I plan to continue to defend editors who deface visa pages in the future. Lades2222 (talk) 06:20, 14 January 2024 (UTC)