Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
Highlights:
This release has many performance improvements at the TCP level, support
for new languages, improvements in various tools and libraries, and some
functional improvements at protocol level.
Detailed information on things that have been done since the last release:
Documentation:
. Added information on performance issues with XEDRV ethernet driver
provided with RSX for non-DECnet systems.
. Updated documentation with new functions and language libraries.
Interfaces:
. Changed default number of receives issues by ETHACP to 6.
. Added SET IFn: RECEIVE n to change how many outstanding receives
to have on ethernet interface. This is now dynamic at runtime.
TCP:
. Added rejection counting for SYN packets to ports with
no listeners.
. Bugfix. MSS should never be larger than the buffer size in TCP.
. Correct TCP ACK repeat rate to also consider the buffer size.
With a small buffer, we cannot have a low ack rate.
. Improve TCP retransmission. If more than one packet is ACKed,
assume we are actually on track, and reverts to normal mode.
. If we have a socket with lots of full size packets, we
do not send window updates immediately if the window is
growing. We might as well keep the slower rate.
. Improved TCP performance at high throughput mode.
. Changed TCP receive ACK generation to do dynamic handling
of how often ACKs needs to be sent.
. Fixed TCP close function to not generate spurious packets.
. Changed TCP slow start window processing.
. Fix TCP retransmission logic. Under some circumstances, packet
only retransmitted with a delay, even though they should have
been retransmitted immediately.
. Improved TCP nagle implementation.
. Improved TCP retransmit recover logic.
. Changed TCP to allow combination of PU.TXT and PU.RXP.
. Changed TCP to start daemons with the installed default UIC.
FTP/FTPD:
. Changed FTP login routines to set system type in login routine
instead of in open routine.
. Added init file for FTP.
. Bugfix. If FTPD was requested to list files in Unix format,
and a file was protected, FTPD could crash.
. Added KEEPALIVE command to FTP.
. Changed FTP client to use nagle on command channel.
. Bugfix in FTP DIR command, which could crash with a stack corrupt.
. Bugfix in FTPD. If FTPD logs in to a directory without a FTP.TXT,
the mode of the command channel ended up wrong.
. Change FTP and FTPD to better utilize tcp high throughput mode.
. Bugfix in FTPD. Files sent to FTPD did not get the correct owner set.
RMD:
. Bugfix in RMD TCP network page. Byte counters had been changed
to 3 word fields.
Multinet:
. Bugfix in MULTINET. Some error messages was printed with a corrupt
line number.
. Changed multinet to always push tcp data.
MAILD:
. Bugfix in MAILD. Other changes had caused MAILD to not be able to
process mails with multiple recipients. MAILQUE.DAT file format had
to change, so the mail queue needs to be reinitialized.
. Added proper message id handling to MAILD.
. Improve dispay of mails when reading.
. Bugfix. Unprivileged users could not create their mailbox in MAIL.
. Improved MAIL11 receive address processing.
HTTPD:
. Added ability for CGI programs to return other than 200 status.
IRCBOT:
. Changed IRCBOT to be more efficient and sane with PUSHes.
Libraries:
. Change BQTLIB to not require privileges for isco() function from C.
. Change IPC library to include listen() as well as sgetc().
Pascal:
. Added support for Oregon Pascal-2.
XLisp:
. Added XLISP and some example programs to distribution.
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
I hope people find this update useful. While there are no really
critical issues that have been solved, I still recommend people to
update, since this new version do contain improvements that are
beneficial and as far as I know there are no issues or problems updating
to this newest version.
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
Johnny
Could you add node 44.46 name RODIUM to your list please.
It is a rebuilt AlphaServer 1200 5/400 dual cpu with 2GB main memory.
Hans
Verstuurd vanaf mijn iPhone
Hi,
Is there a kind soul out there who would grant me access to their (HECnet connected) Itanium-based VMS system so that I can play with some of their compilers (particularly a more modern version of Ada to that available on VMS 7.3 on VAX architecture)?
At some point, based on what I discover, I may even be tempted to buy one of the entry-level Itanium servers for real. I can't explain why I'm not that interested in Alpha other than that I'm perhaps a bit weird.
Hopefully someone can help... with the access, not the weirdness :)
Regards,
Keith
(HECnet) DUNE::SQKEITH
Hi folks,
My Raspberry Pi VAXcluster project?
(https://www.linkedin.com/pulse/retro-computing-vaxcluster-hat-wilm-boerhout/
) is now connected to HECnet.
Nodes are PIVAX0...PIVAX4 (29.200...29.204)
Nothing much to see except the cluster itself, but if you are
interested, I can set up some public access.
*Wilm*
*P.S. *The cluster is physically located in Zwolle, The Netherlands
(home location).
I just got my hands on an rx2660, and I realized to my astonishment
that I do not have a copy of VMS for the Itanium architecture. Can
anyone help me out?
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hi,
I have just finished doing a bit of network cleanup on my ASA and 1841 and
noticed that a number of the HECnet GRE tunnels seems to be down or
possibly misconfigured.
I know that my IP address changed a while back as part of the transition to
Australia's National Broadband Network (NBN) and my router can now be found
at 110.141.227.104. I am pretty sure that Brian sent out an update, but I'm
not sure how well it was applied.
Since changing IP addresses I've only been able to establish a tunnel
with 50.131.218.138 (area 42). However, when I attempt to ping the other
end I am unable to reach 42.1023.
After looking at my firewall logs I noticed that someone at 81.135.164.245
was attempting to establish a GRE tunnel. After looking at the existing
configuration I noticed that it was a similar address to what had been last
configured for area 22. I made the change and now I can establish a link
to area 22 and I can successfully ping 22.1023.
However, that is were it ends. I have tunnels configured for area 59, 23,
61, 9 and 52, but I have no connection to the other end. Worse, I have no
connection to the HECnet as a larger entity.
Is anyone else other than myself and Mark Darvill still using the tunnels?
If there is a lack of interest in the maintenance, I would be happy to take
it over and start running the bridge here too.
Thoughts? Anybody... :-)
Regards, Tim.
Hi HECnet,
I am scouring the Internet for DECnet documentation (I've looked in
the usual places), does anyone have any of the DECnet for DOS or
DECnet for Rainbow documentation?
DECnet-Rainbow Installation Guide
DECnet-DOS Getting Started
DECnet-DOS User's Guide
DECnet-Rainbow Release Notes
DECnet-DOS Installation Guide
Also particularly interested in the version 1.1 of the software too
(we have 1.0 but it was significantly improved/updated with 1.1).
thanks,
nigel.
Is there anyone in the UK/Europe that would be able to provide me with a
connection to HECNet via a multinet link? I'm connected off AS8676 -
the node IP is 217.65.167.14. It's not currently reachable via ICMP but
if you ping 217.65.160.9 you should get a reasonable idea of latency.
cheers, Douglas
