Opened 3 years ago

Last modified 22 months ago

#19988 new defect

Warn when Port addresses have no effect

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay warning logging usability setup annoying confusion
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

Following up #13953, we could also warn:
"Setting Listen Address %s on the %sNoListen port %d has no effect. Tor uses Address for IPv4 and the first advertised port for IPv6.", address_string, ip_version == 6 ? "secondary " : "", port_number

We would warn on every IPv4 NoListen port, and the second and subsequent IPv6 NoListen ports.

I think this could be useful, but it could also be too verbose.

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by s7r

Too verbose / complicated. I think it should suffice just to automatically set Address as the address from the first *Advertised* ORPort and build the descriptor.

comment:2 in reply to:  1 Changed 3 years ago by teor

Replying to s7r:

Too verbose / complicated. I think it should suffice just to automatically set Address as the address from the first *Advertised* ORPort and build the descriptor.

If you want to do that, it's a behaviour change, open a ticket, and mark it 030-proposed.

comment:3 Changed 3 years ago by s7r

#19919 describes exactly this, and it is marked 030-proposed.

comment:4 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 22 months ago by nickm

Keywords: tor-relay warning logging usability setup annoying confusion added
Note: See TracTickets for help on using tickets.