On Fri, 22 Aug 2008 08:11:37 +0200, you wrote:
Well, I would keep LAT and Infoserver traffic separate. :-)
Somewhere into the future somebody will do that too :-)
One of us had just got a beautiful InfoServer 1000 in InfoTower configuration,
and we were longing to test it across the net, so we just addedd its ethertype
to the bridge and ran it. The change from [lat] to [lan] came later, when we
decided to release the update.
BTW, that bridge configuration section already controlled not only LAT but
also MOP Remote Console and Dump/Load, so we just added a protocol to the
circus and then felt that [lan] was a better choice to describe it.
The perfect solution would have been (*) to have at least three different
sections like [lat], [mop] and [infoserver], but we were to lazy to do that
much work and delaying our InfoServer tests :P
G.