Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles

Nuclear Throne Together

An online multiplayer mod for Nuclear Throne. · By YellowAfterlife

Cannot connect to each other when playing under wine/linux

A topic by L29Ah created Aug 31, 2018 Views: 85 Replies: 3
Viewing posts 1 to 2

Tried using a VPN with the same results so it's not a networking problem. The connecting player briefly shows up in the lobby and then leaves. The connecting player's UI says "connection timeout". Console says:


[dp:State] [8/30/2018 9:52:07 PM +1172] Created [u-5 @192.168.7.20:60663] [dp:State] [8/30/2018 9:52:07 PM +1172] Auth from [u-5 @192.168.7.20:60663] [dp:State] [8/30/2018 9:52:07 PM +1172] Issuing slot #1 to [u2 @192.168.7.20:60663] [dp:State] [8/30/2018 9:52:14 PM +1383] [u2 @192.168.7.20:60663] is leaving @ 0. [dp:State] [8/30/2018 9:52:14 PM +1383] Closing [u2 @192.168.7.20:60663]


tcpdump says:

22:16:11.523347 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:11.543361 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 30
22:16:11.543497 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 17
22:16:11.543638 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 27
22:16:11.544042 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 22
22:16:11.544154 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 17
22:16:11.544293 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 20
22:16:11.544393 IP 192.168.116.105.27012 > dsl-trebng11-54f90d-78.dhcp.inet.fi.51110: UDP, length 16
22:16:12.049280 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:12.549296 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:13.049287 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:13.617921 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:14.079276 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:14.649146 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:15.149626 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:15.646537 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:16.219291 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:16.708155 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:17.284956 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:17.775652 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:18.299588 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 57
22:16:18.513782 IP dsl-trebng11-54f90d-78.dhcp.inet.fi.51110 > 192.168.116.105.27012: UDP, length 20

Connecting player's console says:

[dp:State] [8/30/2018 9:37:52 PM +677] Created [u-5 @nbl.hopto.org:30046] [dp:State] [8/30/2018 9:37:52 PM +677] Connecting to nbl.hopto.org:30046... [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Created [u-5 @84.249.13.78:30046] [dp:State] [8/30/2018 9:37:52 PM +683] Closing [u-5 @84.249.13.78:30046]

Any ideas what might be wrong with our setup?

Ignore the different addresses/timestamps plz since we were trying with different configurations and getting the same results every time.

Developer(+1)

Does the same happen if you connect to yourself over localhost / could you get me dumps of the actual packets? It seems like the client is considering the connection to be broken as soon as they get the first packet.

Actually, we found out what's wrong. When one connects to a hostname it doesn't work, but when one uses the ip address, it works.

Developer (1 edit) (+1)

Oh, that's possible - only the other day I had a conversation with someone about how low-level UDP libraries usually do not do URL resolution+caching automatically, and... well, I guess the one I used here doesn't either.

I'll see if this can be addressed later.