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 |
access34 | ||
144.202.254.23 | + | access34-g149.baltimoretechnologypark.com |
144.202.254.25 | + | access34-g249.baltimoretechnologypark.com |
dist01 | ||
144.202.254.9 | + | dist01-g1-1.baltimoretechnologypark.com |
144.202.254.11 | + | dist01-g1-2.baltimoretechnologypark.com |
dist02 | ||
144.202.254.13 | + | dist02-g1-2.baltimoretechnologypark.com |
144.202.254.15 | + | dist02-g1-3.baltimoretechnologypark.com |
mls1 | ||
144.202.157.162 | ~ | 144-202-157-162.baltimoretechnologypark.com |
144.202.157.166 | ~ | 144-202-157-166.baltimoretechnologypark.com |
144.202.157.172 | ~ | 144-202-157-172.baltimoretechnologypark.com |
144.202.254.8 | + | mls1-g1-5.baltimoretechnologypark.com |
144.202.254.12 | + | mls1-g1-6.baltimoretechnologypark.com |
mls1 | ||
144.202.254.33 | ! | mls1-g1-1.baltimoretechnologypark.com |
64.124.202.142 | 64.124.202.142.t00580-01.above.net | |
144.121.128.122 | 144.121.128.122.lightower.net | |
mls2 | ||
144.202.157.164 | ~ | 144-202-157-164.baltimoretechnologypark.com |
144.202.157.168 | ~ | 144-202-157-168.baltimoretechnologypark.com |
144.202.254.14 | + | mls2-g1-5.baltimoretechnologypark.com |
144.202.254.10 | mls2-g1-5.baltimoretechnoogypark.com | |
144.202.157.173 | ~ | 144-202-157-173.baltimoretechnologypark.com |
144.202.157.175 | ~ | 144-202-157-175.baltimoretechnologypark.com |
144.202.157.163 | o | 144-202-157-163.baltimoretechnologypark.com |
144.202.228.202 | o | 144-202-228-202.baltimoretechnologypark.com |