|
Title: no IPv6 peers connecting to my node Post by: Geremia on July 02, 2015, 02:36:07 AM `getnetworkinfo` says IPv6 is working on my node:
Code: {(cf. the related Bitcoin StackExchange question (https://bitcoin.stackexchange.com/q/38365/4334)) Title: Re: no IPv6 peers connecting to my node Post by: KriszDev on July 02, 2015, 07:36:29 AM The proxy ip is ipv4 and you can't make ipv6 through ipv4.
Title: Re: no IPv6 peers connecting to my node Post by: Newar on July 02, 2015, 08:49:03 AM Can you use addnode= adding one manually? They are some listed on https://getaddr.bitnodes.io/.
Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 02, 2015, 02:04:21 PM The proxy ip is ipv4 and you can't make ipv6 through ipv4. I'm not trying to. I don't know why it shows my Tor proxy in the IPv6 section. It's shown this before, even when I've had IPv6 peers.Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 02, 2015, 02:07:54 PM Can you use addnode= adding one manually? They are some listed on https://getaddr.bitnodes.io/. Yes, I can add them, but `getaddednodeinfo true` returnsCode: "connected" : "false" Title: full `getnetworkinfo` output Post by: Geremia on July 02, 2015, 02:17:56 PM Here's the full output of `getnetworkinfo` (with my IPv6 address Xed out for privacy)
Code: {I have Code: onion=127.0.0.1:9050 Title: Re: no IPv6 peers connecting to my node Post by: Foxpup on July 03, 2015, 01:21:48 AM I have Um, because that's what the proxy option is for? If you want to use Tor just to reach .onion nodes, and not as a proxy for other traffic, use the onion option instead, eg, onion=127.0.0.1:9050. (Naturally, connections to non-onion nodes will not be anonymised if you do this.)Code: proxy=127.0.0.1:9050 Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 03, 2015, 03:21:02 AM I have Um, because that's what the proxy option is for? If you want to use Tor just to reach .onion nodes, and not as a proxy for other traffic, use the onion option instead, eg, onion=127.0.0.1:9050. (Naturally, connections to non-onion nodes will not be anonymised if you do this.)Code: proxy=127.0.0.1:9050 Code: onion=127.0.0.1:9050 I'm confused about "--onion" and "--proxy". Are these options for incoming connections, outgoing connections, or both? Title: Re: no IPv6 peers connecting to my node Post by: Foxpup on July 03, 2015, 04:10:45 AM Sorry, I meant to say: It shouldn't. I can't explain that. Or why (as I've just noticed) you've got 44 connections apparently over Tor. That can't be right.Code: onion=127.0.0.1:9050 I'm confused about "--onion" and "--proxy". Are these options for incoming connections, outgoing connections, or both? Both, although you obviously can't get incoming connections over IPv4/IPv6 without a public IP address, which you don't have if you're using Tor as a proxy. The only way you can get incoming connections through Tor is if you're hosting a hidden service.Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 03, 2015, 04:44:25 AM Or why (as I've just noticed) you've got 44 connections apparently over Tor. No, I only have 2 Onion nodes connected. The rest are IPv4.Title: Re: no IPv6 peers connecting to my node Post by: Foxpup on July 03, 2015, 05:04:28 AM No, I only have 2 Onion nodes connected. The rest are IPv4. If your IPv4 network has incoming connections, you're definitely not using Tor as an IPv4 proxy. As I said, I don't know why it says you are.Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 04, 2015, 03:04:51 AM No, I only have 2 Onion nodes connected. The rest are IPv4. If your IPv4 network has incoming connections, you're definitely not using Tor as an IPv4 proxy. As I said, I don't know why it says you are.Code: min=1 Title: Re: no IPv6 peers connecting to my node Post by: Foxpup on July 04, 2015, 02:38:48 PM This may help; my bitcoin.conf file contains these flags: Ah. I think listen and discover allows connections to bypass the proxy (I'm not 100% sure how these options interact).Code: min=1 Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 04, 2015, 05:41:34 PM This may help; my bitcoin.conf file contains these flags: Ah. I think listen and discover allows connections to bypass the proxy (I'm not 100% sure how these options interact).Code: min=1 Code: -listen Accept connections from outside (default: 1 if no -proxy or -connect) Also, I have to specify "--discover=1", otherwise I get this error in my debug log: Code: AppInit2 : parameter interaction: -proxy set -> setting -discover=0 Title: Re: no IPv6 peers connecting to my node Post by: Geremia on July 04, 2015, 06:18:31 PM The issue was that bitcoind was discovering my wrong IPv6 address. (It mistook my link IPv6 address for my public one.) I turned off discover and set my IPv4 and IPv6 addresses manually with "--externalip".
|