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.
There is one very serious bug in TCP that is fixed in this release which
is why I really encourage people to upgrade.
Highlights:
- Stability and reliability improvements in TCP.
- Improved SPOOF detection.
- Improved stability.
Detailed information on things that have been done since the last release:
Installation process:
- The IPGEN script now more smoothly handles updates to an existing
installation.
Ethernet driver:
- Improved driver reset handling.
- Implemented MTU backoff in ethernet driver, to handle unpatched DEC
XU: driver.
TCP:
- At socket close time, if there were pending packets to process still
in the socket, the system pool could become corrupted, causing a crash
at some random later time.
- Add more spoof processing for suspicious connections.
FTPD:
- Improved error handling for not logged in clients.
HTTP:
- Implemented spoof processing for connections which looks suspicious.
MAILD:
- Implemented spoof processing for connections which looks suspicious.
Mail client:
- Added basic hooks for extending mail to deal with several folders
(still not complete).
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
As a final word about this release. As always things progress with time,
but I think it's safe to say by now that BQTCP is now a very stable
TCP/IP with almost all features one can expect. There might always be
some more work on the lower level protocols, but at this point, expect
that most work and updates will be more and more on various daemons and
clients.
If there is anything in particular anyone is looking for, let me know.
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
Before I go looking on Ebay, I thought I'd ask here first.
My Alphaserver 800 5/500 wasn't responding when I came back from a business trip.
And when I rebooted it, I heard the 1-2-4 beep codes and no screen.
Found out it means "Backup cache error. Replace the CPU daughter board"
And I found out in the manual that "The system can be operated with the B-cache disabled until a replacement CPU daughter board is available." After re-seating the CPU board and the memory it still got the error beeps and changed the J1 jumper and it booted up fine.
Does anyone know the impact of running with the B-cache disabled?
The text in the system manual said the jumper setting "Allows the system to run despite bad B-cache until a replacement CPU board is available." How long can the system be run in this mode?
just curious so I know how much time I have to watch for a reasonable price 5/500 CPU module to show up on ebay (since there aren't many VAX/Alpha geeks in DC on craigslist).
Thanks in advance
Mike
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
I accidentally managed to disconnect and connect the power connector to
a TK70 while powered on. Now it seems like the TQK70 no longer wants to
talk to the TK70.
Does anyone recognize this, and have any suggestions on fixing it?
The CPU can talk to the TQK70, and it seems to also be functioning
correctly.
However, the TK70 itself seems to be running through self-tests, and
then blinks all LEDs indicating that something is wrong.
I've tried looking at the board, but cannot see anything burned, and I
cannot see any fuses either...
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
