HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vanhoefm
airsnitch
C2026–2026
vanhoefm / airsnitch

airsnitch

Generalized Wi-Fi Client Isolation Bypasses

2Distinct people
2Mentions
0Explicit recommenders
832GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Generalized Wi-Fi Client Isolation Bypasses

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-02-26 21:38:50 UTC to 2026-02-26 22:59:18 UTC.

012026-02-26 21:00:00 UTC to 2026-02-26 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 26, 21:002026-02-26 22:00:00 UTC to 2026-02-26 23:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 26, 22:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 26, 21:002026-02-26 21:00:00 UTC2026-02-26 22:00:00 UTC101
Feb 26, 22:002026-02-26 22:00:00 UTC2026-02-26 23:00:00 UTC110

What Hacker News says

2 sources
We don't have a CVE number. Whether devices/networks are affected also highly depends on the specific configuration of the device/network. This means that some might interpret some of the identified weaknesses as software flaws, but other weaknesses can also be seen as configuration issues. That's actually what makes some of our findings hard to 'fix': it's easy to say that someone else is responsible for properly ensuring client isolation :) Hence also hard to really assign CVE(s). One of the main takeaway issues, in my view, is that it's just hard to correctly deploy client isolation in more complex networks. I think it can be done using modern hardware, but it's very tedious. We didn't test with VLAN separation, but using that can definitely help. Enterprise devices also require a high amount of expertise, meaning we might have missed
Read the rest
some specialised settings.. So I'd recommend testing your Wi-Fi network, and then see which settings or routing configurations to change: https://github.com/vanhoefm/airsnitch
In AirSnitch: Demystifying and breaking client isolation in Wi-Fi networks [pdf]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.