Date : Sat, 04 Jul 2009 21:52:31 +0100
From : C.J.Thornley@... (Chris Thornley)
Subject: econet bridge protocol
Perhaps it used in building an equavilent of a routers CAM table i.e. a map
of where networks are so routes can be looked up
Like using address 1.xxx 2.xxx denotes the network xxx is the station
number.
Perhaps a disable of a bridge or z80 MDFS rom might help?.
Just a guess really, but it might be a form of network discovery.
Chris
/> Christopher J. Thornley is cjt@...
( //------------------------------------------------------,
(*)OXOXOXOXO(*>=*=O=S=U=0=3=6=*=--------- >
( \\------------------------------------------------------'
\> Home Page :-http://www.coolrose.fsnet.co.uk
-----Original Message-----
From: bbc-micro-bounces+c.j.thornley=coolrose.fsnet.co.uk@...
[mailto:bbc-micro-bounces+c.j.thornley=coolrose.fsnet.co.uk@...
uk] On Behalf Of Phil Blundell
Sent: 04 July 2009 20:42
To: bbc-micro@...
Subject: [BBC-Micro] econet bridge protocol
Does anybody have documentation on the port &9c protocol used by bridges?
Chapter 10 of the MDFS book gives some details but doesn't describe the
messages with control bytes &80 and &81.
Observing the single bridge that I have here, at power up it seems to send a
broadcast with control byte &80, containing in its payload the number of its
other local network; I guess this is the "reset packet"
that the MDFS book talks about.
If I send the bridge one of those packets (cb &80) then it responds with a
series of packets with control byte &81 and, again, the network number of
its far side in the payload. I'm not entirely sure what the meaning of
these packets is, or how (if at all) I am meant to respond to them.
Can anybody shed any light on that? Or, absent any documentation, is there
anybody with two or more bridges who would be prepared to capture some
packet dumps showing them talking to each other?
thanks
p.
_______________________________________________
bbc-micro mailing list
bbc-micro@...
http://lists.cloud9.co.uk/mailman/listinfo/bbc-micro