Bug Report Win10 update broke IP Bind?

[AllSyntaxErrors]

Hello!

So I have to use 2 seperate internet connections to be able to stream and play games (thanks Australia).
Ethernet for slow but stable games and WiFi for fast upload speeds.

For a year I have been using the bind IP feature in OBS, which has been brilliant! And then the microsoft fall update came. I strongly suspect something there change network parameters which has stopped the bind feature from working.

Has anyone else had these updates from Microsoft and is their Bind IP still working? (because I will also not be surprised if this bug has just appeared on my end)

So the problem is that I select the WiFi and click start stream, it fails to start the stream. If I disable the ethernet port leaving Wifi only, then everything works. If I start stream with binding to wifi on, then reactivate ethernet, everything works... for exactly 30 seconds before connections lost and can not be regained.

Opening task manager and looking at network activity shows a lot of activity on ethernet lines when trying to connect when bound to wifi (and, of course, no activity on WiFI). Furthermore, here is a log attached where the last saved setting was default internet bind, that I changed and saved to wifi before attempting to connect (and, of course, it fails). As you can see in the log, it seems it's trying to connect via ethernet (sorry about the junk of scenes and stuff).

I'm using 64 bit OBS, I regularly try to change binding to default, save, and then back to WiFi. WiFi is listed with the correct IP. It's IPv4, not IPv6. I updated my OBS to the latest version to no effect. Ethernet is the default network adapter (Ethernet metric = 1 Wifi = 20 - double checked via powershell and that's still the case)

Note: This update also removed the advanced multiple network metric panel found in the network adapters area, so something's been fiddled with! lol

Any thoughts or ideas? This obviously hits hard when I play a lot of multiplayer games. It's to the point I'm nearly using an old ubuntu computer to proxy the stream via (a fiddly and horrible setup that I HAVE managed to get working.. I just really don't want to keep doing that).

Log => https://gist.github.com/anonymous/3541c63e029ddaa6eb20451a65af0e31

Thanks for any info or support.

 

[Exeldro]

I have had other software stop working beacause microsoft changed the htons & ntohs functions in the fall creator update.
Both of these functions take 16-bit unsigned integer input and return the same. The problem is the functions in the Fall Creator Update are returning a 32-bit value instead!
Both those functions are used in obs. I haven't been able to check, but it can be the problem.

 

[sam686]

If I start stream with binding to wifi on, then reactivate ethernet, everything works... for exactly 30 seconds before connections lost and can not be regained.

Is Wifi turning off or disconnecting 30 seconds after ethernet is plugged in and enabled?
Internet search might have some hints. https://www.google.com/search?q=windows+10+keep+wifi+connected+when+lan+connected

If possible, try to use USB ethernet adapter for the other internet connection, which is better then Wifi wireless.

 

[R1CH]

I have had other software stop working beacause microsoft changed the htons & ntohs functions in the fall creator update.
Both of these functions take 16-bit unsigned integer input and return the same. The problem is the functions in the Fall Creator Update are returning a 32-bit value instead!
Both those functions are used in obs. I haven't been able to check, but it can be the problem.

The function returns a 16 bit value but some programs have declared it as returning a 32 bit value and now get junk in the upper bits due to compiler optimizations. Applications such as OBS which correctly follow the Windows ABI are not affected. Not really sure what is causing this.

 

[AllSyntaxErrors]

Cheers for the replies everyone!

Hmm, I hadn't experienced any other programs having issues with the WiFi but it is a thought, although I have noticed no disconnection or problem with the wifi when switching between the two. Irrespective, the issues isn't that transition between ethernet plugged in or not, it's that OBS SEEMS to not bind to a network like it used to since the latest update (or at least that's my current hypothesis because if it's not that, then it'll be fiddly as fu-dge to fix).

I also ran the test about tethering via USB (which I have found to be a little less stable for me due to a few factors, signal strength sadly one of them - although I have used USB tethering a lot in the past). The USB tether with an android phone behaved the same way. I plugged it in and selected network and it failed to find server. I then disabled ethernet adapter and selected default binding (worked fine - signal was a bit spotty but did not drop). I then disabled that stream and tried binding to usb tethered network. Same issue, couldn't connect and all activity (According to trusty task manager) was on the cable ethernet (which I had to double check because both usb tether and ethernet were called... ethernet... but I am certain which is which). All the usuals, I made sure to select the correct IPv4 network, not IPv6.

At this point I suppose it's prudent I check that someone else is experiencing the same bug else, if not, it's on my end ... somewhere.. and I gratefully ask for thoughts or tips but I won't hound here :-)

Thanks again for the responses (and interesting lessons on the windows network ABI).

 

[AllSyntaxErrors]

Sorry, I'm giving this a bump as I still can't seem to be able to find a solution.

Has anyone had any luck in getting forcebindip working on OBS? I keep getting a locale failed to load error when trying to.

And, again, is anyone able to test this for me? Does this bug happen with others that have the latest windows updates?

 

[R1CH]

ForceBindIP should work as long as you follow the instructions about setting the "Start in" folder.