owner: gmikcon status: active last_reviewed: 2026-10-03 review_interval: 90d confidence: high
Verified 2026-10-03 from live probes (LAN host 192.168.1.253, behind pfSense WAN 172.32.2.78).
The ISP routes client-to-client traffic between its subscriber segments — inter-segment isolation is NOT enforced. A client in one segment can reach hosts in other segments directly (subject to client-side firewalls).
172.32.2.0/24 (pfSense WAN 172.32.2.78).172.32.0.0/24, 172.32.1.0/24, 172.32.3.0/24, 172.32.5.0/24, 172.32.6.0/24, 172.32.7.0/24, 172.32.8.0/24, 172.32.9.0/24, 172.32.10.0/24.172.32.4.1 and 172.32.11.1–172.32.31.1 (segments absent, down, or filtered).172.32.0.5/.100/.150/.200/.104, 172.32.1.5, 172.32.3.23/.36/.50/.100/.106/.115/.250, 172.32.5.78/.141/.219, 172.32.6.33, 172.32.7.5/.33/.81/.106/.115/.150/.161/.212/.219, 172.32.8.5/.10/.50/.141, 172.32.9.5/.36/.50, 172.32.10.48/.50/.81/.106/.212).172.32.0.0/24–172.32.10.0/24 (or another routed range).172.32.2.78 + pfSense firewall log readout, or tracert from his side (second hop = his segment gateway).10-systems/networks/pfsense-router.md — our WAN segment and friend #1 (172.32.2.120, same segment).