I'd be so much more interested in ipv6 if ISPs would just hand out a stable prefix. as it is ipv6 makes very little sense to me
Building a Mostly IPv6 Only Home Network
71–80 of 106 posts
Re: Building a Mostly IPv6 Only Home Network
#72Earlier quoted context omitted.
Well yes, a stateful NAT is stateful. But as that article notes: > For most workloads, there’s plenty of headroom in the table and this will never be an issue. And yes, if you're doing thousands of connections per second then you should evaluate things more carefully for performance, but again... That's rather a lot.
It's interesting that you'd think that. Connection table of a single IP is as high (by default ) as 16,383[0]. I've hit this limit personally, and due to limitations in stateful firewalling we had to move to stateless filters inside our network equipment instead. [0]: https://learn.microsoft.com/en-us/troubleshoot/windows-clien...
It's interesting that I agree with the article that you linked?
I'm not contesting that it's completely possible to hit the limits in play, but 16k connections (per IP) is high enough that I don't think that's a common problem, even in public-facing web services. Granted, I suspect the services I've run professionally all dealt with it by making it the problem of a load balancer in front of the application and internal network, but... you probably have that anyways, so I'm still not seeing the problem.
Re: Building a Mostly IPv6 Only Home Network
#73Earlier quoted context omitted.
It's interesting that you'd think that. Connection table of a single IP is as high (by default ) as 16,383[0]. I've hit this limit personally, and due to limitations in stateful firewalling we had to move to stateless filters inside our network equipment instead. [0]: https://learn.microsoft.com/en-us/troubleshoot/windows-clien...
It's interesting that I agree with the article that you linked? I'm not contesting that it's completely possible to hit the limits in play, but 16k connections (per IP) is high enough that I don't think that's a common problem, even in public-facing web services. Granted, I suspect the services I've run professionally all dealt with it by making it the problem of a load balancer in front of the application and intern…
it’s interesting because I think youve internalised the constraint and built mechanisms around it rather than engaging directly with it, subconsciously.
Re: Building a Mostly IPv6 Only Home Network
#74Earlier quoted context omitted.
Don't use DCHPv6 at home. I tried: you will hate your life, lots of stuff doesn't support it. Android specifically has zero support for it, google says it never will. Use SLAAC. It just works.
How do you handle internal DNS? I'd really like `curl http://mylaptop.internal ` (or so) to work; that's easy with DHCP.
Every device on my LAN handles mDNS, or at least the ones I SSH to do.
Re: Building a Mostly IPv6 Only Home Network
#75Earlier quoted context omitted.
Don't use DCHPv6 at home. I tried: you will hate your life, lots of stuff doesn't support it. Android specifically has zero support for it, google says it never will. Use SLAAC. It just works.
How do you handle internal DNS? I'd really like `curl http://mylaptop.internal ` (or so) to work; that's easy with DHCP.
Nothing is stopping your router which does RA to also work in tandem with an internal dns server that can do hostnames for you mapped to slaac addresses.
Re: Building a Mostly IPv6 Only Home Network
#76Do you actually own that /48? The problem with using the globally routable addresses internally is that your public /48 might change in the future, and and that will force you to change a bunch of internal stuff. I have my router set up to advertise two /64 prefixes on each LAN subnet: one from fddd:deca:fbad::/56* that I use for all internal communication, and one from 2001:5a8:xxxx:xxxx::/56 that is only used for t…
> * You're really supposed to pick a random prefix in fd00::/8, but uniqueness only matters if you intend to merge networks with somebody else later, I care more about it being easy to remember. If you don't care about collision resistance, why didn't you pick fd00:: ? That's way easier to remember than that jumble of letters you selected. It's actually my go-to subnet when someone claims that local-only IPv6 address…
You can write it as 10.1 though
Re: Building a Mostly IPv6 Only Home Network
#77I can’t understand benefits of having ipv6. The only one is public ips but rest is just headache. In my home network I specify disabled v6 everywhere.
Public IPs are a huge benefit and are enough to justify the switch. And there really aren't any headaches in this day and age with IPv6. Once you set it up it works just fine.
Re: Building a Mostly IPv6 Only Home Network
#78I'd be so much more interested in ipv6 if ISPs would just hand out a stable prefix. as it is ipv6 makes very little sense to me
That depends very much on your ISP. Mine (Comcast) does give out a stable prefix. It's not guaranteed to be static forever, but in practice it never changes unless I release it from my router or on the rare occasion they replace their network hardware.
Re: Building a Mostly IPv6 Only Home Network
#79Earlier quoted context omitted.
> * You're really supposed to pick a random prefix in fd00::/8, but uniqueness only matters if you intend to merge networks with somebody else later, I care more about it being easy to remember. If you don't care about collision resistance, why didn't you pick fd00:: ? That's way easier to remember than that jumble of letters you selected. It's actually my go-to subnet when someone claims that local-only IPv6 address…
You can write it as 10.1 though
You could, sure. You shouldn't, because not only is it nonstandard, roughly noone writes it that way.
Without consulting documentation or otherwise querying external memory, tell me what is 10.1.1?
Re: Building a Mostly IPv6 Only Home Network
#80Earlier quoted context omitted.
How do you handle internal DNS? I'd really like `curl http://mylaptop.internal ` (or so) to work; that's easy with DHCP.
Nothing is stopping your router which does RA to also work in tandem with an internal dns server that can do hostnames for you mapped to slaac addresses.
I'm not sure I follow? AIUI, RA lets you tell hosts about a DNS server, and an internal DNS server could have AAAA records pointing at SLAAC addresses, but how would it know what hostnames go to those addresses?