[wt4hq] Patch for wtTunnelSrv

Olivier F5MZN olecam at f5mzn.org
Sun May 20 08:55:02 CEST 2007


Hello,

> I assume that would be me. (say, how many other "german guys" are on this
> list ? :))

Right. Thank you for posting your mail again.

> As you wish, patched source is included. As you will notice its really
> not too much.

Indeed. I have included your mods in my devel trunk.

> You mention that the server has been rewritten; I wonder if the clients
> have been rewritten too, to include a similar feature.

The main improvement consists in the "autolearning route and filter 
feature", which:

1. learn which wtTunnel client a station is located behind
2. when a protocol is sent to a specific station (like the QSO 
synchronisation ones), only forward this protocol to the wtTunnel (aka 
to the LAN) the station is behind

This will save lots a bandwidth because these protocols won't be 
forwarded anymore to everybody when destinated to only one station.

> (unfortunately you do not publish the source for the client so I couldnt
> look). Last year, I suggested some further optimizations in the
> network protocol and I wonder if those have been realized.

I am no against providing the source code of the wtTunnel software on 
conditions that:

1. if someone made improvements in, this must be shared with the WT 
community
2. the patched source code still much work with my old Visual C++ 5.0! :)

> I am not only concerned about the log sync traffic, but about general
> traffic as well. You probably remember  my last year's assessment that
> the huge majority of the traffic were the status frames, and over the
> wan link I certainly would suggest to proxy them down to a more
> sensible rate. (once every two minutes or thereabouts).
> I do not know about you, but we will certainly have some stations
> with only a low bandwith connection.

If you do that way, every stations will be penalized. IMHO, it is 
acceptable to reduce the amount of Status Frames for the "low bandwidth" 
(or "limited bandwidth" due to the cost) but it is not relevant others 
when an "unlimited high bandwidth" inet connection is available.

If so, this need to limit this traffic (for some stations) at the server 
side, not in wtTunnel. This needs too much work than I can spend on this 
project but any patch will be welcome!

Another way for limiting the trafic could be to filter Status Frames for 
some support station. This could be done either at the wtTunnel side or 
at the WT side. We already improved WT addind a way to limit the "QSO 
synchronization broadcast" from some station of the LAN but TBH I don't 
remember where Larry added the option menu for in WT...

73,
-- 
Olivier / f5mzn


More information about the Wt4hq mailing list