Hey Johnny, is the DECUS RSX library up on MIM:: somewhere?
Or does anyone else have it up and accessible via hecnet?
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hi,
Any recommendations on a CISCO switch simulator that runs on Linux
(Ubuntu 17.10) and supports GRE tunneling to a real CISCO switch over
the internet?
TIA
Supratim
Mark Abene <phiber at phiber.com> wrote:
> I'm posting this here in the hopes that there are other KLH10 emulator
> users on HECnet.
There are, I am one of them.
> I've been using KLH10 with the tap patches for years and years, and idling
> has always worked fine. At some point over the recent couple of years,
> idling stopped working for me on linux (I run ubuntu 16.04.4 LTS with
> latest updates as of yesterday, on a 64-bit intel machine). My CPU is stuck
> at 100% utilization, without even starting an emulated OS (I run TOPS-20).
> In fact, as soon as I type "GO" in KLH10 and before doing anything else,
> the CPU immediately shoots to 100%. Is anyone else seeing this? In older
> versions of ubuntu/linux this didn't happen.
Handful of points:
* the idling is done by modifying the idle loop in the guest operating
system to interact with the KLH10 idler device, not by identifying
the idle loop like SIMH does.
* until the OS is up and running, there is no idling. In other words,
while at the BOOT> prompt there will be a loop consuming 100% CPU
waiting for terminal input. This is normal, and it has always been
that way.
* if you have had the same TOPS20 system running, with idling, earlier
everything points at your host os (ubuntu) no longer cooperating with
KLH10. I myself run (mostly) FreeBSD, and I have never had problems
with idling the TOPSxx systems.
* for TOPS10, there are a couple of more things to consider, one of them
is that the idler device by default is at device code 700, which can't
be accessed from the mode the -10 idle code runs in. Using 740 works.
I would look for what has changed in your host os (ubuntu) regarding
system timers and such. Your setup *should* work.
> Thanks,
> Mark
--Johnny
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
This release contains a lot of fixes and improvements in many areas.
There are a couple of very serious bugs in TCP that is fixed in this
release which is why I really encourage people to upgrade. (They do not
happen often, but if they happen, they have a high chance of crashing
the system.)
Highlights:
- Stability and reliability improvements in TCP.
- Improved HTTPD
- Improved MAILD
Magica.Update.UU.SE, which is a real PDP-11/70, have now run with the
latest release for over 3 weeks without any issues, so I think it's safe
to say that this product is now very stable. Mim.Update.UU.SE (an
emulated 11/74) have in the same time served over 7Gb of data over FTP,
HTTP and other lower volume channels. (And both of these machines are
more or less fully exposed to the internet, so they see a *lot* of
connections and random attempts to compromise them all the time.)
Detailed information on things that have been done since the last release:
TCP:
- Improved handling of received TCP push packets.
- Improved TCP ACK handling under lost packet recovery.
- Improved TCP window update handling.
- Bugfix for the condition that a socket was closed while there was
outstanding sends and the remaining window was 0 and the transmission
was not ACKed. This would cause the socket to get stuck in a pending state.
- Improved TCP write handling. The second IOSB word was previously not
set to reflect how much data was written.
- Added new TCP option for sockets to optionally return available data
at read if push was set.
- Bugfix in TCP. An internal data structure was sometimes modified when
it should not be, which could cause a system crash under rare circumstances.
HTTPD:
- Improved error handling for CGI pages.
- Improved subprocess handling for CGI module.
MAILD:
- Improved MAILD to handle broken Linux MAIL11 server.
- Improved MAILD error handling.
- Bugfix in MAIL. When composing mails, the temporary file is now
created under SYS$LOGIN.
- Added timeouts for various parts of MAIL11 processing.
Libraries:
- Improved subprocess handling in BASIC+2 library.
- Updated F77 library and documentation.
Multinet:
- Improved performance.
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
The firewall for Mim have now been removed, so no need for the alternate
ports, but Mim is still listening to the alternate ports as well.
ftp: 10021
telnet: 10023
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
I'm posting this here in the hopes that there are other KLH10 emulator
users on HECnet.
I've been using KLH10 with the tap patches for years and years, and idling
has always worked fine. At some point over the recent couple of years,
idling stopped working for me on linux (I run ubuntu 16.04.4 LTS with
latest updates as of yesterday, on a 64-bit intel machine). My CPU is stuck
at 100% utilization, without even starting an emulated OS (I run TOPS-20).
In fact, as soon as I type "GO" in KLH10 and before doing anything else,
the CPU immediately shoots to 100%. Is anyone else seeing this? In older
versions of ubuntu/linux this didn't happen.
Thanks,
Mark
Hi,
I?m running the bridge with the following bridge.conf:
?? SNIP ---
local eth0
update psilo.update.uu.se:4711
hilanet 84.231.64.229:4711
maguro 38.130.230.105:4711
[decnet]
local
update
hilanet
maguro
[lat]
local
update
hilanet
maguro
? SNIP ?
But when I run the bridge using ?./bridge 4711? I keep getting these weird errors:
Dumped packet from 38.130.230.105 (1024).
Any ideas?
Sampsa
Yes I am interested in that. Let me know when done. Also you can send
scanned docs to bitsavers.
I put each package funetnje and hujinje into git together and uploaded it
into my github account.
For decent for Linux, I converted CVS repo into git repo and uploaded it
into my github too. So you can now apply fixes to that repo.
If you find JNet 2.x software, please let me know. There is programming
guide doc in JNet package through 3.2. It was removed on 3.3 or above. No
they are not in funet and can?t find them through google so far.
Does anyone have JNet for Alpha? I have only JNet 3.5 to 3.7 for VAX.
Tim
On Sat, Feb 17, 2018 at 3:39 AM Erik Olofsen <e.olofsen at xs4all.nl> wrote:
> Tim,
>
> I have the JNet Network Manager's and User's guides, no programming guide,
> for version 2.0$
>
> Let me know if I can look up something for you.
>
> Actually I don't have the software - so you found it at funet?
>
> Erik
>
>
I come from a mostly-UNIX, mostly-TCP/IP background. I don't understand DECnet well yet, but I want to learn more! Much of my interest in joining HECnet and playing around is because I largely skipped over DECnet in its original airing, and now it seems like a weird foreign land that I feel an irrational need to grok in fullness.
What are/were the conventions for providing public services over DECnet Phase IV networks, to remote users without their own local user accounts? I.e., let's say that I had a node on a large DECnet-only network back in the before time, and I wanted to share a file repository in a manner comparable to anonymous FTP on a TCP/IP network. How would I have done that? Were there conventions for doing that sort of thing back then, or was that a foreign concept on large DECnet networks at the time?
Were there any examples of BBS-like servers living on DECnet networks? Online multi-player games such as MUDs? Early DECnet-based examples of "log into the coffee pot to see if the brew is fresh"? DECnet-based analogs to Archie for discovering stuff? DECnet-based USENET-like communities?
I don't know if any of these concepts even made sense in the DECnet world at the time. In addition to only understanding the networks of the 80s from a UNIX-centric, TCP/IP-centric worldview, I'm also having a hard time un-thinking the newer concepts I'm used to after so many years of steeping in a broth of HTTP and social media. I have somewhat conflicting urges to both learn how to think like a 1980s DECnet user, and to retcon modern concepts into an alternate reality where TCP/IP never took off.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
http://www.nf6x.net/
For those interested in running the updated DECnet kernel module
under Ubuntu rather than Slackware, I gave it a go by updating my
machine running 16.04 following the steps at:
>From https://www.maketecheasier.com/build-custom-kernel-ubuntu/
And it was quite easy indeed. [But have plenty of free disk
space, say >20 GB. If the make fails, and you have to start over,
it does a 'clean' first. So even when doing make...]
Of course, after the step to have the kernel source ready,
for example in 'kernelbuild', cd to 'kernelbuild/net' and unzip
the dflkm.zip file, which may be found at RULLFS::
One of my nodes fell off Hecnet (actually a while ago).
I finally got around to reboot it in order to get it back.
The problem? Too much uptime.
Monitor Atle - DEC-10 at work
System uptime 10483:52:41
Current date/time Thursday 8-Feb-2018 8:00:14
Thats what you get for running stable hardware. On the other hand,
this is/was a known problem:
MCO: 12935 Name: WXD Date: 22-May-86:14:12:35
[Symptom]
DECnet stops working correctly. The -10 sees all the nodes
on the ethernet, but isn't seen by any of the nodes.
[Diagnosis]
The -10 has stopped sending ethernet hello messages. This
is caused by the -10 getting an overflow when calculating the DECnet
time (milliseconds of uptime), which is then used to determine when
to send the next message. The algorithm is:
MOVE T1,SYSUPT
IMULI T1,1000.
IDIVI T1,JIFSEC
This overflows at 159 hours, 4 minutes, 22 seconds, and 19. ticks (60hz).
[Cure]
Change IMULI -> MULI, and IDIVI -> DIVI
This algorithm won't overflow until 9544 hours of uptime (395+ days).
--Johnny (the other one)
/\_/\
( *.* )
> ^ <