John Summerfield wrote:
Justin Cook wrote:How about checking your mtu? I've had very strange SSH behavior with MTU too large. Try setting 1300 or so.You said that before.MTU matters on a physical link. Once there's another hop, it's all irrelevant, intermediate systems repackage the data.There's rarely a need for anyone to fiddle with MTU, 1500 works on ethernet end of story.On ADSL, modern setup software gets it right (it's a little less than 1500), and on mainframes (not using ethernet) one might be using around 32k. Whatever my mainframe is using, my PC talking to it and using another physical link still uses 1500 (or a little less over ADSL).Even if MTU can cause a problem (which I doubt), it would do so from the nearby machine (which maybe is on the same switch), not the remote one.
I've had a system which was connecting to a remote system using a VPN and the fragmentation of the packets wasn't being handled correctly (the VPN concentrator wasn't under my control). The ssh connection would drop when doing large transfers via scp and at other random times. Setting the MTU down to 1300 took care of the problem. This was apparently one of those rare occurrences (and it likely could have been taken care of if the VPN concentrator were configured correctly).
However, the initial ssh connection wasn't usually a problem. Hugh
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
