New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ipv6 support #139

Open
baloo opened this Issue Aug 31, 2017 · 9 comments

Comments

5 participants
@baloo

baloo commented Aug 31, 2017

I'm not sure where to report that, but https://utrs.wmflabs.org/ does not have any ipv6 set up. Because it checks the users ip when submitting a form, one can not request a unblock for an ipv6 range if its ipv4 is not blacklisted either.

Maybe there is a better place to report such an issue, please let me know of any better place and I will comply.

Thank you

@Matthewrbowker

This comment has been minimized.

Show comment
Hide comment
@Matthewrbowker

Matthewrbowker Aug 31, 2017

Contributor

See https://phabricator.wikimedia.org/T37947 - There is no way to get IPv6 until the underlying architecture allows it.

Contributor

Matthewrbowker commented Aug 31, 2017

See https://phabricator.wikimedia.org/T37947 - There is no way to get IPv6 until the underlying architecture allows it.

@Salvidrim Salvidrim assigned Salvidrim and unassigned Salvidrim Aug 31, 2017

@Salvidrim

This comment has been minimized.

Show comment
Hide comment
@Salvidrim

Salvidrim Aug 31, 2017

Contributor

Nevertheless, thanks for creating this issue to remind us to follow-up on IPv6 support once the system allows us to implement it.

Plus, we might want to consider putting in a note to direct users appealing IPv6 blocks to e-mail the mailing list instead or some other option besides just "not working".

Contributor

Salvidrim commented Aug 31, 2017

Nevertheless, thanks for creating this issue to remind us to follow-up on IPv6 support once the system allows us to implement it.

Plus, we might want to consider putting in a note to direct users appealing IPv6 blocks to e-mail the mailing list instead or some other option besides just "not working".

@baloo

This comment has been minimized.

Show comment
Hide comment
@baloo

baloo Aug 31, 2017

@Salvidrim out of curiosity (^^), may I ask which mailing I could send a request to? :)

baloo commented Aug 31, 2017

@Salvidrim out of curiosity (^^), may I ask which mailing I could send a request to? :)

@Salvidrim

This comment has been minimized.

Show comment
Hide comment
@Salvidrim

Salvidrim Aug 31, 2017

Contributor

It's in the footer of https://utrs.wmflabs.org !

Contributor

Salvidrim commented Aug 31, 2017

It's in the footer of https://utrs.wmflabs.org !

@baloo

This comment has been minimized.

Show comment
Hide comment
@baloo

baloo Aug 31, 2017

who reads footers nowadays ? (thank you very much)

baloo commented Aug 31, 2017

who reads footers nowadays ? (thank you very much)

@DoRD

This comment has been minimized.

Show comment
Hide comment
@DoRD

DoRD Jan 1, 2018

I just looked at a ticket where someone is requesting the unblock of an IPv6 address by submitting a request from an IPv4 address via a random blocked account. It's a novel approach to the problem, for sure. Is there a timeline for wmflabs.org IPv6 support?

DoRD commented Jan 1, 2018

I just looked at a ticket where someone is requesting the unblock of an IPv6 address by submitting a request from an IPv4 address via a random blocked account. It's a novel approach to the problem, for sure. Is there a timeline for wmflabs.org IPv6 support?

Salvidrim added a commit that referenced this issue Jan 2, 2018

IPv6 note
Until we can support IPv6 (#139) we should at least provide some instructions as to what users should do instead of having them jump through hoops in the more unconventional of ways (see ticket 20206.......); feel free to reword as desired.

The other thing that needs addressing is global blocks but these should be directed to Meta and not the mailing list and I think they should be detectable in the same way as enwiki blocks are thus it would require actual coding of that

@Salvidrim Salvidrim referenced this issue Jan 2, 2018

Closed

IPv6 message #145

@Salvidrim

This comment has been minimized.

Show comment
Hide comment
@Salvidrim

Salvidrim Jan 2, 2018

Contributor

(for reference, DoRD refers to ticket #20206)

Unfortunately @DoRD I don't really know more than what's written in https://phabricator.wikimedia.org/T37947 (in which the last entry is you subscribing in August :p), perhaps asking there will get some better answers. It's not impossible that TParis or DQ might have more insight into the process

I've just filed a pull request (#145) to at least add a note to direct IPv6 blocked users to e-mail us instead of doing weird stuff like that

Contributor

Salvidrim commented Jan 2, 2018

(for reference, DoRD refers to ticket #20206)

Unfortunately @DoRD I don't really know more than what's written in https://phabricator.wikimedia.org/T37947 (in which the last entry is you subscribing in August :p), perhaps asking there will get some better answers. It's not impossible that TParis or DQ might have more insight into the process

I've just filed a pull request (#145) to at least add a note to direct IPv6 blocked users to e-mail us instead of doing weird stuff like that

@dqwiki

This comment has been minimized.

Show comment
Hide comment
@dqwiki

dqwiki Apr 2, 2018

Member

I am working on (workaround) support for both autoblocks and IPv6 today. Sadly I only got as far as dealing with the text and code for autoblocks and not testing autoblocks or touching ipv6. I'll continue on this project. Work is on the ipv6-autoblock branch.

The method at which i'm providing this support is simply to include an option to add their IPv6 address. Not sure if this will only be presented after submitting or not yet.

Member

dqwiki commented Apr 2, 2018

I am working on (workaround) support for both autoblocks and IPv6 today. Sadly I only got as far as dealing with the text and code for autoblocks and not testing autoblocks or touching ipv6. I'll continue on this project. Work is on the ipv6-autoblock branch.

The method at which i'm providing this support is simply to include an option to add their IPv6 address. Not sure if this will only be presented after submitting or not yet.

@dqwiki dqwiki added this to In progress in DeltaQuad's Workboard Apr 2, 2018

@dqwiki

This comment has been minimized.

Show comment
Hide comment
@dqwiki

dqwiki Apr 2, 2018

Member

Tasklist:

Autoblocks

  • Add text and JS behavior to index.php
  • Test index,php implementation
  • Add autoblock field to DB
  • Ensure correct data is being sent to db
  • Change display of appeals.php
  • Verify autoblocks are clearly identified

IPv6 (Roundabout) Support

  • Add text to support addition
  • Add JS behavior to index.php
  • Verify JS behavior only shows post-submit failure
  • Test index,php implementation
  • Add ipv6 field to DB
  • Ensure correct data is being sent to db
  • Change display of appeals.php
  • Verify IPv6 are clearly identified
  • Provide original IPv4 for CU and make sure it's clearly noted that IPv6 is only claimed
Member

dqwiki commented Apr 2, 2018

Tasklist:

Autoblocks

  • Add text and JS behavior to index.php
  • Test index,php implementation
  • Add autoblock field to DB
  • Ensure correct data is being sent to db
  • Change display of appeals.php
  • Verify autoblocks are clearly identified

IPv6 (Roundabout) Support

  • Add text to support addition
  • Add JS behavior to index.php
  • Verify JS behavior only shows post-submit failure
  • Test index,php implementation
  • Add ipv6 field to DB
  • Ensure correct data is being sent to db
  • Change display of appeals.php
  • Verify IPv6 are clearly identified
  • Provide original IPv4 for CU and make sure it's clearly noted that IPv6 is only claimed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment