Backend systems engineer working on internet measurement infrastructure in Rust. Currently building LYNX, a unified L4+L7 TLS scanner.
CS undergrad at Osmania University. Reach out: syedanwaruddin08@gmail.com
Cross-OS hardware locks: debugging Intel AX201 Code 10 failures in Linux/Windows dual boots
If you maintain a Windows and Linux dual-boot workstation, you will eventually run into a baffling hardware state: your wireless network adapter vanishes completely from both operating systems. In Linux, the interface disappears from ip link and network managers report missing hardware. In Windows Device Manager, the controller resurfaces only as an uninitialized or phantom device throwing Code 10 (This device cannot start. {Operation Failed}) or Code 43. Reinstalling OS-level drivers typically fails, and even physically swapping the M.2 Wi-Fi card often leaves the problem untouched. ...
Unified L4+L7 bandwidth governance: rethinking Internet-scale TLS scanning
When you’re scanning the IPv4 space for TLS certificates, the bottleneck isn’t usually the SYN sweep or the TLS handshakes individually. It’s the interaction between them, and the standard tooling doesn’t model that interaction. The canonical research pipeline is ZMap piped through ZTee into ZGrab2. ZMap fires SYNs at a configured L4 rate. ZGrab2 reads verified hosts off the pipe and runs TLS handshakes at a configured worker count. They share an interface, a kernel, and an uplink, but they don’t share a rate budget. The result on dense CDN ranges is that ZGrab2’s certificate traffic can dwarf ZMap’s SYN stream, with no mechanism for the L7 surge to throttle the L4 cannon. On global anycast prefixes the same dynamic causes something more interesting: per-AS scanner detection at the CDN that neither tool would trigger alone. ...