diff --git a/10-systems/networks/pfsense-router.md b/10-systems/networks/pfsense-router.md index 99a6056..f863fc9 100644 --- a/10-systems/networks/pfsense-router.md +++ b/10-systems/networks/pfsense-router.md @@ -1,10 +1,10 @@ --- owner: gmikcon status: active -last_reviewed: 2026-09-29 +last_reviewed: 2026-10-03 review_interval: 90d confidence: high -source_of_truth: owner-confirmed-and-ssh-pfsense +source_of_truth: owner-provided-firewall-log-and-macvendors --- # pfSense Router @@ -69,6 +69,16 @@ - 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). +## Friend Peer Link (verified 2026-10-03) + +A friend of the owner is on the same ISP and the same WAN L2 segment, enabling a direct low-latency peer link (planned: WireGuard router-to-router). + +- Friend WAN: `172.32.2.120`, MAC `24:2f:d0:7e:96:d9` (TP-Link Systems Inc router). +- Friend LAN: `192.168.0.0/24`, gateway `192.168.0.1` (from his tracert to 8.8.8.8). +- Identification method: owner read pfSense Web UI firewall log (Status → System Logs → Firewall) while the friend ran a continuous `ping 172.32.2.78`; the log showed a wall of ICMP echo-requests from `172.32.2.120` to `172.32.2.78` blocked by the default deny rule (1000000103) every second. +- Our WAN blocks inbound ICMP by default (default deny rule), so the friend's ping times out; outbound pings from our side to `172.32.2.120` also get no replies (his router filters inbound ICMP or the ISP filters client-to-client ICMP echo-reply) — direct client-to-client connectivity for the tunnel still needs to be verified after firewall rules are added. +- Planned next steps: add pfSense WAN pass rules for ICMP echo-request/echo-reply and a WireGuard UDP port sourced from `172.32.2.120/32`; then configure WireGuard on both routers (LAN-to-LAN tunnel). + ## Local Services Observed listening services: @@ -112,8 +122,7 @@ - Gateway: `192.168.2.1`. - Router interface: `re0` / `LANTECH`. - Purpose: service network for smart-home and IoT devices. -- Wi-Fi mode: access points. -- Mesh mode: intentionally disabled. +- Wi-Fi mode: access points, not a separate routed Wi-Fi network. - IoT Wi-Fi nodes: - `home_iot_0` - `home_iot_1`