-
Notifications
You must be signed in to change notification settings - Fork 3
Consensus list contains nodes not accessible via port 443 #75
Comments
The circuit building works fine, but the issue comes from the routers selection. |
@cgrigis - can you please check that all nodes are now OK and then close this issue? |
Examining the last few files generated by
but that does not prove the issue is gone ;-) |
You mean adding a test to the generation of the |
What I had in mind was a unit test of the |
Yes, but if we're looking for Heisenbugs the |
I am not talking about heisenbugs, but about verifying that the filtering feature works on test data. Checking in |
So we should do both ;) Test that the IPv6:443 is correctly refused, and that new Volunteers? |
I can create a dummy consensus to test if the filtering works on the different cases. |
@laurent-girod Did you already have a chance to work on this? |
I haven't created the dummy yet. |
Using the [latest files released], I still occasionally experience errors where a circuit cannot be built:
A likely cause is that some nodes are accessed on a port other than 443, as some previous logs look like:
even though the generated consensus file should filter for those.
Examining the latest consensus file, there is an entry as follows:
which uses port 9001 on its IPv4 address, and port 443 on its IPv6 address, which would explain why it went through the filtering.
We also find entries such as:
and
with the same IP but different ports. Could that confuse the circuit building process?
The text was updated successfully, but these errors were encountered: