I d suggest firing up wireshark or equivalent to capture the DECnet traffic. See what
it shows. Wireshark has some DECnet packet annotation (though some of it is badly broken
route packets are not parsed right). Look for packets from the neighbor routers you
re expecting to see. And look at the hello packets from both sides and match them
against what the DECnet routing spec says should happen.
If necessary, post a few lines from the result and we can look it over.
paul
On Jan 14, 2014, at 2:38 AM, Mark Abene <phiber at phiber.com> wrote:
I'm only ever seeing LAT and MOP packets coming over the bridge; my
DECnet 0x6003 packets get silently ignored, and I never see any coming
from the far end of the bridge. Is anyone willing to bridge with me
as a test for comparison? I don't yet have an area assigned by Johnny
since I only have one machine at present (but that may change), so
I've been using the same area number as the remote bridge peer.
-Mark
On Mon, Jan 13, 2014 at 10:45 PM, Mark Abene <phiber at phiber.com> wrote:
OK, I'm at the hair-tearing-out stage... Who here has a TOPS-20 system
connected to HECnet? I'm trying to peer with Sampsa with "bridge" in
his same area as an endnode. Bridge works fine on my end, lots of
activity in debug mode, and I see lots of node number entries if I
send it a SIGUSR1. However I never "see" the adjacent node in NCP,
though my circuit and line are up and active. Adding a few nodes
manually with NCP SET NODE and then trying a SET HOST in the monitor
just times out. If I do this while watching my ethernet with tcpdump,
I see my real DECnet traffic, immediately followed by its encapsulated
udp packet going out over port 4711. However, I never get any
responses to my SET HOST from the remote bridge side. Any suggestions
on debugging this?
Thanks,
Mark