We could definitely make use of that! Can you spare it?
-Dave
On 9/2/23 06:38, Peter Lothberg wrote:
> Dave,
>
> Maybe you need a KS10 repair tool?
>
>
> -P
> ----- Original Message -----
> > From: "Dave McGuire" <mcguire(a)neurotica.com>
> > To: "The Hobbyist DECnet mailing list" <hecnet(a)lists.dfupdate.se>
> > Sent: Monday, August 21, 2023 6:09:58 PM
> > Subject: [HECnet] Re: pssst...
>
> > Hahaaaa, thank you Fred! You really need to come back for a visit,
> > it has been a while. The guys and I have been very busy; we have a lot
> > more hardware up and running now.
> >
> > -Dave
> >
> > --
> > Dave McGuire, AK4HZ
> > New Kensington, PA
> >
> > _______________________________________________
> > HECnet mailing list -- hecnet(a)lists.dfupdate.se
> > To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
>
> _______________________________________________
> HECnet mailing list -- hecnet(a)lists.dfupdate.se
> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
--
Dave McGuire, AK4HZ
New Kensington, PA
So Mark (Matlock) has been after me to get my HECnet connection up and running and me, being an ace procrastinator, has always said "Real Soon Now™", Mark.
I might actually have time to do it as I'm on vacation for a week and a half. Despite the heat I could set something up. My question is how do I set it up. I have a Mac Mini in Las Vegas running VMWare ESXi. I have a VM (Aniketos) running Vyos for a firewall/router, another VM with an Nginx web server (Hermes - irrelevant just mentioned for completeness) and a really small (1 vCPU) Linux VM (Knight) which I want to run Paul's PyDECnet router for the world to connect to. From there I have an IPSec VPN to my Ubiquiti EdgeRouter 4 at home. How can I connect DECnet through the VPN to Knight from home? Is it even possible? Do I need or want GRE tunnels through the VPN?
Am I just making it too complicated and should I set up a PyDECnet router at home and go that way through my dynamic IP? It's possible I could set up an x86 OpenVMS machine as another VM
I'm thinking I need a PyDECnet router at home to collect all the DECnet traffic and shove it through the VPN to the PyDECnet router at the remote site and from there out into the internet to it's HECnet connection points. Does that make sense?
I tried drawing an ASCII picture but apparently I suck at that. Hopefully the description makes sense.
Hoping to get people's thoughts and if you're experienced in designing PyDECnet config files, any pointers are welcome.
--
John H. Reinhardt
I'm moving in a few days and am trying to understand what to do about
connectivity without drowning (in advertising or whining).
I currently have FIOS and had ordered it so that I had a separate
Optical Network Terminal (ONT) and router. I plugged my own router into
the ONT and the FIOS router into my router and all has been well.
The Internet provider at the new location is Optimum Online which
previously had been a lot easier to deal with than FIOS as you could
just plug into the cable modem or get your own. Naturally, I was
provided with a combo ONT/Wireless/Router solution that just isn't going
to cut it. I'm trying to search for an ONT, but am getting deluged with
the usual stream of noise, junk and advertising. For example, I'm
getting Optical-Ethernet converters, which I don't think are what I want.
Can anybody point me at a few ONT-only solutions that don't come with
all the extra garbage, don't do NAT, Etc.? Or some kind of good
introductory information without all the blinking ads?
TOMMYT:: [2.520] and VENTI2:: [2.522] will be offline for a few days
towards the end of the week.
The problem with the OO gear is that there is no bridge mode and that I
will be double nat'ed, which makes a number of things hard.
A business connection has been out of the question for some time; it's
really bring your wallet...
The OO website says you can get your own 'modem', but it isn't specific
about an ONT. I use DynDNS, so a static IP isn't really necessary (but
always nice).
On 7/19/23 1:29 PM, system(a)rsx11m.io wrote:
> I don't know that you can bring your own ONT with consumer grade
> internet, at least my understanding has always been that it can't be
> done. I'm not an Optimum customer but I would imagine there is some
> way to disable the routing portion of things and just run an ethernet
> cable from the ONT to your own gear, similar to FIOS. Otherwise, if
> money isn't a huge issue, you might consider a business connection,
> those are generally more lax and you might even get a static IP for
> your troubles.
> On Jul 19, 2023 at 12:47 PM -0400, Thomas DeBellis
> <tommytimesharing(a)gmail.com>, wrote:
>>
>> I'm moving in a few days and am trying to understand what to do about
>> connectivity without drowning (in advertising or whining).
>>
>> I currently have FIOS and had ordered it so that I had a separate
>> Optical Network Terminal (ONT) and router. I plugged my own router
>> into the ONT and the FIOS router into my router and all has been well.
>>
>> The Internet provider at the new location is Optimum Online which
>> previously had been a lot easier to deal with than FIOS as you could
>> just plug into the cable modem or get your own. Naturally, I was
>> provided with a combo ONT/Wireless/Router solution that just isn't
>> going to cut it. I'm trying to search for an ONT, but am getting
>> deluged with the usual stream of noise, junk and advertising. For
>> example, I'm getting Optical-Ethernet converters, which I don't think
>> are what I want.
>>
>> Can anybody point me at a few ONT-only solutions that don't come with
>> all the extra garbage, don't do NAT, Etc.? Or some kind of good
>> introductory information without all the blinking ads?
>>
>> TOMMYT:: [2.520] and VENTI2:: [2.522] will be offline for a few days
>> towards the end of the week.
>>
>>
>> _______________________________________________
>> HECnet mailing list -- hecnet(a)lists.dfupdate.se
>> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
Area 19 is offline while changes are being made to the network. Additionally, the IP address will change. The new IP address for bridge and pyDECnet connections will be bridge.declab.net when it returns.
Thanks!
-Steve Davidson
STRGTE::SYSTEM
SF:iP1
Where are all of these spelled out? I had looked in the Phase IV NSP
functional specification (NSP401.TXT) for them, but only a few seem to
be there.
The background is that I have further enhanced Kermit-20 to use direct
monitor connections when doing remote terminals and also to print the
text of a disconnect. I duly copied over the list in MONSYM, Etc.,
Etc., Etc. Earlier this week, I put some more contingency code into FAL
to handle server crashes. Basically, the controller would sit in a loop
forever restarting crashed server (DAP) forks. Now it waits a while and
stops completely after a certain number of restarts.
While I was at it, I checked its list and found that it was missing text
for disconnect codes 10, 11, 21, 22 and 23. Well, I put it in but got
to wondering what others there might be. Right now Tops-20 Kermit and
DAP know about the following:
*Code*
*Reason Text*
0
Reject or disconnect by object
1
Resource allocation failure
2
Destination node does not exist
3
Remote node shutting down
4
Destination process does not exist
5
Invalid process name field
6
Object is busy
7
Unspecified error
8
Third party abort)
9
User abort (asynchronous disconnect)
/10/
/Invalid node name/
/11/
/Local node shut down/
/21/
/Connect Initiate with illegal destination address/
/22/
/Connect confirm with illegal destination address/
/23/
/Connect initiate or confirm with zero source address/
24
Flow control violation
32
Too many connections to node
33
Too many connections to destination process
34
Access not permitted
35
Logical link services mismatch
36
Invalid account
37
Segment size too small
38
No response from destination process
39
No path to destination node
40
Link aborted due to data loss
41
Destination process does not exist
42
Confirmation of Disconnect Initiate
43
Image data field too long
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
This is version 2.13 of BQTCP/IP.
It's been almost three months since the last official update. Some major
improvements and bugfixes have been done, and it is strongly recommended
that systems are updated.
Highlights:
. Improved TCP performance.
. XLISP updated to V1.7.
. New patch to the TT: driver in order to make telnetd fully vectorized.
Detailed information on things that have been done since the last release:
TCP:
. Added TCP fast retransmit feature.
. Bugfix in TCP. If IO.RAS is used to setup an AST notification, an AST
should immediately be generated if we have received a FIN.
. Improved TCP retransmit timer calculation. It was wrong on socket
creation. Also added handling of delayed transmit time set to 0.
TELNETD:
. Improved internal time handling in telnetd.
. Added full vectorization for TELNETD (if kernel supports it, otherwise
no change from before).
. Added more checks for errors on snd/rcv for telnetd.
RMD:
. Bugfix in RMD. In port page, if xmit or rcv size was greater than
32767, RMD crashed.
NTPD:
. Changed NTPDATE to use time adjustment functionality in kernel, if it
exists.
MAILD:
. Improved MAILD SMTP send error handling.
. Improved mail queue processing to not retry mails extra times just
because an error notification mail is created for something.
. Changed mail daemon to only send notification mails about temporary
delivery problems when the mail have been in the queue for at least 30
minutes.
LISP:
. Updated XLISP to V1.7.
BQTLIB:
. Added lots of documentaiton for BQTLIB. Cleaned up BQTLIB.
. Added functions in BQTLIB for adjusting time.
Some additional notes:
As usual, I would recommend people to update as soon as possible.
The changes are not critical, but will lead to a much better experience.
The patches to the TT: driver cannot be applied automatically, but
requires users to apply the patches themselves, and then run SYSGEN to
generate a new system.
Once added, the TNC2 task can be run at login, and will define logical
names for the user telling where he is connected from, if using telnet
or LAT.
The TT: driver patches also allows the updated MCR to give more
information with the DEV command (SHOW TERMINAL in DCL).
The patched TT: driver also makes is possible to get telnetd fully
vectorized, as this version provides two more addresses that are
required by telnetd to access information in the kernel.
The other patches to RSX can be applied automatically by IPGEN, either
if used interactively when answering YES to the question about applying
RSX patches, or by running IPGEN explicitly to do the patches, with the
command:
@IPGEN PATCH
Specific information about the patches:
LAT: Fixes a memory leak, and adds the ability to read where a terminal
connection comes from when using LAT, using SF.GMC.
RMSDAP: Fixes a bug in getting the file protection, so the XAB gets
filled in correctly for remote files.
RMSDSP: Fixes that some numbers were displayed in signed octal, which
should have been displayed in decimal or unsigned octal, depending on
number.
DCL: Added terminal attributes for COLOR.
MCR: Too many fixes to be listed here...
INS: Fixes that users cannot circumvent protection on common regions.
HEL: Fix that users can login with session ID, or with directory, in
addition to name and UIC.
ACNT: Add no password change attribute to accounts.
PSW: Add no password change handling.
SYL (SYSLOG): Add terminal idle tracking on accounts without idle logout.
ECL: If the receiving machine is very slow, and the sending machine is
very fast, and the receiver announce several large buffers available,
ECL cannot keep up, and drops packets. This is a problem with the DECnet
flow control, as it is used in RSX. The simple solution is to allow more
outstanding buffers when receiving. A more complex solution would be to
change how RSX DECnet do flow control, but that would require rewriting
a fair chunk of the ECL module.
NMVACP: Fix handling of "show known nodes" command, which could skip
some nodes.
NVP: Add ability to use session ID or directory name for user identity
in DECnet nodename specifications.
EPM: Fix handling of ethernet multicast.
NTDEMO: Fix that hosts without names should display DECnet address.
NCP: Parse of additional information types in NICE messages.
As usual, the distribution is available from:
ftp://mim.stupi.net/bqtcp.dskftp://mim.stupi.net/bqtcp.tap
!!! BQTCP is also available through RPM !!!
(As an additional note, if there are any problems communicating with Mim
using port 21, the ftp service is also available at port 10021)
The documentation is also available through ftp on Mim, or also at
http://mim.stupi.net/tcpipdoc
I hope people find this update useful.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Greetings all,
I'm performing a firewall replacement along with all kinds of other comms related tasks at my office today.
This means Area 35 will be up and down and possibly out for a few hours.
I'll be starting in the next 2 hours or so. All the work will be finished this afternoon.
Cheers, Wiz!!
Since there has been a bunch of work done to revive what is supposedly a DECnet Phase I implementation (DECnet/8 for RTS/8) I realized I could perhaps get some more information going back that far. Some months ago Nathan Brookwood (formerly known as Nathan Teichholz) gave a talk about the beginning of RSTS-11, and in that he mentioned as an aside that he subsequently served as program manager for the initial development of DECnet.
So I asked him if DECnet/8 sounded familiar and if he could tell me anything further about that time. His reply:
----------
I was responsible for coordinating all the versions of DECnet for the initial "Phase I" releases, but developers in each operating system were responsible for the implementations. Each group was building from the definitions of DDCMP and NSP that were extant in the 1973-75 period. There was also a testing and communications protocol called "NICE" (don't ask me what that stood for) and a file transfer utility.
The Phase I versions did not include routing, and when the developers tried to add routing capabilities to those first versions, they discovered that there was a need to make significant changes to NSP that would preclude backwards compatibility with the Phase I versions. The implementation of DDCMP survived intact, since physical link protocols are below the routing protocols level.
----------
That ties into the statement in the Phase III General Description document which says that Phase I nodes can't coexist with later versions in the same network, and it also matches what the DECnet/8 manual makes quite clear in its chapter discussing the protocol details: Phase I NSP is conceptually pretty similar to Phase II NSP, but the packets are 100% incompatible. So the "significant changes" Nathan mentioned are what happened in DECnet Phase II -- which modifies NSP to include sequence numbers and ACKs and in the process also changes lots of other details in the protocol encoding. That still wasn't quite enough, and Phase III filled in some missing details in an upward compatible fashion (the Connect Ack and Retransmitted Connect Initiate message, as well as timeout and retransmit algorithms).
paul
