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

Closed (moved)
(moved)
Open
Created Feb 08, 2011 by Roger Dingledine@arma

bridge users who configure the non-canonical address of a bridge switch to its canonical address

If I run a bridge with

Address 128.31.0.34
ORListenAddress 128.31.0.39

and then somebody runs their Tor client with

bridge 128.31.0.39

then it will connect, fetch the bridge descriptor, try to build a circuit by using 128.31.0.34, fail, and then sit there circuitless and bridgeless.

This bug is important because it means if you run a multihomed bridge, all the clients will immediately switch to using its single canonical address, ignoring all the other addresses you configured. If that canonical address gets blocked, the other addresses don't matter even if they'd still work.

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