Implementing ping from the Ethernet layer (ARP,IPv4,ICMP in user space)
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
I built a user-space implementation of ping that constructs Ethernet frames, performs ARP resolution, builds IPv4 headers, and sends ICMP echo requests manually using AF_PACKET.- ARP (packet format, cache with aging, re-ARP, conflict handling) - IPv4 header construction and checksum - DF handling and ICMP Fragmentation Needed (Type 3 Code 4) - IP fragment reassembly - ICMP echo request/reply parsing - A basic ping loop with loss statisticsThe goal was to understand how packets actually move from Layer 2 upward.
HN · launched Feb 23, 2026 · 9 upvotes (top 51%) · 0 views
Niche: network and communication protocol libraries · 70 launches, 5 in the last 7 days · Explore this niche →
Category and tags
- Horizontal
- Dev tools
- Developer
- Not AI
- Hobby / open-source project
Visit website ↗ Source listing ↗
More like this: all 70 launches in network and communication protocol libraries →
Could you build this?
Partial The scope of a user-space ping is well-defined, but writing raw Ethernet frame manipulation with AF_PACKET, ARP table management, and manual checksum calculations requires low-level networking and C knowledge beyond basic vibe coding.
What it would actually take: Requires low-level C or Rust networking code interacting with Linux raw sockets (AF_PACKET / SOCK_RAW). The hard parts are correctly packing binary protocol headers (Ethernet, ARP, IPv4, ICMP), computing Internet checksums (RFC 1071), handling ARP caching/timeouts, and dealing with OS raw socket permissions and network interface binding. Demands systems-level network protocol programming expertise.
Discussion
2 comments analyzed.
Concerns raised: Fragment reassembly in user space is complex and often skipped, Handling DF bit and ICMP Fragmentation Needed requires path MTU discovery
Feature requests: Implement RFC815 data structure for efficient fragment reassembly, Handle path MTU discovery scenarios beyond basic echo/reply
Competitors
Other products that read as similar to this one : 47 launches clear the similarity bar, closest 8 shown.
Attention rank: #28 of 48 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 111 days after the earliest competitor.
- PingStalker · hn · 2025-11-04 · 77 upvotes · similarity 0.44
- Nat traversal using ICMP Destination Unreachable packets · hn · 2026-07-01 · 5 upvotes · similarity 0.42
- I built a macOS tool for network engineers · hn · 2026-02-10 · 243 upvotes · similarity 0.41
- I built an ISP infrastructure emulator from scratch with a custom vBNG · hn · 2026-03-11 · 68 upvotes · similarity 0.38
- cldap_ping · github · 2026-09-28 · 9 upvotes · similarity 0.36
- Pion SCTP with RACK is 70% faster with 30% less latency · hn · 2025-12-28 · 62 upvotes · similarity 0.36
- We Implemented the IPv8 Internet-Draft in Linux, Libc, and BGP · hn · 2026-08-14 · 73 upvotes · similarity 0.36
- Building WebSocket in Apache Iggy with Io_uring and Completion Based IO · hn · 2025-11-17 · 29 upvotes · similarity 0.36
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.