1
Network / Re: TcpSocket connect on Android does not behave correctly
« Last post by Unicode on Today at 08:04:05 pm »Thanks a lot!
Yeah I've had a look into both. The manifest and everything else is pretty much hidden and generated by the compiler App behind the scene. All one does to code a SFML program is to include it and write code for it. No set up or anything required, but therefore also not accessible.
Wireshark also just confirms that nothing actually leaves the device. The TcpSocket seems to decide when seeing my routers ip: Nope, (almost) every other Ip is fine but this one, naah.
I don't think some other permissions or requirements are the problem either, since it perfectly works with the UdpSocket, the TcpListener and the TcpSocket itself even, though just not when calling the connect() method on a (my) public Ip.
I also couldn't find any other post about this issue, although some have mentioned not being able to connect to public Ips via Tcp. Sadly these threads don't go to much into detail and are left abandoned after a short amount of time.
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.
Yeah I've had a look into both. The manifest and everything else is pretty much hidden and generated by the compiler App behind the scene. All one does to code a SFML program is to include it and write code for it. No set up or anything required, but therefore also not accessible.
Wireshark also just confirms that nothing actually leaves the device. The TcpSocket seems to decide when seeing my routers ip: Nope, (almost) every other Ip is fine but this one, naah.
I don't think some other permissions or requirements are the problem either, since it perfectly works with the UdpSocket, the TcpListener and the TcpSocket itself even, though just not when calling the connect() method on a (my) public Ip.
I also couldn't find any other post about this issue, although some have mentioned not being able to connect to public Ips via Tcp. Sadly these threads don't go to much into detail and are left abandoned after a short amount of time.
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.