hevosenliha wrote:
I'm still struggling with geolink, the first packet I get back from the server has the RST flag set, which geolink (or something) doesn't understand, and continues to wait until it thinks the connection attempt has timed out. Error $81
As I just got my rrnet board to work yesterday I haven't investigated the issue too much.
If the remote server is sending a RST in the first packet then the remote server doesn't like the packet it got from the client to set up the session.
Some options on the server side is - the server is down, or too busy to handle new requests.
Alternatively, sometimes if you reconnect to a server after rebooting, the client ends up choosing the same 'local' port number as the last session, and the server then sees the new SYN request as being part of the last session, and gets confused then ends up reseting the connection.
The 'local' port is somewhat randomised, but there aren't many sources of entropy so the risk of 2 consecutive reboots ending up picking the same 'random' number is actually quite high.