urban@trwspp.UUCP (07/24/84)
We just installed Interlan ethernet controllers on our two
Vaxen running 4.2bsd (plus a Pyramid 90x, but let that pass
for now...). The 4.2bsd net software is a pleasure to use,
when it works. The documentation is kind of oblique when
it comes to figuring out how to set up the configuration
files, but this isn't anything new. However, we seem to
have a few outstanding problems:
1) Telnet seems to drop characters (sometimes) from
the remote host. This is particularly unfortunate because...
2) Sometimes connections (especially rlogin) seem to get
permanently stuck in a state where one end shows
LAST_ACK and the other end shows FIN_WAIT_2. When
this happens to an rlogin connection, no further
rlogins appear to be possible. It would certainly be
nice if there were some kind of call or command that
would amount to "clear the network table". Dream on.
3) "talk" simply won't work across machines. It sits in
the look_up routine waiting for replies from the
foreign talk daemon, which seem to be disappearing.
I know UDP is unreliable, but ... ?
We're also having additional problems where the Pyramid 90x
is concerned, mostly concerning "rcp" and "ftp" file
copying getting hung up. But Pyramid seems to be aware of the
problem.
In any case, can someone out there provide me with some
assistance in these problems? I'm not particularly willing
to wade into the network code at this time, especially
since these problems have probably been solved somewhere
else already. Post replies to me, not the net.
Mike Urban
{ucbvax|decvax}!trwrb!trwspp!urban
By the way, kudos to Doug Kingston at BRL for the network
support in the MDQS queueing stuff, which worked the first
time we needed it.