Hi,
Is anyone else running a HECnet connection using Johnny's bridge and a
BT Infinity line? I don't seem to be able to get any traffic to flow to
Johnny.
Anyone else hosting a bridge that would be willing to add me and see if
we can figure out what's what?
--
Mark @ DECtec.info
twitter.com/DECtecInfo
SG1:: will be offline tomorrow while the WAN circuit is being upgraded to fibre. The static IP address may change as well. If it does I will send another email.
Tomorrow's upgrade will be to 50Mb/20Mb with 100Mb/40Mb possible in the near future. Not bad for a rural area!
-Steve
Sent from my iPhone
I'm happy to announce a new release of TCP/IP for RSX-11M-PLUS.
Since I'm broadening the scope of the announcement slightly, a more
complete list of features is included, and not just what changed since
last. For anyone who is currently running TCP/IP for RSX, I strongly
encourage you to update to this latest version. Several improvements
have gone in in the last couple of weeks. Most important change is that
there now is telnet support, both client and server side.
The TCP/IP for RSX that I've written is sometimes referred to as
BQTCP/IP, just to make clear that it is a different product than Process
Software's TCPWARE, or JSA's TCP/IP.
BQTCP/IP is a rather feature rich TCP/IP implementation, which also
comes with libraries for various high level languages. The API is not
compatible, even at the source level, with Unix, but on the other hand,
if people write some code, they will see that it is a very easy API to
work with. The reasons for the incompatibilities are several, including
both resource concerns and differences between how RSX works and Unix
like operating systems.
BQTCP/IP has tried to comply with all relevant RFCs, but I'm sure there
are corners where it does not do things right. It also does not demand
much resources. It do require RSX-11M-PLUS with split I/D space, and it
has only been tested properly on RSX-11M-PLUS V4.6. It should work on
any version 4 release of RSX-11M-PLUS, but there might be a couple of
tweaks or fixes needed.
BQTCP/IP is distributed in binary form, so very little compilation is
required to get it up and running. However, pretty much all utilities do
come with sources. The actual TCP/IP stack sources are not included. I
do not have a good setup for distributing them in a sane way, and it has
had a low priority on my list of things to do. But I do not mind
distributing the sources as a general principle.
All that said, BQTCP/IP current supports the following protocols:
o Ethernet and loopback interfaces.
o ARP. BQTCP/IP can use Ethernet in co-existance with DECnet, or
standalone using the provided Unibus ethernet device driver.
o IP. The largest IP packets supported are approximately
8KB.
o ICMP.
o UDP. The largest UDP packets supported are approximately
8KB.
o TCP. The window is approximately 8KB in size, and TCP do
manage out of order packets in an efficient way.
BQTCP/IP supports the following applications:
o DHCP. DHCP can be used to configure interface addresses, network
masks, default gateways, DNS servers and NTP servers dynamically.
o NTP. NTP can be used to set the local time.
o TELNET. The TELNET server hooks in to the standard TT: terminal
driver, and the number of terminals to create is configurable.
The TELNET client can be used to connect to other systems.
o FTP. The FTP server can serve all kind of files to other RSX
systems, and can serve text and binary files to any system.
The FTP client can retrieve RSX format files from RSX servers,
and text, binary and block format files from any system.
o TFTP. The TFTP server and client can be used for simpler file
transfer operations.
o RWHOD. RWHOD is a program that reports current users and uptime
from RSX, for other systems to collect.
o IRC. IRC is a program to communicate with other users around
the world.
o IRCBOT. IRCBOT is a small example robot program connecting to IRC
and performing a service for IRC users.
o PCL. PCL is a protocol for printing, used by HP (and other) printers
over a network. The PCL implementation in BQTCP/IP appears as a
print symbiont, which you can create a printer queue for.
o WWW. WWW (or World Wide Web) is a service that can present hypertext
information to clients. The WWW server in BQTCP/IP also supports CGI,
which makes it possible to create dynamic content.
o DNS. BQTCP/IP have DNS implemented as an ACP, that anyone can query
to get translations between IP addresses and domain names. It also
supports different users using different name servers, or private
translations.
o SINK. A standard TCP service.
o ECHO. A standard TCP service.
o DAYTIME. A standard TCP service.
o QUOTD. A standard TCP service.
o IDENTD. A standard TCP service.
BQTCP/IP also have automatic IP spoof detection and prevention.
Additional tools are IFCONFIG, PING, TRACEROUTE, NETSTAT as well as two
new pages for RMD.
High level language libraries exists for BASIC+2, PDP-11 C and FORTRAN-77.
I'm sure I have forgotten a thing or three, but that's a fairly
comprehensive list.
The documentation is a weak point, but there is hopefully enough
documentation to get people running, and I am happy to answer any
questions, or give support if needed. BQTCP/IP is already running on the
internet, and have been for a while. People who are curious to check it
out can ether look at http://madame.update.uu.se/, or telnet to
telnet://madame.update.uu.se and login as user GUEST with password
GUEST, or use ftp against ftp://madame.update.uu.se. Anonymous ftp
account exist.
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 .tap file is an RSX virtual tape. It is only possible to download
and use if you are using FTP from anther RSX system and fetch the file.
The .dsk files are virtual RL02 images that are useful both from within
RSX as well as through emulators.
The documentation is also available through ftp on Madame, or also at
http://madame.update.uu.se/tcpipdoc
Johnny
Mark Benson <md.benson at gmail.com> writes:
>
>
>On 28/08/2015 14:42, Hans Vlems wrote:
>> Yup, that's what my memory thought it was. I've learned to mistrust my =
>own memory s=E2=80=8Eubsystem somewhat....
>> Anyway, SETTIME set to 1 makes VMS behave like standalone backup: it as=
>ks for the date and (optionally) time.
>> Hans
>
>OpenVMS 7.3 appears to save the time when you shut it down and resume=20
>from that time when you boot it up. When I started mine it was still on=20
>August 2014. Like a fool I set the time correctly (and invalidated all=20
>my licenses).
>
>I just booted it up again and it thinks it's 8:49pm last night. Which is=20
>when I shut it down yesterday.
You could always edit SYS$SYSTEM:STARTUP.COM and put:
$ SET TIME="17-NOV-1858"
in it! Your PAKs will not be expired! :)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Hi,
I fired my VAXstation 4000 Model 60 up after a while dormant and it
keeps asking me for a language in the SRM prompt after the self-test.
I know it asked for it previously but I don't remember it needing it
more than once, particularly between power switch cycles.
Is there an issue here, maybe a dead battery I need to look at somewhere
or something else?
--
Mark @ DECtec.info
twitter.com/DECtecInfo
Mark Benson <md.benson at gmail.com> writes:
>
>
>On 27/08/2015 22:58, Hans Vlems wrote:
>> I didn't bother with the replacement units. It's far cheaper to write d=
>own the boot parameters
>
>In my case that's pretty easy, just Language 4 and hit the interrupt=20
>switch and boot DKA0, so it's no sweat really :)
>
>and set the Sysgen variable that forces vms to ask for the date and time.
>
>Do you have the details of that variable?
TIMEPROMPTWAIT
I believe that is is correct. If not, drill down in SYSGEN help.
$ MCR SYSGEN HELP PARAMETER TIMEPROMPTWAIT
VMS will continue to prompt you for time if the TOY is non-functional.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Well, after a long absence due to life being what life is sometimes, I'm
now in my own apartment with my own Broadband line. Alas I'm still on a
dynamic IP. I wondered if anyone had made any progress with allowing us
wandering souls to connect to HECnet.
I aim to renew my VMS Hobbyist licenses (hopefully that still works? Did
it move to VMSsoftware or is HP still doing it?) and get my VAXstation
up and running as well as a couple of RPi's running an older VAX sim
with VMS and PDP-11 sim RSX-11M Plus. I may also dabble in using Tru64
on my Alpha, if I can dig out some bigger disks for it.
Hoping I can get back into DEC as it's about the only esoteric hardware
I have left these days!
Thanks,
--
Mark @ DECtec.info
twitter.com/DECtecInfo
Gregg Levine <gregg.drwho8 at gmail.com> writes:
>Hello!
>Mark, Jordi is right, the original part number isn't made anymore,
>worse luck, but MAXIM does make a drop in replacement as he shown.
>
>They are designed to have a (approximately) five year life time, so
>when did you last use your rig? You're what, based in the UK? Farnell
>is your best bet there.
FYI, if you Google the TOY clock chip, you will find some links to hacking
the battery in the chip. However, I've found it just much easier to order
up the drop in replacement.
Happily, most Alpha and Itanium have replaceable batterys for the TOY and
NVRAM.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
A couple of years ago, there was at least one discussion wherein several of
us attempted to get working TOPS-20 systems up on HECnet. At the time, if I
recall, there seemed to be an issue with the version of DECnet available.
I eventually grabbed Panda and used it to build "joshua", but I'm curious
if anyone has a non-panda TOPS20 up on the [HEC] net.
Joe
I'm going to need to change my ISP in a month or two and a static IP is
going to add about $30-$35/month to the cost. I've decided that dDNS will
suffice for all the stuff I'm currently doing and it's not really worth it,
except maybe Multinet DECnet links to LEGATO. I also looked into using a
VPN provider to establish a static IP gateway that's automatically routed to
my server, but that costs almost as much and is much more hassle to
maintain. I'm thinking about just living without static IPs anymore.
There's about half a dozen sites currently connected to LEGATO - is
anybody going to have a problem if the IP becomes dynamic at some point? As
with most dynamic IP situations, I don't expect that the IP address will
actually change very often (maybe once every few months), but the
possibility exists that it will.
Bob
