Hello - (new to Stellar) I've compiled/setup stellar-core on my VM, and am using a fairly stock .cfg file (based on the default stellar-core_testnet.cfg). When I run stellar, I am seeing the following in the logs -
2018-07-27T17:40:01.867 GASCR [Overlay INFO] New connected peer 90.217.85.183:11625
2018-07-27T17:40:01.938 GASCR [Overlay INFO] New connected peer 193.104.63.62:11625
2018-07-27T17:40:02.999 GASCR [Overlay INFO] New connected peer 174.24.113.58:11625
........
2018-07-27T17:40:03.868 GASCR [Overlay WARNING] idle timeout
2018-07-27T17:40:03.871 GASCR [Overlay INFO] Dropping peer GAAAA@90.217.85.183:11625
2018-07-27T17:40:03.874 GASCR [Overlay ERROR] TCPPeer::drop shutdown socket failed: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. [tcppeer.cpp:195]
2018-07-27T17:40:03.888 GASCR [Overlay WARNING] connectHandler error: The I/O operation has been aborted because of either a thread exit or an application request.
.....
This pattern repeats over and over, as it finds new peers, and then drops them.
Question - is there something simple I might have configured wrong on my side? I've done telnet testing to confirm that my machine can accept TCP 11625 from the outside. Interestingly, none of the peers seem to accept a telnet session...
