Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33385

Closed (moved)
Open
Opened Feb 19, 2020 by David Fifield@dcf

In server, treat a purported client IP address of 0.0.0.0 as missing

In #33157 (moved), proxies sometimes fail to extract a meaningful client IP address from the client's SDP and send ?client_ip=0.0.0.0 to the bridge. The bridge counts an address of 0.0.0.0 as a client that had an IP address, which inflates the numerator in the "in the past %.f s, %d/%d connections had client_ip" log line.

This is a patch to treat a client address of 0.0.0.0 or [::] as if it were not present at all.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33385