You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the existing data collected, you would be able to identify and feature nodes that are being filtered (neighbors). This could help nodes troubleshoot or identify traffic issues compared to unfiltered neighbors.
Return all server address values
resolve DNS to IP addresses
filter only and sort by IP
create filter to detect duplicate IPs on the first 3 octet (x.x.x.y)
create a display page to show any nodes resolving to those duplicate prefixes
The text was updated successfully, but these errors were encountered:
Since commit 11ad6e5 (and 3 more with fixes) there is additional line on each node page showing node IP and it's neighbor nodes count.
Still not sure what to do with IPv6-addresses (they are matched now by first three bytes too) and is it ok to reveal neighbor IPs/IDs (I consider them private so there is just a number now).
With the existing data collected, you would be able to identify and feature nodes that are being filtered (neighbors). This could help nodes troubleshoot or identify traffic issues compared to unfiltered neighbors.
The text was updated successfully, but these errors were encountered: