[wt4hq] Bridgehead bug
Mario Lorenz
ml at vdazone.org
Sat Jul 4 21:46:40 CEST 2009
Am 03. Jul 2009, um 21:36:06 schrieb Laurent HAAS - F6FVY:
> Hi
>
> We've been reported a bug regarding the bridgehead setting in the
> Network Advanced Settings dialog.
>
> Looks like this bug affects all recent versions of Win-Test (HQ or not)
> - not the 3.21.1-HQ
>
> The BridgeHead setting in this dialog is not saved.
>
> If a station is used as a BridgeHead, its .ini file must contain :
>
> BridgeHead=1
Hello Larry,
could you please clarify the settings for me; I think I suffer from
naming confusion...
The old setting "RestrictToLan", when set, marked all Logsync traffic
generated by that host to be LAN-Only. Therefore it had to be set on all
the stations, except the one that was to logsync also over the tunnels
(if you were so adventurous).
What does the Bridgehead setting do and how it is to be set ?
Bridgehead is the one host to communicate, so am i right in
assuming that all stations need this to be set to 0 (or not present)
except the one station that is the bridgehead, ie also talks with the tunnels,
to 1 ?
Some tests here were somewhat inconclusive, but that could be due to
other factors...
73s,
Mario
--
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