I'm not sure what the goal is here judging by Case's and Henrik's post but if it's to ensure the connectivity to your ISP is still good I would suggest using the first hop out. That is the second hop on your traceroute to google.com.
On Fri, Apr 4, 2008 at 7:20 AM, case <casedj at 21cn.com> wrote:
Thanks!
Regards, Case ----- Original Message ----- From: "Henrik Stoerner" <henrik at hswn.dk> To: <hobbit at hswn.dk> Sent: Thursday, April 03, 2008 4:54 PM Subject: Re: [hobbit] How to monitor this Internet public IP of internalFTP server
On Wed, Apr 02, 2008 at 08:21:32PM +0800, casedj wrote:
We have an internal FTP server that's NATed via Cisco's PIX firewall, so it has a Internet public IP and offers public access.
But some people complain that FTP server is not stable. Depending on internal access (to its internal IP of FTP server), it seems ok. But we can't access its Internet public IP from internal network.
There maybe several possible causes, e.g. carrier's line quality, DNS resolution, etc. We want to monitor its Internet public IP of FTP server to check what the root cause is, how?
More of a network issue than a Hobbit one, really.
What I do is to have a Hobbit network probe running on a DSL connection from home, just looking at the publicly available services. Anything sitting on a public IP can be used, really.
Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer