Live data from Hacker News

eBPF Mystery: When is IPv4 not IPv4? When it's pretending to be IPv6

blog.gripdev.xyz

31–35 of 35 posts

Re: eBPF Mystery: When is IPv4 not IPv4? When it's pretending to be IPv6

#31
post #13

Earlier quoted context omitted.

It's a mess when you learn there are also 6in4, 6rd and teredo...

Out of all of those, 6rd is actually a success, though 6rd is built on top of 6to4. Funnily enough, the first ISP to apply 6rd has actually inverted its network and is now using 4rd to provide IPv4 to some of its customers. Not just that, but also 4in6 (IPv4 in modern networks) and 4over6 (an extension to DS-Lite), and don't forget 6in4 being called SIT in an early draft, followed by SIIT being used in another protoc…

6in4 is just a basic "put the v6 packet directly into the payload of a v4 packet" tunnelling approach. It's a sensible way of tunnelling one protocol over another (and it's the same thing as 4in6, just the other way around).

HE's tunnels are 6in4, and 6to4 and 6rd are automatically-configured 6in4 tunnels.

Re: eBPF Mystery: When is IPv4 not IPv4? When it's pretending to be IPv6

#32
post #2

I think of that as the opposite - an IPv6 socket pretending to be IPv4 in order to route to an IPv4 endpoint.

Depends on the vantage point: For a firewall that's ip4 hiding in ip6. For a router, that's ip6 accomodating ip4.

::ffff:0:0/96 is for representing v4 addresses in v6 APIs. You shouldn't even see it on the wire at all, but if you do it's just a regular v6 bogon range and not anything to do with v4, so it doesn't get or need any special handling in firewalls or routers.

Re: eBPF Mystery: When is IPv4 not IPv4? When it's pretending to be IPv6

#34
post #28
post #26

Earlier quoted context omitted.

maybe it just means those a pretty worthless certs focused on training you to shill for cisco instead of teaching you actually important network concepts...

No, it means I didn't spend any time on a random specification that will rarely be seen in a production environment. I feel I gained a lot of networking knowledge.

Not sure if you can call it “rarely”; it is very common in application programming. But it is never sent over the wire (unless there is some very buggy IP stack somewhere), which is probably why you did not encounter it in entry-level router/switch certifications.
Post reply on HN