Shannon Roddy <[EMAIL PROTECTED]> writes: > Well, I just changed the MTU on the linux box that was having problems > scp'ing through the VPN and now I can copy files through. However I > had to change it to *500*! Anything larger would not work! Not being > a networking guy... this is a real pain.
s/real pain/excellent learning opportunity/ weird. what kind of routers do you hav in btween the 3 caltech networks? Can you do some logging or packet sniffing? the key now is to find where exactly the transmission is being stopped. There's no way you MTU should be set way down at 500. that's just odd. how bad is throughput now from this box? also, have you tried other apps for transferring? do you have the same results? > Also, I tried some of the pf stuff the other day and that did not fix > anything. crub, no-df, etc.... > > Can someone clue me in as to what could make the Caltech location > fail, but all other locations work? Number of switches? routers? > switch/router configuration? The same file, etc. would work anywhere > else, but not Caltech. > > Thanks, > Shannon > >>>So, anytime I try to copy a large file from 10.14.0.11 to 10.11.0.10 >>>for instance, it stalls at 36864 bytes. It stalls at the same number >>>of bytes EVERY time. Note also, that on a Solaris box it stalls at >>>49152 bytes and on a Linux box it stalls at 36864. I know that the >>>tunnels are functional bcause I can interactively ssh to and from the >>>network and machines in question. Also ping, traceroute, etc. etc. really interesting that it stops at the same place every single time. -- Scott Harney<[EMAIL PROTECTED]> "...and one script to rule them all." gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
