Hi Robert:

francesco@tya64:~$ ping -M do -s 1472 login.plx.cineca.it
PING login.plx.cineca.it (130.186.16.115) 1472(1500) bytes of data.
>From login.plx.cineca.it (130.186.16.115) icmp_seq=1 Destination Host
Prohibited
>From login.plx.cineca.it (130.186.16.115) icmp_seq=2 Destination Host
Prohibited
>From login.plx.cineca.it (130.186.16.115) icmp_seq=3 Destination Host
Prohibited
>From login.plx.cineca.it (130.186.16.115) icmp_seq=4 Destination Host
Prohibited
>From login.plx.cineca.it (130.186.16.115) icmp_seq=5 Destination Host
Prohibited
>From login.plx.cineca.it (130.186.16.115) icmp_seq=6 Destination Host
Prohibited
^C
--- login.plx.cineca.it ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5007ms

(it continues that way indefinitely)

francesco@tya64:~$


Although I can login as [email protected],

francesco@tya64:~$ ping -M do -s 1472 [email protected]
ping: unknown host [email protected]

thanks
francesco


On Thu, May 22, 2014 at 9:05 AM, Robert Rottscholl <[email protected]> wrote:

> Hi Francesco,
>
> as you have not heared of it, it is unlikely that you use it. So I would
> go for an mtu check. What is 'ping -M do -s 1472 login.plx.cineca.it'
> saying, does it work?
>
> Greets
>
> Robert
>
> Am 22.05.2014 08:53, schrieb Francesco Pietra:
>
>> Hi Robert:
>>
>> francesco@tya64:~$ uname -r
>> 3.2.0-4-amd64
>> francesco@tya64:~$
>>
>>
>> I do not understand "tunnel". I use classical scp, passwordless (my pub
>> keys at the mainframe):
>>
>> francesco@tya64:~$ scp -p
>> [email protected]:/gpfs/scratch/userexternal/
>> fpietra0/P2f_accelMD_H2O_PLX/*30.dcd
>> /home/francesco/PLX
>>
>>
>> and "stalling" occurs randomly. I did not try with another box, where
>> jelly is installed. Also, I did not try either from the Linux prompt
>> (actually I us startx, followed by gnome-session. I am having those
>> problems from the gnome terminal). I never had such problems from a
>> French server at the Univ Picardie, but that automatically probalby uses
>> ftp (and it has to be used from the graphical interface).
>>
>> Thanks
>> francesco
>>
>>
>>
>> On Thu, May 22, 2014 at 8:00 AM, Robert Rottscholl <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Hi Francesco,
>>
>>     what kernel version do you use? There is an unfixed (in mainline)
>>     kernel bug in the tun device which might cause your problems (see
>>     https://bugzilla.kernel.org/__show_bug.cgi?id=74051
>>
>>     <https://bugzilla.kernel.org/show_bug.cgi?id=74051> ). This will
>>     only be a problem if you use a tunnel to connect to your server.
>>
>>     Greets
>>
>>     Robert
>>
>>     Am 21.05.2014 21 <tel:21.05.2014%2021>:16, schrieb Francesco Pietra:
>>
>>
>>         Hello:
>>         Since a few days, scp downloading 500MB file from a
>>         supercomputer at the
>>         Italian center CINECA results quite often in
>>
>>
>>         francesco@tya64:~/PLX$ scp -p
>>         [email protected]:/__gpfs/scratch/userexternal/__
>> fpietra0/P3f_accelMD_H2O_PLX/*__29.dcd
>>
>>         /home/francesco/PLX
>>         npt_accel-29.dcd                                3%   13MB
>>         0.0KB/s -
>>         stalled -
>>
>>
>>         No problem with small files.
>>
>>         Check at CINECA resulted in no malfunction. The provider
>>         (TELECOM ITALY)
>>         says their adsl if percetly functioning. Actually, the speed, ca
>>         600kb/s, is as expected (don't smile, Italy is at that speed; if
>>         you pay
>>         more, you can just hope to download at 1000kb/s, while out is
>> always
>>         impracticably slow).
>>
>>         My question is: can scp, as available from my installation on a
>>         wheezy
>>         amd64 box, be responsible?
>>
>>         thanks for advice
>>
>>         francesco pietra
>>
>>
>>
>>     --
>>     To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.__debian.org
>>     <mailto:[email protected]>
>>
>>     with a subject of "unsubscribe". Trouble? Contact
>>     [email protected] <mailto:[email protected]>
>>     Archive: https://lists.debian.org/[email protected]
>>     <https://lists.debian.org/[email protected]>
>>
>>
>>
>
> --
> To UNSUBSCRIBE, email to [email protected]
> with a subject of "unsubscribe". Trouble? Contact
> [email protected]
> Archive: https://lists.debian.org/[email protected]
>
>

Reply via email to