Acting as a DNS-level ad blocker, Pi-hole intercepts and blocks requests to known ad and tracking domains before they ever reach your devices. It’s fast, private, and works network wide.

Because Pi-Hole is intercepting DNS requests, we need to be careful about its availability, if your DNS goes down, your internet goes down. That’s why, in my VLAN segmented home network, I decided to go with Redundant/highly available Pi-hole deployment for resiliency.

Acting as a DNS-level ad blocker, Pi-hole intercepts and blocks requests to known ad and tracking domains before they ever reach your devices. It’s fast, private, and works network wide.

Because Pi-Hole is intercepting DNS requests, we need to be careful about its availability, if your DNS goes down, your internet goes down. That’s why, in my VLAN segmented home network, I decided to go with Redundant/highly available Pi-hole deployment for resiliency.

Acting as a DNS-level ad blocker, Pi-hole intercepts and blocks requests to known ad and tracking domains before they ever reach your devices. It’s fast, private, and works network wide.

Because Pi-Hole is intercepting DNS requests, we need to be careful about its availability, if your DNS goes down, your internet goes down. That’s why, in my VLAN segmented home network, I decided to go with Redundant/highly available Pi-hole deployment for resiliency.

Acting as a DNS-level ad blocker, Pi-hole intercepts and blocks requests to known ad and tracking domains before they ever reach your devices. It’s fast, private, and works network wide.

Because Pi-Hole is intercepting DNS requests, we need to be careful about its availability, if your DNS goes down, your internet goes down. That’s why, in my VLAN segmented home network, I decided to go with Redundant/highly available Pi-hole deployment for resiliency.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

In today’s threat landscape, developers and security teams must lean on trusted frameworks, tools, and industry practices to ensure their systems are resilient against evolving cyber threats.

This post is a list or pointer to some of the most respected and widely adopted tools and standards in the software security ecosystem.

MITRE ATT&CK: Understanding the Adversary

Website: https://attack.mitre.org

The MITRE ATT&CK framework is a globally accessible knowledge base that catalogs adversary tactics and techniques based on real world observations. It provides invaluable insight into how attackers operate at various stages of the cyber kill chain, helping defenders anticipate and detect malicious behavior.

IPv6 addresses are 128 bits long. One key architectural shift with IPv6 is the fixed boundary between the network and host portions of an address, which is set at /64. Eliminates ambiguity around subnetting, routing continues to work by prefix, just as it did with CIDR under IPv4, but routers are not required to examine all 64 bits of the network portion.

IPv6 Address Notation: The Basics

An IPv6 address is expressed as 8 groups of 16 bits, separated by colons. For example:

IPv6 addresses are 128 bits long. One key architectural shift with IPv6 is the fixed boundary between the network and host portions of an address, which is set at /64. Eliminates ambiguity around subnetting, routing continues to work by prefix, just as it did with CIDR under IPv4, but routers are not required to examine all 64 bits of the network portion.

IPv6 Address Notation: The Basics

An IPv6 address is expressed as 8 groups of 16 bits, separated by colons. For example:

IPv6 addresses are 128 bits long. One key architectural shift with IPv6 is the fixed boundary between the network and host portions of an address, which is set at /64. Eliminates ambiguity around subnetting, routing continues to work by prefix, just as it did with CIDR under IPv4, but routers are not required to examine all 64 bits of the network portion.

IPv6 Address Notation: The Basics

An IPv6 address is expressed as 8 groups of 16 bits, separated by colons. For example:

When it comes to syncing files across directories or devices, most developers and power users turn to time tested tool like rsync. It’s fast, efficient, and ideal for one way synchronization. But what if you need true bidirectional sync, where changes in either directory are reflected in the other, automatically resolving conflicts and preserving the most recent updates?

That’s where Unison comes in.

Why Not Just Use rsync?

rsync excels at unidirectional sync, usually from a source to a target. However, It does not fit for use-case of trying to have a mirrored locally mounted directories of two cloud providers:

When it comes to syncing files across directories or devices, most developers and power users turn to time tested tool like rsync. It’s fast, efficient, and ideal for one way synchronization. But what if you need true bidirectional sync, where changes in either directory are reflected in the other, automatically resolving conflicts and preserving the most recent updates?

That’s where Unison comes in.

Why Not Just Use rsync?

rsync excels at unidirectional sync, usually from a source to a target. However, It does not fit for use-case of trying to have a mirrored locally mounted directories of two cloud providers:

When it comes to syncing files across directories or devices, most developers and power users turn to time tested tool like rsync. It’s fast, efficient, and ideal for one way synchronization. But what if you need true bidirectional sync, where changes in either directory are reflected in the other, automatically resolving conflicts and preserving the most recent updates?

That’s where Unison comes in.

Why Not Just Use rsync?

rsync excels at unidirectional sync, usually from a source to a target. However, It does not fit for use-case of trying to have a mirrored locally mounted directories of two cloud providers:

When it comes to syncing files across directories or devices, most developers and power users turn to time tested tool like rsync. It’s fast, efficient, and ideal for one way synchronization. But what if you need true bidirectional sync, where changes in either directory are reflected in the other, automatically resolving conflicts and preserving the most recent updates?

That’s where Unison comes in.

Why Not Just Use rsync?

rsync excels at unidirectional sync, usually from a source to a target. However, It does not fit for use-case of trying to have a mirrored locally mounted directories of two cloud providers:

When it comes to syncing files across directories or devices, most developers and power users turn to time tested tool like rsync. It’s fast, efficient, and ideal for one way synchronization. But what if you need true bidirectional sync, where changes in either directory are reflected in the other, automatically resolving conflicts and preserving the most recent updates?

That’s where Unison comes in.

Why Not Just Use rsync?

rsync excels at unidirectional sync, usually from a source to a target. However, It does not fit for use-case of trying to have a mirrored locally mounted directories of two cloud providers:

I’ve been wanting to create a personal blog for a while, a place to share what I’ve learned, what I’m building, and random notes that might help someone (or future me). Today, I finally took the first step and set it up!

I wanted something minimal and fast, mainly to publish text and a few images. My first thought was to build it using plain HTML and JavaScript, and host it on GitHub Pages to kickstart. But as I started digging in, I discovered some better tools that made the process smoother and more flexible and fun.

I’ve been wanting to create a personal blog for a while, a place to share what I’ve learned, what I’m building, and random notes that might help someone (or future me). Today, I finally took the first step and set it up!

I wanted something minimal and fast, mainly to publish text and a few images. My first thought was to build it using plain HTML and JavaScript, and host it on GitHub Pages to kickstart. But as I started digging in, I discovered some better tools that made the process smoother and more flexible and fun.

I’ve been wanting to create a personal blog for a while, a place to share what I’ve learned, what I’m building, and random notes that might help someone (or future me). Today, I finally took the first step and set it up!

I wanted something minimal and fast, mainly to publish text and a few images. My first thought was to build it using plain HTML and JavaScript, and host it on GitHub Pages to kickstart. But as I started digging in, I discovered some better tools that made the process smoother and more flexible and fun.

I’ve been wanting to create a personal blog for a while, a place to share what I’ve learned, what I’m building, and random notes that might help someone (or future me). Today, I finally took the first step and set it up!

I wanted something minimal and fast, mainly to publish text and a few images. My first thought was to build it using plain HTML and JavaScript, and host it on GitHub Pages to kickstart. But as I started digging in, I discovered some better tools that made the process smoother and more flexible and fun.

I’ve been wanting to create a personal blog for a while, a place to share what I’ve learned, what I’m building, and random notes that might help someone (or future me). Today, I finally took the first step and set it up!

I wanted something minimal and fast, mainly to publish text and a few images. My first thought was to build it using plain HTML and JavaScript, and host it on GitHub Pages to kickstart. But as I started digging in, I discovered some better tools that made the process smoother and more flexible and fun.