search

MidLevel / Ruffles

Lightweight and fully managed reliable UDP library.
MIT License
212 stars 28 forks source link

Ruffles transport: client can't connect #2

Closed dosomder closed 5 years ago

dosomder commented 5 years ago

Describe the bug Client can not connect to a host using Ruffles Transport. Error message is "Connection not alive". Firewall on host is disabled, netstat shows port is being listened

To Reproduce Simple project using Ruffles transport

Expected behavior Client connects successfully

Environment (please complete the following information):

OS: Windows 10 & Oculus Quest (Android) Unity Version: 2019.1.6f1 MLAPI Version: 10.13.0 Ruffles: No version shown in Unity, Ruffles.dll says 1.0.0

TwoTenPvP commented 5 years ago

Describe the bug Client can not connect to a host using Ruffles Transport. Error message is "Connection not alive". Firewall on host is disabled, netstat shows port is being listened

To Reproduce Simple project using Ruffles transport

Expected behavior Client connects successfully

Environment (please complete the following information):

OS: Windows 10 & Oculus Quest (Android) Unity Version: 2019.1.6f1 MLAPI Version: 10.13.0 Ruffles: No version shown in Unity, Ruffles.dll says 1.0.0

Does it work with two Windows builds? (on the same machine)

dosomder commented 5 years ago

It did not work in my environment with two seperate Windows machines or with one Windows (host) and one Android (client).

I can try to connect from the same computer tomorrow.

TwoTenPvP commented 5 years ago

This appears to be a Ruffles issue. Connections from Linux to Linux work fine. Android connection to Linux server does not work and I get the same results as you.

dosomder commented 5 years ago

Did you already have a chance to look into this?

TwoTenPvP commented 5 years ago

Nope, will check this asap. Sorry about the delay. MLAPI has been my main focus.

TwoTenPvP commented 5 years ago

Should be fixed in the latest version. It will be updated to NuGet and to the MLAPI Transport shortly.

dosomder commented 5 years ago

Thanks a lot, that's great. I will test it soon

dosomder commented 5 years ago

The final issue for me was that the time on the client and server did not match! Seems UNET does not care about time but Ruffles does. So make sure the time is the same.

TwoTenPvP commented 5 years ago

The time thing is a security feature on Ruffles. It can be turned off.

dosomder commented 5 years ago

Sure I understand that. Would be good if it was documented though. Or if the error message was visible on Android 👍

TwoTenPvP commented 5 years ago

Right, maybe even implement NTP.

Ruffles is WIP. I want to add fragmentation before docs.