When you decide to map ordinary linux USER1 to SElinux sysadm_u user you will not be able to ssh to USER1.Still present in glibc-2.9_p20081201-r2. USER1 is now an ordinary Linux user, and by default this linux user USER1 is mapped to SElinux unconfined_u USER1, and by default all created user will be under SElinux unconfined_u, even root user Scenario: you create ordinary linux user here Let me explain, by default all user created on linux have the same unconfined_u SElinux user context, this means ordinary linux users are able to do what the root does, an explicit change or mapping between Linux user to SElinux user could prevent ssh from working properly. the date you posted your question/message, you may have been using a kernel version which was actually buggy.Īctually i found a solution to the problem, Please check your Linux users if they were mapped to your SELinux users. I'm not saying your problem is specifically due to the kernel 4.8, but wrt. I need to make some bisection from 4.8.1 to 4.8.11 for that. We can see the TCP channel of the SSHv2 protocol is being reset (RST flag of TCP set to 1) causing the connection to abort. On the technical side, we can narrow a little bit the issue thanks to the wireshark dump below I made. The destination side can remain on 4.8 if you want, in my use case this was working (tested). I switched the source (sending side) to 4.4 LTS and the problem disappeared (rsync, scp were working nicely again).
#XQUARTZ SSH BROKEN PIPE DRIVERS#
Like specified, playing with SSH KeepAlive parameters or kernel TCP parameters (TCPKeepAlive on/off) does not solve the problem.Īfter playing with usb to ethernet drivers and TCP dump, I realized the issue was due to the kernel 4.8. I experienced this problem as well and spent a few days tried to bissect it.
If not and the problem is still present, read on. It will auto-reconnect to SSH automatically whenever SSH session dead.įirst, make sure your issue is not related to this one.
#XQUARTZ SSH BROKEN PIPE INSTALL#
If you can't install mosh-server on your servers, then you could use my script here:
It will auto reconnect when your packets lost, that's pretty cool and suit all our needs, I think. You will need to install mosh-server in your target (the server you want to ssh'ed to) and mosh-client in your host machine. The only solution I found so far is mobile-shell. Then this error must be there with you over and over. So basically, if you are trying to use ssh over a VPN (corporate environment). Broken pipe generally means there was a network disconnect for some reason. If it is happening to a personal server of yours, you need to provide more information on what were you doing on the sshd server side, when this happened. If you are in a corporate environment, check with your firewall admins and see if they were updating rules and/or restarting the firewall after some sort of a change when this happens. Let me show you a comment from MelBurslan,
0 kommentar(er)
