On 23 Dec 2012, at 20:22, Dave McGuire <mcguire at neurotica.com> wrote:
So you're running an internal nameserver (bravo!) and your inverse
zone is hosed somehow?
Pretty much, yeah. But it resolves the names to IPs correctly, so I'm happy with the current (temporary) setup.
I'll fix the reverse later.
Sampsa
On 12/23/2012 01:19 PM, sampsa at mac.com wrote:
Weirdly enough, it tries to do a reverse lookup on the name server
when invoking NSLOOKUP.
Nslookup has done this forever.
Steve D's MWATCH (MULTINET Tunnel updater) uses NSLOOKUP to figure
out the new IP address for the tunnel.
As I don't need the internal name server on GORVAX, I just set the
name server to 8.8.8.8 and everything works.
So you're running an internal nameserver (bravo!) and your inverse
zone is hosed somehow?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Weirdly enough, it tries to do a reverse lookup on the name server when invoking NSLOOKUP.
Steve D's MWATCH (MULTINET Tunnel updater) uses NSLOOKUP to figure out the new IP address for the tunnel.
As I don't need the internal name server on GORVAX, I just set the name server to 8.8.8.8 and everything works.
Sampsa
On 23 Dec 2012, at 20:17, Dave McGuire <mcguire at neurotica.com> wrote:
On 12/23/2012 11:20 AM, sampsa at mac.com wrote:
Any Bind gurus out here?
Can you contact me off list, having problem with reverse zones...
I can help you with BIND, but I don't see how Multinet could be borked
due to a borked BIND config.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 12/23/2012 11:20 AM, sampsa at mac.com wrote:
Any Bind gurus out here?
Can you contact me off list, having problem with reverse zones...
I can help you with BIND, but I don't see how Multinet could be borked
due to a borked BIND config.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 23 Dec 2012, at 13:14, "Rob Jarratt" <robert.jarratt at ntlworld.com> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Paul_Koning at Dell.com
Sent: 23 December 2012 17:08
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] SIMH PDP-10 + Networking?
On Dec 23, 2012, at 12:37 AM, John Wilson wrote:
From: <Paul_Koning at Dell.com>
FWIW, DMC and DMR are the same at the programmer level.
(Except for some trivial differences.) My notes say the limit on
outstanding TX or RX buffers is 7 for DMC vs. 64 for DMR. Also, BSEL3
is a read/write reg that survives master clears on DMC but gives diag
completion status on DMR (which is how INIT.SYS tells them apart).
And opcode 02 is HALTR on DMR and reserved on DMC. Is there other
stuff?
I didn't know of those details, or other differences that matter to a
driver.
The way I've seen it done is that a DMC driver (7 buffers max) works fine
for
DMR, and there wasn't any real reason to do DMR-specific things.
Indeed, I have seen the source for a VMS driver that works for both DMC and
DMR, there appear to be some tiny differences in there that I don't recall,
but they are similar enough to use the same driver.
So, my question still stands: If I add DMC11 to the SIMH KS10 emulation, is
there anyone who can help me with getting TOPS-10 to work with it, or if you
know how to get TOPS-20 V4.1 to work with it that would be even better.
I can't help with writing drivers, but i'd be willing to help with testing. I think the documentation covers this configuration of DMC links. I'm not the best with TOPS-10 or TOPS-20, but i'm learning.
They are somewhat different at the protocol level -- DMC uses an
older version of DDCMP and has some bugs in that implementation,
especially in the "high speed" (1 Mb/s) version.
Buggy WRT dealing with correct implementations, or buggy even talking
to each other? Just curious (I have a pair of them around here
somewhere).
Buggy in the sense of not being 100% compliant to the DDCMP spec as
written. They talk fine to each other. If you want to have another DDCMP
implementation talk to them, you have to be aware of those details. I
don't
remember them but can find them if needed -- they would be in the NODVR
(software DDCMP) RSTS/E driver sources.
paul
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Paul_Koning at Dell.com
Sent: 23 December 2012 17:08
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] SIMH PDP-10 + Networking?
On Dec 23, 2012, at 12:37 AM, John Wilson wrote:
From: <Paul_Koning at Dell.com>
FWIW, DMC and DMR are the same at the programmer level.
(Except for some trivial differences.) My notes say the limit on
outstanding TX or RX buffers is 7 for DMC vs. 64 for DMR. Also, BSEL3
is a read/write reg that survives master clears on DMC but gives diag
completion status on DMR (which is how INIT.SYS tells them apart).
And opcode 02 is HALTR on DMR and reserved on DMC. Is there other
stuff?
I didn't know of those details, or other differences that matter to a
driver.
The way I've seen it done is that a DMC driver (7 buffers max) works fine
for
DMR, and there wasn't any real reason to do DMR-specific things.
Indeed, I have seen the source for a VMS driver that works for both DMC and
DMR, there appear to be some tiny differences in there that I don't recall,
but they are similar enough to use the same driver.
So, my question still stands: If I add DMC11 to the SIMH KS10 emulation, is
there anyone who can help me with getting TOPS-10 to work with it, or if you
know how to get TOPS-20 V4.1 to work with it that would be even better.
They are somewhat different at the protocol level -- DMC uses an
older version of DDCMP and has some bugs in that implementation,
especially in the "high speed" (1 Mb/s) version.
Buggy WRT dealing with correct implementations, or buggy even talking
to each other? Just curious (I have a pair of them around here
somewhere).
Buggy in the sense of not being 100% compliant to the DDCMP spec as
written. They talk fine to each other. If you want to have another DDCMP
implementation talk to them, you have to be aware of those details. I
don't
remember them but can find them if needed -- they would be in the NODVR
(software DDCMP) RSTS/E driver sources.
paul
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Cory Smelosky
Sent: 23 December 2012 17:38
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] SIMH PDP-10 + Networking?
On 23 Dec 2012, at 05:29, Jordi Guillaumes i Pons
<jg at jordi.guillaumes.name> wrote:
Al 22/12/12 18:23, En/na Cory Smelosky ha escrit:
Is it at all possible to do networking in SIMH's PDP-10 emulator?
No. SIMH emulates a KS10, and IIRC there was no DPNI support for that
machine (there was another network interface which worked for ITS, but not
for TOPS-10, and anyway it is not emulated in SIMH).
I wonder if simh will ever add support for emulating a KL10.
I would love to see this too. However, I believe this is a non-trivial
undertaking. It is one that I have in the back of my mind, but no plans to
start anything any time soon
Turns out I need to reinstall TOPS-10. ;)
So I either need to:
1). Stage TOPS-10 in SIMH then move to KLH10's KS emulator (seems to
uses different disk format) 2). Install TOPS-10 directly in klh10
(How would I change tapes during runtime using KLH10?) 3). Not have
networking. ;)
There is a built KL TOPS-10 image with network support at
http://klh10.trailing-edge.com/twonky-a11120.tar. Its not so fun as
building
it yourself, but it works. Of course you can do it yourself. And to swich
tapes
you go to KLH10>> prompt (the default key is CTRL-\) and issue a "devmount
mta0 tape_image_file.tap and then a continue command, very similar to
simh.
BTW you will need to do a MONGEN to set your DECNET address :).
Doing a MONGEN is proving a little challenging. However! I've learned my
way around a bit more to the point I can extract the monitor sources. I
just
kept hitting a little roadblock due to not having SETSRC. :)
I /think/ i can work around that by extracting the sources to DSKA and
then
using PATH (what's the appropriate way to use PATH? the monitor
generation documentation only mentions SETSRC)
Is configuring networking in KLH10's KS emulation the same as using
it's
KL emulation? devdef nib et cetera?
AFAIK the syntax of the config file varies a little bit since the KS has
a
different addressing method.
On 23 Dec 2012, at 12:37, Cory Smelosky <b4 at gewt.net> wrote:
On 23 Dec 2012, at 05:29, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
Al 22/12/12 18:23, En/na Cory Smelosky ha escrit:
Is it at all possible to do networking in SIMH's PDP-10 emulator?
No. SIMH emulates a KS10, and IIRC there was no DPNI support for that machine (there was another network interface which worked for ITS, but not for TOPS-10, and anyway it is not emulated in SIMH).
I wonder if simh will ever add support for emulating a KL10.
Turns out I need to reinstall TOPS-10. ;)
So I either need to:
1). Stage TOPS-10 in SIMH then move to KLH10's KS emulator (seems to uses different disk format)
2). Install TOPS-10 directly in klh10 (How would I change tapes during runtime using KLH10?)
3). Not have networking. ;)
There is a built KL TOPS-10 image with network support at http://klh10.trailing-edge.com/twonky-a11120.tar. Its not so fun as building it yourself, but it works. Of course you can do it yourself. And to swich tapes you go to KLH10>> prompt (the default key is CTRL-\) and issue a "devmount mta0 tape_image_file.tap and then a continue command, very similar to simh.
BTW you will need to do a MONGEN to set your DECNET address :).
Doing a MONGEN is proving a little challenging. However! I've learned my way around a bit more to the point I can extract the monitor sources. I just kept hitting a little roadblock due to not having SETSRC. :)
I /think/ i can work around that by extracting the sources to DSKA and then using PATH (what's the appropriate way to use PATH? the monitor generation documentation only mentions SETSRC)
PATH is self-explanatory, never mind. ;)
However: i'm hitting some issues:
?MCRCFU CANNOT FIND UNIVERSAL MACSYM
and
? Wrong version of MONGEN was used in SYS dialog
MACRO: COMDEV
?MCRCFU CANNOT FIND UNIVERSAL D36PAR
How can I have the wrong version of MONGEN?...
Is configuring networking in KLH10's KS emulation the same as using it's KL emulation? devdef nib et cetera?
AFAIK the syntax of the config file varies a little bit since the KS has a different addressing method.
On 23 Dec 2012, at 05:29, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
Al 22/12/12 18:23, En/na Cory Smelosky ha escrit:
Is it at all possible to do networking in SIMH's PDP-10 emulator?
No. SIMH emulates a KS10, and IIRC there was no DPNI support for that machine (there was another network interface which worked for ITS, but not for TOPS-10, and anyway it is not emulated in SIMH).
I wonder if simh will ever add support for emulating a KL10.
Turns out I need to reinstall TOPS-10. ;)
So I either need to:
1). Stage TOPS-10 in SIMH then move to KLH10's KS emulator (seems to uses different disk format)
2). Install TOPS-10 directly in klh10 (How would I change tapes during runtime using KLH10?)
3). Not have networking. ;)
There is a built KL TOPS-10 image with network support at http://klh10.trailing-edge.com/twonky-a11120.tar. Its not so fun as building it yourself, but it works. Of course you can do it yourself. And to swich tapes you go to KLH10>> prompt (the default key is CTRL-\) and issue a "devmount mta0 tape_image_file.tap and then a continue command, very similar to simh.
BTW you will need to do a MONGEN to set your DECNET address :).
Doing a MONGEN is proving a little challenging. However! I've learned my way around a bit more to the point I can extract the monitor sources. I just kept hitting a little roadblock due to not having SETSRC. :)
I /think/ i can work around that by extracting the sources to DSKA and then using PATH (what's the appropriate way to use PATH? the monitor generation documentation only mentions SETSRC)
Is configuring networking in KLH10's KS emulation the same as using it's KL emulation? devdef nib et cetera?
AFAIK the syntax of the config file varies a little bit since the KS has a different addressing method.
On Dec 23, 2012, at 12:37 AM, John Wilson wrote:
From: <Paul_Koning at Dell.com>
FWIW, DMC and DMR are the same at the programmer level.
(Except for some trivial differences.) My notes say the limit on outstanding
TX or RX buffers is 7 for DMC vs. 64 for DMR. Also, BSEL3 is a read/write
reg that survives master clears on DMC but gives diag completion status on
DMR (which is how INIT.SYS tells them apart). And opcode 02 is HALTR on
DMR and reserved on DMC. Is there other stuff?
I didn't know of those details, or other differences that matter to a driver. The way I've seen it done is that a DMC driver (7 buffers max) works fine for DMR, and there wasn't any real reason to do DMR-specific things.
They are somewhat different at the protocol level -- DMC uses an older
version of DDCMP and has some bugs in that implementation, especially in
the "high speed" (1 Mb/s) version.
Buggy WRT dealing with correct implementations, or buggy even talking to
each other? Just curious (I have a pair of them around here somewhere).
Buggy in the sense of not being 100% compliant to the DDCMP spec as written. They talk fine to each other. If you want to have another DDCMP implementation talk to them, you have to be aware of those details. I don't remember them but can find them if needed -- they would be in the NODVR (software DDCMP) RSTS/E driver sources.
paul
