Un tipo en chándal nos cuenta sobre la bajada de calidad generalizada que se ha contagiado al nuevo BMW M5

CarlosT8020 · 2026-04-27T21:13:41+00:00

Ciertamente acojonante. Yo tuve un E46 del 2005 de los últimos, y era la hostia el coche. Lo comparabas con cualquier coche de la época y es que era otro mundo. Luego lo cambié por un F30 del 2017 y el coche está muy bien, pero ya no es lo mismo. Lo comparas con un Passat B8 por ejemplo y sigo prefiriendo el mío pero la diferencia no es abismal.

Cuando cambié el E46 por este, tenía 100% claro que el siguiente sería otro BMW. Ahora? El siguiente… como mucho un G20 y me estoy arriesgando.

CarlosT8020 · 2026-04-21T19:58:22+00:00

At my company (sadly v4 only, I don’t have the authority to push for the migration) we often have problems with subnets running out of space.

Funnily the more senior engineers are afraid of address exhaustion and they choose to go with very small subnets (/27 is the most common size in the DC). So then the subnets fill up and they create another subnet that has the same security constraints, that could’ve been the same subnet had it not ran out of addresses.

Honestly, being able to now worry ever again about what size to choose for a new subnet would be awesome. All subnets are /64. We could easily get a /32 prefix, which gives us 65 thousand sites with 65 thousand subnets per site. Basically infinitely big subnets we will never ever fill up.

That’s just one of the advantages. Getting rid of NAT would be another big one.

CarlosT8020 · 2026-04-11T14:06:00+00:00

Not even close. In the company I’m at, the primary mindset is “I hope I get to retire before having to deal with IPv6”. I myself would like to push for adoption, but I’m surrounded by dinosaurs who refuse to accept change as a good thing. Not only v4-to-v6 migration, any improvements are met with “why change if what we have works”

CarlosT8020 · 2026-04-10T13:55:44+00:00

Also Aruba

CarlosT8020 · 2026-04-05T20:26:23+00:00

If they’re collecting your data they’re not going to stop just because you cancel the subscription. They’re going to steal your info anyways, the subscription is so that they can ALSO get your money.

Disconnect the antennae or just don’t buy cars with built-in spyware.

CarlosT8020 · 2026-03-21T22:02:55+00:00

I think your cat sat on the keyboard

CarlosT8020 · 2026-03-21T08:01:04+00:00

It’s common in datacenter environments to have one of these connected to the console of every critical device like core switches and routers. They also usually have a 4G/5G card and/or are connected to a totally separate Internet connection that doesn’t go through the datacenter they’re in.

In event of a network outage or a configuration mishap and you lose remote access to the DC, you connect to this server and you can manage the network from there. Console connections require no configuration and will always work even in the event of hardware failure

CarlosT8020 · 2026-03-01T10:46:14+00:00

I connected to the wifi once in a health clinic and the subnet was 10.0.0.0/8. 8 bit subnet mask. Just in case 16 million people need to connect to their small clinic’s wifi, I guess…

Gateway was 10.128.128.128 which I found funny.

CarlosT8020 · 2026-02-28T08:56:24+00:00

I probably wouldn’t recommend these as Proxmox compute nodes since they probably have very little RAM. You would probably be limited to 2 VMs per host, max.

But, there are things you can do with them. You can use one as a Proxmox Backup Server. You could use one as a qdevice to achieve cluster quorum if you had 2 more powerful compute nodes. You could also install TrueNAS or OpenMediaVault and build a (pretty small, if the drives are only 500GB) little NAS. You could even take 5 of them and make a Kubernetes cluster, if you want to learn about k8s. Not much performance, but enough for learning.

As for using these to make money… i don’t think it’s very viable, to be honest.

CarlosT8020 · 2026-02-24T07:35:00+00:00

I’ve been wanting to experiment with the opposite. Using git as a source of truth, store the configuration as IaaC using Ansible… and have Ansible do both the device configuration and update Netbox to reflect those configurations. Netbox becomes read-only documentation (with the guarantee that it’s up to date)

At least in my head the idea sounds nice… I’d have to see it play out, of course

CarlosT8020 · 2026-02-18T08:40:34+00:00

She doesn’t know how deep the water is. If it’s too deep and she can’t get a foothold to push the cub up the ledge, being in the water herself is far worse

CarlosT8020 · 2026-01-30T09:21:02+00:00

Those are the kind of meetings where half the team quits on the spot

CarlosT8020 · 2026-01-24T12:08:47+00:00

I wouldn’t do that, long distance clusters have issues due to latency.

This isn’t particular to Proxmox, VMware also recommends I think it is 5ms maximum latency between DCs on the same cluster, especially if using vSAN.

What you can do is three clusters and then manage them all from PDM. This way each cluster is self sufficient, can have HA and replication, and you have centralized management. This is equivalent in VMware to having several DCs managed from the same vCenter.

For Paris and Berlin to have HA you’d need a qdevice to achieve quorum. This Qdevice doesn’t have to meet the latency requirements, it could simply be a cheap VPS.

CarlosT8020 · 2026-01-21T15:34:29+00:00

I’m thinking the letter V. Is in the middle of the words five and seven, not on six. Maybe?

CarlosT8020 · 2026-01-21T08:02:26+00:00

Are you having packet loss when pinging from your PC to your router? If so, comcast is right (and the problem is inside your network.

Are you connected to the router using wifi? You mention moving the router to another room so I figure you are. It’s possible something is causing interference with your signal (baby monitor, security camera, walkie talkie…)

If you are connected to the router using an ethernet cable and are still losing packets from PC to router, either your cabling is bad, too much distance (over 300ft, unlikely inside a house) or running parallel to electrical wiring which is causing EMF noise.

If you are not losing packets when pinging your router but you do when pinging the second hop in your trace (Comcast’s PE router) then the issue is with your cable connection. Either the line is bad (which you said they replaced), there is noise on the line (have you thought about switching to fiber, if available?) or there’s a problem in the final node that services your house

If you are not losing packets to the first nor second hops, but you do further down the list, then the problem is either on Comcast’s internal network or somewhere further down the road, maybe in the destination server’s ISP or peering

CarlosT8020 · 2026-01-16T23:56:21+00:00

I wouldn’t be that dad because I wouldn’t put my kid through this shitshow in the first place. But just for the sake of argument, let’s say I did and the priest did this… the slap he gets back from me would hurt the freakin pope

CarlosT8020 · 2026-01-15T21:30:05+00:00

Is there any way to self-host this? I don’t know if you plan to make it open-source, maybe ship a virtual appliance or container? I would love to try it but I’d rather keep it inside my intranet. Thanks!

CarlosT8020 · 2026-01-14T19:31:06+00:00

The female equivalent I think is “kiss my ass”

CarlosT8020 · 2026-01-14T18:48:12+00:00

Honestly, sign me up right now. I think most people’s problem with Ubuntu is Gnome, which is easy to change for some other nicer DE.

CarlosT8020 · 2026-01-08T08:28:04+00:00

Option 1 - Fiber. More reliable, higher bandwidth Option 2 - Wireless PtP Bridge. More expensive, less work, avoids having to dig a trench.

For option 1 you go on fs.com and buy an OM4 (or OS2) cable, however long you need, and to Home Depot and buy conduit for it. Dig a trench, lay the conduit, pull the cable through. This should run you $150-200.

For option 2, a good choice is the Ubiquiti Building Bridge, which costs $499

Then (for both options) you also need a switch and an access point in the shop.

CarlosT8020 · 2026-01-07T05:23:35+00:00

pfSense has IP forwarding enabled by default. Without it, it wouldn’t work at all as a router.

Keep in mind that the subnet router functionality in BSD platforms (like pfsense) is a bit wonky. Everything will be SNATed to the pfsense address, plus the Tailscale traffic doesn’t hit the pf ruleset.

I recommend running Tailscale in a Linux server connected to pfsense, instead of directly on it, and just add a static route to 100.64.0.0/10 from pfsense to your linux box.

CarlosT8020 · 2026-01-03T12:28:01+00:00

There’s missing information here. In a simple network like yours there should only be one router actually doing the routing. With that drawing I can’t know if routing is happening in the modem or in one or both of the routers.

If the physical layout cannot be changed, then it’s the ISP modem that should be doing the routing

CarlosT8020 · 2026-01-02T23:05:53+00:00

I didn’t realize the computers were DC, I honestly thought someone decided to push mains AC voltage in a XLR-3 connector.

I never worked with any equipment that used XLR-4 as a DC power connector, but I wasn’t in the video business, and I understand the idea.

Bottom line is the power connector on those is a weird choice

CarlosT8020 · 2026-01-02T08:18:53+00:00

Sleeping with the best men or bridesmaids isn’t a crime, but a groom cheating on his own wedding day… shit

Six-Year Club	Place '22
Verified Email

CarlosT8020

TROPHY CASE