On 2012-07-02 00:35, Gregg Levine wrote:
On Sun, Jul 1, 2012 at 6:13 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-07-01 23:50, Gregg C Levine wrote:
Hello!
Once again I've been spending a lot of free time to consider an
interesting
question. What can connect to our network, and what can't? Or for that
matter what shouldn't be connected at all.
Not sure I understand the question...
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
Hello!
Okay think of it this way: What operating systems can be connected,
and running on what (emulated) hardware?
Oh!
Do you also want to know versions of software? That can become a rather complex list.
Not even sure anyone knows the full answer... There are/were DECnet implementations for quite a few systems.
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
On Sun, Jul 1, 2012 at 6:13 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-07-01 23:50, Gregg C Levine wrote:
Hello!
Once again I've been spending a lot of free time to consider an
interesting
question. What can connect to our network, and what can't? Or for that
matter what shouldn't be connected at all.
Not sure I understand the question...
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
Hello!
Okay think of it this way: What operating systems can be connected,
and running on what (emulated) hardware?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 2012-07-01 23:50, Gregg C Levine wrote:
Hello!
Once again I've been spending a lot of free time to consider an interesting
question. What can connect to our network, and what can't? Or for that
matter what shouldn't be connected at all.
Not sure I understand the question...
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
On 2012-07-01 22:05, Bob Armstrong wrote:
I'll start!
Various such lists have been started over time, but I don't think anybody
was willing to maintain them.
I agree that it's hard to figure out routing issues when the network
topology is unknown! A nice HECnet map would be worth its weight in gold
about now.
Area: 2
Name: Bob Armstrong
Location: Milpitas, CA (Western US)
Router: LEGATO:: - connected via bridge and Multinet Tunnels
I have a list which is pretty authoritative on who "owns" each area, but I have not kept any other information around, such as routers, geographical information, or anything similar.
Partly also because areas are not necessarily geographically coherent.
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
Hello!
Once again I've been spending a lot of free time to consider an interesting
question. What can connect to our network, and what can't? Or for that
matter what shouldn't be connected at all.
----
Gregg C Levine
gregg.drwho8 at gmail.com
"This signature does not exist!"
Ditto here, although there are fewer nodes/areas online now than
previously. LEGATO continues to think that it can reach areas 52 and 59 via
A54RTR, although I don't believe any nodes are actually up in either area.
As far as I can see, LEGATO is probably correct in what it is thinking.
The GRE tunnels from A54RTR to area 59 are up.
a54rtr>show decnet neighbors
Net Node Interface MAC address Flags
0 59.60 Tunnel590011 0000.0000.0000 A
0 59.59 Tunnel590059 0000.0000.0000 A
0 54.59 Ethernet0 aa00.0400.3bd8 V A
0 54.188 Ethernet0 aa00.0400.bcd8
a54rtr>
Attempting to query some nodes in area 59 results in:
-SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
which sounds like a node that is reachable but doesn't have an NML listener.
If the node was not reachable the resulting error would likely be:
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Regards,
Peter Coghlan.
How does the Cisco DECnet decide what's up and what's down? It looks like
these Cisco boxes may think that areas are up and reachable even when
they're not.
I expect they behave the same as DECnet routers implemented by Dec.
I don't think they are reporting anything up that is is not really up.
Regards,
Peter Coghlan.
Hi all:
My turn ... :)
Area: 33
Name: Fred Coffey
Location: Sandusky, Ohio (midwest, between Toledo and Cleveland)
Router: FRUGAL:: - connected via Multinet Tunnels to area 2 and 19
Cheers,
Fred
Everything looks ok from here now. I can reach area 7.
Ditto here, although there are fewer nodes/areas online now than
previously. LEGATO continues to think that it can reach areas 52 and 59 via
A54RTR, although I don't believe any nodes are actually up in either area.
Bob
A54RTR is a Cisco IGS which has GRE tunnels to area 59 on test.
How does the Cisco DECnet decide what's up and what's down? It looks like
these Cisco boxes may think that areas are up and reachable even when
they're not.
The router(s) in area 52 and 59 don't appear to speak (much) NML either.
Probably more of the same Cisco boxes...
Bob
