Astro Hacker News - Free v4 front end for your v6 site

supermatt |next [-]

This is a service that will allow them to intercept your HTTP/S traffic being offered for free by a company that has been legally dead (following bankruptcy) for 12 years: https://datacvr.virk.dk/enhed/virksomhed/33753284

The company number I used to lookup is the one shown in the footer at http://www.netiter.com/

Maybe best to avoid!

EDIT: I don't mean to imply malice - many of us trust our *AAS providers with exactly this daily. But combined with the bankrupt company and overall vibe, I wouldn't be using it.

phoe-krk |root |parent |next [-]

Huh, you are right. https://datacvr.virk.dk/enhed/virksomhed/33753284?fritekst=3... mentions "Opløst efter konkurs".

supermatt |root |parent [-]

Thats a better link than I originally gave so i have updated my comment with it. Thanks.

dgellow |root |parent |previous [-]

Yeah, that looks pretty shady

bayesnet |next |previous [-]

I don’t understand how this was intended to work (not technically but as a “free” service). They want ISPs that don’t support v6 to pay them. Their free trial (for ISP) says

> Your free trial starts when the frontend receives the first connection from your IPv4 range.

> Registering on this page means that we can send you an email to inform you, that your free trial period is about to end. If you do not register and we are unable to find usable contact information for you, then your customers will experience service disruption trying to access sites through this frontend.

But as a website owner using this service I would just want it to work regardless of whether the users ISP is playing ball with Netiter. And there’s the coordination problem with the IPv6 transition in a nutshell I guess.

Also, “Netiter have allocated bandwidth for free trials until the end of 2014,” so I suppose this doesn’t work anymore anyway.

RealCodingOtaku |next |previous [-]

Not sure how this even got to the front page, don't ever do this, you are sending your traffic to someone else who _will_ start phishing attempts once you forget about it.

If you don't want to support ipv4, you should either just host a static page or a text file saying you don't support ipv4, or just don't add an A record.

If you want a frontend to ipv4, just add an A record with your ipv4 address, it's that simple.

theblazehen |previous [-]

How does this work, technically?

Does it try guess the upstream by SNI / Host header and forward the data on? That'd only work for http(s) though.

somat |root |parent |next [-]

Probably. I was trying to figure out if it could be done with an address family translation, and while ip4 is trivially embedded in an ip6 address, going the other way just does not have enough information. but if you know the domain, that is a simple lookup.

The fun part is, with a dns entry like that they could technically get certs issued for peoples domains if they wanted to. I will be charitable and assume it is just a neat relay someone put together, but they could get up to some real shenanigans if they had a malicious bent. Really nothing worse than cloudflare where much their business is ssl hijacking(correction)termination.

phoe-krk |root |parent |previous [-]

Probably no need to guess at all. If it's given a domain, it can perform a DNS lookup for the domain - if its A entry matches, it can tunnel to the IP that the respective AAAA points to. Clever.