Can anybody tell me the secret to making DECnet work on Ubuntu 14.04
(Precise)? Yes, this release is out of date but it's the one I need to
use for other compatibility reasons.
I installed the dnet-common, dnet-progs and libdnet packages from the
standard repository. I configured the /etc/decnet.conf and dnet.conf files
(and I don't care about decnet.proxy just yet). Nothing seems to give an
error, the dnetd daemon is running, and the MAC of my eth0 has been changed
to match my DECnet address. dneigh shows the correct adjacent routing node
on the network.
But nothing can communicate. All the DECnet commands (sethost, dnping,
etc) give "socket: no such device" errors, and all the other DECnet machines
on the network think the Linux host is unavailable.
I seem to remember that there was some problem with the DECnet startup
with upstart, but I don't remember the details and Google isn't being
helpful today.
Thanks,
Bob
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
Highlights:
This release have some performance improvements, bugfixes, and
additional functionality. It also includes a print symbiont for the
queue manager, which spools files over TCP/IP to remote printers.
Detailed information on things that have been done since the last release:
IP:
. Added routing capability.
. Added command to IFCONFIG to enable/disable routing.
TCP:
. Reworked TCP retransmit strategy for improved performance.
. Bugfix in TCP timeouts. Sometimes the wrong time was used.
. Change to allow creation of a new port if there is an existing port
which is in time wait.
. Improve TCP probe logic.
. Bugfix in CR mode. CR was not padded by NUL if followed by another CR.
. Added PU.RBL option to TCP sockets, for reading without blocking.
. Bugfix in daemon creation. TCP could create more daemons than it was
allowed to.
TELNETD:
. Added a shorter timeout for TELNETD incoming connection establish.
. Added proper handling of low pool situation in TELNETD.
. Bugfix in option processing. "Don't binary" option was not handled right.
FTP:
. Bugfix in FTP. Checking for existing file to not overwrite files at
MGET incorrectly caused some transfers to not proceed.
. Bugfix in FTP. PASSIVE command responded with the wrong message.
. Bugfix in FTP. The initial connection from command line caused FTP to
enter wrong transfer mode if the remote system was RSX.
. Bugfix in FTP. The keepalive command in an INIT file caused the
processing of the INIT file to abort.
FTPD:
. Improved statistics output at connection close.
MAILD:
. Improved performance.
. Improved robustness of SMTP receive processing.
. Changed mail queue format for better efficiency.
. Fixed MAIL11 sending. Nonexistent node is a fatal error.
. Increased stack size of MAILD task to avoid some crashes.
NTPDATE:
. Bugfix. If local time offset was too far from UTC, NTPDATE failed to
correctly adjust time because some arithmetic was done with 16-bit integers.
LPT:
. Added new LPT spooler that runs under the queue manager.
XLISP:
. Added another example program.
Libraries:
. BQTLIB - Fixed checking for disabled accounts. (This affected FTPD).
. IPC - Fixed sclose(). This function leaked file descriptor.
Distribution:
. Added SLIPACP and DLXACP. Both are to be considered very experimental,
and might crash the system. But if someone is interested in SLIP, or IP
over DDCMP, please contact me for more information.
. Fixed generated IPINS.CMD file to work if CLI is not MCR.
. Added default for LINE question in IPGEN.
. Added two forgotten files with HTTPD server.
. Added [1,1]DAPSLX.ODL, which should have been on RSX distribution.
. Added RSXERR.MSG to distribution.
*** A special note on the routing capability in BQTCP/IP:
This functionality have been added since it might be needed if more
interfaces than the standard ethernet and loopback is configured. This
is at the moment very experimental, in the form of SLIP and DDCMP lines.
If you do not use more than ethernet for external communication, you
should not enable IP routing on the RSX host, as it is considered bad
practice to have hosts in general do routing.
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
I hope people find this update useful. While there are no really
critical issues that have been solved, I still recommend people to
update, since this new version do contain improvements that are
beneficial and as far as I know there are no issues or problems updating
to this newest version.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
A GRE tunnel up from 31.1023 to 23.1023; area 23 nodes are reachable through it, but 23.1023 does not show up in the known nodes list of another router (31.1, openvms 7.3) in the same local network. Both 31.1 and 31.1023 are L2; and 31.1 is connected to MIM via MULTINET. 23.1023 does not show as known to MIM either. But MIM and 31.1 do know about area 23 nodes piglet, owl, rabbit etc.
How is 23.1023 going stealth?
---------
|31.1 |
|IMPVAX |---Multinet/TCP---HECnet
---------
|
|
-----------------
| Bunch of |
| Area 31 nodes |
-----------------
|
|
---------
|31.1023|
|IMPRTR |---GRE Tunnels to other areas
---------
Tunnel from 31.1023 to 23.1023:
Area Cost Hops Next Hop to Node Expires Prio
*23 4 1 Tunnel23 -> 23.1023 42 64 A+
This email is directed to owners of Cisco routers with GRE tunnels; to
the best of my limited knowledge, Dave McGuire, Ian McLaughlin, Brian
Hechinger, Mark Darvill, Cory Smelosky, Peter L?thberg ... who else?
I already have a stable GRE tunnel to A12RTR for a while now, and am
looking for end-points on other Cisco routers on HECnet to connect to. I
will be coming in from IP address 45.62.248.66, DECnet node 1.919.
If possible, please let me know what GRE end-points I can connect to.
You can, of course, DM me too.
Thank you.
Supratim
+1-240-483-8572 (cell)
--
Sent from a Compaq CQ61 running Linux Mint Tessa
-
Ain't got no cash, ain't got no style
Ain't got no gal to make you smile
Don't worry, be happy
- Bobby McFerrin
Hi,
sorry to bother you all with none net related things, but I reckoned
this was the most likely place to get an answer. Does one of you own a
VAXstation 3100 or similar? I'm looking for the external dimensions so
I can whip up a small scale replica case to house a Raspberry Pi
inside. I could go by guesswork and memory, but I'd rather do it
right.
Thanks,
Tony
--
Tony Blews
tonyblews at gmail.comhttp://www.tonyblews.co.uk/
Mob: +44(0)7832 237251 Twit: @tonyblews
Hey folks, slightly OT, but there's PDP-11 stuff in here. :) For
those of you who aren't on (blech) Facebook, here's my post of a few
minutes ago.
-Dave
-----
Hi folks! We have a great update for you today. Our fundraiser was
successful, and we've just finished executing a successful four-stop
road trip in a 26-foot rental truck.
The first stop was local; we went to the University of Pittsburgh's
CompSci building in downtown Pittsburgh. Pitt was kind enough to donate
a large volume of DEC hardware to LSSM/MACT, constituting the bulk of
their internal CompSci Department computer museum. There are several
PDP-11s, but the centerpiece is an absolutely stunning PDP-11/t55 system
with a large complement of peripherals including several RK05 and RK07
drives, two TU56+TC11 subsystems, a TU16 9-track tape drive, a Three
Rivers Computer Unibus monitor...the list goes on and on. Lots of
parts, documentation, RK05 and RK07 disk packs, etc etc. A big thanks
to Dr. Bob Hoffman and the University of Pittsburgh for this fantastic
donation! We'll have that PDP-11/t55 up and running soon. This
equipment almost completely filled the truck, so we went back to the
museum after that to unload.
Next, we hit the road with an empty truck for Minneapolis, Minnesota, to
pick up an HP-3000 series 39 system, complete with a 7978 9-track tape
drive, a 7935 disk drive, and two 7914 disk/tape subsystems. Sadly
there were no terminals, but the system is otherwise complete and in
very good condition considering its age. It was donated by the family
of Mr. Terry Stolp in his memory, and it will have a good home here.
Next, we visited the positively huge IBM facility in Rochester,
Minnesota where we picked up a model 3774 RJE terminal with a 3501 card
reader, a 3521 card punch with controller, and a 3784 line printer. We
thank IBM for this fantastic donation, and we appreciate their
dedication to the preservation of their (large) part of history.
Last but not least, we visited the amazing Steppenwolf Theatre in
Chicago, where we picked up a beautiful and very rare Singer/Friden
System Ten computer system, complete with two large disk drives, a line
printer, two terminals, and documentation. Thanks to Chad Hain of
Steppenwolf for this very unusual donation. The photo attached to this
post is the System Ten's CPU.
So now we're back and unloaded, and the truck is returned. When we are
all recovered from this rather exhausting trip, we'll take some pictures
and post them here for your viewing pleasure, over the next few days.
Thank you all for your donations, which made this pickup run possible!
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello everyone, :)
while doing some housekeeping in one of my VMS systems I just came
across the PSTHRU.EXE DECnet tool for VAX which I downloaded from some place
I could not remember anymore, maybe some freeware collection.
PSTHRU.EXE implements DECnet PMR (Poor's Man Routing), i.e. the ability to
specify a route directly in the connection string, that was especially
useful when dealing with hidden areas because it relieved both users and
system managers from the need to have accounts on any intermediate
system(s). In simpler words it allows for things like the following:
$ SET HOST GATEWY::OTHRGW::HIDDEN::
With the exception of FAL and MAIL, whenever DECnet finds that a connection
string to some remote network object contains a list of nodes rather than
just one, it redirects that connection request to object 123 on the leftmost
node of the list. There, PSTHRU forwards the connection to the next node on
the list (either to object 123 or to the actual intended object, depending
on how many nodes are left to be passed through), and so on until the source
could be connected to its intended target. For different reasons both FAL
and MAIL have their own way of doing PMR and thus do not require PSTHRU or
anything similar for it to work.
Now the question is: does anyone have the source of PSTHRU.EXE (does it
exist at all?) and/or does anyone have an Alpha version of that image?
Also, by looking at a dump of PSTHRU.EXE it appears that it contains some
reference to some PSTHRU.DAT, so another question is: does anyone know how
to use it? I suspect that it could be a file where complex paths could be
listed so that one wouldn't have to remember all of them...
Thanks!
G.
Anyone using DECnet Phase-V on VAX/VMS V7.3 in the HECnet community?
I am rebuilding SGC::. It is MUCH bigger and faster so I may go the Phase-V route if it has any real value. Comments?
Thanks!
-Steve
