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 |
| core1.portland | ||
| 66.78.83.6 | + | ve1.core1.portland.ipns.com |
| 216.162.207.60 | + | ve254.core1.portland.ipns.com |
| 208.110.128.52 | ve255.core1.portland.com | |
| core1.saltlakecity | ||
| 208.110.128.9 | + | ve1.core1.saltlakecity.ipns.com |
| 208.110.128.49 | + | ve255.core1.saltlakecity.ipns.com |
| core1.seattle | ||
| 216.162.207.65 | + | fe-3-2.core1.seattle.ipns.com |
| 208.110.128.44 | + | ve254.core1.seattle.ipns.com |
| 216.162.207.58 | + | ve255.core1.seattle.ipns.com |
| core2.saltlakecity | ||
| 208.110.128.10 | + | ve1.core2.saltlakecity.ipns.com |
| 208.110.128.42 | + | ve254.core2.saltlakecity.ipns.com |
| 208.110.128.50 | + | ve255.core2.saltlakecity.ipns.com |
| ebr1.portland | ||
| 216.162.207.59 | + | ge-0-1-0-888.ebr1.portland.ipns.com |
| ebr1.saltlakecity | ||
| 208.110.128.43 | + | ge-0-3-0-2000.ebr1.saltlakecity.ipns.com |
| 208.110.128.51 | + | ge-0-3-0-2001.ebr1.saltlakecity.ipns.com |
| ebr1.seattle | ||
| 216.162.207.57 | + | ge-1-0-0-888.ebr1.seattle.ipns.com |
| 216.162.207.66 | o | fe-5-7.core1.seattle2.ipns.com |
| 209.95.37.11 | pdx-pm01.navi.net | |
| 216.162.207.129 | ve4.core1.seattle.sitespecific.net | |