[tor-bugs] #9729 [Tor]: Make bridges publish a bridge descriptor per ORPort address

[Tor Bug Tracker & Wiki]

#9729: Make bridges publish a bridge descriptor per ORPort address
----------------------------------------------+----------------------------
 Reporter:  sqrt2                             |          Owner:
     Type:  enhancement                       |         Status:  new
 Priority:  normal                            |      Milestone:
Component:  Tor                               |        Version:  Tor:
 Keywords:  ORPort bridge multiple addresses  |  0.2.4.16-rc
Parent ID:                                    |  Actual Points:
                                              |         Points:
----------------------------------------------+----------------------------
 I run Tor 0.2.4.17-rc as a bridge configured with multiple IPv4 addresses
 and one ORPort line for each, like so:

 ORPort <n1>:443
 ORPort <n2>:443
 ...
 ORPort <nN>:443

 When starting tor, the log will show that only <n1> is self-tested and a
 bridge descriptor is published:

 [notice] Now checking whether ORPort <n1>:443 is reachable... (this may
 take up to 20 minutes -- look for log messages indicating success)
 [notice] Self-testing indicates your ORPort is reachable from the outside.
 Excellent. Publishing server descriptor.

 Tor should publish bridge descriptors for all the available addresses and
 the bridge authorities should probably put them into pools of different
 confidentiality levels.

 For clarity, the documentation should explain Tor's bandwidth allocation
 as configured with Relay(Bandwidth|Burst)Rate (per address or total).

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9729>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online