Pages:
Author

Topic: IPv6 now live on bitcoin network - please test (Read 10685 times)

legendary
Activity: 2226
Merit: 1052
It's funny how at the begining of the internet when they were developing tcp/ip, some of the common critics were "this will not be able to scale up, it will fail".
Now it's the same with Bitcoin.
Cant wait to see were we are in 10 years, and the ridiculous price of it.
We are already on the seventh year Wink
legendary
Activity: 1372
Merit: 1252
It's funny how at the begining of the internet when they were developing tcp/ip, some of the common critics were "this will not be able to scale up, it will fail".
Now it's the same with Bitcoin.
Cant wait to see were we are in 10 years, and the ridiculous price of it.
hero member
Activity: 644
Merit: 500
P2P The Planet!
What's the benefit of using IPv6?

No one needs to OPEN ANY PORTS!!! Thats the benefit. Imagine if everyone could download the bitcoin core and actually contribute to the netowork without having to do anything! Thats how bitcoin should be. If everyone used ipv6 because it was the standard, we would have 50x more connections than we do have at the moment.

Port forwarding is a bitch and there are so many variables that can make port forwarding not work.

What is the point of bumping a three years old thread ?

I'm not trying to actually "privatly converse with him", its a public forum and people like you read this shit as it gets bumped. Maybe it sparks some thought. 7000 views and only ~20 replies; its not about the direct conversation but about the public reading it.

hero member
Activity: 616
Merit: 500
I AM A SCAMMER
What's the benefit of using IPv6?

No one needs to OPEN ANY PORTS!!! Thats the benefit. Imagine if everyone could download the bitcoin core and actually contribute to the netowork without having to do anything! Thats how bitcoin should be. If everyone used ipv6, we would have 50x more connections than we do have at the moment.

Port forwarding is a bitch and there are so many variables that can make port forwarding not work.

What is the point of bumping a three years old thread ?
hero member
Activity: 644
Merit: 500
P2P The Planet!
What's the benefit of using IPv6?

No one needs to OPEN ANY PORTS!!! Thats the benefit. Imagine if everyone could download the bitcoin core and actually contribute to the netowork without having to do anything! Thats how bitcoin should be. If everyone used ipv6, we would have 50x more connections than we do have at the moment.

Port forwarding is a bitch and there are so many variables that can make port forwarding not work.
legendary
Activity: 1072
Merit: 1189
The problem is that I have a dynamic IPv4 and static IPv6. It seems like I don't get any incoming IPv4 connections if I set externalip to an my v6.

You can specify -externalip more than once.
legendary
Activity: 1260
Merit: 1000
Drunk Posts
Fixed by disabling use_tempaddr on the interface, now it only has 1 ipv6.

Can you explain how you did that?

Thanks

sysctl net.ipv6.conf.eth0.use_tempaddr=0
sr. member
Activity: 294
Merit: 250
Fixed by disabling use_tempaddr on the interface, now it only has 1 ipv6.

Can you explain how you did that?

Thanks
full member
Activity: 168
Merit: 100
I already got IPv6 working here but I'll wait until this feature will gets into official release. Compiling just isnt my thing but I support the move to IPv6 Smiley
legendary
Activity: 1260
Merit: 1000
Drunk Posts
How does bitcoind select which ipv6 address to advertise and listen on for incoming connections? I have 3-6 public ipv6 addrs on each computer, but only the one assigned by my dhcpv6 server (via a reservation) has ports open on the firewall.

You may want to look at the new -externalip option. It tries to be smart by default, but if you have several addresses in the same network, it can fail.

The problem is that I have a dynamic IPv4 and static IPv6. It seems like I don't get any incoming IPv4 connections if I set externalip to an my v6.

Fixed by disabling use_tempaddr on the interface, now it only has 1 ipv6.
legendary
Activity: 1072
Merit: 1189
How does bitcoind select which ipv6 address to advertise and listen on for incoming connections? I have 3-6 public ipv6 addrs on each computer, but only the one assigned by my dhcpv6 server (via a reservation) has ports open on the firewall.

You may want to look at the new -externalip option. It tries to be smart by default, but if you have several addresses in the same network, it can fail.
legendary
Activity: 1260
Merit: 1000
Drunk Posts
How does bitcoind select which ipv6 address to advertise and listen on for incoming connections? I have 3-6 public ipv6 addrs on each computer, but only the one assigned by my dhcpv6 server (via a reservation) has ports open on the firewall.
sr. member
Activity: 250
Merit: 250
Glad to hear that Bitcoin has gone IPv6! Unfortunately I don't have IPv6 equipment just yet, to test but soon (I hope...)
full member
Activity: 152
Merit: 100
Nybble, By 'somewhat larger' what do you mean, how many more IPv6s can there be than possible IPv4s?
It's not a matter of how many more IPv6 addresses there are in absolute terms. The database would only store prefixes, so the increase in table entries is just from having individual prefixes for each end-user where currently you might block an entire ISP due to dynamic IPs or high-level NAT. This is the price for avoiding the false positives which are inevitable with IPv4, but not with IPv6. If you already have the end user's IPv4 address in the table, or don't care about the existing false positives, then there is no change in the number of entries.

However, IPv6 addresses are 128-bit rather than 32-bit as in IPv4, so each table entry would go from five bytes to 17 bytes, including one byte in each case for the prefix length. That's assuming you use a flat table with fixed record sizes rather than prefix compression or similar.

NOTE: You could cut the IPv6 record size down to 9 bytes by assuming the prefix is no longer than 64 bits, which is reasonable since each end-user is supposed to have at least a /64, if not a /56 or /48.
legendary
Activity: 1072
Merit: 1189
By somewhat larger, how many more IPv6s can there be than possible IPv4s?

79228162514264337593543950336 times more.
full member
Activity: 205
Merit: 100
Nybble, By 'somewhat larger' what do you mean, how many more IPv6s can there be than possible IPv4s?
full member
Activity: 205
Merit: 100
By somewhat larger, how many more IPv6s can there be than possible IPv4s?
full member
Activity: 152
Merit: 100
Ipv6 is a superset of ipv4, meaning that every ipv4 address corresponds to an ipv6 address, but there are far more ipv6 addresses than can ever be represented by ipv4.

Spam is a problem independent of the protocol used to send it. If you want less of it, encourage a society that does not incentivize such profit seeking behavior.
If IPv6 addresses are a subset of IPv4s, then spammy IPv4 ranges can be blocked without having to look into an insanely large database at every possible spam query.

But I notice by your answer where you say it's not the fault of the technology that this may not be the case. If so then it would be terrible news and allow for tons of spam.
There are actually several ways to encode an IPv4 address as an IPv6 address, though only one--6to4--is in common use. This version associates a /48 IPv6 subnet with each 32-bit public IPv4 address. To filter these you would extract the IPv4 address and look it up in a normal IPv4 database.

However, most IPv6 addresses will not correspond to any IPv4 address. Only networks which have been assigned an increasingly scarce public IPv4 address can use 6to4 as a substitute for native IPv6, and the remaining IPv6 addresses have no connection to the IPv4 namespace. However, each end user is to be assigned a single, contiguous subnet, ranging from a /48 to a /64. Tracking these subnet prefixes in a database for filtering should be no more difficult than tracking individual public IPv4 addresses, and less prone to false positives due to address sharing (dynamic IPs and NAT). The databases would be somewhat larger, due to the longer addresses and more specific targeting, but not unmanageably so.
legendary
Activity: 1526
Merit: 1134
FWIW I have tested this and it worked fine.
legendary
Activity: 1500
Merit: 1022
I advocate the Zeitgeist Movement & Venus Project.


Ipv6 is a superset of ipv4, meaning that every ipv4 address corresponds to an ipv6 address, but there are far more ipv6 addresses than can ever be represented by ipv4.

Spam is a problem independent of the protocol used to send it. If you want less of it, encourage a society that does not incentivize such profit seeking behavior.

If IPv6 addresses are a subset of IPv4s, then spammy IPv4 ranges can be blocked without having to look into an insanely large database at every possible spam query.

But I notice by your answer where you say it's not the fault of the technology that this may not be the case. If so then it would be terrible news and allow for tons of spam.

Superset, not subset.
Pages:
Jump to: