13 Jan
2015
13 Jan
'15
3:40 p.m.
Well, it's been a long time project, but I'm happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
This is the result of over 20 years of development. Needless to say,
I've been doing a lot of things over the years, and this code have been
through four reimplementations over the years.
What I now release is something that I believe is a nice and useful
piece of software. I am aware of the fact that most people do not use
these machines any longer, but if someone actually wants to talk to me
about support for this or other RSX software, let me know.
Also, feel free to spread this information to anyone who might be
interested, anywhere.
So - what is in this release?
It is a complete implementation of ARP, IP, UDP, and TCP for
RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work
on any V4 release. There might be some small tweaks or fixes required,
but nothing major.
It do require a system with split I/D-space, or else at least the TCP
part will not fit.
For Unibus machines, it should be possible to run without any additional
software except what is in a base RSX distribution.
For Q-bus machines, DECnet is required for ethernet networking.
The TCP/IP stack can co-exist with DECnet.
Some utilities also utilize RMS for file access.
A bunch of tools, utilities and libraries are also included. These include:
. IFCONFIG network configuration tool.
. NETSTAT network information tool.
. PING
. TRACEROUTE
. DNS client
. FTP daemon
. FTP client
. HTTP server
. TELNET client (rudimentary)
. TFTP client
. TFTP server
. INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT
. NTP client
. LPR client that sits in the queue manager (rudimentary)
. FORTRAN-77 library
. BASIC+2 library
. PDP-11 C library
The implementation fulfills most of the requirements put forth in RFC
1122. There are a few limitations because of restrictions in the PDP-11,
but none of them should really cause any problems.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
A bunch of test programs and example programs are also included, as well
as the sources of all tools and libraries.
The TCP/IP stack itself only comes in binary form.
All tools are also included precompiled in the distribution, so an
installation only have to build the stack itself for your system, and
then you should be ready to go.
The API only have a slight resemblance to the Unix sockets API. However,
if someone sits down to write code to use TCP/IP under RSX, I'm sure
they will discover that it is extremely easy to use the libraries, or
the basic functions.
The TCP/IP implementation is mostly written as device drivers. This also
have some other interesting implications, such as it is possible to
access TCP as a normal file. You can, for instance do something similar
to the Unix netcat command by issuing the MCR command:
PIP TI:=TC:"foo.com";4711
which would open a connection to foo.com, on port 4711, and any data
sent from that machine will be shown on the terminal.
The resources used by TCP/IP are modest. A memory area (size selectable
at generation/startup) is used internally. The amount of memory in the
private pool limits the amount of data that can be buffered. Normal pool
is used in a small quantity for each TCP port that is open.
People are welcome to play around with this, and make improvements.
Contributions of code is most welcome.
There are still lots of things to do. The programs marked as rudimentary
should be rewritten.
The most obvious thing still missing is a telnet daemon, which probably
is my next step.
However, the reason for now announcing the release is that it can
finally be distributed natively from an RSX host.
The main locations to download the TCP/IP for RSX are:
Madame.Update.UU.SE (anonymous ftp).
This is one of my development systems for this software. It runs under
E11, and if things are down, I blame E11. :-)
When connected, you are already in the right directory. There is both an
RL02 disk image there, which can be downloaded by anyone. If you happen
to have an RSX system which you are conneting from, you can also try
getting the BQTCP.TAP tape image. Such an image will not transport
cleanly to a non-RSX system, however. Sorry.
ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip
The disk image is normally duplicated to ftp.update.uu.se as well, so
the same file can be found there.
I hope some people will find this useful/amusing. :-)
Johnny Billquist
--
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
13 Jan
13 Jan
8:01 p.m.
On Jan 13, 2015, at 3:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
Well, it's been a long time project, but I'm
happy to finally announce a more public initial release of TCP/IP for RSX-11M-PLUS.
<snip!>
I hope some people will find this useful/amusing. :-)
I don't find it amusing, I find it amazingly cool! This is fantastic news! The HTTP
server and LPR client sound especially interesting. Now we have a freely available TCP/IP
stack for both RT-11 and RSX-11M-PLUS. I just wish there was one for RSTS/E, but as far
as I know, it has never even had a commercial stack.
Zane
8:38 p.m.
On 13/01/15 11:01 PM, Zane Healy wrote:
On Jan 13, 2015, at 3:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
I agree, very impressive.
You said that contributions are welcome, but the TCP/IP stack is binary
- will you be open sourcing it at any point?
--Toby
Well, it's been a long time project, but
I'm happy to finally announce a more public initial release of TCP/IP for
RSX-11M-PLUS.
<snip!>
I hope some people will find this useful/amusing.
:-)
I don't find it amusing, I find it amazingly cool! This is fantastic news! The HTTP
server and LPR client sound especially interesting. Now we have a freely available TCP/IP
stack for both RT-11 and RSX-11M-PLUS. I just wish there was one for RSTS/E, but as far
as I know, it has never even had a commercial stack.
Zane
14 Jan
14 Jan
12:39 a.m.
On 2015-01-14 05:38, Toby Thain wrote:
On 13/01/15 11:01 PM, Zane Healy wrote:
Well, my initial thinking was that there are so many tools, utilities,
daemons and clients waiting to be written, as well as improving on the
ones I've done, that I was hoping for contributions there.
The stack itself can also be improved, I'm sure. It's just way more
complex to modify, since that piece is device drivers in RSX. Any
changes there needs to be done understanding the whole environment of it.
But yes, I'm fine with getting the source to that part out too. But be
warned. It will not be easy to work on it. In addition, the built system
is less forgiving and less flexible. Can't promise that you'll be able
to even built it with some fiddling of your own.
I'll try and make a script to screate a source kit soon.
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
On Jan 13, 2015, at 3:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
I agree, very impressive.
You said that contributions are welcome, but the TCP/IP stack is binary
- will you be open sourcing it at any point? Well, it's been a long time project, but
I'm happy to finally
announce a more public initial release of TCP/IP for RSX-11M-PLUS.
<snip!>
I hope some people will find this useful/amusing.
:-)
I don't find it amusing, I find it amazingly cool! This is fantastic
news! The HTTP server and LPR client sound especially interesting.
Now we have a freely available TCP/IP stack for both RT-11 and
RSX-11M-PLUS. I just wish there was one for RSTS/E, but as far as I
know, it has never even had a commercial stack.
Zane
12:35 a.m.
On 2015-01-14 05:01, Zane Healy wrote:
On Jan 13, 2015, at 3:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
Not that the LPR client actually talks PCL. I wanted to hook up a
printer I have on my local network. So that is what it is geared
towards. But it's written in C, so people should probably not find it to
hard to modify.
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
Well, it's been a long time project, but
I'm happy to finally announce a more public initial release of TCP/IP for
RSX-11M-PLUS.
<snip!>
I hope some people will find this useful/amusing.
:-)
I don't find it amusing, I find it amazingly cool! This is fantastic news! The HTTP
server and LPR client sound especially interesting. Now we have a freely available TCP/IP
stack for both RT-11 and RSX-11M-PLUS. I just wish there was one for RSTS/E, but as far
as I know, it has never even had a commercial stack. 
13 Jan
13 Jan
8:54 p.m.
On Wed, Jan 14, 2015 at 12:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
Well, it's been a long time project, but I'm
happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
Amazing and very cool! Gives me immediate motivation to build an 11/70 with
one of my QED boardsets. Goal: webserver running proper DEC OS with proper
blinkenlights :-)
The TCP/IP stack itself only comes in binary form.
Ahhh. That will give a lot of people pause for thought, and, some will
probably say, might be a distraction from the achievement itself. I trust
you know what you're doing :-)
Mike
http://www.corestore.org
'No greater love hath a man than he lay down his life for his brother.
Not for millions, not for glory, not for fame.
For one person, in the dark, where no one will ever know or see.'
14 Jan
14 Jan
12:44 a.m.
On 2015-01-14 05:54, Mike Ross wrote:
Well, you already have most of the sources, as everything except the
device drivers comes with sources.
But I'm going to make the last bits available as well, but it's not
going to be super easy for someone to work on, or modify those parts. It
will be more like a snapshot of my build system.
And building the whole distribution takes about 1.5h on a real 11/93
with modern disks.
But for people who actually wants to read several hundred K of
MACRO-11... Here is your chance... :-)
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
On Wed, Jan 14, 2015 at 12:40 PM, Johnny Billquist
<bqt at softjar.se> wrote:
Yes. We actually have that at Update, in form of a real PDP-11/70 with
this code installed. However, the machine is down much of the time at
the moment because of the cooling system needing to be fixed. (It's been
this way for years, but we are making slow progress on it.)
Well, it's been a long time project, but
I'm happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
Amazing and very cool! Gives me immediate motivation to build an 11/70 with
one of my QED boardsets. Goal: webserver running proper DEC OS with proper
blinkenlights :-) The TCP/IP
stack itself only comes in binary form.
Ahhh. That will give a lot of people pause for thought, and, some will
probably say, might be a distraction from the achievement itself. I trust
you know what you're doing :-) 
8:10 a.m.
Well, it's been a long time project, but I'm
happy to finally
announce a more public initial release of TCP/IP for RSX-11M-PLUS.
This is very impressive. Even for bqt@, this is very impressive.
If you happen to have an RSX system which you are
conneting from, you
can also try getting the BQTCP.TAP tape image. Such an image will not
transport cleanly to a non-RSX system, however.
I'm curious: why wouldn't it? Do the FTP client and server recognize
one another, or is it more "will not transport cleanly to a system not
implementing $OBSCURE_FTP_FEATURE", or what?
I hope some people will find this useful/amusing. :-)
I won't find it useful personally, at least not in the near future; I'm
not running RSX. And I wouldn't call it amusing. I'd call it other
things, such as "impressive" or "awesome". I'm tempted to pick up
the
code just to read it over, as I'm sure there's a lot I could learn from
it, but I doubt I'll have the leisure to indulge that inclination
anytime soon. :-(
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
2:01 p.m.
On 2015-01-14 17:10, Mouse wrote:
Thanks.
Nah. The problem is simpler than that. It all relates to the fact that
files under RSX are very different than under Unix. File in RSX are
organized in different ways. And virtual tapes are of variable sized
records. So, how would I communicate that across FTP? And the actual
length of those records?
Essentially any binary file under RSX cannot be transferred over FTP,
with a couple of exceptions:
Fixed length record files under RSX will transfer all the content of the
file over the link. You will of course not know what the record length
was, but that you could reconstruct after the fact.
Binary files where the record lengths are irrelevant. These will also
work just fine.
When the FTP client under RSX talks to another RSX machines FTP server,
it detects this fact, and do transfer a bunch of metadata about the file
in addition to the actual file content, so that all stuff gets preserved.
This also means that you can FTP indexed files over FTP between RSX
machines. I have a plan to extend this to also work against VMS
machines. I just need a little more time.
It will take a lot of time to browse through the thing. The basic ARP,
IP, UDP, TCP, and a couple of tools alone are about 500K of MACRO-11.
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
Well, it's
been a long time project, but I'm happy to finally
announce a more public initial release of TCP/IP for RSX-11M-PLUS.
This is very impressive. Even for bqt@, this is very impressive. If you happen
to have an RSX system which you are conneting from, you
can also try getting the BQTCP.TAP tape image. Such an image will not
transport cleanly to a non-RSX system, however.
I'm curious: why wouldn't it? Do the FTP client and server recognize
one another, or is it more "will not transport cleanly to a system not
implementing $OBSCURE_FTP_FEATURE", or what? I hope some
people will find this useful/amusing. :-)
I won't find it useful personally, at least not in the near future; I'm
not running RSX. And I wouldn't call it amusing. I'd call it other
things, such as "impressive" or "awesome". I'm tempted to pick
up the
code just to read it over, as I'm sure there's a lot I could learn from
it, but I doubt I'll have the leisure to indulge that inclination
anytime soon. :-(
2:21 p.m.
If you happen to have an RSX system which you are
conneting from,
you can also try getting the BQTCP.TAP tape image. Such an image
will not transport cleanly to a non-RSX system, however.
I'm curious: why
wouldn't it? [...] Essentially any binary file under RSX cannot be
transferred over FTP,
[...]
Sounds to me as though the truth is more like, cannot be transferred to
or from typical "everything is a bag of bytes" Unix-mindset FTP
implementations. Unless there's something particularly arcane you
haven't hinted at, I don't see anything that would prevent transferring
them over standard FTP, given a server and client that actually
understand that FTP is more than a bag-of-bytes transfer tool.
I'm
tempted to pick up the code just to read it over, as I'm sure
there's a lot I could learn from it, but I doubt I'll have the
leisure to indulge that inclination anytime soon. :-(
It will take a lot of time
to browse through the thing. The basic
ARP, IP, UDP, TCP, and a couple of tools alone are about 500K of
MACRO-11.
2:30 p.m.
On 2015-01-14 23:21, Mouse wrote:
Nah. The problem is simpler than that. It all relates to
the fact
that files under RSX are very different than under Unix. File in RSX
are organized in different ways. And virtual tapes are of variable
sized records. So, how would I communicate that across FTP? And the
actual length of those records?
FTP has a lot of capabilities many people are totally unaware of; see
RFC 959. (Admittedly, depressingly many people are unaware FTP even
_exists_....) For what you sketch, I'd suggest record structure
(STRU R) and block mode (MODE B).
Oh how I wish. Have you tried giving those command in an ftp client
under Unix? :-)
Essentially, for transfer to/from Unix systems, you are stuck with STRU
F, MODE S
Since the struct and mode abilities in the FTP protocol will not easily
cover enough anyway, I decided to do a similar trick I noticed VMS is doing.
So I support a "STRU O RSX" command, will will enable the extra bells
and whistles needed to transfer files properly between RSX systems.
No, you are right. And that is what I do when talking between a properly
able FTP server and FTP client.
Since that essentially boils down to an RSX system talking to an RSX
system, I did it with an extension that makes it easy for me. The effect
when talking to other systems are the same. Using the existing stuff in
RFC 959 would only mean I would have problems transferring between RSX
systems, and still not able to transfer to anything else anyway.
So it's nothing really arcane. It's just that I will not be able to
transfer something like a binary native RSX file to a non-RSX system.
But that was almost expected anyway.
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
If you happen
to have an RSX system which you are conneting from,
you can also try getting the BQTCP.TAP tape image. Such an image
will not transport cleanly to a non-RSX system, however.
I'm curious: why
wouldn't it? [...] Essentially
any binary file under RSX cannot be transferred over FTP,
[...]
Sounds to me as though the truth is more like, cannot be transferred to
or from typical "everything is a bag of bytes" Unix-mindset FTP
implementations. Unless there's something particularly arcane you
haven't hinted at, I don't see anything that would prevent transferring
them over standard FTP, given a server and client that actually
understand that FTP is more than a bag-of-bytes transfer tool. 
9:59 p.m.
On Wed, Jan 14, 2015 at 11:01:55PM +0100, Johnny Billquist wrote:
Nah. The problem is simpler than that. It all relates to the fact
that files under RSX are very different than under Unix. File in RSX
are organized in different ways. And virtual tapes are of variable
sized records. So, how would I communicate that across FTP? And the
actual length of those records?
Is there some kind of backup/archiving tool on rsx which you
could wrap files and metadata in?
Before transfer to bag-of-bytes systems?
/P
15 Jan
15 Jan
1:42 a.m.
On 2015-01-15 06:59, Pontus Pihlgren wrote:
On Wed, Jan 14, 2015 at 11:01:55PM +0100, Johnny
Billquist wrote:
Yes. I could certainly do that. However, that means someone would need
to write an unpacking tool from this format, and to then write some
"userful" output under a Unix system. But this would definitely be doable.
But it's not some kind of backup/archive tool that is needed. Any such
tool would have the same "problematic" output file.
But I've written a tool in the past that can encode binary files in a
text file format. Similar to uuencode/uudecode. And then you have a text
file which still preserves all the metadata of the original file.
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
Nah. The problem is simpler than that. It all relates to the fact
that files under RSX are very different than under Unix. File in RSX
are organized in different ways. And virtual tapes are of variable
sized records. So, how would I communicate that across FTP? And the
actual length of those records?
Is there some kind of backup/archiving tool on rsx which you
could wrap files and metadata in?
Before transfer to bag-of-bytes systems?
5:48 a.m.
On Thu, Jan 15, 2015 at 10:42:11AM +0100, Johnny Billquist wrote:
On 2015-01-15 06:59, Pontus Pihlgren wrote:
Of course, I was under the impression that the target was
another RSX system and the unix system was just an intermediate
step. But I might have dreamt that part :)
/P
Is there some kind of backup/archiving tool on rsx which you
could wrap files and metadata in?
Before transfer to bag-of-bytes systems?
Yes. I could certainly do that. However, that means someone would
need to write an unpacking tool from this format, and to then write
some "userful" output under a Unix system. But this would definitely
be doable.
6:14 a.m.
On 2015-01-15 14:48, Pontus Pihlgren wrote:
On Thu, Jan 15, 2015 at 10:42:11AM +0100, Johnny
Billquist wrote:
I'm not entirely clear what the purpose was. I pointed out that
transferring the tape file over ftp to a different type of system was
not possible, as information is lost.
If you want to just store intermediately on another system, then my
encoding/decoding program is perfect. But most of the time, if you are
going to transfer between two RSX systems, you can just do it directly
instead, and FTP will do it right already.
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
On 2015-01-15 06:59, Pontus Pihlgren wrote:
Of course, I was under the impression that the target was
another RSX system and the unix system was just an intermediate
step. But I might have dreamt that part :)
Is there some kind of backup/archiving tool on rsx which you
could wrap files and metadata in?
Before transfer to bag-of-bytes systems?
Yes. I could certainly do that. However, that means someone would
need to write an unpacking tool from this format, and to then write
some "userful" output under a Unix system. But this would definitely
be doable.
14 Jan
14 Jan
10:08 a.m.
On Tue, Jan 13, 2015 at 6:40 PM, Johnny Billquist <bqt at softjar.se> wrote:
First of all, thank you, Johnny!! This project is a beautiful thing that
I've personally been holding my breath waiting on since you announced you
were starting work on it twenty years ago when I was still using pdp11s in
my daily work. Your efforts here will likely result in my rededicating one
of my unix pdp11s back to rsx.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
I can't get any of my things to read the .doc file. Any chance of a
runoff or ascii version? I'll offer to do the reformatting work if it
pleases you and would be viewed as helpful (assuming I find a way to read
it).
As to sources, if you decide to get it all out there, would it be cool if
I put it on github? And, while at it, I hate to bring up silly stuff, but
do you have a license in mind?
Thank you _so_ much again!
jake
10:13 a.m.
The documentation is a plain ascii file. Generated from runoff. ?
Jacob Ritorto <jacob.ritorto at gmail.com> skrev: (14 januari 2015 19:08:33 CET)
On Tue, Jan 13, 2015 at 6:40 PM, Johnny Billquist
<bqt at softjar.se>
wrote:
First of all, thank you, Johnny!! This project is a beautiful thing
that
I've personally been holding my breath waiting on since you announced
you
were starting work on it twenty years ago when I was still using pdp11s
in
my daily work. Your efforts here will likely result in my rededicating
one
of my unix pdp11s back to rsx.
Documentation is still on the thin side, but example configs are also
--
Skickat fr?n min Android-telefon med K-9 E-post. Urs?kta min f?ordighet.
provided, along with installation scripts.
I can't get any of my things to read the .doc file. Any chance of a
runoff or ascii version? I'll offer to do the reformatting work if it
pleases you and would be viewed as helpful (assuming I find a way to
read
it).
As to sources, if you decide to get it all out there, would it be cool
if
I put it on github? And, while at it, I hate to bring up silly stuff,
but
do you have a license in mind?
Thank you _so_ much again!
jake
15 Jan
15 Jan
7:47 p.m.
New subject: [HECnet] Announcing TCP/IP for RSX-11M-PLUS
There have been lots of positive comments, and obviously some people
have even tested using the software.
Of course, a bug was also found. A really weird corner case with
severely loading the network stack and having a socket in listen state
programatically could trigger a corruption of kernel memory.
So I've cut a new release with the bug fixed.
While I'm at it I also realize that I forgot to mention that included in
the distribution is also a simple IRC client as well as a simple IRC robot.
I've also taken a little time to slightly improve the documentation, and
the documentation is now also available directly by ftp from
Madame.Update.UU.SE, so you do not need to get the whole distribution
and unpack it to just read something.
So - same as before. Disk image and tape image are available at
Madame.Update.UU.SE. Use anonymous ftp.
Disk image is also available at ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip.
The disk image is a virtual RL02 disk. Can be used with any emulator, or
also directly inside RSX if you have virtual devices available.
Happy hacking.
Johnny
On 2015-01-14 00:40, Johnny Billquist wrote:
Well, it's been a long time project, but I'm
happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
This is the result of over 20 years of development. Needless to say,
I've been doing a lot of things over the years, and this code have been
through four reimplementations over the years.
What I now release is something that I believe is a nice and useful
piece of software. I am aware of the fact that most people do not use
these machines any longer, but if someone actually wants to talk to me
about support for this or other RSX software, let me know.
Also, feel free to spread this information to anyone who might be
interested, anywhere.
So - what is in this release?
It is a complete implementation of ARP, IP, UDP, and TCP for
RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work
on any V4 release. There might be some small tweaks or fixes required,
but nothing major.
It do require a system with split I/D-space, or else at least the TCP
part will not fit.
For Unibus machines, it should be possible to run without any additional
software except what is in a base RSX distribution.
For Q-bus machines, DECnet is required for ethernet networking.
The TCP/IP stack can co-exist with DECnet.
Some utilities also utilize RMS for file access.
A bunch of tools, utilities and libraries are also included. These include:
. IFCONFIG network configuration tool.
. NETSTAT network information tool.
. PING
. TRACEROUTE
. DNS client
. FTP daemon
. FTP client
. HTTP server
. TELNET client (rudimentary)
. TFTP client
. TFTP server
. INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT
. NTP client
. LPR client that sits in the queue manager (rudimentary)
. FORTRAN-77 library
. BASIC+2 library
. PDP-11 C library
The implementation fulfills most of the requirements put forth in RFC
1122. There are a few limitations because of restrictions in the PDP-11,
but none of them should really cause any problems.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
A bunch of test programs and example programs are also included, as well
as the sources of all tools and libraries.
The TCP/IP stack itself only comes in binary form.
All tools are also included precompiled in the distribution, so an
installation only have to build the stack itself for your system, and
then you should be ready to go.
The API only have a slight resemblance to the Unix sockets API. However,
if someone sits down to write code to use TCP/IP under RSX, I'm sure
they will discover that it is extremely easy to use the libraries, or
the basic functions.
The TCP/IP implementation is mostly written as device drivers. This also
have some other interesting implications, such as it is possible to
access TCP as a normal file. You can, for instance do something similar
to the Unix netcat command by issuing the MCR command:
--
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
PIP TI:=TC:"foo.com";4711
which would open a connection to foo.com, on port 4711, and any data
sent from that machine will be shown on the terminal.
The resources used by TCP/IP are modest. A memory area (size selectable
at generation/startup) is used internally. The amount of memory in the
private pool limits the amount of data that can be buffered. Normal pool
is used in a small quantity for each TCP port that is open.
People are welcome to play around with this, and make improvements.
Contributions of code is most welcome.
There are still lots of things to do. The programs marked as rudimentary
should be rewritten.
The most obvious thing still missing is a telnet daemon, which probably
is my next step.
However, the reason for now announcing the release is that it can
finally be distributed natively from an RSX host.
The main locations to download the TCP/IP for RSX are:
Madame.Update.UU.SE (anonymous ftp).
This is one of my development systems for this software. It runs under
E11, and if things are down, I blame E11. :-)
When connected, you are already in the right directory. There is both an
RL02 disk image there, which can be downloaded by anyone. If you happen
to have an RSX system which you are conneting from, you can also try
getting the BQTCP.TAP tape image. Such an image will not transport
cleanly to a non-RSX system, however. Sorry.
ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip
The disk image is normally duplicated to ftp.update.uu.se as well, so
the same file can be found there.
I hope some people will find this useful/amusing. :-)
Johnny Billquist
22 Jan
22 Jan
8:47 a.m.
New subject: [HECnet] Announcing TCP/IP for RSX-11M-PLUS
I just thought I'd make yet an announcement.
(Maybe I should find a better forum for this?)
The last week I've been busy with FTP improvements and performance, and
I've managed to improve this a lot.
Enough that it is worth sending information out that people should
upgrade if they have installed this.
The FTP client and server have improved performance and some additional
features. Along with this I also changed the protocol format for RSX
special mode transfers. This is not backwards compatible, and due to an
initial design miss, the old ftp client/server will not reliably detect
this incompatibility, resulting in broken files if RSX mode is used
between the old and new version. This will not be a problem going
forward. If you run FTP from RSX to fetch the new package, use BLOCK
mode instead of RSX mode, and fetch the disk image and not the tape
image, and you'll be fine. Once upgraded, RSX mode is definitely the
recommended mode for the future. For all kind of files.
TCP itself increased the receive buffer size, which also improves
performance for everything that would be interested in higher throughput.
I've also gone over the distribution and installation scripts and fixed
a few minor details.
As usual, the distribution is available from:
ftp://madame.update.uu.se/bqtcp.dsk
ftp://madame.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Madame, or also at
http://madame.update.uu.se/tcpipdoc
Johnny
All in all,
On 2015-01-16 04:47, Johnny Billquist wrote:
There have been lots of positive comments, and
obviously some people
have even tested using the software.
Of course, a bug was also found. A really weird corner case with
severely loading the network stack and having a socket in listen state
programatically could trigger a corruption of kernel memory.
So I've cut a new release with the bug fixed.
While I'm at it I also realize that I forgot to mention that included in
the distribution is also a simple IRC client as well as a simple IRC robot.
I've also taken a little time to slightly improve the documentation, and
the documentation is now also available directly by ftp from
Madame.Update.UU.SE, so you do not need to get the whole distribution
and unpack it to just read something.
So - same as before. Disk image and tape image are available at
Madame.Update.UU.SE. Use anonymous ftp.
Disk image is also available at ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip.
The disk image is a virtual RL02 disk. Can be used with any emulator, or
also directly inside RSX if you have virtual devices available.
Happy hacking.
Johnny
On 2015-01-14 00:40, Johnny Billquist wrote:
Well, it's been a long time project, but
I'm happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
This is the result of over 20 years of development. Needless to say,
I've been doing a lot of things over the years, and this code have been
through four reimplementations over the years.
What I now release is something that I believe is a nice and useful
piece of software. I am aware of the fact that most people do not use
these machines any longer, but if someone actually wants to talk to me
about support for this or other RSX software, let me know.
Also, feel free to spread this information to anyone who might be
interested, anywhere.
So - what is in this release?
It is a complete implementation of ARP, IP, UDP, and TCP for
RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work
on any V4 release. There might be some small tweaks or fixes required,
but nothing major.
It do require a system with split I/D-space, or else at least the TCP
part will not fit.
For Unibus machines, it should be possible to run without any additional
software except what is in a base RSX distribution.
For Q-bus machines, DECnet is required for ethernet networking.
The TCP/IP stack can co-exist with DECnet.
Some utilities also utilize RMS for file access.
A bunch of tools, utilities and libraries are also included. These
include:
. IFCONFIG network configuration tool.
. NETSTAT network information tool.
. PING
. TRACEROUTE
. DNS client
. FTP daemon
. FTP client
. HTTP server
. TELNET client (rudimentary)
. TFTP client
. TFTP server
. INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT
. NTP client
. LPR client that sits in the queue manager (rudimentary)
. FORTRAN-77 library
. BASIC+2 library
. PDP-11 C library
The implementation fulfills most of the requirements put forth in RFC
1122. There are a few limitations because of restrictions in the PDP-11,
but none of them should really cause any problems.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
A bunch of test programs and example programs are also included, as well
as the sources of all tools and libraries.
The TCP/IP stack itself only comes in binary form.
All tools are also included precompiled in the distribution, so an
installation only have to build the stack itself for your system, and
then you should be ready to go.
The API only have a slight resemblance to the Unix sockets API. However,
if someone sits down to write code to use TCP/IP under RSX, I'm sure
they will discover that it is extremely easy to use the libraries, or
the basic functions.
The TCP/IP implementation is mostly written as device drivers. This also
have some other interesting implications, such as it is possible to
access TCP as a normal file. You can, for instance do something similar
to the Unix netcat command by issuing the MCR command:
PIP TI:=TC:"foo.com";4711
which would open a connection to foo.com, on port 4711, and any data
sent from that machine will be shown on the terminal.
The resources used by TCP/IP are modest. A memory area (size selectable
at generation/startup) is used internally. The amount of memory in the
private pool limits the amount of data that can be buffered. Normal pool
is used in a small quantity for each TCP port that is open.
People are welcome to play around with this, and make improvements.
Contributions of code is most welcome.
There are still lots of things to do. The programs marked as rudimentary
should be rewritten.
The most obvious thing still missing is a telnet daemon, which probably
is my next step.
However, the reason for now announcing the release is that it can
finally be distributed natively from an RSX host.
The main locations to download the TCP/IP for RSX are:
Madame.Update.UU.SE (anonymous ftp).
This is one of my development systems for this software. It runs under
E11, and if things are down, I blame E11. :-)
When connected, you are already in the right directory. There is both an
RL02 disk image there, which can be downloaded by anyone. If you happen
to have an RSX system which you are conneting from, you can also try
getting the BQTCP.TAP tape image. Such an image will not transport
cleanly to a non-RSX system, however. Sorry.
ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip
The disk image is normally duplicated to ftp.update.uu.se as well, so
the same file can be found there.
I hope some people will find this useful/amusing. :-)
Johnny Billquist
17 Mar
17 Mar
8:38 a.m.
New subject: [HECnet] Announcing TCP/IP for RSX-11M-PLUS
It's been close to two months since the last announcement. I have been
busy with improving thing since then, and I guess it's time to announce
a new version, for people who might be interested.
Improvements since last announcements:
. FTP client and server have had extensive bugfixing, performance
improvements and feature enhancements.
. NETSTAT has been rewritten to be more useful and friendly.
. Bugfix in INETD. It never checked the result from the ACCEPT.
. TCP have had several bugfixes and improvements:
. At tcp close, retransmit didn't happen if only FIN was left
unacknowledged.
. If both sides sent FIN at the same time, the socket could get out
of sync.
. Improved performance at FIN time by allowing ACK to be delayed.
. Accept legal packets after the FIN.
. Cleanup of how offspring task sockets are handled.
. Added the ability to transmit TCP URGENT data.
. Redesigned the TCP receive window handling for improved performance.
. TCP PUSH could transmit more data with push flag that it should.
. Added handling of ICMP error packets to TCP.
. Installation procedure have been updated with the ability to not
install some command files. The helps with updates of existing installation.
. Documentation have been updated (although it still miss a lot of pieces.)
I encourage everyone who have installed BQTP/IP on an RSX system to
update to the latest version, as some of these fixes can make a big
difference.
As usual, the distribution is available from:
ftp://madame.update.uu.se/bqtcp.dsk
ftp://madame.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Madame, or also at
http://madame.update.uu.se/tcpipdoc
Johnny
On 2015-01-22 17:47, Johnny Billquist wrote:
I just thought I'd make yet an announcement.
(Maybe I should find a better forum for this?)
The last week I've been busy with FTP improvements and performance, and
I've managed to improve this a lot.
Enough that it is worth sending information out that people should
upgrade if they have installed this.
The FTP client and server have improved performance and some additional
features. Along with this I also changed the protocol format for RSX
special mode transfers. This is not backwards compatible, and due to an
initial design miss, the old ftp client/server will not reliably detect
this incompatibility, resulting in broken files if RSX mode is used
between the old and new version. This will not be a problem going
forward. If you run FTP from RSX to fetch the new package, use BLOCK
mode instead of RSX mode, and fetch the disk image and not the tape
image, and you'll be fine. Once upgraded, RSX mode is definitely the
recommended mode for the future. For all kind of files.
TCP itself increased the receive buffer size, which also improves
performance for everything that would be interested in higher throughput.
I've also gone over the distribution and installation scripts and fixed
a few minor details.
As usual, the distribution is available from:
ftp://madame.update.uu.se/bqtcp.dsk
ftp://madame.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Madame, or also at
http://madame.update.uu.se/tcpipdoc
Johnny
All in all,
On 2015-01-16 04:47, Johnny Billquist wrote:
There have been lots of positive comments, and
obviously some people
have even tested using the software.
Of course, a bug was also found. A really weird corner case with
severely loading the network stack and having a socket in listen state
programatically could trigger a corruption of kernel memory.
So I've cut a new release with the bug fixed.
While I'm at it I also realize that I forgot to mention that included in
the distribution is also a simple IRC client as well as a simple IRC
robot.
I've also taken a little time to slightly improve the documentation, and
the documentation is now also available directly by ftp from
Madame.Update.UU.SE, so you do not need to get the whole distribution
and unpack it to just read something.
So - same as before. Disk image and tape image are available at
Madame.Update.UU.SE. Use anonymous ftp.
Disk image is also available at
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip.
The disk image is a virtual RL02 disk. Can be used with any emulator, or
also directly inside RSX if you have virtual devices available.
Happy hacking.
Johnny
On 2015-01-14 00:40, Johnny Billquist wrote:
Well, it's been a long time project, but
I'm happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
This is the result of over 20 years of development. Needless to say,
I've been doing a lot of things over the years, and this code have been
through four reimplementations over the years.
What I now release is something that I believe is a nice and useful
piece of software. I am aware of the fact that most people do not use
these machines any longer, but if someone actually wants to talk to me
about support for this or other RSX software, let me know.
Also, feel free to spread this information to anyone who might be
interested, anywhere.
So - what is in this release?
It is a complete implementation of ARP, IP, UDP, and TCP for
RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work
on any V4 release. There might be some small tweaks or fixes required,
but nothing major.
It do require a system with split I/D-space, or else at least the TCP
part will not fit.
For Unibus machines, it should be possible to run without any additional
software except what is in a base RSX distribution.
For Q-bus machines, DECnet is required for ethernet networking.
The TCP/IP stack can co-exist with DECnet.
Some utilities also utilize RMS for file access.
A bunch of tools, utilities and libraries are also included. These
include:
. IFCONFIG network configuration tool.
. NETSTAT network information tool.
. PING
. TRACEROUTE
. DNS client
. FTP daemon
. FTP client
. HTTP server
. TELNET client (rudimentary)
. TFTP client
. TFTP server
. INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT
. NTP client
. LPR client that sits in the queue manager (rudimentary)
. FORTRAN-77 library
. BASIC+2 library
. PDP-11 C library
The implementation fulfills most of the requirements put forth in RFC
1122. There are a few limitations because of restrictions in the PDP-11,
but none of them should really cause any problems.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
A bunch of test programs and example programs are also included, as well
as the sources of all tools and libraries.
The TCP/IP stack itself only comes in binary form.
All tools are also included precompiled in the distribution, so an
installation only have to build the stack itself for your system, and
then you should be ready to go.
The API only have a slight resemblance to the Unix sockets API. However,
if someone sits down to write code to use TCP/IP under RSX, I'm sure
they will discover that it is extremely easy to use the libraries, or
the basic functions.
The TCP/IP implementation is mostly written as device drivers. This also
have some other interesting implications, such as it is possible to
access TCP as a normal file. You can, for instance do something similar
to the Unix netcat command by issuing the MCR command:
PIP TI:=TC:"foo.com";4711
which would open a connection to foo.com, on port 4711, and any data
sent from that machine will be shown on the terminal.
The resources used by TCP/IP are modest. A memory area (size selectable
at generation/startup) is used internally. The amount of memory in the
private pool limits the amount of data that can be buffered. Normal pool
is used in a small quantity for each TCP port that is open.
People are welcome to play around with this, and make improvements.
Contributions of code is most welcome.
There are still lots of things to do. The programs marked as rudimentary
should be rewritten.
The most obvious thing still missing is a telnet daemon, which probably
is my next step.
However, the reason for now announcing the release is that it can
finally be distributed natively from an RSX host.
The main locations to download the TCP/IP for RSX are:
Madame.Update.UU.SE (anonymous ftp).
This is one of my development systems for this software. It runs under
E11, and if things are down, I blame E11. :-)
When connected, you are already in the right directory. There is both an
RL02 disk image there, which can be downloaded by anyone. If you happen
to have an RSX system which you are conneting from, you can also try
getting the BQTCP.TAP tape image. Such an image will not transport
cleanly to a non-RSX system, however. Sorry.
ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip
The disk image is normally duplicated to ftp.update.uu.se as well, so
the same file can be found there.
I hope some people will find this useful/amusing. :-)
Johnny Billquist
8 Jun
8 Jun
9:56 a.m.
New subject: [HECnet] Announcing TCP/IP for RSX-11M-PLUS
About three months since I last announced anything. There have been
various development since, and I figured I should encourage people who
are using BQTCP/IP for RSX to upgrade to the latest release.
A short list of changes:
ICMP:
. ICMP packets accidentally lost the source IP address informaton when
returning information to a program. - Fixed.
TCP:
. User timers on TCP sockets could erroneously stop. - Fixed.
. User timers now reset on completed reads, so that you do
not get a timeout if you are constantly completing reads.
. Sockets in Fin-Wait-2 could sometimes get stuck in that state.
- Fixed.
. If a TCP session got an RST, it could get into a bad state. - Fixed.
. Added the ability to send URGENT data in TCP. (Receive ignores any
URGENT flags.)
. Added a special I/O function to read from TCP without formatting.
DNS:
. Improved stability of DNS client daemon code.
FTP:
. FTP client and server performance improved.
. FTP server logging added.
. Improvements in FTP server and client for handling files with implicit
CFLF.
. Implemented primitive handling of Unix file paths implemented in FTP
server. This allows most web browsers to access FTP repositories
under RSX.
I also did some performance testing using FTP.
FTP from a modern Unix system of BQTCP.DSK in binary mode to both RSX
and 2.11BSD, running under simh on the same physical machine:
2.11BSD: 210s
RSX: 141s
From RSX (E11) to the same machines:
2.11BSD: 240s
RSX: 137s
I honestly do not know why transfer from RSX to 2.11BSD took longer than
from Unix, but transfer from RSX to RSX was faster
compared to Unix to
RSX. I would have expected both to be slower or faster. But the
numbers
are interesting, and show that the RSX TCP implementation is doing
fairly well, even through it goes through the DECnet ethernet driver, as
compared to 2.11BSD which runs TCP/IP more "native".
As usual, the distribution is available from:
ftp://madame.update.uu.se/bqtcp.dsk
ftp://madame.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Madame, or also at
http://madame.update.uu.se/tcpipdoc
I hope people will find this latest release useful, and my next project
right now is telnet.
Johnny
On 2015-01-16 04:47, Johnny Billquist wrote:
There have been lots of positive comments, and
obviously some people
have even tested using the software.
Of course, a bug was also found. A really weird corner case with
severely loading the network stack and having a socket in listen state
programatically could trigger a corruption of kernel memory.
So I've cut a new release with the bug fixed.
While I'm at it I also realize that I forgot to mention that included in
the distribution is also a simple IRC client as well as a simple IRC robot.
I've also taken a little time to slightly improve the documentation, and
the documentation is now also available directly by ftp from
Madame.Update.UU.SE, so you do not need to get the whole distribution
and unpack it to just read something.
So - same as before. Disk image and tape image are available at
Madame.Update.UU.SE. Use anonymous ftp.
Disk image is also available at ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip.
The disk image is a virtual RL02 disk. Can be used with any emulator, or
also directly inside RSX if you have virtual devices available.
Happy hacking.
Johnny
On 2015-01-14 00:40, Johnny Billquist wrote:
Well, it's been a long time project, but
I'm happy to finally announce a
more public initial release of TCP/IP for RSX-11M-PLUS.
This is the result of over 20 years of development. Needless to say,
I've been doing a lot of things over the years, and this code have been
through four reimplementations over the years.
What I now release is something that I believe is a nice and useful
piece of software. I am aware of the fact that most people do not use
these machines any longer, but if someone actually wants to talk to me
about support for this or other RSX software, let me know.
Also, feel free to spread this information to anyone who might be
interested, anywhere.
So - what is in this release?
It is a complete implementation of ARP, IP, UDP, and TCP for
RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work
on any V4 release. There might be some small tweaks or fixes required,
but nothing major.
It do require a system with split I/D-space, or else at least the TCP
part will not fit.
For Unibus machines, it should be possible to run without any additional
software except what is in a base RSX distribution.
For Q-bus machines, DECnet is required for ethernet networking.
The TCP/IP stack can co-exist with DECnet.
Some utilities also utilize RMS for file access.
A bunch of tools, utilities and libraries are also included. These
include:
. IFCONFIG network configuration tool.
. NETSTAT network information tool.
. PING
. TRACEROUTE
. DNS client
. FTP daemon
. FTP client
. HTTP server
. TELNET client (rudimentary)
. TFTP client
. TFTP server
. INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT
. NTP client
. LPR client that sits in the queue manager (rudimentary)
. FORTRAN-77 library
. BASIC+2 library
. PDP-11 C library
The implementation fulfills most of the requirements put forth in RFC
1122. There are a few limitations because of restrictions in the PDP-11,
but none of them should really cause any problems.
Documentation is still on the thin side, but example configs are also
provided, along with installation scripts.
A bunch of test programs and example programs are also included, as well
as the sources of all tools and libraries.
The TCP/IP stack itself only comes in binary form.
All tools are also included precompiled in the distribution, so an
installation only have to build the stack itself for your system, and
then you should be ready to go.
The API only have a slight resemblance to the Unix sockets API. However,
if someone sits down to write code to use TCP/IP under RSX, I'm sure
they will discover that it is extremely easy to use the libraries, or
the basic functions.
The TCP/IP implementation is mostly written as device drivers. This also
have some other interesting implications, such as it is possible to
access TCP as a normal file. You can, for instance do something similar
to the Unix netcat command by issuing the MCR command:
PIP TI:=TC:"foo.com";4711
which would open a connection to foo.com, on port 4711, and any data
sent from that machine will be shown on the terminal.
The resources used by TCP/IP are modest. A memory area (size selectable
at generation/startup) is used internally. The amount of memory in the
private pool limits the amount of data that can be buffered. Normal pool
is used in a small quantity for each TCP port that is open.
People are welcome to play around with this, and make improvements.
Contributions of code is most welcome.
There are still lots of things to do. The programs marked as rudimentary
should be rewritten.
The most obvious thing still missing is a telnet daemon, which probably
is my next step.
However, the reason for now announcing the release is that it can
finally be distributed natively from an RSX host.
The main locations to download the TCP/IP for RSX are:
Madame.Update.UU.SE (anonymous ftp).
This is one of my development systems for this software. It runs under
E11, and if things are down, I blame E11. :-)
When connected, you are already in the right directory. There is both an
RL02 disk image there, which can be downloaded by anyone. If you happen
to have an RSX system which you are conneting from, you can also try
getting the BQTCP.TAP tape image. Such an image will not transport
cleanly to a non-RSX system, however. Sorry.
ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip
The disk image is normally duplicated to ftp.update.uu.se as well, so
the same file can be found there.
I hope some people will find this useful/amusing. :-)
Johnny Billquist
20 Oct
20 Oct
10:08 a.m.
About four months since I last announced anything. There have been
various development since, and I figured I should encourage people who
are using BQTCP/IP for RSX to upgrade to the latest release.
A short list of changes:
TCP:
. Small bugfixes in various states.
. Bugfix in window handling. TCP reception could occasionally accept
data outside of window.
. Added ability to dynamically change transmit and receive buffer size.
. Bugfix. SYN packets could result in lost pool if sockets were closed
with outstanding SYN packets queued.
. Bugfix. If pool is full, system could crash on incoming connections.
FTP:
. Added SUMMARY, PROMPT, MGET and MPUT commands.
. Improved filename parsing and handling for mapping between local and
remote filenames.
. Bugfix. FTP would abort if a long file transfer took place, since the
command channel had a timeout.
. Much improved progress line for file transfers, including ETA and
delta between updates.
FTPD:
. Bugfix. If a file transfer was followed by an immediate close of the
connection, the file could be left in a locked state.
. Expanded time stamp information in directory listings to include seconds.
TELNET:
. Bugfix in telnet options processing.
TELNETD:
. Bugfix in telnet options processing.
IFCONFIG:
. Added commands for setting default and maximum allowed tcp transmit
and receive buffer sizes.
RMD:
. Added information on task page about UDP connections.
TRACERT:
. Added /NUMERIC switch
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 believe the state of the code is now good enough that I expect there
will be fewer updates to the basic networking drivers in the future. I
plan to find some new protocols to work on next, and also improve some
of the current clients and servers as the need arises.
(On a different note, Madame.Update.UU.SE is now a CNAME for
Mim.Update.UU.SE, making the naming of the machine consistent between
DECnet and TCP/IP, in case someone wonders why the name have changed...)
Johnny
3116
days inactive
3396
days old
21 comments
8 participants
participants (8)
-
bqt＠softjar.se -
bqt＠update.uu.se -
healyzh＠aracnet.com -
jacob.ritorto＠gmail.com -
mouse＠Rodents-Montreal.ORG -
pontus＠Update.UU.SE -
tmfdmike＠gmail.com -
toby＠telegraphics.com.au