--K/NRh952CO+2tg14
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 08, 2004 at 02:44:07PM +0200, Brad du Plessis wrote:
>=20
> The issue I'm seeing is that while a telnet session between the two seems=
 to
> work fine, an ftp session does not. After initiating the ftp connection,
> doing a directory listing on the remote system (ls) works ok most of the
> time. However, attempting to transfer a file in either direction appears =
to
> transmit no data whatsoever.
>=20
> What's more interesting, is that when I set the transmit and receive buff=
er
> size for the ftp session to 512 bytes, I can transfer data without a prob=
lem
> (albeit very slowly, about 2KBytes / second).

In my humble experience, the three most likely causes of this are:

1. serial handshaking problem, resulting in bytes lost resulting in ppp
   packet  loss
2. serial handshaking problem, resulting in bytes lost resulting in ppp
   packet  loss
3. serial handshaking problem, resulting in bytes lost resulting in ppp
   packet  loss.

a) make sure the TAs create and obey cts/rts

b) make sure your machine's serial ports are used with crt/rts (your=20
   variant of ppp will have to be configured for this; for "normal" pppd
   it's the "crtscts" keyword, I think)

c) make sure your serial cable has at least 8 connected lines:
   2,3,4,5,6,7,8,20

	-is


--K/NRh952CO+2tg14
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBQbb3HDCn4om+4LhpAQGq9QgAhwLrUue70Bg1hP0BI9JxgQFMKg3/594y
enAyLPVF0yBE1DMKtdf77LgYLqEnb3m5aB7jmEmOOiCHSmxPnpJzi4kUfBaLGPbV
iEvd0ltB32IhpyfhZHssX5UiCSwJqe/sDjTkd8B9jPQk8ToATL9v5iDTpVZ/gktN
3bWlbj5ei6gd/DDmS1N0ATdJxJlkU56kuU6mOUqMXoSAdwViNfk0D0ERevJZHvUN
jvjOyjBxbKd4MEWFMLSTAybZ0HAMY6gXW0RN9qpyzKMDFe1INEX/04bcc/zVL/4u
UeCfE4rruZwCgCCtK7OzrTO1uGjWqiNYtsyseL+nSPh7YXuI7FZoLg==
=Jjj2
-----END PGP SIGNATURE-----

--K/NRh952CO+2tg14--