5 Nov
2021
5 Nov
'21
6:11 p.m.
Yes, that's a typical issue. Or DNA-compliant equipment that has NICE turned off or
restricted. I looked into using the DECnet MIB to get information out of Cisco routers
but that didn't seem to be practical.
If a Cisco router is visible from a compliant router, it should appear. But if you have a
Cisco router behind another one, the behind one won't be mapped unless there is
another router in the same area, one that does speak NICE, so it's seen as reachable.
paul
On Nov 5, 2021, at 1:04 PM, Johnny Billquist <bqt
at softjar.se> wrote:
Probably the problem that Cisco equipment don't talk NICE. :-)
Johnny
On 2021-11-05 17:53, Dave McGuire wrote:
On 11/5/21 11:08 AM, Paul Koning wrote:
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol You can look at the map
(http://akdesign.dyndns.org:8080/map <http://akdesign.dyndns.org:8080/map>).
Physicallly closest may not be the best answer -- closest to the rest of the net is also
interesting -- but both of those should be visible on the map. You can turn off Level 1
nodes and links to see the area routing backbone only, that's probably the best
resource to answer your question.
We may have discussed this before, but that map
shows nothing coming in our out of our site here, but there are quite a few tunnels. Is
this a protocol support or access issue?
-Dave