Opened 5 years ago

Closed 5 years ago

#13108 closed defect (fixed)

Should I give up my relay with FDC address

Reported by: tmpname0901 Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Archived/general Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

My relay, in use for 18 months, was recently rendered useless by the decision to block the FDC address space. This is seen by this line in the logs:

[warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '194.109.206.212:80'. Please correct.

Now I'm being invoiced to continue this server. Should I just discontinue the server, or will the Authdir policy soon restore the usefulness of having an IP address in the FDC address space?

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by arma

Which relay is it?

Just because one directory authority is still refusing to vote about relays in that netblock doesn't mean a threshold of them still are.

comment:2 Changed 5 years ago by tmpname0901

It is not just one directory authority. I simplified for brevity. In real life it looks like this:

Sep 10 12:48:36.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '194.109.206.212:80'. Please correct.
Sep 10 12:48:36.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '193.23.244.244:80'. Please correct.
Sep 10 12:48:36.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '154.35.32.5:80'. Please correct.
Sep 10 12:48:36.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '208.83.223.34:443'. Please correct.
Sep 10 12:48:37.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '76.73.17.194:9030'. Please correct.
Sep 10 14:19:05.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '194.109.206.212:80'. Please correct.
Sep 10 14:19:05.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '193.23.244.244:80'. Please correct.
Sep 10 14:19:05.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '154.35.32.5:80'. Please correct.
Sep 10 14:19:05.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '208.83.223.34:443'. Please correct.
Sep 10 14:19:08.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '76.73.17.194:9030'. Please correct.
Sep 10 15:49:34.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '194.109.206.212:80'. Please correct.
Sep 10 15:49:34.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '193.23.244.244:80'. Please correct.
Sep 10 15:49:34.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '154.35.32.5:80'. Please correct.
Sep 10 15:49:34.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '208.83.223.34:443'. Please correct.
Sep 10 15:49:35.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '76.73.17.194:9030'. Please correct.

So every 90 minutes I am informed that five directory authorities don't like my address.

These relays rendered useless by the recent prohibition on FDC address space:

CzechMate E1A20DA2FF48852A4FCB89ECC7DC8F9175A06468
risky 4237EA00DCA74621921B0196220C8378E4CC9953

comment:3 Changed 5 years ago by Sebastian

Faravahar, dannenberg, dizum, urras, turtles. "Die üblichen Verdächtigen".

sorry tmpname, we'll try to sort it out. Thanks for being a relay and supporting the network

comment:4 Changed 5 years ago by arma

Looks like dizum resumed allowing them, and that was enough that these two relays are back in the consensus.

But only just barely, so we should try to get another directory authority or two to do the switch still.

comment:5 Changed 5 years ago by Sebastian

dizum still doesn't, urras does

comment:6 Changed 5 years ago by tmpname0901

Well, now I'm being blackballed by only 3 directory authorities. That's progress, I guess.

Sep 13 16:01:35.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '194.109.206.212:80'. Please correct.
Sep 13 16:01:35.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '193.23.244.244:80'. Please correct.
Sep 13 16:02:16.000 [warn] http status 400 ("Authdir is rejecting routers in this range.") response from dirserver '76.73.17.194:9030'. Please correct.

comment:7 Changed 5 years ago by Sebastian

Resolution: fixed
Status: newclosed

6/9 should ensure you're in the consensus reliably again. I can't force the other dirauth ops to act on this, so closing. Thanks for your support

Note: See TracTickets for help on using tickets.