search

beyond-all-reason / BYAR-Chobby

Currently used legacy lobby for BAR, for the new lobby development see https://github.com/beyond-all-reason/bar-lobby
57 stars 68 forks source link

Connecting to server fails behind NAT64 #513

Open d5xtgr opened 9 months ago

d5xtgr commented 9 months ago

An IPv4 host can log into the server even when behind a NAT44 gateway as in most home LANs. However, an IPv6-only host (using NAT64 and DNS64) fails when I click the login button with an error message naming the host and port (server4.beyondallreason.info and 8200, respectively).

I haven't identified any workaround.

p2004a commented 9 months ago

At the moment a bunch of BAR services are running on IPv4 only, and I'm not even sure the code in some places is even ready for IPv6.

FIr3baL commented 8 months ago

At the moment a bunch of BAR services are running on IPv4 only, and I'm not even sure the code in some places is even ready for IPv6.

I just tried it purely out of curiosity and switched my Router (Fritz!Box 7590) to "IPV6 only mode" using a win10 machine. Can't reach:

  1. https://github.com
  2. https://www.beyondallreason.info
  3. Bar-Launcher hangs forever at trying to download the updates But i CAN access google.de and browse some fritzbox help websites!

So, i don't know how you test this, but for me it doesn't even load into chobby, when i start from normal bar-launcher.

That said, i'm pretty sure the engine itself (recoil) is capable of ipv6 only. For Teiserver i believe it should be possible with some config tuning. (Didn't test it)