Category Archives: Networking

Arch Linux: “mysterious” DNS timeouts and “in search of the Ethernet truth”
5 (1)

20 January 2026

For a couple of months now, my work laptop, a Lenovo ThinkPad T14 Gen 5 running Arch Linux, has been having trouble opening new websites – for the first 10-15 seconds, the site loads in “pieces”, for example: But then it “wakes up”, and everything starts working perfectly: Finally, when I started setting up a… Read More: Arch Linux: “mysterious” DNS timeouts and “in search of the… »

Loading

FreeBSD: Home NAS, part 7 – NFSv4 and use with Linux clients
5 (2)

5 January 2026

The next step in the process of setting up a home NAS on FreeBSD is to add an NFS share. We set up Samba in the previous part – now we let’s add NFS shares to it. My idea is for the Samba share to be used for various media resources requiring access from phones… Read More: FreeBSD: Home NAS, part 7 – NFSv4 and use with… »

Loading

TCP/IP: SYN flood attack on the RTFM server, and “Hacker News hug of death”
0 (0)

2 January 2026

Got an alert from the monitoring system this morning, indicating that the blog is down: Well, I thought: another one DDoS, not the first time. Investigating the issue I went to the Cloudflare admin, enabled the Under Attack Mode, and started the investigation. Checked the requests: I think, okay, it’s simple – requests are coming… Read More: TCP/IP: SYN flood attack on the RTFM server, and “Hacker… »

Loading

FreeBSD: Home NAS, part 6 – Samba server and client connections
4.6 (7)

28 December 2025

Continuing the setup of my home NAS on FreeBSD. Actually, a NAS is a Network System, and it’s desirable to have access to it from other devices – Linux and Windows hosts, phones, and TVs. Here we have two main options – Samba and NFS. One could also mention sshfs – but this solution is… Read More: FreeBSD: Home NAS, part 6 – Samba server and client… »

Loading

FreeBSD: Home NAS, part 4 – Local DNS with Unbound
5 (1)

26 December 2025

In the previous post, FreeBSD: WireGuard VPN, Linux peer and routing between networks, we set up a VPN to connect two networks – my office and home – and everything is working perfectly. However, currently, to connect to any host in the networks, you have to specify an IP address. Of course, you could manually… Read More: FreeBSD: Home NAS, part 4 – Local DNS with Unbound5… »

Loading

FreeBSD: Home NAS, part 3 – WireGuard VPN, Linux peer, and routing
4.1 (15)

25 December 2025

I am continuing to set up my home server on FreeBSD 14.3, which is intended to serve as a NAS. In the previous post, FreeBSD: introduction to Packet Filter (PF) firewall, we got acquainted with firewalls; the next step is to configure a VPN for access. The main idea is to (finally!) connect my “office”… Read More: FreeBSD: Home NAS, part 3 – WireGuard VPN, Linux peer,… »

Loading

FreeBSD: Home NAS, part 2 – introduction to Packet Filter (PF) firewall
3.7 (6)

24 December 2025

I’m continuing to gradually set up my home NAS on FreeBSD, and the first thing I want to dive into is FreeBSD firewalls. I used to work with IPFW back in the day – FreeBSD: initial setup of IPFW, from 2012. Currently, there are three “built-in” firewalls in the system – Packet Filter (PF), IP… Read More: FreeBSD: Home NAS, part 2 – introduction to Packet Filter… »

Loading

TCP/IP: OSI and TCP/IP models, TCP packets, Linux sockets and ports
0 (0)

19 July 2025

It’s difficult to describe in one post what thousands of books have been written about in a thousand pages, but today we’ll try to quickly review the basics of how hosts communicate on a network. First, let’s talk about the OSI and TCP/IP models, then about packet structure and connection establishment, and finally, we’ll look… Read More: TCP/IP: OSI and TCP/IP models, TCP packets, Linux sockets and… »

Loading

Kubernetes: 503 errors with AWS ALB possible causes and solutions
0 (0)

9 July 2025

After migration to a new EKS cluster, we started getting alerts about 503 errors sometimes. The errors were happened in three cases: sometimes without any deployment, when all Pods were Running && Ready sometimes during deployment – but only on Dev, because there is only one Pod for API and sometimes during Karpenter Consolidation. Let’s… Read More: Kubernetes: 503 errors with AWS ALB possible causes and solutions0… »

Loading