diff --git a/10-systems/networks/pfsense-router.md b/10-systems/networks/pfsense-router.md index 48a34f6..99a6056 100644 --- a/10-systems/networks/pfsense-router.md +++ b/10-systems/networks/pfsense-router.md @@ -23,6 +23,7 @@ - `ai_agent_ro` (uid 2000, group nobody) can run basic commands (`date`, `ls`, `id`, `cat /etc/ssh/sshd_config`) but CANNOT read `/var/log/*` — all logs are `root:wheel` mode 600. - No `sudo`, no `clog` binary in PATH, no Match/ForceCommand block in sshd_config — the restriction is plain file permissions. - WAN outage analysis must therefore use alternative sources: NetworkManager connectivity logs on LAN hosts (`journalctl | grep "state is now"`), OpenVPN reconnect logs on tunnel endpoints, or the pfSense Web UI (owner). +- The default shell for `ai_agent_ro` is `csh`; complex one-liners must be wrapped as `sh -c '...'` (nested quoting is fragile — build the command programmatically). ## Role @@ -57,6 +58,17 @@ - `192.168.2.0/24` is directly connected through `re0`. - Host routes for `8.8.8.8` and `2.2.2.2` are present through `re3`. +## WAN L2 Domain (verified 2026-10-03) + +The WAN interface `re3` (172.32.2.0/24) shares a **flat, unfiltered L2 segment with other ISP clients** — it is not an isolated point-to-point uplink. + +Evidence from `arp -a` over SSH (`ai_agent_ro`): + +- 169 ARP entries on `re3` (including own address 172.32.2.78 and gateway 172.32.2.1 at `d4:01:c3:6b:86:b9`); roughly 160+ distinct neighbor MACs of other ISP clients. +- Examples: `172.32.2.5 → 54:ef:33:4b:5a:3d`, `172.32.2.46 → 20:32:33:ea:b3:5a`, `172.32.2.104 → 54:ef:33:4b:5a:a3`, `172.32.2.106 → 00:e0:4c:8d:6b:06`, `172.32.2.141 → d4:da:21:1d:ba:f0`, `172.32.2.195 → 48:8f:5a:3b:3c:32`. +- ICMP ping from pfSense to 20 sampled neighbor addresses (172.32.2.5, .23, .33, .45, .46, .48, .81, .85, .92, .104, .106, .128, .141, .146, .155, .161, .195, .212, .219, .250): 17/20 replied; .106, .141, .219 did not answer ICMP but their MACs were present in ARP — ICMP is partially filtered by client firewalls, ARP is the reliable indicator. +- Implication: other ISP subscribers are on the same broadcast domain; treat WAN-side exposure seriously (no trusted traffic on 172.32.2.0/24, firewall rules on WAN should assume hostile neighbors). + ## Local Services Observed listening services: