1
Network / Re: TcpSocket connect on Android does not behave correctly
« Last post by eXpl0it3r on June 02, 2024, 10:34:03 pm »The TcpSocket seems to decide when seeing my routers ip: Nope, (almost) every other Ip is fine but this one, naah.Can you describe your setup again in more detail?
... just not when calling the connect() method on a (my) public Ip.
If you're trying to call your own public IP within the same network and it doesn't work, then this might actually just be a NAT loopback issue. Your router may need to be configured to directly route packets back into the network that address itself.
Regarding Wireshark, if you're tracking the network from your own device, makes sure you're scanning the whole network and if you're unlucky, you might not even see the wifi chatter on the network.
Could I somehow see where the status Disconnected comes from exactly? I could only pinpoint it down to the two calls ::connect() and select() in the TcpSocket connect() method but can't find where those themselves are coming from.You could try to get more information from the specific that is mapped in SFML: https://github.com/SFML/SFML/blob/2.6.x/src/SFML/Network/Unix/SocketImpl.cpp#L89