Daniel Dib
@ddib.bsky.social
Network Architect with expertise in network design and architecture, routing, switching, SD-WAN. Runs a blog at lostintransit.se.
I haven't seen many enterprise uses of it. I know there is some proxy auto configuration you can do. You could argue to use it for some collab apps, I guess, but what use cases have you seen?
January 13, 2025 at 2:43 PM
I haven't seen many enterprise uses of it. I know there is some proxy auto configuration you can do. You could argue to use it for some collab apps, I guess, but what use cases have you seen?
Yeah, often you'll see same message on both v4 and v6 which means you have 2x the traffic.
January 13, 2025 at 2:42 PM
Yeah, often you'll see same message on both v4 and v6 which means you have 2x the traffic.
Very good!
Gathering requirements is an interesting process because like you alluded to, it's both about gathering, but also understanding the organization, where they're coming from, and what their current infra looks like.
Gathering requirements is an interesting process because like you alluded to, it's both about gathering, but also understanding the organization, where they're coming from, and what their current infra looks like.
December 13, 2024 at 12:20 PM
Very good!
Gathering requirements is an interesting process because like you alluded to, it's both about gathering, but also understanding the organization, where they're coming from, and what their current infra looks like.
Gathering requirements is an interesting process because like you alluded to, it's both about gathering, but also understanding the organization, where they're coming from, and what their current infra looks like.
Excellent! These are all great things to ask.
December 13, 2024 at 12:19 PM
Excellent! These are all great things to ask.
The containerization movement has been contained.
As always, it turns out that new solutions fit some use cases, some not so much. There is no one size fits all in IT.
It's been interesting to read the posts coming out recently on what people learned by deploying them.
As always, it turns out that new solutions fit some use cases, some not so much. There is no one size fits all in IT.
It's been interesting to read the posts coming out recently on what people learned by deploying them.
November 9, 2024 at 7:22 PM
The containerization movement has been contained.
As always, it turns out that new solutions fit some use cases, some not so much. There is no one size fits all in IT.
It's been interesting to read the posts coming out recently on what people learned by deploying them.
As always, it turns out that new solutions fit some use cases, some not so much. There is no one size fits all in IT.
It's been interesting to read the posts coming out recently on what people learned by deploying them.
I would consider self hosting the norm still for RADIUS. People typically have less on-prem than they used to. Putting stuff in public cloud can also be a way to get access to regions you don't have DCs in, or services you don't have natively, such as LBs.
October 25, 2024 at 12:35 PM
I would consider self hosting the norm still for RADIUS. People typically have less on-prem than they used to. Putting stuff in public cloud can also be a way to get access to regions you don't have DCs in, or services you don't have natively, such as LBs.
Yeah, unless you use RadSec, then it runs over TLS or DTLS.
Exactly, haven't found an easy way of avoiding these type of fragments. Should work with RadSec if it's using TCP, because then you don't need IP to chop the data.
Exactly, haven't found an easy way of avoiding these type of fragments. Should work with RadSec if it's using TCP, because then you don't need IP to chop the data.
October 25, 2024 at 12:34 PM
Yeah, unless you use RadSec, then it runs over TLS or DTLS.
Exactly, haven't found an easy way of avoiding these type of fragments. Should work with RadSec if it's using TCP, because then you don't need IP to chop the data.
Exactly, haven't found an easy way of avoiding these type of fragments. Should work with RadSec if it's using TCP, because then you don't need IP to chop the data.