Running on 127.0.0.1 breaks Windows support

[connorcarpenter]

As per @smokku in https://github.com/naia-rs/naia-socket/issues/24

Change bd5365c breaks Windows support.

    Finished dev [unoptimized + debuginfo] target(s) in 0.84s
     Running `D:\devel\naia-socket\target\debug\naia-client-socket-miniquad-example.exe`
Naia Client Socket Example Started
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 10049, kind: AddrNotAvailable, message: "Żądany adres jest nieprawidłowy w tym kontekście." }', demo\client\miniquad\src\app.rs:39:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `D:\devel\naia-socket\target\debug\naia-client-socket-miniquad-example.exe` (exit code: 101)

[connorcarpenter]

as per @Meshiest in https://github.com/naia-rs/naia-socket/issues/24

I'm running into this.

replacing client_ip_address with "0.0.0.0" in the udp socket bind fixes it for me
https://github.com/naia-rs/naia-socket/blob/master/client/src/impls/native/socket.rs#L41

[ineentho]

I can confirm that the same fix works for me on windows.

I'd be interested in contributing a fix, if could give me advice on the best path forward please? The different options I see:

• Add a new option client_bind_address: Option to SocketConfig, which would be used instead of the current automatic detection if defined.
• Add a special case to the automatic detection: if addr == 127.0.0.1 then addr = 0.0.0.0
• The above special case, but only for windows

[SonicZentropy]

Also running into this and fix also works for me. I'd also be happy to help fix the problem rather than maintaining my own fork

[SonicZentropy]

Adding in a bit more info, my fix originally used the auto-detection option, but that one can break as well. Sometimes naia returns my LAN IP (192.168.1.100) rather than localhost (127.0.0.1), in which case the auto-detect obviously fails. I'm now brute forcing it to 0.0.0.0 when cfg(target_os = "windows")