[wt4hq] Bridgehead-Bug / LogSync

[Laurent HAAS - F6FVY]

Hi again

Mario Lorenz a écrit :

> Unexpectedly however I saw the ADDQSO traffic on the tunnel server:
> ADDQSO: "E15SSB2" "C40SSB" "X10SSB_1" 1247162569 142276 1 5 0 0 4 1 25 "4L1FP"
>  "59" "59" "" "" "" 0 "" "" "" 59002
> 
> (E115SSB and C40SSB are in the same LAN, C40SSB was turned on fresh)
> 
> I do not remember seing this last year, so I dont know if this behaviour
> has changed. Shouldnt the tunnel client
> know - similar to the server - which station is local and which is
> on the WAN, and hence not forward this kind of traffic ?

There is no filtering on ADDQSO: in wtTunnel

Filtering is applied only on IHAVE: (described in my previous message) 
and NEEDQSO: (only those with external destination are forwarded to the 
WAN).

As far as I remember (and our CVS does confirm it), it always worked 
like this. Actually, the ADDQSO: _must_ be forwarded, as it is the same 
frame that is used when you manually enter a QSO. Maybe we could 
consider a different set of frame IDs for sync, and filter it 
appropriately in wtTunnel... (Just an idea - No deep analysis of the 
consequences on the current WT code yet ;-) ).

73

Larry - F6FVY