I use cox in N.O. and never have this happen (unless my power goes
out in my house).  This email is being sent out that way now.

Considering the connection never drops between you and your gateway
but it does drop between the gateway and your office, I don't see
how you can point at cox as the problem. (not that they'd help
you anyway).  The portion where you're losing the connection is
inside the LAN.  You're not losing the part of the connection that
runs over cox.  Run ssh verbosely and see if there's some hint in the
output when the connection drops (ssh -V)

what versions of ssh do you have on the firewall and your office box?


On Tue, Aug 13, 2002 at 09:11:43AM -0500, Brad Bendily wrote:
> I have a question for all the cox.net users out there.
> 
> I often use ssh sessions from my home, using my cox.net
> connection, to my work. Very often my sessions get dropped.
> None of my peers seems to have this problem when connecting
> from their home to our office. So I can only assume the 
> problem is on my end. I have linux box as a gateway/firewall
> for my cox connection. I first ssh to my gateway then ssh
> to my office. I never loose the connection to my gateway just 
> the session to my office. It seems to happen at random times.
> Usually I'll leave my session open all the time, and at least
> once a day lately it gets dropped. I really depends on how
> often I use it as to how often it gets dropped. Sometimes I
> can't sustain a connection cause it'll get dropped repeatedly.
> But then I can go for about a week and not loose a session.
> 
> Has any other cox.net users out there experienced this behavior?
> 
> I'm leaning the blame towards cox, but I don't know how they'll
> take it if I call and say my ssh sessions keep getting dropped
> this sucks what are you gonna do about it?
> 
> Any ideas?
> 
> Thanks
> -- 
> Brad Bendily - CNA
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://brlug.net/mailman/listinfo/general_brlug.net

-- 
Scott Harney<[EMAIL PROTECTED]>

Reply via email to