Resolved Unity Transport failed while Unet Transport succeeded!

meetjane · Aug 24, 2022

Platform: windows 10 enterprise
Unity: 2021.3.8f1c1

Steps:
1.Create a new project using 3D template.
2.Add package by searching name "com.unity.netcode.gameobjects".
3.Create an empty GameObject and add component "NetworkManager" on it.
4.Add Player prefabs with a new 3D capsule GameObject.
5.Select "Unity Transport" in "NetworkManager".
6.Play the scene and click "Start Host" in "NetworkManager".

Errors:

Server is shutting down due to network transport start failure of UnityTransport!
UnityEngine.Debug:LogError (object)
Unity.Netcode.NetworkManager:StartHost () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Core/NetworkManager.cs:1099)
Unity.Netcode.Editor.NetworkManagerEditor:OnInspectorGUI () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Editor/NetworkManagerEditor.cs:321)
UnityEngine.GUIUtility: ProcessEvent (int,intptr,bool&)

Server failed to bind
UnityEngine.Debug:LogError (object)
Unity.Netcode.Transports.UTP.UnityTransport:ServerBindAndListen (Unity.Networking.Transport.NetworkEndPoint) (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Transports/UTP/UnityTransport.cs:469)
Unity.Netcode.Transports.UTP.UnityTransport:StartServer () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Transports/UTP/UnityTransport.cs:1252)
Unity.Netcode.NetworkManager:StartHost () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Runtime/Core/NetworkManager.cs:1097)
Unity.Netcode.Editor.NetworkManagerEditor:OnInspectorGUI () (at Library/PackageCache/com.unity.netcode.gameobjects@1.0.0/Editor/NetworkManagerEditor.cs:321)
UnityEngine.GUIUtility: ProcessEvent (int,intptr,bool&)

If I remove component "Unity Transport" and select "Unet Transport", then it works as expected after I click "Start Host".
I've confirmed that the default port 7777 has never been ocupied by others.
I've also debug in NetworkDriver.cs.In the line 973, there is a statement

Code (CSharp):

var protocolBind = s_NetworkProtocols[m_NetworkProtocolIndex].Bind(s_NetworkInterfaces[m_NetworkInterfaceIndex], ref ifEndPoint);

m_InternalState[InternalStateBound] = protocolBind == 0 ? 1 : 0;

return protocolBind;

which get -1 for variable "protocolBind" after execution.

Can someone help me out please? Thanks.

simon-lemay-unity · Aug 24, 2022

Could you try setting the 'Server Listen Address' setting to 0.0.0.0? Is IPv4 enabled on your local network adapter (you can check that under the advanced properties)?

Also if you're willing to debug that deeply, the method that is taking care of binding the socket in Unity Transport is
BaselibNetworkInterface.Bind
(in the
BaselibNetworkInterface.cs
file, in the same directory as
NetworkDriver.cs
). There are a few places where it can return -1, typically following a check on some
error.code
value. If you could log that
error.code
value when -1 is returned, that'd be helpful in finding out what could be causing the issue.

meetjane · Aug 25, 2022

simon-lemay-unity said: ↑
Could you try setting the 'Server Listen Address' setting to 0.0.0.0? Is IPv4 enabled on your local network adapter (you can check that under the advanced properties)?

Also if you're willing to debug that deeply, the method that is taking care of binding the socket in Unity Transport is
BaselibNetworkInterface.Bind
(in the
BaselibNetworkInterface.cs
file, in the same directory as
NetworkDriver.cs
). There are a few places where it can return -1, typically following a check on some
error.code
value. If you could log that
error.code
value when -1 is returned, that'd be helpful in finding out what could be causing the issue.
Click to expand...
Thx for replying.
Setting "Server Listen Address" to 0.0.0.0 is also not working and get the same error as before.
I can't find advanced properties for checking IPv4, would you please describe the detail step?
Still, I've checked Ipv4 is enabled in my network adaper settings.Inputing "ipconfig" in cmd will also display my ipv4 address.

I've debugged the place BaselibNetworkInterface.Bind you memtioned, here's the result:

Code (CSharp):

Binding.Baselib_RegisteredNetwork_Endpoint_GetNetworkAddress(local, &localAddress, &error);

This statement gets Success in error.code.

Code (CSharp):

var socket = Binding.Baselib_RegisteredNetwork_Socket_UDP_Create(

&localAddress,

Binding.Baselib_NetworkAddress_AddressReuse.Allow,

checked((uint)configuration.sendQueueCapacity),

checked((uint)configuration.receiveQueueCapacity),

&error);

This statement gets UnexpectedError in error.code which is -1 after converting to type int.
The method Bind() also returned next to this.

Code (CSharp):

if (error.code != ErrorCode.Success)

return (int)error.code == -1 ? -1 : -(int)error.code;

simon-lemay-unity · Aug 25, 2022

This might appear as a weird suggestion, but could you try enabling IPv6 (it's a checkbox in the screenshot you posted), restarting your PC, and then trying again?

meetjane · Aug 26, 2022

simon-lemay-unity said: ↑

This might appear as a weird suggestion, but could you try enabling IPv6 (it's a checkbox in the screenshot you posted), restarting your PC, and then trying again?
Click to expand...

It doesn't help as well.
I've learnt that the fundamental implement of Unity Transport is the same as Unet Transport.Since Unet is working on my pc, I doubt if the problem is in Unity Transport itself?

simon-lemay-unity · Aug 29, 2022

meatjam said: ↑

I've learnt that the fundamental implement of Unity Transport is the same as Unet Transport.
Click to expand...

What do you mean by that? I don't believe Unity Transport and UNet share any code.

meetjane · Aug 30, 2022

simon-lemay-unity said: ↑

What do you mean by that? I don't believe Unity Transport and UNet share any code.
Click to expand...

Maybe I'm wrong? I mean the way they bind port or the windows API they use may be the same?
If that's true, then it must be somewhere wrong in application layer of Unity Transport.
You see, I'm trying locating the problem.

simon-lemay-unity · Aug 30, 2022

I see what you mean, thank you. Yes, ultimately binding will use the same system calls in both. But I'm thinking that it's not the actual binding of the socket that might be going wrong here. In Unity Transport, the bind operation will first create the socket. And on Windows, we use registered I/O for performance, which implies allocating and registering buffers on top of creating the socket.

I'm thinking that what may be going wrong is the initialization of the RIO mechanism (that's what the error you reported would tend to indicate). I suggested enabling IPv6 because there appears to be a dependency on that in our RIO initialization code, but otherwise I'm unfortunately a bit at a loss regarding what could be causing it to fail.

meetjane · Aug 31, 2022

simon-lemay-unity said: ↑

I see what you mean, thank you. Yes, ultimately binding will use the same system calls in both. But I'm thinking that it's not the actual binding of the socket that might be going wrong here. In Unity Transport, the bind operation will first create the socket. And on Windows, we use registered I/O for performance, which implies allocating and registering buffers on top of creating the socket.

I'm thinking that what may be going wrong is the initialization of the RIO mechanism (that's what the error you reported would tend to indicate). I suggested enabling IPv6 because there appears to be a dependency on that in our RIO initialization code, but otherwise I'm unfortunately a bit at a loss regarding what could be causing it to fail.
Click to expand...

Do you have any idea to test if RIO works besides Unity Transport?
I've got another computer which is the same windows platform and Unity version as this one, but that pc works all fine.
That's really weird.

simon-lemay-unity · Aug 31, 2022

Yeah, I agree it's really weird.

Unfortunately, besides writing a C/C++ program that initializes the RIO subsystem, I'm not sure there's much that can be done to check that it works. (If you wish to go that route, the Microsoft documentation I linked to should provide all the necessary information.)

You may want to make a quick test in C# though and create an IPv6 UDP socket from a Unity script. That would mimic the socket we create internally to initialize the RIO subsystem. Something like:

Code (CSharp):

using System.Net.Sockets;

var s = new Socket(AddressFamily.InterNetworkV6, SocketType.Dgram, ProtocolType.Udp);

meetjane · Sep 1, 2022

simon-lemay-unity said: ↑

Yeah, I agree it's really weird.

Unfortunately, besides writing a C/C++ program that initializes the RIO subsystem, I'm not sure there's much that can be done to check that it works. (If you wish to go that route, the Microsoft documentation I linked to should provide all the necessary information.)

You may want to make a quick test in C# though and create an IPv6 UDP socket from a Unity script. That would mimic the socket we create internally to initialize the RIO subsystem. Something like:

Code (CSharp):

using System.Net.Sockets;

var s = new Socket(AddressFamily.InterNetworkV6, SocketType.Dgram, ProtocolType.Udp);

Click to expand...

Here's the result of test codes in C#:

Code (CSharp):

Debug.Log($"is Socket OSSupportsIPv6:{Socket.OSSupportsIPv6}");

var s = new Socket(AddressFamily.InterNetworkV6, SocketType.Dgram, ProtocolType.Udp);

Debug.Log($"is bound: {s.IsBound}, is connected: {s.Connected}");

Is the RIO subsystem you mentioned can only tested in C/C++ program rather than C#?
I'm not quite familiar with that. If "yes", I'll take a try to test RIO with C/C++.

simon-lemay-unity · Sep 1, 2022

I'm not aware of RIO being exposed through C# APIs, so unfortunately writing C/C++ would be the only way of testing it. But fortunately, it might not be necessary to do that here. Digging through our code, I found that if RIO fails to be initialized, we fall back to using normal sockets. So it's doubtful that RIO is the problem here.

The unexpected error you observed seems to only be generated following an error from a socket API call. If you still wish to investigate this further, you could try tracing the socket calls. Windows provides such a mechanism, but there are other tools to do the same (here's one, although this would trace all Windows API calls, which is likely to be quite noisy).

meetjane · Sep 2, 2022

simon-lemay-unity said: ↑

I'm not aware of RIO being exposed through C# APIs, so unfortunately writing C/C++ would be the only way of testing it. But fortunately, it might not be necessary to do that here. Digging through our code, I found that if RIO fails to be initialized, we fall back to using normal sockets. So it's doubtful that RIO is the problem here.

The unexpected error you observed seems to only be generated following an error from a socket API call. If you still wish to investigate this further, you could try tracing the socket calls. Windows provides such a mechanism, but there are other tools to do the same (here's one, although this would trace all Windows API calls, which is likely to be quite noisy).
Click to expand...

Thanks for your suggestion!
I've used WinAPIOverride64 you recommended to trace socket calls.It seems like nothing special in the logs, no function call get any error.
Here's the detail of logs and the whole Log file you can open in WinAPIOverride64.

meetjane · Sep 2, 2022

And Here's the API library file I chose to monitor calls:
ws2_32.txt

simon-lemay-unity · Sep 4, 2022

Thanks a lot! That's actually very helpful!

So this does indeed look like it's an issue initializing RIO. The RIO calls are not listed here (presumably because they're made through function pointers), but the sequence of system calls would tend to indicate that the
RIOCreateRequestQueue
call is failing with error code
WSAEOPNOTSUPP
(10045, from the
WSAGetLastError
call).

I've done some digging, and it seems this can occur if there are TDI filters in place. These filters are normally installed by older antivirus software. It might be worth a shot to disable your antivirus, or to update it (my understanding is that these filters are deprecated and shouldn't be used anymore).

meetjane · Sep 5, 2022

simon-lemay-unity said: ↑
Thanks a lot! That's actually very helpful!

So this does indeed look like it's an issue initializing RIO. The RIO calls are not listed here (presumably because they're made through function pointers), but the sequence of system calls would tend to indicate that the
RIOCreateRequestQueue
call is failing with error code
WSAEOPNOTSUPP
(10045, from the
WSAGetLastError
call).

I've done some digging, and it seems this can occur if there are TDI filters in place. These filters are normally installed by older antivirus software. It might be worth a shot to disable your antivirus, or to update it (my understanding is that these filters are deprecated and shouldn't be used anymore).
Click to expand...
Thanks! It is the TDI filter that causes the problem!
I've check my windows EventViewer by eventvwr.msc and found several warnings about unauthorized TDI filter being detected.It infers to the file names "LgdCatcherTdi.sys" locating at "C:\WINDOWS\system32\drivers".I realized that I've used a game accelerator called "LeiGod" several weeks ago. This driver file should belongs to it.After temporarily remove this file and reboot my system.Everything works as expected perfectly.

Thanks for your great help sincerely!

yourihua · Dec 7, 2022

simon-lemay-unity said: ↑
Thanks a lot! That's actually very helpful!

So this does indeed look like it's an issue initializing RIO. The RIO calls are not listed here (presumably because they're made through function pointers), but the sequence of system calls would tend to indicate that the
RIOCreateRequestQueue
call is failing with error code
WSAEOPNOTSUPP
(10045, from the
WSAGetLastError
call).

I've done some digging, and it seems this can occur if there are TDI filters in place. These filters are normally installed by older antivirus software. It might be worth a shot to disable your antivirus, or to update it (my understanding is that these filters are deprecated and shouldn't be used anymore).
Click to expand...
If the game I developed uses netcode, then I can’t ask every user to delete the tdi program, so how can I solve it completely?

meetjane · Dec 7, 2022

yourihua said: ↑

If the game I developed uses netcode, then I can’t ask every user to delete the tdi program, so how can I solve it completely?
Click to expand...

I believe the majority of players won't have problem like this, for the rest of players. Maybe give them some tips about solving network problem? Otherwise, you have to use another multiplayer framework.

simon-lemay-unity · Dec 7, 2022

First of all, this problem is specific to Unity Transport, not to the entire Netcode for GameObjects framework. If you're very concerned about this issue, there are other transports you can use with the framework.

Otherwise, I agree with @meatjam that this is unlikely to be a problem for many users. TDI filters are pretty much deprecated by Microsoft. Drivers that want to get official support for Windows are not even allowed to install them, for example.

We've also identified a way to circumvent the issue on our end, so eventually this will not be an issue at all anymore. Unfortunately it requires modifications to core Unity networking code and at this point I'm not able to say when the fix will be available.

yourihua · Dec 12, 2022

simon-lemay-unity said: ↑

First of all, this problem is specific to Unity Transport, not to the entire Netcode for GameObjects framework. If you're very concerned about this issue, there are other transports you can use with the framework.

Otherwise, I agree with @meatjam that this is unlikely to be a problem for many users. TDI filters are pretty much deprecated by Microsoft. Drivers that want to get official support for Windows are not even allowed to install them, for example.

We've also identified a way to circumvent the issue on our end, so eventually this will not be an issue at all anymore. Unfortunately it requires modifications to core Unity networking code and at this point I'm not able to say when the fix will be available.
Click to expand...

First of all, thank you very much for your reply. And in our development team, most team members use game VPN tools, and we use netcode for entities, not netcode for gameobjects. So if it can be fixed, can it be as soon as possible? thank you very much.

simon-lemay-unity · Dec 12, 2022

Have you experienced the issue firsthand? If so, do you know which piece of software is installing TDI filters? If we had examples of legitimate and recent software that is installing TDI filters, it would help us in prioritizing this issue.

yourihua · Dec 13, 2022

simon-lemay-unity said: ↑

Have you experienced the issue firsthand? If so, do you know which piece of software is installing TDI filters? If we had examples of legitimate and recent software that is installing TDI filters, it would help us in prioritizing this issue.
Click to expand...

Yes, there is a high probability of encountering problems when installing the following software:

leigod

astrill

WeGame

In China, there are many gamers who install these programs. And of course my colleagues.So sorry for the trouble.Thanks again.

simon-lemay-unity · Dec 13, 2022

Thanks for the information! I'll add it to our internal task tracking this issue and bump the priority accordingly.

Proportion1 · Feb 7, 2023

hi, i had this same problem. the program that was bugging it out using the tdi filter stuff was networx by softperfect. works fine now heh.

c0nfig69 · Feb 15, 2023

after wasting a work day I can confirm same problem with tdi filter from FortiEDR by FortiNet. Unfortunately our company policy does not allow uninstall the antivir program.

simon-lemay-unity · Feb 15, 2023

Thank you for reporting back and providing more examples of software that is causing this issue. We're currently working on a fix for this. I'll report back here when I have a better idea of when it will be available. Thank you for your patience on this, I understand that it's a frustrating issue to deal with.

simon-lemay-unity · Mar 17, 2023 at 5:48 PM

Finally some good news regarding this issue: the fix has been made and will be released in upcoming editor versions. The first versions with the fix will be 2021.3.22f1, 2022.2.13f1, 2023.1.0b9, and 2023.2.0a7.

ChangeEternity · Mar 21, 2023 at 4:57 AM

meetjane said: ↑

Thanks! It is the TDI filter that causes the problem!
I've check my windows EventViewer by eventvwr.msc and found several warnings about unauthorized TDI filter being detected.It infers to the file names "LgdCatcherTdi.sys" locating at "C:\WINDOWS\system32\drivers".I realized that I've used a game accelerator called "LeiGod" several weeks ago. This driver file should belongs to it.After temporarily remove this file and reboot my system.Everything works as expected perfectly.

Thanks for your great help sincerely!
Click to expand...

Thank you very much for your answer. The problem that has been bothering me all day has been solved

Search Unity

Unity ID

Resolved Unity Transport failed while Unet Transport succeeded!

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Attached Files:

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies