3 ms·
I'd gladly listen about the difficulties of setting up enterprise networks! No irony; listening to experts is always enlightening. BTW a homelab often tries to
by nine_k 10mo ago
I'd gladly listen about the difficulties of setting up enterprise networks! No irony; listening to experts is always enlightening.
BTW a homelab often tries to imitate more complex setups, in order to be a learning experience. Can these difficulties be modelled there?
- tguvot 10mo agocompany where i work has deployments across the world with few hundreds of thousands of hardware hosts (in datacenters), vms and containers + deployments in a few clouds. also a bunch of random hardware from multitude of vendors. multiple lines for linking datacenters and clouds. also some lines to more specific service providers that we are using. all of it ipv4 based. ipv6 maybe in distant future somewhere on the edge in case our clients will demand in. inside our network - probably not going to happen
- nine_k 10mo agoI find this completely fine. I don't see much (if any) upside in migrating a large existing network to anything new at all, as long as the currently deployed IPv4 is an adequate solution inside it (and it obviously is). Public-interfacing parts can (and should) support IPv6, but I don't see much trouble exposing your public HTTP servers (and maybe mail servers) using IPv6, because most likely your hosting / cloud providers do 99.9% of it already, out of the box (unless it's AWS, haha), and the rare remaining cases, like, I don't know, a custom VPN gateway, are not such a big deal to handle.
- tguvot 10mo agovast majority of our stuff is self hosted. http servers in a way are the least important way for our clients to work with us. amount of work to support ipv6 on the edge will be very big and none of our clients asked for it as far as i know. the only time we discussed it, it's when we were getting fedramp certification. because of this https://www.gsa.gov/directives-library/internet-protocol-version-6-ipv6-policy-1 https://www.gsa.gov/directives-library/internet-protocol-ver...
- iov6throwaway 10mo agoI ran network team at an organization with hundreds of thousands hardware hosts in tens-of-megawatts large data centers, millions of VMs and containers, links between data centers, links to ISPs and IXes. We ran out of RFC1918 addresses at around 2011-2012 and went IPv6-only. IPv4 is delivered as a service to nodes requiring it via an overlay network. We intentionally simplified network design by doing so. This is neither hard nor expensive.
- tguvot 10mo agodifferent environments. for us at this point of time it will be expensive without added benefit.
- bigfatkitten 10mo agoThis is one of the only scenarios in which it’s actually easy.