-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 Nodes #84
Comments
My idea for showing IP addresses in the list would then be to show the IPv6, then IPv4 ontop of each other, instead of only IPv4. Or even better, just remove it. |
If IPv6 support is added, I believe it would also be nice to be able to filter for IPv6/IPv4/Dualstack nodes... |
Thank you for the advice. I will try to implement that. However, it doesn't look like it will happen anytime soon because most of the "probers" I have don't have (or explicitly disable) IPv6. My estimate is that it will take around 1 to 2 months before we can implement and carry out testing. |
This commit accept IPv6 nodes submission. When user submit new public node, the server will check IP addresses from given hostname. If host IP addresses doesn't have IPv4, it will be recorded as "IPv6 only" node. Probers that support IPv6 may add `IPV6_CAPABLE=true` to the `.env` file. Please note that this feature still experimental and may not being merged to the main branch.
Hi @juliaszone , I've change the code to accept IPv6 node and enabling IPv6 on one of the probers (linode). Can you please try add your nodes to see how it goes? |
I tried to add it by domain, but it says it already exists. Those still show up as an IPv4 despite being dual stack. I would show IPv6 then IPv4 address in the list like so (edited in browser devtools): I have tried adding IPv6 addresses, and it worked. They can be removed now. A nice feature for dualstack nodes would be to crawl it on IPv4 and IPv6. If either is broken, then display it like this: |
This commit add IsIPv6Only function inside `internal/ip` package and moving `geo` package from `internal/geo` to `internal/ip/geo`. Although it increases server resource usage, checking hostname to IP is required every time the prober sends a report so that the `ipv6_only` record in the database is not up-to-date. Previously, this feature did not exist.
Wraps IPv6 host in square brackets, returns as-is for domain names or IPv4 addresses.
If you have more than one A and/or AAAA DNS record, the current cycle and the next cycle may display different IP address. It depends on the first IP address obtained from the hostname lookup. Therefore, I removed the IP address information from the table (but still exists from API call result) and replaced it with information about whether the host only supports IPv6 or not (61cc98e). So, if the submitted node is IPv6 address (or domain name that doesn't have IPv4) it will show IPV6 only info. Speaking of IP addresses, maybe I could add an "IP lookup" button or something like that so that visitors can get that information only when needed. But I can't promise that it will be available anytime soon.
I wouldn't implement something like that. Performing RPC calls for every A/AAAA record for each node would take many times more resources than it needs to.
Sure, will do. Thanks for your help! |
I think you're right Julia. For some reason, I need to shows IP addresses of each nodes. ( issue #105 ) |
For future use investigations about "suspicious" nodes. #105
Hi, I run 2 IPv6 enabled nodes and I saw that only IPv4 is supported by the website.
Are there any plans for IPv6 support?
The text was updated successfully, but these errors were encountered: