[evla-sw-discuss] remote MIB access
James Robnett
jrobnett at aoc.nrao.edu
Tue Jun 7 10:17:05 EDT 2005
I thought there was a ticket on this but apparently not.
The VPN concentrators at the AOC and CV have been fixed so
they advertise routes for 10.80 and 10.64 addresses. Previously
they didn't advertise those routes so packets from remote machines
would go over commodity internet(1) which didn't work so well.
Please let me know if there are any subsequent problems with
remote MIB access.
James
1) At which point the packet should have just died, it's bad form
to route private address packets outside of an internal LAN (like
ours). SDC was apparently routing packets ... as were a sufficient
number of their peers (like sprint) so that ping packets to say
10.80.114.234 went to some computer in Maryland. Which is
why people claimed they could ping MIBS but not telnet to them.
They were pinging some poor saps private network in Maryland.
More information about the evla-sw-discuss
mailing list