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)
/\_/\
( *.* )
> ^ <
On a virtual machine with lubuntu 12.04, kernel 3.2.0, I have
DECnet for Linux V.2.5.68s working, with dnprogs version 2.65.
It is node RULLFL.
The daemons and utilities use decnet.conf with node information,
so something useful would be to create it from mim::nodenames.dat.
On a VAX, TYPEing it works well, but on the Linux machine, dntype
hangs after giving parts of the file; dndir mim:: works well.
Does anyone have dntype mim::nodenames.dat working properly (with
perhaps different versions of the above)?
Thanks!
