=== iflema is now known as Guest10123
[06:43] <valorin> Anyone have any experience debugging SSH problems with  the error message of "Write failed: Broken pipe"?
[07:26] <gorilla> valorin: Sorry for the late response but I have...
[07:27] <gorilla> I have found that to be the case when I have ssh'ed from my work machine to my home machine and leave it for a while. I think it is caused by either end timing out. Nat connection at both ends bring on IPv6!
[07:42] <valorin> I've got IPv4 with NAT
[07:42] <valorin> its annoying cos our sys admins don't know what is happening
[07:46] <gorilla> In my experience, if you keep the connection busy (keep alive), you shouldn't see that message.
[07:47] <gorilla> I should probably look into it further but give that I don't control my work network, my understanding is going to be restricted at best.
[07:51] <head_victim> valorin: https://bbs.archlinux.org/viewtopic.php?id=97003 has a few tips
[07:51] <valorin> Yeah, nah, it's ok. I've got one of the admins checking it for me at the moment. It's probably something to do with the complex DMZ setup they've got
[07:52] <head_victim> gorilla: you might find it interesting to solve your issue as well
[07:52] <valorin> I'll take a look, thanks head_victim 
[07:53] <head_victim> valorin: I hope it helps :)
[07:55] <valorin> Mmm... I don't think the issue is server related, I'd say it's the firewalls which are causing my issue. Since we've rolled out identicial systems with the same config without issue outside this enviroment
[07:55] <valorin> Thanks anyway guys :)
[10:15] <gorilla> head_victim: for me it's not really an issue as the problem only occurs when I leave the connection idle overnight...
=== croppa is now known as croppa_
=== croppa_ is now known as croppa