Jump to content

Big Wi-Fi hole reported

Recommended Posts

Current:  JRiver 24 on Win 10 PC (AMD Ryzen 5 2600 with 32 GB RAM) or Daphile on an I5-2500K with 16 GB RAM


Pre-amp - Rotel RC-1590

Amplification - Pioneer M-22 (winter) - Sony TA-N55ES (summer)

Speakers - Revel M126Be with 2 REL 7/ti subwoofers

Cables - Tara Labs RSC Reference and DiMarzio Interconnects

Link to post
Share on other sites

I wonder how well this works on a wifi access point that is not also a router. Now that I think I have to worry much, but it's still interesting.

No electron left behind...

Link to post
Share on other sites
16 hours ago, AudioDoctor said:

I wonder how well this works on a wifi access point that is not also a router.


This is way over my head but my impression of the problem is fake traffic can be injected in the form of unencrypted wifi packet fragments. If that's the case, the wifi client devices can be forced into picking up phony dns without involvement from any upstream router/dhcp server. This sounds extremely serious as any wardriver with a big enough antenna can redirect your traffic and grab your userid/password just like that. But wouldn't private dns on client devices cause the fake dns to be dropped and bypass the problem? Also, wouldn't encrypting most app level traffic inside the compromised wifi pipe at least make sure most of your data can't be snooped? And wouldn't isolating lan traffic originating from wifi devices into a low trust segment contain the problem so it won't spill over to the main lan?


The above might well be total daydream of course. So would the real network experts here clarify the real nature of the problem and what that would imply?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...