| 2026-10-03 |
pfSense: correct C6 stock VPN facts — C6 v2 supports OpenVPN server per official TP-Link FAQ
...
Correction: official TP-Link FAQ 1544 lists Archer C6 v2 (and A6 v2/v3) as supporting OpenVPN server in stock firmware. Previous claim 'stock C6 has NO VPN server' was wrong for v2. Updated candidate approaches: OpenVPN server on his C6 + pfSense client as option 1.
|
pfSense: friend router = Archer C6 (no VPN on stock, OpenWrt possible); SSH-proxy approach chosen; WG readiness verified
...
Owner confirmed friend's router model: TP-Link Archer C6. Verified via OpenWrt/TechInfoDepot: stock firmware has no VPN server (port forwarding only), OpenWrt supported on all hardware versions. Chosen approach documented: SSH port-forward proxy first, WireGuard as upgrade path. pfSense WireGuard readiness verified live (wg binary, if_wg.ko module, DHCP WAN).
|
| 2026-10-01 |
ISP inter-segment routing: client-to-client traffic routed between segments
...
New doc: ISP inter-segment routing verified via live ping probes. Client-to-client traffic is routed between subscriber segments (172.32.0-10.x). Friend #2 in another district is directly reachable. Segment map, evidence, and identification procedure documented.
|
pfSense: friend MAC as stable identifier + rediscovery procedure
...
Added stable identifier (MAC 24:2f:d0:7e:96:d9, TP-Link OUI 24:2F:D0) for the friend peer link since WAN IP is DHCP-assigned and may change. Documented rediscovery procedure: ping-trap via pfSense firewall log (preferred) and MAC-prefix scan fallback. Added caveat: inbound packets do not refresh ARP entries on FreeBSD.
|
pfSense: document friend peer link (172.32.2.120, same ISP L2 segment)
...
Friend peer link discovery: friend WAN 172.32.2.120 (TP-Link, MAC 24:2f:d0:7e:96:d9), same ISP L2 segment as our WAN 172.32.2.78. Identified via pfSense firewall log during continuous ping from friend. Planned WireGuard router-to-router link.
|
| 2026-09-30 |
pfSense: document shared WAN L2 domain on re3 (169 ARP entries, ISP neighbors)
...
Live diagnostics over SSH chain local→gbook→pfSense (ai_agent_ro): arp -a on re3 showed 169 entries including ~160+ neighbor MACs of other ISP clients in 172.32.2.0/24; ICMP ping sweep of 20 sampled neighbors got 17 replies (.106, .141, .219 silent but present in ARP). Added "WAN L2 Domain" section to 10-systems/networks/pfsense-router.md and a csh-shell note for ai_agent_ro.
|
| 2026-09-29 |
Document pfSense SSH key location on gmikcon PC and ai_agent_ro log-read limitations
...
Discovered 2026-09-29: pfSense SSH key location (gmikcon PC, ~/.ssh/gnexus_book_pfsense_ro) and that ai_agent_ro cannot read /var/log (root-only, no sudo/clog) — verified live over SSH.
|
| 2026-05-09 |
Document pfSense interfaces and router services
Eugene Sukhodolskiy
committed
on 9 May
|
Document home LAN topology and discovery observations
Eugene Sukhodolskiy
committed
on 9 May
|
Add documentation foundation and backend maintenance API
Eugene Sukhodolskiy
committed
on 9 May
|