[Novalug] determining where a port is blocked

[gregory pryzby]

On Tue, Nov 13, 2007 at 10:01:44PM -0500, Kevin Dwyer wrote:
> Unless you have a "business" account with a favorable agreement, you'll
> only raise your blood pressure.

yep... I am breaking TOS. 
 
> Greg: It's not usually possible to figure out where packets are being
> dropped without access to the nodes involved.  Since they're just
> dropping instead of rejecting, you don't even really have much to go on.

that is what I thought, but wanted to make sure there wasn't something
that I didn't know or had forgotten.
 
> -kpd
> 
> On Tue, Nov 13, 2007 at 09:49:12PM -0500, Jay Hart wrote:
> > Call'em and raise heck...
> > 
> > Jay
> > 
> > > Looks like only port 22 is allowed into the verizon network and to my
> > > box.
> > >
> > > Is there a way to figure out when a packet is blocked for a port while
> > > transversing the network?
> > >
> > > I don't want to run imaps on port 22 b/c I need/want shell access and
> > > forwarding...
> 

-- 
greg pryzby                              greg at pryzby dot org
AIM: gpryzby                             http://pryzby.org/
fingerprint: 8A1A DB90 869F 5DD1 D6E9 EEB6 C156 6B04 849F A86F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://calypso.tux.org/pipermail/novalug/attachments/20071113/501df99b/attachment.pgp