Bitcoin Forum
May 08, 2024, 10:40:31 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Core: Network settings tab options  (Read 178 times)
bhku (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
March 15, 2018, 06:26:32 PM
Last edit: March 15, 2018, 07:29:43 PM by bhku
 #1

Hi,

I want Bitcoin Core to connect to Internet through TOR network.

I have some options in network settings tab:

1) Map port using UPnP
2) Allow incoming connections
3) Connect through SOCKS5 proxy (default proxy)
4) Use separate SOCKS5 proxy to reach peers via Tor hidden services

Main question is what's difference between 3rd and 4th options? Can i just use 3rd option with 127.0.0.1 port 9050 (it's TOR port)?
Or i need to use only 4th option for TOR (with the same settings: 127.0.0.1 port 9050)?
Or, maybe, i need to use both 3rd and 4th (both with 127.0.0.1 port 9050)?

Also, i want to ask you about 1st and 2nd option. For what purpose they are?

Do i need to disable incoming connections for maximum security?

Thank you so much!
1715164831
Hero Member
*
Offline Offline

Posts: 1715164831

View Profile Personal Message (Offline)

Ignore
1715164831
Reply with quote  #2

1715164831
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715164831
Hero Member
*
Offline Offline

Posts: 1715164831

View Profile Personal Message (Offline)

Ignore
1715164831
Reply with quote  #2

1715164831
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
March 15, 2018, 10:18:43 PM
 #2

Main question is what's difference between 3rd and 4th options?
The 3rd option proxies all of your traffic. The 4th option only proxies TOR connections. So setting the 4th option allows you to connect to node's that are listening over TOR while connections to IPv4 and IPv6 nodes happen over your normal connection. The 3rd option will proxy ALL connections.

Can i just use 3rd option with 127.0.0.1 port 9050 (it's TOR port)?
Yes.

Also, i want to ask you about 1st and 2nd option. For what purpose they are?
The first option enables UPnP which will automatically tell your router (if it supports UPnP) to allow connections through to Bitcoin Core's P2P port. Typically routers will block such connections. Such routers will need port forwarding enabled for the P2P port. UPnP does that automatically.

The 2nd option disables the incoming connections entirely.

Do i need to disable incoming connections for maximum security?
No. The security risk is the same.

bhku (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
March 15, 2018, 11:05:21 PM
 #3

Main question is what's difference between 3rd and 4th options?
The 3rd option proxies all of your traffic. The 4th option only proxies TOR connections. So setting the 4th option allows you to connect to node's that are listening over TOR while connections to IPv4 and IPv6 nodes happen over your normal connection. The 3rd option will proxy ALL connections.

Can i just use 3rd option with 127.0.0.1 port 9050 (it's TOR port)?
Yes.

Also, i want to ask you about 1st and 2nd option. For what purpose they are?
The first option enables UPnP which will automatically tell your router (if it supports UPnP) to allow connections through to Bitcoin Core's P2P port. Typically routers will block such connections. Such routers will need port forwarding enabled for the P2P port. UPnP does that automatically.

The 2nd option disables the incoming connections entirely.

Do i need to disable incoming connections for maximum security?
No. The security risk is the same.

Thank you! For what purpose i need incoming connections to my wallet?
ranochigo
Legendary
*
Offline Offline

Activity: 2968
Merit: 4168



View Profile
March 16, 2018, 01:49:56 AM
 #4

Thank you! For what purpose i need incoming connections to my wallet?
Solely for the purpose of allowing people to connect to your node.

The connections are usually bi-directional which means that you are still sending and receiving transactions and blocks to all of your connections, including the ones that you connect to. If you were to allow people to connect to your node, you're helping the network even more. Normal users don't have to do this unless they want to help the network by allowing more people to connect to their node.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
crypto_sec_please
Copper Member
Newbie
*
Offline Offline

Activity: 8
Merit: 1


View Profile
March 16, 2018, 11:06:23 AM
 #5

Hi,

I want Bitcoin Core to connect to Internet through TOR network.

I have some options in network settings tab:

1) Map port using UPnP
2) Allow incoming connections

[..]

Also, i want to ask you about 1st and 2nd option. For what purpose they are?

Do i need to disable incoming connections for maximum security?

Thank you so much!

To answer the remaining question, (1) allows your client to talk to your network device(s) such as gateway router/modem on how to clear a path for the data (identify one another and agree on connection settings like ports) without you having to manually configure them.

(2) Allows your node to support the network fully by allowing other nodes to initiate connections to 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!