Unexpected KISS TCP client application 0 on port 8100

[dranch]

Per https://groups.io/g/direwolf/topic/alternate_kiss_port/90387650, it seems Direwolf 1.7E for Windows seems to ALWAYS create a KISS TCP session on port 8100 regardless of being configured or not. The above thread mentions a workaround but this should be corrected.

[j4nr6n]

Same issue