mike 78beedeabc dnsmasq: enable log-dhcp permanently; document rogue-DHCP-server incident ...

Found and fixed a second, uncontrolled DHCP server on the LAN (a WiFi
router still in router mode instead of access-point mode) that was
intermittently handing out wrong DNS/IP config to clients. log-dhcp
was key to spotting it via the 'wrong server-ID' DHCPNAK pattern, so
keeping it enabled going forward; log-queries (diagnostic-only, noisy)
was removed again.

2026-08-19 07:44:01 +02:00

..

dnsmasq.d

dnsmasq: enable log-dhcp permanently; document rogue-DHCP-server incident

2026-08-19 07:44:01 +02:00

sysctl.d

Doku: Router-Setup (DHCP/DNS/NAT für enp7s0 10.0.0.0/24)

2026-08-18 11:02:02 +02:00

systemd/dnsmasq.service.d

dnsmasq: Restart=on-failure gegen Boot-Race mit enp7s0

2026-08-18 11:23:23 +02:00

network-interfaces

Doku: Router-Setup (DHCP/DNS/NAT für enp7s0 10.0.0.0/24)

2026-08-18 11:02:02 +02:00

nftables.conf

ipadm: Port-Forwarding hinzufügen (-pa/-pl/-pd) + nftables-Include verdrahten

2026-08-18 11:43:29 +02:00