GameDr04
New Around Here
I have been having a very bizarre issue with terminal-based file transfers for the past couple months, now.
This issue has taken a full five weeks of the most outrageous troubleshooting steps to identify (it's how I roll).
I removed the cable that Xfinity put on the outside of my house and replaced it with my own, full-copper, quad-shield cable that I buried in conduit in my backyard, myself.
I upgraded and changed my modem...four times (by the way, Motorola MB8611 and Netgear CM2050V are pretty great.)
After all that...it seems to be at the router level.
Any time I scp or rsync something larger than a few megabytes from home to one of my many off-premises servers, I will inevitably be presented with this error:
HOWEVER
If I connect to a VPN on the sending machine at home and scp/rsync through that, every transfer is guaranteed to complete successfully.
This is true for NordVPN, three of my friends' OpenVPN servers, and even a PPTP VPN I setup at work just to test this.
A few years ago, somebody mentioned a similar problem on SNB, and he narrowed it down to CTF (NAT Acceleration).
https://www.snbforums.com/threads/ssh-broken-pipe-somehow-related-to-nat-acceleration.50294/
Unfortunately, disabling CTF is not an option on the AX11000 so I can't readily test that.
Has anybody else been having problems with SSH, SCP, RSYNC, or any other such terminal-level things?
This issue has taken a full five weeks of the most outrageous troubleshooting steps to identify (it's how I roll).
I removed the cable that Xfinity put on the outside of my house and replaced it with my own, full-copper, quad-shield cable that I buried in conduit in my backyard, myself.
I upgraded and changed my modem...four times (by the way, Motorola MB8611 and Netgear CM2050V are pretty great.)
After all that...it seems to be at the router level.
Any time I scp or rsync something larger than a few megabytes from home to one of my many off-premises servers, I will inevitably be presented with this error:
Code:
client_loop: send disconnect: Broken pipe
rsync: [sender] write error: Broken pipe (32)
HOWEVER
If I connect to a VPN on the sending machine at home and scp/rsync through that, every transfer is guaranteed to complete successfully.
This is true for NordVPN, three of my friends' OpenVPN servers, and even a PPTP VPN I setup at work just to test this.
A few years ago, somebody mentioned a similar problem on SNB, and he narrowed it down to CTF (NAT Acceleration).
https://www.snbforums.com/threads/ssh-broken-pipe-somehow-related-to-nat-acceleration.50294/
Unfortunately, disabling CTF is not an option on the AX11000 so I can't readily test that.
Has anybody else been having problems with SSH, SCP, RSYNC, or any other such terminal-level things?