Timeline for Are there actual peers with IPv6 addresses?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2017 at 4:08 | comment | added | quadruplebucky | Well, I'm a peer and I'm IPv6. But I don't let anybody know because geth is badly broken WRT ipv6 (seriously, I see requests for "::" hitting my local resolver, what is that?). Peer discovery when ipv6 is preferred in /etc/gai.conf or similar is painful to watch. | |
| Jul 23, 2016 at 13:55 | comment | added | bortzmeyer | Also, to repeat once more that it is not a network issue, but an Ethereum one: on the very same machine, bitcoind has IPv6 peers and I see IPv6 traffic on the Bitcoin port. | |
| Jun 17, 2016 at 22:16 | comment | added | Ivan Frimmel | I don't believe nmap would be able to prove or disprove the issue at hand. That said .. when you ran nmap .. : Did you nmap from an external host .. or nmap internally pointed at an external host? Or just the firewall/gateway ? i.e. What did you nmap specifically and what command line parameters did you use when running nmap? i.e did you do a full port scan , etc ? I am very familiar with nmap .. I am intrigued to know how you managed to figure out a way to completely rule out the firewall/gateway/DHCP server using just this tool, since it shows OPEN/ACTIVE ports .. not "available/closed/firew | |
| Jun 15, 2016 at 15:32 | history | edited | bortzmeyer | CC BY-SA 3.0 |
List of current nodes?
|
| Jun 15, 2016 at 14:59 | history | edited | bortzmeyer | CC BY-SA 3.0 |
Incomingg SSH
|
| Jun 12, 2016 at 7:14 | answer | added | Non-mask-able Interrupt | timeline score: 2 | |
| Jun 11, 2016 at 1:59 | answer | added | Non-mask-able Interrupt | timeline score: 2 | |
| Jun 9, 2016 at 19:34 | history | edited | bortzmeyer | CC BY-SA 3.0 |
More details on IPv6 connectivity of the node
|
| Jun 9, 2016 at 16:33 | comment | added | bortzmeyer | Of course, IPv6, works, I ssh into my machine with it. And, yes, I can ping Google. And there are non-Ethereum IPv6 traffic on this machine (checked with tcpdump). I use neither SLAAC nor DHCPv6 (and I don't see what could be the relationship with my question). For a peer-to-peer system like Ethereum, IPv6 is clearly a big plus, avoiding all the brittle workarounds needed because of NAT. | |
| Jun 9, 2016 at 4:30 | comment | added | Non-mask-able Interrupt | You don't actually mentioned whether your ipv6 stack is working and/or what it is. Can you actually ping -6 google ? Are you using SLAAC or DHCPv6 ? IMHO ipv6 is a massive PITA, I am not sure getting it working gets you anything except "Super Cool Techie Points". | |
| Jun 8, 2016 at 13:51 | history | asked | bortzmeyer | CC BY-SA 3.0 |