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

Bob Wilson, N6TV n6tv at arrl.net
Tue Jun 23 19:47:11 CEST 2026


On Tue, Jun 23, 2026 at 2:48 AM Michael Ruttenberg <mjruttenberg at gmail.com>
wrote:

> Subnet mask 255.255.252.0 restricts the traffic massively, to only 1 IP
> address.
>

The net mask of 255.255.252.0 provides 10 bits of locally accessible IP
addresses, instead of only 8 bits like the normal netmask (255.255.255.0),
so the opposite is true.  Perhaps you were thinking the netmask was
255.255.255.252, but that was not the case here.

This is explained in more detail in this AI-generated article.  To read it
all, just click Close when prompted, then click the cookies prompt, then
close the sign-on window):

https://www.perplexity.ai/search/6e809c6e-2124-4ed4-9128-2359d5612698

I had to help out M0MDS with this exact same issue recently, where his 5G
> router had that setting and it stopped WinTest HQ version from seeing other
> stations. Changing the subnet mask range fixed it.
>

That's one way to fix it, but since the netmask is usually assigned to the
PC automatically as part of the DHCP mechanism, just correcting the
broadcast address in each Win-Test instance, and in wtDxTelnet, was a much
easier fix..

73,
Bob, N6TV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20260623/ddd0aebe/attachment.htm>


More information about the support mailing list