Debugging my new network, when 10 Gigabit Ethernet Runs at 300 Megabits

Re:Debugging my new network, when 10 Gigabit Ethernet Runs a... by iso1631 on Tuesday September 01, 2026 @12:19PM (#49524115)

> Architecturally, dealing with two different address spaces is a complication

I completely agree, which is why dual stack is terrible.

> Have you ever had to merge IPv4 networks from different companies? It's rarely the case that they don't have overlapping ranges.

Dual stack doesn't solve that

> stateful IPv6 firewalling is very different from NAPT in IPv4 because the applications cannot reason about the ports being used

The source port is ephemeral for almost all applications, and I can't think of a good reason it wouldn't be, just legacy crap

I'd love to have an ipv6 only network with NAT66 at the boundary, at home and at work, but while it still requires ipv4 I don't see the point.

[ Parent | on HN ]

Re:Debugging my new network, when 10 Gigabit Ethernet Runs a... by jcgl on Tuesday September 01, 2026 @04:12PM (#49527472)

I'm not advocating dual stack either. Like I said in my other reply to you, I am suggesting IPv4-as-a-service using standard translation technologies and architectures.

[ Parent | on HN ]