Connect command line bugs (multiple) #1873

When using connect command line function it opens two connections to the IP specified...

09/27/12 17:32:31 accepted connection xx:22348 09/27/12 17:32:31 accepted connection xx:22347

It also continues to open connections up to your maximum # of outgoing connections rather than the stated "Connect only to the specified node(s)". The double connection is counted as 1, so if you have the default max of 8 outgoing connections, it'll open 7 more. It doesn't allow incoming connections.

observed behavior in bitcoin-qt and bitcoind (windows)

This message is a bit confusing. The "accepted connection" message only occurs for incoming connections.

Maybe you can provide your exact bitcoin.conf (sans password) and command line being used?

bitcoin-qt.exe -connect=5.x.x.x, or bitcoind -connect=5.x.x.x (when I run it with maxconnections=1, it'll still open two connections to the peer listed under -connect, but no others)

whoops, should have included source log:

09/27/12 17:40:29 connected 5.x.x.x (no port shown) 09/27/12 17:40:29 send version message: version 60002, blocks=200778, us=0.0.0.0:0, them=5.x.x.x:8333, peer=5.x.x.x:8333 09/27/12 17:40:29 connected 5.x.x.x:8333 09/27/12 17:40:29 send version message: version 60002, blocks=200778, us=0.0.0.0:0, them=5.x.x.x:8333, peer=5.x.x.x:8333 09/27/12 17:40:30 receive version message: version 60002, blocks=200778, us=76.x.x.x:22379, them=5.x.x.x:8333, peer=5.x.x.x:8333 09/27/12 17:40:30 receive version message: version 60002, blocks=200778, us=76.x.x.x:22378, them=5.x.x.x:8333, peer=5.x.x.x:8333

You need to pass -nolisten as well if you want no further connections. -connect limits the number of outgoing connections to one, but by design doesn't limit the number of incoming connections.