I told the flight attendant "the WiFi isn't working"

Original Article ↗ Hacker News Discussion ↗

Airline passengers are sharing stories about in‑flight Wi‑Fi failures and the surprisingly low‑tech remedies cabin crews use, such as a cockpit-style “INTERNET RESET” button that simply reboots the onboard network. Many see this as good UX for non-technical staff, contrasting it with the complex realities of DHCP, captive portals, and IP address exhaustion that often cause connectivity problems on planes and at conferences. Alongside humor and pop‑culture references, commenters highlight broader points about designing resilient systems, making deep networking knowledge more accessible, and the security and legal gray areas around probing shared networks.

Humor and Cultural References

  • Many comments riff on the absurdity of an “INTERNET RESET” button, likening it to “turn it off and on again,” The IT Crowd’s “Internet box,” and South Park’s giant router gag.
  • Some note that what sounds like a joke (“reset the Internet”) now has an intuitive meaning to most people: reboot the nearest access device.

UX, Labeling, and Operations

  • Several argue the label is excellent UX for non-technical flight crews: simple, unambiguous, no jargon like “router restart” or “DHCP lease renewal.”
  • Others suggest alternatives like “Fix Internet” or “Turn Internet off and on again,” but pushback notes these could imply different behavior (e.g., needing to hold the button).
  • Some point out the button might also serve as a signal for automated diagnostics, not just a hard reboot, though this is seen as an extra failure point.
  • Proposals include pressing the button at every flight turnover to avoid lease exhaustion, but others prefer systems that “just work” without crew actions.

Networking and DHCP on Planes

  • The original incident (DHCP lease exhaustion on an aircraft network) resonates; commenters say inflight WiFi often has misconfigured DHCP, small address pools, or long leases.
  • Suggested technical fixes: larger subnets, shorter lease times, dual-stack IPv6 with SLAAC, better vendor configuration.
  • There’s criticism that aircraft WiFi systems can be as limited as “shitty home routers with aviation-grade reset buttons.”

Learning and Practicing Networking

  • Multiple recommendations: build a home lab, use OpenWrt/pfSense/OPNsense, read RFCs, follow networking textbooks and HOWTOs, or study for certifications like CCNA/CCNP/CCIE.
  • Several reminisce that older environments forced you to understand DHCP, ARP, routing, and port forwarding just to get basic connectivity.

Captive Portals, MAC Randomization, and Workarounds

  • Discussion of captive portals implemented via DNS hijacking; complaints they’re fragile and unfriendly to headless/IoT devices.
  • People describe workarounds: travel routers, MAC spoofing, chaining tethering through multiple devices, and using special non-HTTPS sites to trigger portals.
  • MAC randomization is common on mobile; on laptops it’s constrained by DHCP state, captive portals, and session continuity.

Security and “Hacking” Concerns

  • Some warn that active WiFi manipulation or running “hacker tools” on a plane could attract law-enforcement attention or no-fly listing.
  • Others distinguish passive sniffing/diagnostics from actual intrusion, but acknowledge that laypeople and authorities may not recognize the difference.