Bitcoin Forum
May 13, 2024, 06:02:31 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: suspicious "connected to self" inboud/outbound connections  (Read 171 times)
hopebit (OP)
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 22, 2018, 06:51:20 AM
 #1

Bitcoin Client Software and Version Number: Bitcoin Core 0.15.1
Operating System: Ubuntu
Description of Problem: I'm running a bitcoin core full node some hours a day since years now and it never got more than 8 connections.
This morning after leaving it run all night there were 10 connections (never happened before).
But two connections were from 127.0.0.1 and looked somehow "symmetrical" meaning that one was "inbound", the other was "outbound", and the amounts of "Sent" and "Received"  bytes were crossed e.g. one was Sent: 107 Kb Received: 185 Kb the other was Sent: 185 Kb Received: 107 Kb

debug.log  contains several entries in the form:
2018-01-22 xxxxxx connected to self at 127.0.0.1:xxxxx, disconnecting

While it nearly looks legit I've never seen this before so I'm wondering has my system been compromised?
1715580151
Hero Member
*
Offline Offline

Posts: 1715580151

View Profile Personal Message (Offline)

Ignore
1715580151
Reply with quote  #2

1715580151
Report to moderator
1715580151
Hero Member
*
Offline Offline

Posts: 1715580151

View Profile Personal Message (Offline)

Ignore
1715580151
Reply with quote  #2

1715580151
Report to moderator
"Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715580151
Hero Member
*
Offline Offline

Posts: 1715580151

View Profile Personal Message (Offline)

Ignore
1715580151
Reply with quote  #2

1715580151
Report to moderator
1715580151
Hero Member
*
Offline Offline

Posts: 1715580151

View Profile Personal Message (Offline)

Ignore
1715580151
Reply with quote  #2

1715580151
Report to moderator
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4316

<insert witty quote here>


View Profile
January 22, 2018, 10:00:52 AM
 #2

I've seen this happen if you use "addnode". Do you have addnode=127.0.0.1 in your bitcoin.conf? or have you used the "addnode 127.0.0.1 add" command in the debug console?

Alternatively, do you have any other wallet software like Armory running on that machine?

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
hopebit (OP)
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 23, 2018, 06:37:29 AM
 #3

Yes I do have a "addnode=127.0.0.1" in my bitcoin.conf

Also I use Armory but I'm pretty sure it wasn't running that day, and when it's Armory, it's just ONE inbound connection at 127.0.0.1:xxxxx and also bitcoin core tells it is Armory

By the way this morning I found it again.    Restarted bitcoin core and it only gets normal inbound connections.
It looks like those two inbound/outbound matching connections appear after some hours of work (i.e. I leave it running while I sleep).




achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
January 24, 2018, 01:04:42 AM
 #4

Yes I do have a "addnode=127.0.0.1" in my bitcoin.conf
Why? Bitcoin Core does not need to connect to itself. Addnod'ing your local node is why this is happening. You don't need to have addnode set to use Armory either.

hopebit (OP)
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 25, 2018, 06:15:31 AM
 #5

Yes I do have a "addnode=127.0.0.1" in my bitcoin.conf
Why? Bitcoin Core does not need to connect to itself. Addnod'ing your local node is why this is happening. You don't need to have addnode set to use Armory either.
OK, I commented out "addnode=127.0.0.1" in my bitcoin.conf and Armory still works.  Don't remember why I had added it but curiously enough there's people on the Armory forum suggesting to add it.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!