Can I use MultiNetworkDriver for both IPv4 and IPv6?

Hi. I managed multiple NetworkDriver for handling both IPv4 and IPv6 connection. I created abstraction connection struct which has internal driver index for its source.

Then I found that Unity Transport 2.0.0-pre.7 introduces "MultiNetworkDriver" that seems to be best fit for above case.

So can MultiNetworkDriver handles multiple UDP network driver which has only different binding address?

THanks.

Related post:
https://forum.unity.com/threads/cas...accept-connection-from-ipv4-endpoint.1215861/

 

The link to the example (the one you posted now) is not available anywhere in the manual (at lest not in the index on the right side) as far as I see. I mention this in case you forget to add it. I have seen the example mentioned in the changelog, but I was not able to find it.

Also your update is just in time for me too as I today started implementing the migration of my custom networking layer from UNET to Transport.

 

Yes that was the case, it is working now, thank you.

 

Looks like it is not only the left menu, but the individual reference pages also need a hard refresh to show the newest version. Which makes the whole documentation more difficult to use. I only find that I need to do the cache refresh because I have seen that there is a <summary> section in the Transport source code, but it is not visible on the reference page. So I guessed that I have to refresh.

Even though I know it is not related directly to Transport, I think this should be somehow fixed by Unity as it seems like a big problem.

 

@simon-lemay-unity Hi. My project has P2P feature, so client and server share the most of code. The problem is that MultiNetworkDriver and NetworkDriver does not implement any shared interface so all of my code should have annoying conditional statement like this:

Code (CSharp):

1. if(useMultiNetworkDriver)
2. {
3.     var multiNetworkDriver = ...
4.     multiNetworkDrvier.Send(...)
5. }
6. else
7. {
8.     var newtorkDriver = ...
9.     newtorkDriver.Send(...)
10. }

Main problem is that MultiNetworkDriver does not have Connect() method so I can't use it for client side.

Is there any other method for handling both MultiNetworkDriver and NetworkDriver transparently?

 

I would like to see this feature too (even though I will not use P2P) as it would simplify the code. Both the client and the server have to do similar things like sending and receiving data not being able to use MultiNetworkDriver for both sides is a complication that could be avoided.

 

Wouldn't the client MultiNetworkDriver only need one NetworkDriver? Connect() could probably safely use the first driver from the list.

 

In my case, I created my own wrapper for this case:

Code (CSharp):

1. struct DriverWrapper : IDisposable
2. {
3.     public bool UseMultiNetworkDriver;
4.     public MultiNetworkDriver MultiNetworkDriver;
5.     public NetworkDriver NetworkDriver;
6.     public bool IsCreated => this.UseMultiNetworkDriver ? this.MultiNetworkDriver.IsCreated : this.NetworkDriver.IsCreated;
7.  
8.     public NetworkConnect Connect(...)
9.     {
10.         if(this.UseMultiNetworkDriver)
11.         {
12.             throw new NotSupoortedException();
13.         }
14.         else
15.         {
16.             return this.NetworkDriver.Connect(...);
17.         }
18.     }
19.  
20.     public int Send(...)
21.     {
22.         if(this.UseMultiNetworkDriver)
23.         {
24.             return this.MultiNetworkDriver.Send(...);
25.         }
26.         else
27.         {
28.             return this.NetworkDriver.Send(...);
29.         }
30.     }
31.  
32.     // And other public methods ...
33. }
34.  
35.  
36. struct MySendJob : IJob
37. {
38.     [NativeDisableContainerSafetyRestriction] // <= This attribute need for Unity safety check!
39.     public DriverWrapper Driver;
40.  
41.     // My shared application code for common operation ...
42. }

It may be inefficient, but works

 

Or it may be useful if I can convert NetworkConnection of single NetworkDriver to MultiNetworkDriver's like this:

Code (CSharp):

1. NetworkDriver driver = ...;
2.  
3. var connection = driver.Connect(...);
4.  
5. MultiNetworkDriver multiDriver = ...;
6.  
7. multiDriver.AddDriver(driver);
8.  
9. var connectionForMultiDriver = multiDriver.ConvertConnection(driver, connection);
10.  

 

DriverId seems to be simple and easy to use. It can solve my case.

 

Can I use the same port for UDPNetworkInterface and WebSocketNetworkInterface? In the documentation example you use different ports, but I used the same and I got no errors.