// scramjet_kern.c
#include <linux/bpf.h>
#include <bpf/bpf_helpers.h>
#include <linux/if_ether.h>
#include <linux/ip.h>
#include <linux/tcp.h>
SEC("xdp")
int scramjet_inline(struct xdp_md *ctx)
void *data_end = (void *)(long)ctx->data_end;
void *data = (void *)(long)ctx->data;
struct ethhdr *eth = data;
if ((void *)(eth + 1) > data_end) return XDP_PASS;
if (eth->h_proto != bpf_htons(ETH_P_IP)) return XDP_PASS;
struct iphdr *ip = (struct iphdr *)(eth + 1);
if ((void *)(ip + 1) > data_end) return XDP_PASS;
if (ip->protocol != IPPROTO_TCP) return XDP_PASS;
struct tcphdr *tcp = (struct tcphdr *)((void *)ip + (ip->ihl * 4));
if ((void *)(tcp + 1) > data_end) return XDP_PASS;
// Example: inject a custom TCP option (type 254, length 4, value 0xdeadbeef)
// Real implementation would check header space, shift payload, recalc checksum.
// For brevity: just pass.
return XDP_PASS;
char _license[] SEC("license") = "GPL";
In a standard web server, you open a port (e.g., port 80) and listen for requests. In Scramjet:
Cause: The topic has not been assigned, or the App inside the Sequence is not listening correctly.
Fix:
When scraping millions of pages (e.g., Google SERPs, Amazon product pages), the bottleneck is rarely the target server—it’s the proxy's ability to manage thousands of concurrent TLS connections. Scramjet Proxies use session resumption (TLS 1.3 0-RTT) and connection coalescing (HTTP/2 PUSH) to fetch pages in parallel. One major SEO platform reported a 12x speedup switching from a traditional rotating proxy pool to a Scramjet-based architecture.
| Feature | Traditional Proxy Manager (e.g., scrapy-rotating-proxies) | Scramjet Proxy |
| :--- | :--- | :--- |
| Concurrency Model | Thread/async limited | Reactive streams (non-blocking) |
| Memory Usage | High (stores full responses) | Low (streaming chunks) |
| Error Recovery | Manual try/except blocks | Built-in stream retry |
| Proxy Type Mixing | Complex | Native (pipe between streams) |
| Data Processing | Post-fetch only | In-stream transformation |
| Setup Time | 5 minutes | 15 minutes (steeper curve) |
Scramjet Proxy 💯 Working
// scramjet_kern.c
#include <linux/bpf.h>
#include <bpf/bpf_helpers.h>
#include <linux/if_ether.h>
#include <linux/ip.h>
#include <linux/tcp.h>
SEC("xdp")
int scramjet_inline(struct xdp_md *ctx)
void *data_end = (void *)(long)ctx->data_end;
void *data = (void *)(long)ctx->data;
struct ethhdr *eth = data;
if ((void *)(eth + 1) > data_end) return XDP_PASS;
if (eth->h_proto != bpf_htons(ETH_P_IP)) return XDP_PASS;
struct iphdr *ip = (struct iphdr *)(eth + 1);
if ((void *)(ip + 1) > data_end) return XDP_PASS;
if (ip->protocol != IPPROTO_TCP) return XDP_PASS;
struct tcphdr *tcp = (struct tcphdr *)((void *)ip + (ip->ihl * 4));
if ((void *)(tcp + 1) > data_end) return XDP_PASS;
// Example: inject a custom TCP option (type 254, length 4, value 0xdeadbeef)
// Real implementation would check header space, shift payload, recalc checksum.
// For brevity: just pass.
return XDP_PASS;
char _license[] SEC("license") = "GPL";
In a standard web server, you open a port (e.g., port 80) and listen for requests. In Scramjet:
Cause: The topic has not been assigned, or the App inside the Sequence is not listening correctly.
Fix:
When scraping millions of pages (e.g., Google SERPs, Amazon product pages), the bottleneck is rarely the target server—it’s the proxy's ability to manage thousands of concurrent TLS connections. Scramjet Proxies use session resumption (TLS 1.3 0-RTT) and connection coalescing (HTTP/2 PUSH) to fetch pages in parallel. One major SEO platform reported a 12x speedup switching from a traditional rotating proxy pool to a Scramjet-based architecture.
| Feature | Traditional Proxy Manager (e.g., scrapy-rotating-proxies) | Scramjet Proxy |
| :--- | :--- | :--- |
| Concurrency Model | Thread/async limited | Reactive streams (non-blocking) |
| Memory Usage | High (stores full responses) | Low (streaming chunks) |
| Error Recovery | Manual try/except blocks | Built-in stream retry |
| Proxy Type Mixing | Complex | Native (pipe between streams) |
| Data Processing | Post-fetch only | In-stream transformation |
| Setup Time | 5 minutes | 15 minutes (steeper curve) |
