Oh I didn’t catch that part, that’s even better than how I understood it, thanks so much for clarifying!

This is very cool but all the machines I would use this on are headless with no GUI installed. Womp womp for me.

Sometimes all we really want or need is the equivalent of comfort food in television format.

When you do it for work, you log what you have changed each time you make a change to try to fix it, and you log what you revert, so you can keep track of what you have tried, what worked, and what didn’t and have a clearer idea of what the solution was.

Sometimes it really does take a while to nail down though, and sometimes it isn’t entirely clear why what worked worked. Especially if you’re a junior network engineer without as much experience.

Nobody:

Absolutely No One:

EMH:

No Farts, Just Sharts

#bloblife

That’s the way to do it, smart planning. I’m glad you were able to make it happen even if it set you back more than you had hoped.

I only wish I had money to get in before prices bump up. 😭

Being poor sucks.

I had never heard of this so went looking. Super useful stuff here!

A link for anyone interested: https://thingino.com/

I am Error.

*crying in IPv4 subnet calculations

IPv4 has DHCP. Is there something in the way of applying a similar solution to IPv6?

That in itself is implemented a few different ways, and each one is more useful dependent on your use-case, but these also have very little to do with how your ISP hands out the IP to your modem. When you get an IP handed out to your modem by your ISP, it’s often not being handed out by DHCP but an entirely different technology purpose built for whatever medium (cable/DSL/fiber) is actually going into your modem, so knowing their implementation is still important. Things work a little differently at enterprise-level. Although you’re not wrong that eventually there could be routers with auto-configuration based on which type of IPv6 network the router detects, there just currently aren’t any that I know of.

But if you’re interested in the modern equivalents of DHCP you should look into SLAAC vs. DHCPv6 which are similar but oh so very different.

Thanks for holding us back, champ.

I guess fuck stateful packet inspection as a tool or anything.

NAT isn’t a security measure you know that right?

Further, there’s often not clear documentation from your ISP which of the ways they have it set up!

It’s like the opposite of Dr. House’s “It’s never Lupus.”

“It’s always DNS.”

I feel like we really need to speed up the embrace of IPv6 to solve this kind of issue. DNS is helpful to humans sure but a lot of these outages are triggered by services not being able to reach one another because they’re hard-coded to a DNS to avoid shifting IPs due to things like NAT.

It feels like we could do an end-run around a lot of this by having a failover to an IPv6 address that is associated with the DNS entry if the DNS fails. Kind of like you generally have multiple DNS servers in sequence in case one of not-responsive, what if, at the service-level we stopped relying on DNS so much and instead used the benefits of IPv6 to not have services fail when DNS does? DNS should be for humans not for computers especially not in a world where IPv6 exists.

(someone who is more familiar with the ins-and-outs of IPv6 is welcome to tell me if and why I am wrong in thinking this)

Not enough Biggowron

“Hey, I need a transfer to 172.20.100.93.”

“I’m sorry sir, there’s no route to that host.”

They can never escape the normie-ness since Arnold Rimmer was the prototype.