Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #31413

Closed (moved)
(moved)
Open
Created Aug 14, 2019 by Neel Chauhan@neel

Check for internal IPv6 connects and extends

In teor's comment in #31088 (moved):

You've added some code that isn't needed yet. Please reject all IPv6 extends in this patch, and open a separate child ticket of #24403 (moved) for allowing IPv6 extends.

Edited to add:

When we add support for IPv6 extends, we should check for internal IPv6 addresses in extends. And we should check for internal IPv6 connects on non-bridge clients, relays, and authorities.

ExtendAllowPrivateAddresses should disable these new checks.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking