Newer
Older
gnexus-book / 10-systems / networks / isp-inter-segment-routing.md

owner: gmikcon status: active last_reviewed: 2026-10-03 review_interval: 90d confidence: high

source_of_truth: live-ping-probes-2026-10-03

ISP Inter-Segment Routing

Verified 2026-10-03 from live probes (LAN host 192.168.1.253, behind pfSense WAN 172.32.2.78).

Summary

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).

Segment map

  • Our segment: 172.32.2.0/24 (pfSense WAN 172.32.2.78).
  • Reachable segments (gateways respond): 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.
  • No response from gateways 172.32.4.1 and 172.32.11.1–172.32.31.1 (segments absent, down, or filtered).

Evidence

  • Ping probes from our LAN host to hosts in other segments: multiple hosts in segments 0, 1, 3, 5, 6, 7, 8, 9, 10 replied (e.g. 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).
  • Roughly 60% of probed addresses did not answer — consistent with client-side firewalls, not routing blocks (a routing block would silence ALL hosts in a segment).
  • Latency between segments is comparable to intra-segment (single-digit ms), consistent with routing at the ISP aggregation layer.

Implications

  • A friend in another district on the same ISP is directly reachable if his segment is within 172.32.0.0/24–172.32.10.0/24 (or another routed range).
  • Identification procedure is the same as for friend #1: continuous ping to 172.32.2.78 + pfSense firewall log readout, or tracert from his side (second hop = his segment gateway).
  • Client-to-client traffic between segments traverses ISP routing infrastructure — treat as untrusted transit; WireGuard tunnel is still the right transport layer.
  • 10-systems/networks/pfsense-router.md — our WAN segment and friend #1 (172.32.2.120, same segment).