Windows socket error #1

New Issue

2025-12-31T16:38:57+01:00

adam commented

2025-12-31 16:38:57 +01:00

Originally created by @starek4 on GitHub (Oct 9, 2019).

Originally assigned to: @starek4 on GitHub.

Bug description

On Windows (or WSL), there is sometimes (quite rarely) a bug caused by boofuzz lib. Bug is tracked here: https://github.com/jtpereyda/boofuzz/issues/296

It is caused by non-terminated TCP connections. There are sockets which hangs in state TimeWait and blocks specific port number.

Thrown exception

On Windows: [WinError 10048]
In WSL: [Errno 98]

Workaround

Just use docker instead of native running on Windows. Or you can run WFuzz on any Linux, for example in some virtual environment, like Hyper-V.

Originally created by @starek4 on GitHub (Oct 9, 2019). Originally assigned to: @starek4 on GitHub. # Bug description On Windows (or WSL), there is sometimes (quite rarely) a bug caused by boofuzz lib. Bug is tracked here: https://github.com/jtpereyda/boofuzz/issues/296 It is caused by non-terminated TCP connections. There are sockets which hangs in state [TimeWait](http://www.serverframework.com/asynchronousevents/2011/01/time-wait-and-its-design-implications-for-protocols-and-scalable-servers.html) and blocks specific port number. # Thrown exception **On Windows:** [WinError 10048] **In WSL:** [Errno 98] # Workaround Just use docker instead of native running on Windows. Or you can run WFuzz on any Linux, for example in some virtual environment, like Hyper-V.

adam added the bug label 2025-12-31 16:38:57 +01:00

adam closed this issue

2025-12-31 16:38:57 +01:00

adam commented

2025-12-31 16:38:58 +01:00