Green |
+ | Inferred identifier, true positive when evaluated against training data |
Orange |
- | Inferred identifier, false negative when evaluated against training data |
Red |
! | Inferred identifier, false positive when evaluated against training data |
Red |
x | Inferred identifier, but contains part of IP address literal embedded in hostname |
~ | False negative, not matched | |
o | No regex matched the interface, but the interface was the only interface in this suffix on the router | |
* | A filter regex matched the interface |
bb1.hiroshima | ||
61.114.162.101 | + | ge-1-0-0-1.bb1.hiroshima.fcc.ad.jp |
61.114.160.190 | + | so-1-3-0-0.bb1.hiroshima.fcc.ad.jp |
bb1.otemachi | ||
61.114.160.1 | + | ge-0-0-0-0.bb1.otemachi.fcc.ad.jp |
61.114.160.5 | + | ge-0-0-1-0.bb1.otemachi.fcc.ad.jp |
61.120.145.206 | ge-0-2-0.a21.tokyjp01.jp.ra.gin.ntt.net | |
bb1.shinjuku | ||
61.114.160.6 | + | ge-0-1-0-0.bb1.shinjuku.fcc.ad.jp |
202.176.57.1 | + | ge-0-3-0-2.bb1.shinjuku.fcc.ad.jp |
61.114.160.13 | + | ge-1-3-0-0.bb1.shinjuku.fcc.ad.jp |
bb2.hiroshima | ||
61.114.162.102 | + | ge-1-0-0-1.bb2.hiroshima.fcc.ad.jp |
61.114.160.194 | + | so-1-3-0-0.bb2.hiroshima.fcc.ad.jp |
bb2.osaka | ||
61.114.160.34 | + | ge-0-1-0-0.bb2.osaka.fcc.ad.jp |
61.114.160.134 | + | ge-0-1-1-0.bb2.osaka.fcc.ad.jp |
bb2.otemachi | ||
61.114.174.250 | + | ge-0-1-0-990.bb2.otemachi.fcc.ad.jp |
61.114.163.154 | + | ge-0-1-0-993.bb2.otemachi.fcc.ad.jp |
pe1.shinjuku | ||
61.114.160.18 | + | ge-0-0-0-0.pe1.shinjuku.fcc.ad.jp |
swh1.shinjuku | ||
61.114.168.250 | + | ge-0-1-0-0.swh1.shinjuku.fcc.ad.jp |
61.114.168.254 | + | ge-0-1-1-0.swh1.shinjuku.fcc.ad.jp |