I don't know if this is a fedora question or not, but I'm hoping it's an OS-level config issue.
I have a laptop that runs Fedora 24, and a virtual machine with CentOS that I use as my mailserver. I'm an old fogey who doesn't like all this multimedia mail stuff, so I still use pine/alpine and text emails.
The problem is this. When I ssh to my virtual machine from my laptop and run pine, it will work for a few minutes and then hang. If I close the terminal (which kills pine) and ssh in again, it works again -- for a few minutes. Then it hangs.
I don't *think* it's a pine/alpine issue itself. If I come in using shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
If I just ssh in and do other stuff, it doesn't hang.
Finally, it only happens at work. My workplace has a very restricted wired network and a very open wireless network. We are supposed to "work" on the wired network and attach our cellphones and private laptops to the wireless network, which solves a lot of social engineering type security issues. If you want to do streaming media, or download cute stuff, don't use the work box -- use your own. So, the problem occurs on this wireless system. It doesn't seem to happen when I connect from my wireless at home.
Any pointers? It's very frustrating...
billo
On Tue, 20 Sep 2016, vendor@billoblog.com wrote:
I don't *think* it's a pine/alpine issue itself. If I come in using shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
Sigh. I take that back. I just happened using shellinabox. I guess it just happens less often...
billo
*have you tried tossing a few -v's in your cmdlin ?*
*ssh -v -v -v usr@host ???* *also you might consider setting debug logging ssh_config*
On Tue, Sep 20, 2016 at 5:41 AM, vendor@billoblog.com wrote:
On Tue, 20 Sep 2016, vendor@billoblog.com wrote:
I don't *think* it's a pine/alpine issue itself. If I come in using shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
Sigh. I take that back. I just happened using shellinabox. I guess it just happens less often...
billo
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Sep 20, 2016 7:42 AM, vendor@billoblog.com wrote:
On Tue, 20 Sep 2016, vendor@billoblog.com wrote:
I don't *think* it's a pine/alpine issue itself. If I come in using
shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
Sigh. I take that back. I just happened using shellinabox. I guess it just happens less often...
billo
Determine if pine itself is hanging by running it in screen on the remote host. Determine if you have connection problems by making the ssh client verbose, ssh -vvv. If your environment requires you to proxy ssh through a bastion to get to hosts in the wild, know the bastion's keepalive/timeout configs.
-- Pete
On 09/20/2016 09:23 AM, Pete Travis wrote:
On Sep 20, 2016 7:42 AM, <vendor@billoblog.com mailto:vendor@billoblog.com> wrote:
On Tue, 20 Sep 2016, vendor@billoblog.com
mailto:vendor@billoblog.com wrote:
I don't *think* it's a pine/alpine issue itself. If I come in using
shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
Sigh. I take that back. I just happened using shellinabox. I guess it just happens less often...
billo
Determine if pine itself is hanging by running it in screen on the remote host. Determine if you have connection problems by making the ssh client verbose, ssh -vvv. If your environment requires you to proxy ssh through a bastion to get to hosts in the wild, know the bastion's keepalive/timeout configs.
I added a /etc/sysctl.d/10-openupssh.conf file that contains the following:
net.ipv4.tcp_sack = 0
which may help. Without it, certain SSH things like scp and sftp would slow to a crawl after a while. This may be what you're seeing. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - I was married by a judge. I should have asked for a jury. - - -- Groucho Marx - ----------------------------------------------------------------------
Try to use screen/tmux. i think it will help u.
В Вт, 20/09/2016 в 07:38 -0500, vendor@billoblog.com пишет:
I don't know if this is a fedora question or not, but I'm hoping it's an OS-level config issue.
I have a laptop that runs Fedora 24, and a virtual machine with CentOS that I use as my mailserver. I'm an old fogey who doesn't like all this multimedia mail stuff, so I still use pine/alpine and text emails.
The problem is this. When I ssh to my virtual machine from my laptop and run pine, it will work for a few minutes and then hang. If I close the terminal (which kills pine) and ssh in again, it works again -- for a few minutes. Then it hangs.
I don't *think* it's a pine/alpine issue itself. If I come in using shellinabox and open pine using a browser terminal, it doesn't happen. If I use some other client, e.g. roundcube, it doesn't happen.
If I just ssh in and do other stuff, it doesn't hang.
Finally, it only happens at work. My workplace has a very restricted wired network and a very open wireless network. We are supposed to "work" on the wired network and attach our cellphones and private laptops to the wireless network, which solves a lot of social engineering type security issues. If you want to do streaming media, or download cute stuff, don't use the work box -- use your own. So, the problem occurs on this wireless system. It doesn't seem to happen when I connect from my wireless at home.
Any pointers? It's very frustrating...
billo _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org