diff --git a/10-systems/networks/pfsense-router.md b/10-systems/networks/pfsense-router.md index f863fc9..5d9f706 100644 --- a/10-systems/networks/pfsense-router.md +++ b/10-systems/networks/pfsense-router.md @@ -79,6 +79,14 @@ - 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). +### Stable identifier and rediscovery + +- The friend's WAN IP is DHCP-assigned and may change on lease renewal. The MAC `24:2f:d0:7e:96:d9` is the stable identifier. The pfSense WAN DHCP lease file (`/var/db/dhclient.leases.re3`) is root-only readable through `ai_agent_ro`, so lease duration is unknown — assume the friend's lease can change at any time. +- Rediscovery procedure if the friend's WAN IP changes: + 1. Preferred: the friend runs a continuous ping to `172.32.2.78`; the owner reads the pfSense firewall log (Status → System Logs → Firewall, filter ICMP) — the source IP of the ICMP wall is his new WAN address. + 2. Without his cooperation: scan the segment (`nmap -sn 172.32.2.0/24` from a LAN host), then read `arp -a` on pfSense `re3` and match the MAC prefix `24:2F:D0` (TP-Link OUI). Other TP-Link routers in the segment may share the prefix — verify candidates with the ping-trap from step 1. +- Note: inbound packets do not refresh ARP entries on FreeBSD — ARP snapshots alone cannot distinguish an active pinger from a stale entry; use the firewall log as the source of truth for active traffic. + ## Local Services Observed listening services: