I'd say the majority of the time this is a due to an unreliable
internet connection or inconsistent equipment (routers, etc.) on the
connection. My router at home is a piece of crap (aren't all consumer
grade routers?) and if I leave an SSH connection open for several
hours it will eventually hang
Interesting, we use OpenVPN heavily, but we also have a lot not behind
the vpn. That will be something to test out, I haven't kept track of
which servers it happens with.
-matt
On 7/15/07, Tim Meanor <[EMAIL PROTECTED]> wrote:
I've seen a similar issue when I've had an ssh connection open to a
I've seen a similar issue when I've had an ssh connection open to a
remote site over a VPN connection (not a VPN client on my PC, but a
VPN connection between my site and the remote site, between Cisco
routers). Catting a large file would hang the connection, and I had
to kill and re-estab
Yeah I've set that on a few machines just to test. But these
connections aren't inactive. I'm actively working in that session
when it happens.
-matt
On 7/15/07, Jay Leafey <[EMAIL PROTECTED]> wrote:
Matt Shields wrote:
> It shouldn't be dns because the session is already established and it
>
Matt Shields wrote:
It shouldn't be dns because the session is already established and it
now IP based. I don't believe ssh tries to keep resolving the IP
again and again.
No session doesn't come back ever. It just hangs permanently.
-matt
We were seeing something similar to this a while b
Up till now I haven't had the time or energy to put into sniffing or
debugging at all. But it's getting to be a pain in the @ss, that's
why I'm trying to see if anyone else has these issues.
Here are the locations and hardware:
Home: comcast with linksys cable/dsl router, hard wired (no wifi),
On 7/12/07, Matt Shields <[EMAIL PROTECTED]> wrote:
No session doesn't come back ever. It just hangs permanently.
Curiouser and curiouser.
My first thought would be a firewall/router/switch timing out, but
that typically happens for idle sessions, and you said somewhere that
this is happenin
It shouldn't be dns because the session is already established and it
now IP based. I don't believe ssh tries to keep resolving the IP
again and again.
No session doesn't come back ever. It just hangs permanently.
-matt
On 7/12/07, Paul Valentin <[EMAIL PROTECTED]> wrote:
most problem in thi
most problem in this case is DNS!!
does the session comes ca. 30sec later?
problem can be:
1) the server has wrong dns-server in /etc/resolv.conf
2) the client ip is a private ip, and not in /etc/hosts
3) the server ip is not in clients /etc/hosts
point 2) is the problem i have most time
bg, p
selinux is turned off on both servers and desktops
On 7/12/07, Tru Huynh <[EMAIL PROTECTED]> wrote:
On Thu, Jul 12, 2007 at 09:46:00AM -0400, Matt Shields wrote:
> I've noticed this in CentOS 4 & 5 and Fedora 5 & 6. If I'm in Gnome
> desktop and using any of the terminal programs and I ssh into
On Thu, Jul 12, 2007 at 09:46:00AM -0400, Matt Shields wrote:
> I've noticed this in CentOS 4 & 5 and Fedora 5 & 6. If I'm in Gnome
> desktop and using any of the terminal programs and I ssh into any
> server, the connection just hangs. Not drops, it just hangs and
> doesn't recover.
>
ssh -vvv
11 matches
Mail list logo
