Bypassing DPI with eBPF Sock_ops
The article discusses a method to bypass Deep Packet Inspection (DPI) using eBPF sock_ops. It describes how a fake ClientHello is sent to mislead the DPI while allowing the real connection to pass through. Additionally, it explains the use of a local DoH server to handle DNS queries securely.
- ▪The method involves sending a fake ClientHello with a different SNI to trick the DPI.
- ▪The eBPF program is used to manipulate TCP settings to fragment the real ClientHello.
- ▪A local DoH server is implemented to encrypt DNS queries and prevent interception.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Bora |
| Canonical URL | https://bora.sh/bypassing-dpi-with-ebpf/ |
| Publication time | Tue, 28 Apr 2026 12:43:37 +0000 |
| Retrieval time | 2026-04-28T12:54:31.957Z |
| Last seen | 2026-04-28T12:54:31.957Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | IOFYqoiogUZ2 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The problemA site I wanted to open never loaded. The TLS handshake stalled. Somewhere upstream, a middlebox was reading the SNI in my ClientHello and dropping the connection.DNS was the other half. Even if you slip past the DPI, the resolver hands you a fake IP that lands on a block page. So both have to be dealt with.Most fixes mean a VPN or a proxy. I didn’t want either. A VPN sends every byte you have through some remote server. Way too much for this. A proxy needs per-app configuration, and plenty of apps just ignore the system proxy. What I wanted was simpler: system-level, transparent, one command.sudo gecit run The ideaThe trick is simple. Send a fake ClientHello before the real one reaches the DPI.The fake carries a different SNI, www.google.com, with a low TTL.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Bora.
Discussion
0 commentsMore from Bora
