On 29 Oct 2012, at 17:03, Cory Smelosky <b4 at gewt.net> wrote:
On 29 Oct 2012, at 16:55, Marc Chametzky <marc at bluevine.net> wrote:
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
Had it bind to eth0 instead of vmbr0, the error went away and it can see an adjacent node.
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
That is now configured correctly. Seems this problem can easily be solved by just bringing up another VM, I have the RAM and DISK. ;)
Got it running in a VM but now?
https://www.refheap.com/paste/9b3f3fb3baae4d8ef23814976
Everything seems configured correctly, but it doesn't work. What'd I miss?
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
On 29 Oct 2012, at 16:55, Marc Chametzky <marc at bluevine.net> wrote:
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
Had it bind to eth0 instead of vmbr0, the error went away and it can see an adjacent node.
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
That is now configured correctly. Seems this problem can easily be solved by just bringing up another VM, I have the RAM and DISK. ;)
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
On 29 Oct 2012, at 16:40, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 10/29/2012 4:23 PM, Jordi Guillaumes i Pons wrote:
El 29/10/2012, a les 21:21, Marc Chametzky <marc at bluevine.net> va escriure:
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
If you are so lazy as am I:
http://www.powerdog.com/addrconv.cgi
On the other hand, the current linux dnet-tools contains a setether command which does the math for you.
I was just going to post that link. :)
-brian
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
On 10/29/2012 4:23 PM, Jordi Guillaumes i Pons wrote:
El 29/10/2012, a les 21:21, Marc Chametzky <marc at bluevine.net> va escriure:
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
If you are so lazy as am I:
http://www.powerdog.com/addrconv.cgi
On the other hand, the current linux dnet-tools contains a setether command which does the math for you.
I was just going to post that link. :)
-brian
El 29/10/2012, a les 21:21, Marc Chametzky <marc at bluevine.net> va escriure:
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
If you are so lazy as am I:
http://www.powerdog.com/addrconv.cgi
On the other hand, the current linux dnet-tools contains a setether command which does the math for you.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 10/29/2012 04:22 PM, Jordi Guillaumes i Pons wrote:
El 29/10/2012, a les 21:18, Dave McGuire <mcguire at neurotica.com> va
escriure:
Is there any way to configure the terminal driver so the <ESC>
don't get cleared?
I don't know, but I can tell you that ANNOUNCE banners with
embedded escape sequences were always frowned upon when I was a
commercial VMS admin.
Hehehe that is the good part of being a hobyist :)
On the other hand, we used those banners back in the day... no one
complained. In fact, everyone used them. :)
In commercial shops? From my perspective that's pretty unusual.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Do you have a mapping for the SETNOD binary input file? I define the nodes using a procedure full of SET NODE instructions, and it is really slow...
I don't even know where the binary database file went, so I've not looked at it to know what it looks like on the inside. I don't recall it taking very long to TAKE the input file to prepare the database.
--Marc
El 29/10/2012, a les 21:18, Dave McGuire <mcguire at neurotica.com> va escriure:
Is there any way to configure the terminal driver so the <ESC> don't get cleared?
I don't know, but I can tell you that ANNOUNCE banners with embedded
escape sequences were always frowned upon when I was a commercial VMS admin.
Hehehe that is the good part of being a hobyist :)
On the other hand, we used those banners back in the day... no one complained. In fact, everyone used them. :)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
Here's what I did to get DECnet running on my TOPS-20 system (Panda distribution).
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
It's 33*1024 + 254 = 84fe, and then you swap the bytes.
Does that sound right to others?
--Marc
