Closed trombonehero closed 7 years ago
Note: this tuple is now passed as four separate values: {client,server}_{ip,port}
.
This seems to work, thanks!
Actually, it looks like this filtering only applies to sockets and not connections?
Seems fixed by efd4eda1c0219d17453af2b3100a915693eda87d.
The
/nodes
query endpoint should also accept a 4-tuple (maybe namedtcp_tuple
?) as a parameter. This should return connections that definitely match the tuple as well as sockets that might.