Skip to content
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

Expand valid/invalid tests to check v4/v6 separately #37

Open
mahtin opened this issue Apr 17, 2020 · 2 comments
Open

Expand valid/invalid tests to check v4/v6 separately #37

mahtin opened this issue Apr 17, 2020 · 2 comments

Comments

@mahtin
Copy link

mahtin commented Apr 17, 2020

It would be nice to show the valid/invalid URL fetch results with v4 and v6 answers separated. Mainly to confirm both are working or not working. Of course this could also show that no v6 is seen by the browser - which is not the point of this site.

@fuero
Copy link

fuero commented Apr 17, 2020

And it would prevent false positives if people are forced to use a tunnel broker for v6.

@ardje
Copy link

ardje commented Apr 20, 2020

I got a false positive on xs4all that is my main v6 provider, because it falls back to v4 and uses my primary v4 provider tweak. By hand xs4all tests 100% clear (which I expected them to).
wget -4qO - https://valid.rpki.cloudflare.com
{"status":"valid", "asn":25596, "name": "Cambrium BV."}
wget -6qO - https://valid.rpki.cloudflare.com
{"status":"valid", "asn":3265, "name": "XS4ALL Internet B.V."}
So having a {in,}valid-v{4,6} would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants