6 May
2020
6 May
'20
12:34 a.m.
On 5/5/20 6:30 PM, Tomas Prybil wrote:
Unfortunately this doesn't seem to be feasible. The issue is that my ISP blocks SNMP
outbound -- I have no idea why they would so such a thing. And as far as I can tell there
isn't any way to tell Cisco to accept incoming SNMP requests on any port other than
the standard one.
paul Why don't we all agree on another portnumber like 10161 and do a PAT to
161 on
our destinations?
Well, only if we can ALSO run on 161. My upstream is bridged, and my
routing is done by the same Cisco as my DECnet stuff, so I can't easily
translate that for inbound requests.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
The Cisco
DECnet router implementation does not speak "decnet management" as
we all knew. The way we are using them the tunnel end-points are on the Internet.
Most of the information "missing" is actually available through the SNMP MIB,
so if we could agree on a common read-only community and publish the IP addresses
of those routers it would be possible to complete Paul's map..
I would definitely be up for that. Maybe "hecnet-ro" for the community
name?
Regards, Tim.