Got the reply in the end. Not sure why it took so long to get to me, but it
made it in the end!
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Robert Jarratt
Sent: 19 March 2015 19:15
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Mail gateway?
Oooh, didn't know about that. I tried sending myself an email to HECnet
and it
worked perfectly. I have just tried a reply but nothing has come through
yet.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On
Behalf Of Robert Armstrong
Sent: 19 March 2015 16:53
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Mail gateway?
Yes, LEGATO is running one. You can send mail to
"user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user
name.
I've been tempted to kill it - it spends most of its time processing
SPAM
- but for the moment it's still working.
Bob
Oooh, didn't know about that. I tried sending myself an email to HECnet and
it worked perfectly. I have just tried a reply but nothing has come through
yet.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Robert Armstrong
Sent: 19 March 2015 16:53
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Mail gateway?
Yes, LEGATO is running one. You can send mail to
"user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user
name.
I've been tempted to kill it - it spends most of its time processing
SPAM
- but for the moment it's still working.
Bob
Oh cool. What I did was open a Google Apps account for my domain (chimpymail.com) and then used fetchmail to pull the mail down - that way Google did the spam filtering - too bad they charge real money new accounts now.
I'd be happy to host it on GORVAX if somebody helped me set it up...
Sampsa
On 19 Mar 2015, at 16:52, Robert Armstrong <bob at jfcl.com> wrote:
Yes, LEGATO is running one. You can send mail to "user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user name.
I've been tempted to kill it - it spends most of its time processing SPAM
- but for the moment it's still working.
Bob
Yes, LEGATO is running one. You can send mail to "user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user name.
I've been tempted to kill it - it spends most of its time processing SPAM
- but for the moment it's still working.
Bob
Yes, LEGATO is running one. You can send mail to "user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user name.
I've been tempted to kill it - it spends most of its time processing SPAM
- but for the moment it's still working.
Bob
Yes, LEGATO is running one. You can send mail to "user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user name.
I've been tempted to kill it - it spends most of its time processing SPAM
- but for the moment it's still working.
Bob
Yes, LEGATO is running one. You can send mail to "user at node.decnet.org",
where "user" and "node" are your HECnet node name and your local user name.
I've been tempted to kill it - it spends most of its time processing SPAM
- but for the moment it's still working.
Bob
On Mar 19, 2015, at 12:32 PM, Sampsa Laine <sampsa at mac.com> wrote:
Guys,
Is anyone running a mail gateway between HECnet and the Internet?
Just asking out of interest, CHIMPY:: used to be able to gateway mail but the new ISP doesn't like the address formats so drops the outgoing mails..
A possible solution to that issue is not to relay via the ISP, but to have your local mail agent deliver directly to the recipient. That assumes the ISP doesn t block port 25, of course.
paul
Guys,
Is anyone running a mail gateway between HECnet and the Internet?
Just asking out of interest, CHIMPY:: used to be able to gateway mail but the new ISP doesn't like the address formats so drops the outgoing mails..
Sampsa
El 19/03/2015, a les 15:38, Steve Davidson <steve at davidson.net> va escriure:
SGC:: is a level 1 router and SGC:: is an area router. SGC:: is functioning normally but SG1:: is not. Apparenty the TOY clock is not functioning. When that happens the default boot device reverts to the Ethernet port. In SG1::'s case, booting using the Ethernet port results in booting into the STRGTE:: cluster for maintenance purposes and no Multinet and no area router. I will try to install/configure Multinet in this variant sometime today - remotely.
Ouch, that sounds like a dead DS1287A...
As you probably know, the DS12887A is a drop-in replacement, and it is easily available (11,52 at Farnell).
SGC:: is a level 1 router and SGC:: is an area router. SGC:: is functioning normally but SG1:: is not. Apparenty the TOY clock is not functioning. When that happens the default boot device reverts to the Ethernet port. In SG1::'s case, booting using the Ethernet port results in booting into the STRGTE:: cluster for maintenance purposes and no Multinet and no area router. I will try to install/configure Multinet in this variant sometime today - remotely.
-Steve
Sent from my iPhone
On Mar 19, 2015, at 07:18, <Paul_Koning at Dell.com> <Paul_Koning at Dell.com> wrote:
On Mar 18, 2015, at 5:00 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
...
Now I'm a little bit lost. I think a node must be configured as an Area router to be able to route between two areas via the multinet link.
There are two reasons why a node may have to be an area router:
1. If it needs to have other nodes that are in a different area as neighbors
2. If you want to be able to see the area routing tables
But if your neighbor is in the same area as you, the whole network is reachable to any node type (endnode, L1 router, area router). The L1 router doesn t have a map of the areas, but instead it sends all out-of-area traffic to the nearest L2 router which is represented in the L1 routing data by the entry for address 0.
The datalink type is not a factor here; Multinet is no different from any other point to point link in this respect.
paul
On Mar 18, 2015, at 5:00 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
...
Now I'm a little bit lost. I think a node must be configured as an Area router to be able to route between two areas via the multinet link.
There are two reasons why a node may have to be an area router:
1. If it needs to have other nodes that are in a different area as neighbors
2. If you want to be able to see the area routing tables
But if your neighbor is in the same area as you, the whole network is reachable to any node type (endnode, L1 router, area router). The L1 router doesn t have a map of the areas, but instead it sends all out-of-area traffic to the nearest L2 router which is represented in the L1 routing data by the entry for address 0.
The datalink type is not a factor here; Multinet is no different from any other point to point link in this respect.
paul
On Wed, 18 Mar 2015, Dave McGuire wrote:
On 03/18/2015 07:07 PM, Ian McLaughlin wrote:
I try to take my VAXen on vacation with us in our hotel room, but my wife objects.
http://www.plentyoffish.com/http://www.match.com/
Not much makes me literally laugh involuntarily, but that one did.
Dave, you almost owed me a new keyboard. ;)
Fred
---
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
I am working on a Raspberry Pi with a micro terminal screen/mouse/keypad for just such events. When I am done it will be able to come up as either a VAXserver-3900 or a PDP-11/23+, PDP-11/73...
-Steve
Sent from my iPhone
On Mar 18, 2015, at 16:25, Dave McGuire <mcguire at neurotica.com> wrote:
On 03/18/2015 07:07 PM, Ian McLaughlin wrote:
I try to take my VAXen on vacation with us in our hotel room, but my wife objects.
http://www.plentyoffish.com/http://www.match.com/
--
Dave McGuire, AK4HZ/3
New Kensington, PA
On 03/18/2015 07:07 PM, Ian McLaughlin wrote:
I try to take my VAXen on vacation with us in our hotel room, but my wife objects.
http://www.plentyoffish.com/http://www.match.com/
--
Dave McGuire, AK4HZ/3
New Kensington, PA
El 19/03/15 a les 00:07, Ian McLaughlin ha escrit:
I try to take my VAXen on vacation with us in our hotel room, but my wife objects.
Sent from my iPhone
I'm not sure the hotel administrator would be very happy in case you plug in some 780's :)
Enjoy your vacation. I'm using the bridge as a backup, so I'm fine. I simply wasn't completely sure the problem wasn't in my side of things. Until two weeks ago I was trying to hook into SG1 simultaneously from two of my machines, one of those was not configured as a router. As you can imagine, it didn't go very well ;)
I try to take my VAXen on vacation with us in our hotel room, but my wife objects.
Sent from my iPhone
On Mar 18, 2015, at 3:48 PM, Steve Davidson <steve at davidson.net> wrote:
I will look at SG1 this evening from my hotel room and see what is going on.
-Steve
Sent from my iPhone
On Mar 18, 2015, at 14:00, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
Hello,
I don't have Steve's email, so I'm asking this here.
I've lost again connectivity to SG1 via Multinet UDP link. Since I have been doing... funny things at my side, I have checked the situation a little bit and I've found SG1 is broadcasting ENDNODE Hello packets (which I get through Johnny's bridge):
514 15.000758 19.41 DECNET-Phase-IV-end-node-Hello-packets DEC DNA 60 Routing control, Endnode Hello message
Now I'm a little bit lost. I think a node must be configured as an Area router to be able to route between two areas via the multinet link. Actually, SG1 is unreachable even thru Johnny's bridge, which probably means there is no area router configured for the area 19... I've tried to reach SG1 from MIM, and it is not reachable from there either, so (for one time) the problem won't be at my side ;)
Am I missing anything?
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=0047DD56CDC111E49…
I will look at SG1 this evening from my hotel room and see what is going on.
-Steve
Sent from my iPhone
On Mar 18, 2015, at 14:00, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
Hello,
I don't have Steve's email, so I'm asking this here.
I've lost again connectivity to SG1 via Multinet UDP link. Since I have been doing... funny things at my side, I have checked the situation a little bit and I've found SG1 is broadcasting ENDNODE Hello packets (which I get through Johnny's bridge):
514 15.000758 19.41 DECNET-Phase-IV-end-node-Hello-packets DEC DNA 60 Routing control, Endnode Hello message
Now I'm a little bit lost. I think a node must be configured as an Area router to be able to route between two areas via the multinet link. Actually, SG1 is unreachable even thru Johnny's bridge, which probably means there is no area router configured for the area 19... I've tried to reach SG1 from MIM, and it is not reachable from there either, so (for one time) the problem won't be at my side ;)
Am I missing anything?
Hello,
I don't have Steve's email, so I'm asking this here.
I've lost again connectivity to SG1 via Multinet UDP link. Since I have been doing... funny things at my side, I have checked the situation a little bit and I've found SG1 is broadcasting ENDNODE Hello packets (which I get through Johnny's bridge):
514 15.000758 19.41 DECNET-Phase-IV-end-node-Hello-packets DEC DNA 60 Routing control, Endnode Hello message
Now I'm a little bit lost. I think a node must be configured as an Area router to be able to route between two areas via the multinet link. Actually, SG1 is unreachable even thru Johnny's bridge, which probably means there is no area router configured for the area 19... I've tried to reach SG1 from MIM, and it is not reachable from there either, so (for one time) the problem won't be at my side ;)
Am I missing anything?
On 2015-03-18 04:54, Cory Smelosky wrote:
Sent from my iPhone
On Mar 17, 2015, at 22:26, Mark Matlock <mark at matlockfamily.com> wrote:
Johnny,
Thanks for the update. I've been installing some of the various updates that you have put out since the early version, and have seen the number of the improvements you have made. It is so nice to have the ability to move files with ftp from linux or the internet directly into files-11 !! Even whole .dsk files from bitsavers which can be loaded as virtual disks in RSX.
I have been using it both on a real PDP-11/83 and with Simh on Mac, Ubuntu and Raspberry PI2. Also, thanks for distributing the precompiled versions of the utilities as this helps when BP2 and PDP-11 C are not readily available.
Is Split I&D a requirement?
It is for the TCP driver itself. Sorry, I don't have any plans on trying to squeeze it on a machine that don't have split I/D space. While it would be possible, it would take a lot of work.
Johnny
I hope to have some time to read the sources and learn much more about TCP/IP. I've already found the NTPDATE.C program quite interesting.
Thanks again for your efforts to keep RSX alive for those of us who have such affection for it.
Best Regards,
Mark Matlock
On Mar 17, 2015, at 10:38 AM, Johnny Billquist wrote:
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
Hi, Mark.
On 2015-03-18 03:26, Mark Matlock wrote:
Johnny,
Thanks for the update. I've been installing some of the various updates that you have put out since the early version, and have seen the number of the improvements you have made. It is so nice to have the ability to move files with ftp from linux or the internet directly into files-11 !! Even whole .dsk files from bitsavers which can be loaded as virtual disks in RSX.
You are welcome. It's great that some people find it useful.
Yes, the fact that disk images can be ftp:d right in, and used by the virtual device driver is a big win.
I have been using it both on a real PDP-11/83 and with Simh on Mac, Ubuntu and Raspberry PI2. Also, thanks for distributing the precompiled versions of the utilities as this helps when BP2 and PDP-11 C are not readily available.
If there are any binaries that fail to run, let me know. Maybe some shared library is missing, or something, that I could provide.
I hope to have some time to read the sources and learn much more about TCP/IP. I've already found the NTPDATE.C program quite interesting.
Please do. I think the code should be pretty easy to follow, both for the C and BASIC+2 sources. And it's really easy to write your own programs to access TCP/IP. Much easier than under Unix.
Thanks again for your efforts to keep RSX alive for those of us who have such affection for it.
Keep using it.
Johnny
Best Regards,
Mark Matlock
On Mar 17, 2015, at 10:38 AM, Johnny Billquist wrote:
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
Sent from my iPhone
On Mar 17, 2015, at 22:26, Mark Matlock <mark at matlockfamily.com> wrote:
Johnny,
Thanks for the update. I've been installing some of the various updates that you have put out since the early version, and have seen the number of the improvements you have made. It is so nice to have the ability to move files with ftp from linux or the internet directly into files-11 !! Even whole .dsk files from bitsavers which can be loaded as virtual disks in RSX.
I have been using it both on a real PDP-11/83 and with Simh on Mac, Ubuntu and Raspberry PI2. Also, thanks for distributing the precompiled versions of the utilities as this helps when BP2 and PDP-11 C are not readily available.
Is Split I&D a requirement?
I hope to have some time to read the sources and learn much more about TCP/IP. I've already found the NTPDATE.C program quite interesting.
Thanks again for your efforts to keep RSX alive for those of us who have such affection for it.
Best Regards,
Mark Matlock
On Mar 17, 2015, at 10:38 AM, Johnny Billquist wrote:
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
Johnny,
Thanks for the update. I've been installing some of the various updates that you have put out since the early version, and have seen the number of the improvements you have made. It is so nice to have the ability to move files with ftp from linux or the internet directly into files-11 !! Even whole .dsk files from bitsavers which can be loaded as virtual disks in RSX.
I have been using it both on a real PDP-11/83 and with Simh on Mac, Ubuntu and Raspberry PI2. Also, thanks for distributing the precompiled versions of the utilities as this helps when BP2 and PDP-11 C are not readily available.
I hope to have some time to read the sources and learn much more about TCP/IP. I've already found the NTPDATE.C program quite interesting.
Thanks again for your efforts to keep RSX alive for those of us who have such affection for it.
Best Regards,
Mark Matlock
On Mar 17, 2015, at 10:38 AM, Johnny Billquist wrote:
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
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
On 2015-03-16 21:05, Clem Cole wrote:
On Mon, Mar 16, 2015 at 3:55 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Nitpick: The 11/40 "class" machines did not have split I/D space.
Split I/D space was the 11/45,11/50,11/55 and 11/70, before we move
into "modern" PDP-11s..
That's what I said - "shared I/D" as opposed to "split I/D"
Doh! Color me stupid then. :-)
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
