Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for 1.4.0 version #17

Open
imerr opened this issue Jun 10, 2021 · 1 comment · May be fixed by #23
Open

Support for 1.4.0 version #17

imerr opened this issue Jun 10, 2021 · 1 comment · May be fixed by #23
Labels

Comments

@imerr
Copy link
Contributor

imerr commented Jun 10, 2021

Hey,
I'm currently in the process of evaluating using GNS as a network backend
Your wrapper works well (thanks!), but we're having some issues getting the whole thing to run on linux and I think I've tracked it down to a 1.3.0 compatibility issue. Seems to work perfectly with 1.2.0

The issue presents itself as follows:
1.3.0:

$ mono GNSTest.exe
Client 65879239 -> None
Client 65879239 -> 5003

(5003 is a new server timeout status)

1.2.0:

$ mono GNSTest.exe
Client 1015838903 -> Connecting
Client 1015838903 -> Connected
Client connected - ID: 1015838903, IP: 192.168.0.x
[...]
  • Connecting to a windows-based server, either localhost or a different machine on lan works fine (WAN likely too)
  • Connecting to a linux-based server (as a different machine on LAN) does not work, the server gets/initialized the connection in the "None" state and then times out after the x second connection timeout
  • Connecting to the "example_chat" server running on the same linux machine works
  • Tried 1.3.0 libraries built on the same linux machine and ci-built ones, with dependencies from the os package manager (apt) and ones built from source

I've had a browse through the release notes & changes, but there isn't anything obvious I could spot to cause the issue. I'm just using the example server code from the readme (with/without span) to reproduce it

Any chance you could have a look at this or point me towards how to investigate this further?

@nxrighthere
Copy link
Owner

I haven't touched 1.3.0 yet, only 1.2.0 is supported at the moment.

@nxrighthere nxrighthere changed the title 1.3.0 linux issues Support for 1.3.0 version Jun 10, 2021
@nxrighthere nxrighthere changed the title Support for 1.3.0 version Support for 1.4.0 version Jan 29, 2022
@ifshuaishuai ifshuaishuai linked a pull request Oct 27, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants