Skip to content

(WIP) A hand-made mini TCP DDoS shield based on eBPF/XDP(eXpress Data Path)

active 2025-04-182025-06-01 (UTC)

Complete coverage26,667 / 26,667 hourly files (100%) · 2 absent upstream2023-08-152026-08-30 (UTC)
Events
120
Pushes
46
Pull requests
9
Issues
10
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 45 days from 2025-04-18 to 2025-06-01. Pushes: 46 total, peak 6 in a day. Pull requests: 9 total, peak 3 in a day. Issues: 10 total, peak 2 in a day. Comments: 25 total, peak 6 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
KnightChaser8746919
Copilot18006

Recent activity

Latest issues, pull requests and releases

  • Issue comment#13KnightChaser2025-05-24 03:40
    Bug/12: Ensure consistency of byte ordering of IP addresses at XDP/C program
  • Pull request#13KnightChaser2025-05-24 03:38
  • Issue comment#12KnightChaser2025-05-24 03:22
    Bug: IP byte-order reversed in logs
  • Issue#12KnightChaser2025-05-24 03:06
    Bug: IP byte-order reversed in logs
  • Issue comment#11KnightChaser2025-05-24 03:04
    Task/10: Improve testbed for l4shieldx
  • Issue#10KnightChaser2025-05-24 03:03
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Pull request#11KnightChaser2025-05-24 03:03
  • Pull request#11KnightChaser2025-05-24 02:47
  • Issue comment#10KnightChaser2025-05-24 02:42
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Issue comment#10KnightChaser2025-05-23 02:14
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Issue comment#10KnightChaser2025-05-23 02:09
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Issue comment#10KnightChaser2025-05-16 00:55
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Issue#10KnightChaser2025-05-16 00:27
    Task: Revision, enhance and fix implementation flaws testbed for l4shieldx
  • Issue comment#9KnightChaser2025-05-14 02:48
    Feat/8: Implemented port-based, per-PID DDoS protection logic (Alternative of cgroup-based approach, #6))
  • Pull request#9KnightChaser2025-05-14 02:46
  • Pull request#9KnightChaser2025-05-14 02:30
  • Issue comment#6KnightChaser2025-05-12 15:44
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue comment#6KnightChaser2025-05-12 15:07
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue comment#6KnightChaser2025-05-12 14:24
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue comment#6KnightChaser2025-05-12 13:47
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue comment#6KnightChaser2025-04-30 12:52
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue#5KnightChaser2025-04-30 12:50
    Task: Create and utilize per-IP access count map in eBPF/XDP programs to establish criteria of DDoS attacks
  • Issue comment#7KnightChaser2025-04-30 12:49
    Task/5: Create and utilize per-IP access count map + auto source traffic block policy enforcement
  • Issue#6KnightChaser2025-04-30 11:34
    Feat: Scope DDoS filter to selected processes via cgroup
  • Issue comment#5KnightChaser2025-04-30 11:02
    Task: Create and utilize per-IP access count map in eBPF/XDP programs to establish criteria of DDoS attacks

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.