[wt4hq] Bridgehead-Bug / LogSync

Mario Lorenz ml at vdazone.org
Thu Jul 9 22:20:19 CEST 2009


Am 09. Jul 2009, um 18:15:50 schrieb Laurent HAAS - F6FVY:
> Again...
> 
> I forgot to mention you need wtTunnel (Client) 1.10 too (as stated in my 
> email dated 01/07/2009 11:06

Of course :)

Being busy with much other setup, I have not been able to do all the tests
I wanted to do today. What I have tested however is putting a new
station onto the local lan. No station is bridgehead (setting is not in .ini)
Logsync enabled. As expected the station would sync up all the Q's.

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 ?

Mario
> 
> 73
> 
> Larry - F6FVY
> _______________________________________________
> Wt4hq mailing list
> Wt4hq at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/wt4hq
-- 
Mario Lorenz                            Internet:    <ml at vdazone.org>
                                        Ham Radio:   DL5MLO at DB0ERF.#THR.DEU.EU
"Your mouse has moved. Windows NT must be restarted
 for the change to take effect. Reboot now ?   [ OK ]"


More information about the Wt4hq mailing list