Great Circle Associates Firewalls
(April 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: discovering what a firewall can pass
From: John Fitzpatrick <72702 . 1667 @ CompuServe . COM>
Date: 27 Apr 96 19:11:47 EDT
To: Michael Baumann <baumann @ proton . llumc . edu>
Cc: firewall newsgroup <FIREWALLS @ GREATCIRCLE . COM>

>>
Try Telnet.. if it works you can. 
"Can I ping?" Try to ping a known host.
"Can I ftp?" Try a well known site.
"Can I UseNet?" Use your newsreader, point to a remote NNTP server
"Can I http?" Try a browser
"Can I rlogin?" The answer to this one better be no.
you get the idea... :)
<<

Thanks, Michael!

Sound advice.  However, if, for example, I cannot telnet to
somehost.someplace.com, does that mean that 
a> the firewall doesn't allow it?
b> somehost.someplace.com is down?
c> my ip stack is misconfigured?
d> some internal router is hosed?
e> the Internet has been dismantled by the FCC?
you get the idea... ;)

Appreciatively,
John



Follow-Ups:
Indexed By Date Previous: FW: FW: NT & C2
From: MIKE MOORE <msquard @ flash . net>
Next: RE: destruktiv hackers
From: Russ <Russ @ RC . Toronto . on . ca>
Indexed By Thread Previous: Re: discovering what a firewall can pass
From: Darren Reed <avalon @ coombs . anu . edu . au>
Next: Re: discovering what a firewall can pass
From: Kirill Bolshakov <raven @ ssrouter . ioffe . rssi . ru>

Google
 
Search Internet Search www.greatcircle.com