Opened 6 years ago

Closed 4 years ago

#9212 closed defect (worksforme)

arm can not parse "auto" port

Reported by: hsn Owned by: atagar
Priority: Medium Milestone:
Component: Core Tor/Nyx Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If you have configuration "ORPort 216.17.99.45:auto" then arm fails to parse it correctly.

self.sortPort = int(self.foreign.getPort())ValueError: invalid literal for int() with base 10: '216.17.99.45:auto'

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by arma

Wow -- does that work with Tor? (even ignoring arm)

comment:2 Changed 6 years ago by hsn

yes, it picks random port.

Its good, if you have too much traffic and want few days rest, just restart relay and it will take a while until tor clients will discover new port.

comment:3 Changed 6 years ago by atagar

Thanks for letting me know. The auto port feature came out after arm's last release. Arm definitely shouldn't choke this way, though I'm not quite sure how some features will handle it. Is there a way of getting tor to say what its real ORPort is? If not then I'll probably need to have arm disable its connection panel when set.

comment:4 Changed 6 years ago by hsn

Parse tor log.

comment:5 Changed 6 years ago by cypherpunks

ValueError: invalid literal for int() with base 10: '443 NoListen'

ORPort 443 NoListen
ORPort 10.0.0.7:9443 NoAdvertise

comment:6 Changed 4 years ago by atagar

Resolution: worksforme
Severity: Normal
Status: newclosed

Cleaning up old tickets. Nyx is undergoing a rewrite, if this is still relevant then feel free to reopen.

Note: See TracTickets for help on using tickets.