HP3000-L Archives

August 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Wed, 9 Aug 2000 09:07:40 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Jim Phillips wrote:
>
> Okay, as I sit here at 9:47 PM EDT waiting for the MCI network tech to call
> back and (hopefully) get our frame relay circuit back up, I'm mulling around
> something that yet another MCI techie told me this afternoon (as we were
> troubleshooting why our redundant, diversely-routed, backup circuit doesn't
> seem to work - sure could use it now!) as he was pinging around our network.
> He said, "Hey, what's a Jet Direct?" and I told him what it was and what it
> was used for and he said "Well, I just telnetted and/or pinged it [I'm not
> sure which].  Don't you have a firewall there?"
>
> To which I replied, "Why?  Don't we have a private IP address space?" (All
> of our IP addresses begin with 10.251.46.xxx).  And he said, "Yes, but we
> (meaning the MCI techs whom we pay a great deal of money to watch over our
> network for us) can access it".

The Internet has no way of knowing that you own 10.251.46.xxx, so the tech
couldn't have accessed your private addresses from the outside world.

What possibly happened is maybe the tech telnetted and logged on to your
router, if he has the password to do that, and from there was able to
telnet/ping to your internal network.

- Mark B.

ATOM RSS1 RSS2