On Sun, 14 May 2000, Stewart Wilkinson wrote:
> Gerd wrote:
> > >
> > > Do you have a case where this leads to actual problems so we can see if
> > > something needs to be fixed?
> >
> > Yes, I am aware of such a case. You run into problems when a
> > user enters a node on L2, goes out on L2 again on the same port
> > to another node where he also enters and goes out on a L2
> > connection. If everything here happens on the same port the
> > second node sends out frames that seem to come from the original
> > user (i.e., they have the same SSID as the user). If the user's TNC
> > receives such a frame by accident, it either sends out DM- or
> > reports protocol errors (FRMR).
>
> But that applies for other NODE software too. As the SSID gets
> inverted twice. (ie: -0 > -15 > -0 )
Exactly. I guess I could come up with some other scheme for the SSID
change but then it would probably cause problems elsewhere. Not worth the
trouble IMO...
> I recall sometime ago, having another problem (perhaps in earlier
> versions), whereby Linux NODE used the wrong callsign in outgoing
> connects.
>
> (I seem to recall this occured when one Linux NODE linked to another
> at L3/4 and then on again at L2, but I am not currently able to
> reproduce the problem).
Never heard of such a problem. If you can reproduce it please send me a
bug report.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04 Amprnet: [EMAIL PROTECTED]
