Problem with scp: blocks after starting scp -t on remote machine
Hello,
we've got a puzzling situation - two boxes : A (with interfaces
10.2.10.2 and 10.0.0.1) and B (with interface 10.0.0.2) both run debian
woody with a stock kernel-image-2.4.18-686 (uname -a gives: Linux bes
2.4.18-386 #2 Sun Apr 14 10:38:08 EST 2002 i686 unknown).
dpkg -l ssh says: ii ssh 3.4p1-1
/etc/ssh/ssh_config and /etc/ssh/sshd_config on both machines are
unchanged from the versions shipped.
We can happily ssh from A to B and from B to A. We also can run scp on
A to copy from or to B. But, running the following on B:
scp /etc/services root@10.0.0.1:/tmp/piet
hangs. We can see that it already started an scp on A. ps ax | grep
scp gives:
259 ? S 0:00 scp -t /tmp/piet
265 pts/0 S 0:00 grep scp
On our other boxes we have no problem - the only funny thing about these
is that A's 10.0.0.1 is connected to B's 10.0.0.2 with a x-over cable,
the 10.0.0.x adresses are not in the dns, A's 10.2.10.2 is in the dns.
A also had debian's ipmasq package installed to masquerade B, but we
removed the package and iptables -L on A now gives:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Any help would be appreciated
- Iwan Vosloo
Reply to: