[WT-support] SOLVED -- Win-Test Networking over a mesh Network

[Bob Wilson, N6TV]

Correction, that was supposed to say PING command not PINT command.

73,
Bob, N6TV


On Mon, Jun 22, 2026 at 8:29 PM Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> I just helped a fellow contester who was struggling to get a Win-Test
> network to work again, after he had just "upgraded' his house to a mesh
> network to get more WiFi range for new security cameras.
>
> But both PCs were on WIRED Ethernet.  The IP addresses of the two Win-Test
> PCs were 192.168.4.xxx and 192.168.4.yyy (where xxx and yyy are numeric
> values I can't remember).  The PINT command between the two PCs worked
> fine, but the Win-Test network did NOT work at all, no Gab, no QSOs, no
> wtDxTelnet spots.
>
> The IPCONFIG command revealed that this particular mesh network by default
> had the Subnet Mask set to 255.255.252.0 instead of the typical
> 255.255.255.0.  So, instead of using the "normal" UDP broadcast address
> that Win-Test calculates for you (192.168.4.255), I had to tell Win-Test to
> use 192.168.7.255.  I needed help from AI to calculate the proper UDP
> broadcast address for a LAN with a netmask of 255.255.252.0.  Fortunately,
> it gave me the right answer.
>
> Perhaps Win-Test can look at the current Netmask as well as the current IP
> address so that the "Default" button on the Win-Test Interface
> Configuration screen can do all the work for you.
>
> 73,
> Bob, N6TV
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20260622/88d914d6/attachment.htm>