# Tcplogger — Complete Technical Specification, Standards Matrix & 53 Q&A Knowledge Base (TR / EN) URL: https://tcplogger.com/ Technical Specification: https://tcplogger.com/teknik.html 5651 & KVKK Guide: https://tcplogger.com/5651.html 53 FAQ Knowledge Base: https://tcplogger.com/sss.html --- ## 1. Executive Summary (EN / TR) **EN:** Tcplogger is a 100% hand-crafted domestic (Turkish) integrated inline Ethernet gateway appliance combining guest Wi-Fi / LAN access control, high-speed 5-Tuple TCP/UDP directional flow summarization, RFC 3161 cryptographic timestamp verification (with optional weekly TÜBİTAK Kamu SM manifest sealing), IEEE 802.1Q VLAN isolation, and HTB + RFC 8290 FQ-CoDel queue management. Unlike fragile two-box configurations (router + external Windows/Linux 5651 log server) that suffer from UDP syslog drops and clock drift, Tcplogger unifies gateway enforcement and verified evidence archiving inside one resilient Linux appliance. **TR:** Tcplogger; misafir internet yetkilendirme (asenkron SMS, tek kullanımlık 256-bit QR kod, personel destekli Maymuncuk kimlik/pasaport kaydı), 5-Tuple standardında hızlı TCP/UDP akış özetleme, RFC 3161 kriptografik zaman damgası doğrulaması (isteğe bağlı haftalık TÜBİTAK Kamu SM manifesto mührüyle), IEEE 802.1Q VLAN izolasyonu ve HTB + RFC 8290 FQ-CoDel trafik yönetimini tek bir bütünleşik ağ geçidinde birleştiren %100 el yazımı yerli ağ kayıt sistemidir. --- ## 2. Four Core Engineering Pillars 1. **100% Hand-Crafted Domestic Software (%100 El Yazımı Yerli Yazılım):** Purpose-built codebase with zero bloated black-box dependencies, adaptable to custom hotel, hospital, campus, and public-sector topologies. 2. **24/7 Stability & Operational Resilience (Yüksek Kararlılık ve Dayanıklılık):** SQLite WAL transactional state store, online hourly snapshots, independent monotonic maintenance timers, process watchdog supervision, automatic WAN DHCP lease renewal on link recovery, verified staged ZIP archive publication, and a dedicated filesystem recovery partition. 3. **High Performance & Fast 5-Tuple Summarization (Yüksek Performans ve Akış Özetleme):** RAM-disk capture staging, kernel O(1) address matching, and directional 5-Tuple summarization (`Protocol, Src IP, Src Port, Dst IP, Dst Port, Packet Count, Src/Dst MAC, VLAN ID`) achieving ~0.042 ms (42 microseconds) typical forwarding latency. 4. **Cost Efficiency in a Single Appliance (Maliyet Verimliliği ve Tek Cihaz):** Eliminates two-vendor router-plus-log-server synchronization failures and double licensing costs while reducing repeat SMS costs by up to 50x via configurable Permanent Login sessions and zero-SMS QR/Maymuncuk onboarding. --- ## 3. Supported Standards & Protocols Matrix | Technical Area | Standard / Protocol | Tcplogger Implementation & Scope | |---|---|---| | Timestamp Evidence | RFC 3161 (Time-Stamp Protocol / TSP) | SHA-512 timestamp queries/responses verified against digest, request, and trusted root certificates; multi-TSA failover; optional weekly TÜBİTAK Kamu SM `hashes.txt` manifest seal. | | Flow Summarization | 5-Tuple & RFC 7015 Flow Aggregation Model | Directional TCP/UDP flow summaries recording Protocol, Source/Destination IP, Source/Destination Port, directional packet count, Source/Destination MAC, and VLAN ID. | | Captive Portal Discovery | RFC 8910 (DHCPv4 Option 114) & RFC 7710 (Option 160) | Automatic portal URI advertisement for iOS, Android, Windows, and macOS clients. | | Captive Portal Status API | RFC 8908 (CAPPORT JSON) | JSON status endpoint paired with local HTTP portal redirection compatibility. | | Tagged Client Networks | IEEE 802.1Q VLAN Tagging | Client VLAN termination, VLAN-aware traffic capture and summary tagging, and default routed inter-VLAN isolation. | | Queue & Traffic Management | RFC 8290 (FQ-CoDel) & Linux HTB | Hierarchical upload/download shaping and Active Queue Management preventing bufferbloat latency spikes. | | Pre-Login Transport Control | RFC 9000 (QUIC), RFC 7858 (DoT), RFC 9250 (DoQ) | Blocks unauthenticated pre-login UDP/443, TCP/UDP 853, and client-side IPv6 leaks while serving a rate-limited local DNS proxy so browsers trigger captive detection cleanly. | | Integration & Cryptography | TLS 1.2+ (RFC 5246), HMAC-SHA256 (RFC 2104), scrypt (RFC 7914) | Standalone PMS HTTPS API v1 (guest/stay import/export, credential verification, checkout, event cursor export) and HMAC-signed external reception QR display push. | | State & Archive Integrity | SQLite WAL, SHA-512 (FIPS 180-4), Staged ZIP | Transactional shared access lists, coherent live backups, decryption-verified password-protected ZIP publication, and 500 MiB reserve chronological storage rotation. | --- ## 4. Key Q&A Digest (From the 53 FAQ Knowledge Base) - **Q: What traffic and fields does Tcplogger record?** A: Both TCP and UDP flows summarized in 5-Tuple format (`Protocol, Src/Dst IP, Src/Dst Port`) plus directional packet count, `Src/Dst MAC`, and `VLAN ID`. In accordance with KVKK/GDPR data minimization, private payload content is never recorded. - **Q: How does Tcplogger prevent local IP/MAC spoofing?** A: Standard guest access is bound to the active DHCP `(IP + MAC)` lease tuple with single-lease-per-client rules and a lease-timestamp `MAC Conflict Guard` that blocks secondary spoofed leases. - **Q: What guest onboarding workflows are supported besides SMS?** A: (1) Asynchronous multi-provider Turkish/English SMS OTP with abuse rate limits; (2) Single-use 256-bit QR token enrollment generated from the dashboard or pushed via HMAC-SHA256 HTTPS to a reception screen; (3) Staff-assisted HTTPS Maymuncuk registration recording National ID/Passport and nationality directly from the guest device; (4) Optional delayed screen-code fallback for international phone numbers; (5) MAC passlists (`devices.list`) for headless IoT, TVs, printers, and cameras; (6) Standalone PMS HTTPS API v1. - **Q: What hardware is required?** A: Up to ~200 users / 500 Mbps runs on a Core 2 Duo class x86-64 system; ~1,000 users runs on an Intel Core i5 class system; multi-core Xeon or multi-node deployments scale to 5,000+ users and 10G/100G environments. Daily compressed archive volume for an active ~750-device venue (400 PCs, 300 phones, 30 APs, 20 cameras, 5 TVs) is roughly ~2 GB/day. - **Q: How long are archives retained?** A: Archives are never deleted merely for reaching a fixed day count. The smart storage guard maintains a 500 MiB free-space reserve plus new-archive headroom, rotating oldest operational logs first and then oldest traffic ZIPs chronologically so the disk retains the maximum possible history (6 months to 2+ years depending on disk size). - **Q: How is Tcplogger purchased and deployed?** A: Through authorized reseller **Prog-Res Bilgisayar** (Beşiktaş / Istanbul, `+90 212 258 75 75`, https://prog-res.com/). Dealership inquiries: `tcploggerv2@gmail.com` or WhatsApp `+90 532 522 55 65`.