Direwolf still listens on port 8001 when KISSPORT is set to a different port

[drizzlecombe]

Platform: Windows 11, prebuilt Direwolf 1.8 binary (direwolf-1.8.0-390d4a8_x86_64.zip).

Winlink Express uses port 8001 for its HTTP forms server.

Direwolf is launched using a packet session with KISSPORT is set to 8100. Notice that when Direwolf starts up, it says it's listening on port 8001 (default) as well as 8100.

Open a new Winlink message and try to use a form, Winlink complains that port 8001 is being used.

Workaround

Set KISSPORT 0 first before resetting KISSPORT 8100. This seems to stop Direwolf 1.8 listening on port 8001.

I haven't tested this on prior versions so I do not know if this issue happened prior to version 1.8.

[mfncooper]

This is a duplicate of issue #342 . As noted there, what you are seeing appears to be by design, such that the "workaround" you reference is actually the intended behaviour. The updated source reference is:

https://github.com/wb2osz/direwolf/blob/dev/src/config.c#L5059

[drizzlecombe]

Ahh, thanks, Martin. I did search to see if this had cropped up before, but somehow it didn't come up. Clearly I didn't search well enough! I'd recommend a fix to the documentation to ensure all and sundry know. Much appreciated. Andrew --

…

On Wed, 5 Nov 2025 at 18:01, Martin Cooper ***@***.***> wrote: *mfncooper* left a comment (wb2osz/direwolf#619) <#619 (comment)> This is a duplicate of issue #342 <#342> . As noted there <#342 (comment)>, what you are seeing appears to be by design, such that the "workaround" you reference is actually the intended behaviour. The updated source reference is: https://github.com/wb2osz/direwolf/blob/dev/src/config.c#L5059 — Reply to this email directly, view it on GitHub <#619 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMXPLT5H6PITVFPQGKPX2SL33KTWVAVCNFSM6AAAAACLI3KRTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJUGQ4DKNBYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>