Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
This release contains a lot of fixes and improvements in many areas. I
really encourage people to upgrade, as some of these changes can have a
noticeable impact on stability.
Highlights:
- Distribution now includes the PDP-11 C and BASIC+2 resident libraries,
so that various tools and utilities that are built against them can
be installed even if the full language is not installed on a system.
- Improved stability.
Detailed information on things that have been done since the last release:
Ethernet driver:
- The ethernet driver could under some overload situations become deaf,
and not receive any more packets.
TCP:
- TCP FIN handling. Under some circumstances, TCP could get into a state
where both sides would be sending FIN packets, and not acknowledging the
other sides FIN.
- TCP sequence handling. Under some circumstances, TCP packets with bad
sequence numbers could be accepted as valid packets.
- IO.KIL function for normal TCP ports removed. It turned out that it
was very undesirable to process IO.KIL for connected sockets. (A
separate function with the same effect does exist.)
- Added counted for rejected TCP SYN packets.
- Improved task activation code for TCP daemons.
HTTP:
- Improved logging.
MAILD:
- Improved new mail notification handling.
- Correct handling of EHLO/HELO for SMTP.
- Implemented proper MAIL11 protocol, version 3.
- Rewritten address rewrite logic to better process both SMTP and MAIL11
addresses.
MAIL:
- Simple mail client now exist.
Libraries:
- Unified user lookup functions. User lookups now happen both on
lastname, UIC, SID and login directory. This is used both by MAIL, FTP
and HTTP.
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
The firewall for Mim have now been removed, so no need for the alternate
ports, but Mim is still listening to the alternate ports as well.
ftp: 10021
telnet: 10023
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Hi,
Just letting those people who use the Cisco GRE tunnels that my static
IP has changed (moved networks). It is no longer 120.146.225.243. It
is now 110.141.227.104.
Regards, Tim.
Tony,
Flakiness seems to have gone down a wee bit once I replaced
/usr/sbin/dnetnml with a binary built from dnet-progs source. It is
staying up and responding to SHOW EXEC CHAR requests for almost a full
day now.
So far I have replaced two binaries in /usr/sbin with built-from-src -
dnetnml and ctermd.
BTW I tried to reach MASTER but it was down. My two nodes are at 1.553
and 1.554. Would you like an account? And could I have an account on MASTER?
Thanks
Supratim
I've been busy (as usual) with writing stuff for RSX. And been a bit
annoyed at not having a nice mail gateway between TCP/IP and DECnet. So
I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really
appreciate any error reports, feature requests, thought, or just stress
tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also, this
mail gateway can also deal with local mail on Mim, in case anyone
wonders. And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm not
officially making a release yet. That is what the next week or so of
testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP
side. Also, Mim is behind a firewall, so for most people, SMTP access
directly to Mim does not work. However, Mim also have an MX record
pointing to an intermediate machine which then relays the messages on to
Mim, but this introduces about a 10s delay in mails sent from the
Internet to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Hi,
I regret I have lost the email announcing the internet email to VMS mail
gateway and would appreciate if someone could forward me those details
one more time.
Thank you in advance,
Supratim
