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
  • #17873

Closed (moved)
Open
Opened Dec 16, 2015 by cypherpunks@cypherpunks

replacing 0.0.0.0 listeners at runtime fails

I had DNSPort 0.0.0.0:53 set. Some jerks on the internet started flooding me with DNS requests so I reconfigured tor to only have the DNSPort on my LAN interface. I sent tor a HUP to reload the config, and it exited because it tried to bind the new listener before unbinding the old one:

Dec 16 16:19:51.000 [notice] Opening DNS listener on 172.16.0.1:53
Dec 16 16:19:51.000 [warn] Could not bind to 172.16.0.1:53: Permission denied
Dec 16 16:19:51.000 [notice] Closing no-longer-configured DNS listener on 0.0.0.0:53
Dec 16 16:19:51.000 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Dec 16 16:19:51.000 [err] Reading config failed--see warnings above. For usage, try -h.
Dec 16 16:19:51.000 [warn] Restart failed (config error?). Exiting.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.3.5.x-final
Milestone
Tor: 0.3.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#17873