Re:IPv6 support for cloning Git repositories from GitHub
by Symbiote on Wednesday August 24, 2022 @02:36PM
(#32583834)
With most people leaving their router switched on all the time, the difference between a static and dynamic IPv4 address from the point of view of the ISP is probably marginal.
Re:IPv6 support for cloning Git repositories from GitHub
by foepys on Wednesday August 24, 2022 @02:47PM
(#32583981)
In Germany all bigger DSL providers still disconnect you once a day and issue new IPs.
Bad for at home hosting, good for privacy.
Re:IPv6 support for cloning Git repositories from GitHub
by Wubdidu on Wednesday August 24, 2022 @03:37PM
(#32584666)
Is that so? At least Telekom doesn't do that for IPv4 anymore. They do have a 24h dynamic prefix for IPv6 though (which feels very weird, considering they stopped doing that for IPv4)
Re:IPv6 support for cloning Git repositories from GitHub
by dark-star on Wednesday August 24, 2022 @07:07PM
(#32587060)
The ephemeral IPv6 addresses are just the IPv6 privacy extensions at work. They're just following RFCs
I guess their router stack provides this for free, while the "Zwangstrennung" (disconnect every 24h) was implemented somewhere on their side. So it's actually easier now for them
Re:IPv6 support for cloning Git repositories from GitHub
by apk17 on Wednesday August 24, 2022 @05:21PM
(#32585938)
Partially. Telekom keeps up the line for months at a time. I guess that is due to telephony being done via VoIP, and they don't want to interrupt your late night calls.
Others, even Congstar (which is a cheap telekom brand), do 24h disconnects with a new v4 address, and no v6 at all.
The DSL I use gives me a fixed v4 and v6 range, but still needs to do the daily disconnects.
Re:IPv6 support for cloning Git repositories from GitHub
by ranger_danger on Thursday August 25, 2022 @07:39AM
(#32592335)
how do you know what ALL of the them do??
Re:IPv6 support for cloning Git repositories from GitHub
by nfriedly on Wednesday August 24, 2022 @02:42PM
(#32583914)
Yeah, that's true enough.
I guess the point I was trying to make is that I think IPv6 is a better solution to their problem of not having enough IPv4 addresses.
Re:IPv6 support for cloning Git repositories from GitHub
by codebje on Wednesday August 24, 2022 @08:55PM
(#32587950)
The difference is typically between a static _public_ IPv4 address or a dynamic _private_ IPv4 address, and CGNAT sharing public IPv4 addresses across subscribers.
Re:IPv6 support for cloning Git repositories from GitHub
by bombcar on Wednesday August 24, 2022 @04:14PM
(#32585150)
For a long time I ran a HE tunnel to get me some sweet static IPv6, but now that my cable company has turned it on I no longer need that (probably should still have it as a backup).
Re:IPv6 support for cloning Git repositories from GitHub
by pelorat on Wednesday August 24, 2022 @05:56PM
(#32586302)
Guess they are sticking with their old equipment, because IPv6 is free in any modern industrial ISP router.
Re:IPv6 support for cloning Git repositories from GitHub
by heywire on Wednesday August 24, 2022 @09:47PM
(#32588401)
I also have Metronet, but haven’t found any compelling reason for a static IP. I use Tailscale for remote access, and though I don’t host anything from home currently, Cloudflare Tunnel should work.
I don't need a static IP. I'd be completely fine with a dynamic IPv4 or even dynamic IPv6. But they don't offer that. Just static IPv4 or CGNAT IPv4. Oh well, some day...