Dagger2

7 ms·

91.
by Dagger2 6mo ago
Try it and see! 192.168.1.1$ ip link set sit0 up 192.168.1.2$ ip link set sit0 up 192.168.1.2$ ping ::192.168.1.1 64 bytes from ::192.168.1.1: icmp_seq=1 ttl=64 time=0.812 ms (It works over the Internet too, though make sure yo
92.
by Dagger2 6mo ago
We don't. If you're not familiar with IETF drafts, this should give you an idea of the amount of vetting and community support is necessary to get something published as one: https://www.ietf.org/archive/id&#x
93.
by Dagger2 6mo ago
But only if you don't hide everybody away behind routers that require HTTP and a host header.
94.
by Dagger2 6mo ago
Meanwhile, everybody else is using a plastic skull that they carry around with them to pre-chew the inedible food, which is the majority of the food you can get these days. "It's not inedible," they say. "Just let me get
95.
by Dagger2 6mo ago
I'm not sure if I'm misreading you, but a /48 would never be an entire country's v6 allocation. If we're talking home networks, you can reliably expect a /48 to a) not be announced in BGP itself, and b) cover o
96.
by Dagger2 6mo ago
I mean, you own 2002:101:101::/48. You also own ::1.1.1.1, ::ffff:1.1.1.1 and 64:ff9b::1.1.1.1. > If they just gave me 1.1.1.1:: in v6, anyone migrating v4 to v6 would have the same route to me as before, and other changes like DNS6
97.
by Dagger2 6mo ago
German ISPs commonly seem to have an option of their "old" platform (v4 only, no v6) or their "new" one (v6 and CGNATed v4). Maybe you're on their old one? Or maybe they only use it for certain account tiers or some
98.
by Dagger2 6mo ago
Remember that, at one stage, the only two types that were useful were FTP and telnet. HTTP and SSH didn't even exist. Let's not strangle the next big thing that doesn't exist yet before it can even be born, yeah?
99.
by Dagger2 6mo ago
So... how many records and zones? I'm pretty sure I could convey it if I could work out what you were talking about. You went from "you can't even comprehend or convey the massive number of records and zones that are involved
100.
by Dagger2 6mo ago
Copying and pasting was just my attempt to demonstrate how simple a v6 rDNS record is to add. If you were interested in hiring me to write a solution for your ISP, that's fine, but you can't seriously expect random people to do it
101.
by Dagger2 6mo ago
How so? The same working group published e.g. https://www.rfc-editor.org/rfc/rfc1933 , and it's hard to see how v6 could have been designed for backwards compatibility in ways that it wasn't already. I've
102.
by Dagger2 6mo ago
So you'll never have a permanent unchanging v6 address to ID your traffic with. Privacy extensions are orthogonal here; they only affect the suffix, not the prefix. As for dealing with a changing prefix... I'm afraid you'll j
103.
by Dagger2 6mo ago
They went with SIPP, which was one of the backwards-compatible options. It should be kind of obvious from the vast number of backwards compatibility methods available in v6 that v6 is actually backwards compatible... but for some reason a l
104.
by Dagger2 6mo ago
Many mobile ISPs handle v4 via NAT64 or CGNAT. Routers capable of doing those are far more expensive than regular routers, so there tends to be fewer of them. v4 traffic has to travel out of its way to reach one of those routers, whereas v6
105.
by Dagger2 6mo ago
Questions like this suggest that 1&1 do: https://forum.openwrt.org/t/solved-dsl-over-ds-lite-with-isp... I'm less sure about Telekom. For obvious reasons, it's hard to find info in English.
106.
by Dagger2 6mo ago
There is -- you can see the weekday/weekend difference is smaller when people are working from home en masse.
107.
by Dagger2 6mo ago
::203.0.113.42 (tunnels to 203.0.113.42 over v4) 64:ff9b::203.0.113.42 (translates to v4 at nearest NAT64 point) ::ffff:203.0.113.42 (opens a v4 connection via an AF_INET6 socket) What are these then?
108.
by Dagger2 6mo ago
$ dig -x 2606:7100:1:67::26 | grep PTR ;6.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.6.0.0.1.0.0.0.0.0.1.7.6.0.6.2.ip6.arpa. IN PTR Run this, then copy/paste the output into your zone file. Remove the ; and add "example.com."
109.
by Dagger2 6mo ago
If you think v6 isn't backwards compatible then literally anything bigger than 32 bits will never count as backwards compatible for you. The whole point of making the address space bigger is to make it bigger, so what do you expect to
110.
by Dagger2 6mo ago
You're thinking of MAC addresses. Machines don't have permanently-assigned v6 addresses, rather the IP is assigned by whatever network they're currently attached to and will change based on that network's whims, just lik
111.
by Dagger2 6mo ago
It's very common. German ISPs collectively went with DS-Lite, so most of that 77% with v6 have CGNATed v4.
112.
by Dagger2 6mo ago
None of which are any help when connecting to someone who doesn't have those.
113.
by Dagger2 6mo ago
https://datatracker.ietf.org/doc/html/draft-wkumari-not-a-dr...
114.
by Dagger2 6mo ago
Has it been abysmally slow? What's the par time for migrating millions of independent networks, managed by as many independent uncoordinated administrators, to a new layer 3 protocol? We've never done this before at this scale.
115.
by Dagger2 6mo ago
The prod servers work. The app does a DNS lookup, receives something like 64:ff9b::140.82.112.5 and 140.82.112.5 from the ISP's DNS servers, and then connects to 64:ff9b::140.82.112.5. Some part of the ISP network translates the connec
116.
by Dagger2 6mo ago
Privacy extensions are additional addresses that are used by default for outbound connections. You still have the non-privacy address, which doesn't change; put that one into DNS. This approach prevents outbound connections from leakin
117.
by Dagger2 6mo ago
So anybody without the new stack loses access to your site, because they're querying for the A record that you removed. How is this "a gradual migration" or "expanding the address space without inventing a new stack&quot
118.
by Dagger2 6mo ago
So you haven't solved the incompatibility at all. Your v8 requires the client, server and everything between them to support v8 or it has to fall back to using v4, just like v6 does. > There are two groups that should update to v8 i
119.
by Dagger2 6mo ago
So basically, instead of extending the v4 address space you're going to make a new stack and everybody needs to switch to it to be able to communicate with v8. That's the exact thing you said you weren't doing. > If it rec
120.
by Dagger2 6mo ago
Port forwarding requires a port forward rule that matches the inbound connection. If there's no such rule... NAT won't stop the connection, it will just ignore it. If no other aspect of your setup blocks the connection, it'll

More ›