Gerd wrote:
>
> Hello Tomi, hello all,
>
> > LinuxNode only inverts the callsign if the user is coming in via a L2
> > connection and going out again on a L2 connection and on the _same_port_.
> > In all other cases users callsign-ssid is left untouched. When I coded
> > this I tried to think of all the possible cases and only saw inverting
> > necessary in that one particular case.
> >
> > 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 )
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).
--
Stewart G0LGS
