News for hackers. Stuff that matters.
Re:The sad state of Linux Wi-Fi by captainmuon on Wednesday July 23, 2014 @02:25PM (#8076026)
One problem is that WiFi is completely opaque, especially but not only on Linux. You get no low-level and no debugging information. It just connects and you get some bars, or it doesn't. I never know where to start when debugging a bad connection, and I wouldn't know where to start if I wanted to improve Linux WiFi.

For example, sometimes I can see a network, but can't connect. Why? I'd like to see something like "sent 100 low level packets, checksum failed on 88 of them, disconnecting".

Or I'd like some way to see whether receiving or sending is the problem - do I get garbled packets, or do I get good ones, but no answers to the ones I send.

Sometimes I know a connection is WPA2, but it stubbornly tries another encryption method. Why? Does the AP suggest it, or is it my configuration? Sometimes I can't enter a text password, it only accepts a fixed-length hexadecimal string (happens on Windows a lot). Again why? There is no good central low-level log file or debug tool that lets me see what is going on.

Re:The sad state of Linux Wi-Fi by switch007 on Wednesday July 23, 2014 @02:58PM (#8076261)
I've never dug in to it before, but some googling just suggested

  /sys/kernel/debug/ieee80211/phy*/ 
e.g.

  # cat /sys/kernel/debug/ieee80211/phy*/netdev:*/stations/*/rc_stats

  rate      throughput  ewma prob  this prob  this succ/attempt   success    attempts
       1         0.6       68.0      100.0             0(  0)         9          12
  ...
Re:The sad state of Linux Wi-Fi by gnu8 on Wednesday July 23, 2014 @06:08PM (#8077215)
Looks interesting, but which devices and drivers does it apply to? I have no expectation that this would work over every common wifi interface in current laptops (to say nothing of the typical home gateway with their embedded linux distribution and custom proprietary drivers).
Re:The sad state of Linux Wi-Fi by switch007 on Thursday July 24, 2014 @02:50AM (#8078436)
Any driver which supports debugfs. Proprietary drivers of course will always be problematic.

Manufacturers could always agree on some kind of debugging protocol... I'm sure we'd up with only one "standard" ;-)

Re:The sad state of Linux Wi-Fi by klodolph on Wednesday July 23, 2014 @07:13PM (#8077450)
It's opaque on Linux, but that's not the big problem. It's opaque on OS X and Windows as well, but nobody cares because it works.

I wonder if we'll eventually get the kind of stability that we currently have with ethernet drivers... once the speeds are high enough that we stop upgrading, once the chips go into long-term production instead of changing every few years, once things settle down...

Re:The sad state of Linux Wi-Fi by deathanatos on Wednesday July 23, 2014 @09:08PM (#8077785)
I disagree. It's possible to get advanced output from various command line tools in Linux, and it's possible to get networking information. It's much more difficult to do that on other OSs, especially Windows. I loathe debugging network troubles in Windows, because there is essentially no information. OS X has most of your standard tools, though some in some odd places, e.g., printing the routing table not being done with `route`.

Furthermore, I care. My 2013 Macbook Pro is terribly slow to associate to even nearby APs, and drops the connection often. I have no idea why, because it is opaque: how do you list nearby APs? their signal strength or encryption type? I didn't learn this until just now, and it's,

    /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport -s
Seriously. There's no way I'll remember it, and if you're reaching for it, you likely can't Google it. And it appears to be deprecated. It's a much shorter command in Linux, and in general I find it easier to determine if the problem is the network connection or DHCP failure. IIRC, Network Manager's icon changes — admittedly not much – depending on which one it's on, so even without command line tools, I have some idea what's going on.

OS X has the troubleshooter dialog, but that's never been able to fix the problem. (In general, I feel, those things never do. They also never tell you what they're doing. For all I know, they're just progress bars and timers.) WiFi off, WiFi on fixes a lot of problems.

Re:The sad state of Linux Wi-Fi by chrisbolt on Wednesday July 23, 2014 @10:21PM (#8077946)
Open Wireless Diagnostics in /System/Library/CoreServices/Applications, then click Window -> Utilities. Gives lots of detailed info, frame capture, logging, etc.

https://www.dropbox.com/s/2ndc35q0gxynffl/Screenshot%202014-...

Re:The sad state of Linux Wi-Fi by kalleboo on Wednesday July 23, 2014 @11:09PM (#8078052)
You can access it easier by holding down the "option" key and selecting the Wifi menu http://imgb.mp/jxy.jpg
Re:The sad state of Linux Wi-Fi by rasz_pl on Thursday July 24, 2014 @07:38AM (#8079060)
>I disagree. It's possible to get advanced output from various command line tools in Linux

dont worry, Lennart Poettering (systemD/pulseaudio) is working to solve this problem

Re:The sad state of Linux Wi-Fi by jaseemabid on Thursday July 24, 2014 @08:49AM (#8079310)
Sarcasm?
Re:The sad state of Linux Wi-Fi by stevenhuang on Saturday July 26, 2014 @04:11AM (#8089207)
Oh man, the audio problems I sometimes had with pulseaudio...
Re:The sad state of Linux Wi-Fi by lloeki on Thursday July 24, 2014 @04:01AM (#8078600)
airport -s is incredibly important in setting up roaming correctly with heterogeneous APs. You absolutely want SECURITY column to be identical, else devices won't roam.

> There's no way I'll remember it

I have history(1) and a symlink in a toolbox git repo.

> you likely can't Google it

"!g OSX airport command" works fine

> route

I found netstat -r is the most "Unix-portable" way of querying the routing table (Windows route is a peculiar beast anyway). route is deprecated on linux in favor of ip route.

Re:The sad state of Linux Wi-Fi by TwiztidK on Thursday July 24, 2014 @10:25AM (#8079704)
> > you likely can't Google it

> "!g OSX airport command" works fine

Of course. The parent was referring to a situation when someone lacks internet access, due to a networking problem they are trying to fix, rendering them unable to use Google to find the command.

Re:The sad state of Linux Wi-Fi by koffiezet on Thursday July 24, 2014 @11:55AM (#8080239)
On OSX, just press option and click on your wifi-icon. You'll see the signal strength, channel, speed, encryption type etc of the AP you're connected to expanded in the dropdown menu.
Re:The sad state of Linux Wi-Fi by ori_b on Wednesday July 23, 2014 @11:53PM (#8078147)
I wish. On OSX, I often see a connection with full bars, which fails to connect. I have no idea why. It's incredibly frustrating.
Re:The sad state of Linux Wi-Fi by emmelaich on Thursday July 24, 2014 @12:11AM (#8078180)
Yeah, OSX is good but it still has problems.

    . chooses 2.4 over 5
    . not automatically connecting to my mobile wifi even though I use it all the time
    . simply tries and fails to connect over and over and over .. I have to stop wifi and start it, and then it just works.
My 2013 Air has had three updates including firmware that mention wifi fixes but it still has problems.

OTOH, my Fedora 20 install has been behaving beautifully (though to be said in far less challenging environments)

Re:The sad state of Linux Wi-Fi by vacri on Wednesday July 23, 2014 @09:02PM (#8077775)
Given that wifi has been constantly evolving since it started, it's not going to settle on chips any time soon. 802.11ac has just been released, prompting a new round of chips.
Re:The sad state of Linux Wi-Fi by phunge on Wednesday July 23, 2014 @03:16PM (#8076369)
I've wondered the same thing. Up until now I've avoided digging deep into my issues -- I've never found good docs, googling leads you to misleading forum posts and generally had bad signal-to-noise, and the WiFi stack is nested so deep that it requires a lot of knowledge. But I guess I assumed that the underlying stuff was generally correct and written by experts in the field. Maybe it's time a motivated layman like me dug in and started asking dumb questions.
Re:The sad state of Linux Wi-Fi by tomn on Wednesday July 23, 2014 @06:58PM (#8077390)
NetworkManager doesn't relay any error information to the interface at all, but it's log files are quite detailed.

At least on systemd based distributions (tested on arch), running

  journalctl -fu NetworkManager
will show you the live logs of NetworkManager interleaved with the logs of it's subprocesses; this has lots of juicy information that i've found quite usefull for debugging.
Re:The sad state of Linux Wi-Fi by aye on Wednesday July 23, 2014 @07:15PM (#8077464)
> journalctl -fu NetworkManager

Perfectly sums up my feelings about NetworkManager.

Re:The sad state of Linux Wi-Fi by JetSpiegel on Wednesday July 23, 2014 @11:38PM (#8078115)
What so bad about Network Manager? nmcli is really useful.
Re:The sad state of Linux Wi-Fi by rphlx on Thursday July 24, 2014 @05:37AM (#8078793)
Unnecessarily complex daemon; three lines in /etc/network/interfaces and a few shell scripts will suffice, thank you very much.
Re:The sad state of Linux Wi-Fi by andor on Thursday July 24, 2014 @06:33AM (#8078904)
What's good for you might not be the best option for the majority of people.

Making things that "just work" means handling complexity for users, and leads to somewhat complex code. Debian's static network configuration is great for servers and okay for desktops that never move. But it's nothing that you should put on laptops operated by enterprise users (the people that pay for Linux desktop development). Imagine users calling support from a Starbucks, trying the edit the wifi config files.

Re:The sad state of Linux Wi-Fi by clarry on Thursday July 24, 2014 @08:16AM (#8079165)
Handling complexity by piling more complexity on top is sadly very common, even so common that people think it's inevitable. But it's not the only way. The other way can sometimes be harder, and it tends to take more thought, but in the end you may actually solve and get rid of complexity.
Re:The sad state of Linux Wi-Fi by andor on Thursday July 24, 2014 @09:23AM (#8079445)
Complexity can be caused by the developers of the software, and in that case it is unwarranted. But my assumption is that NetworkManager developers are reasonably competent, and take good decisions in all the trade-offs they have to make.

In their case, they need to support lots of features, and make all of them work seamlessly: multiple Ethernet, Wifi and VPN interfaces, IPv4/IPv6 configuration, modems, firewall policies, and so on. n^m different states. To get rid of this complexity, you'd need to remove options at the bottom of the stack, e.g. only allow communication via serial port at a fixed rate.

Re:The sad state of Linux Wi-Fi by simpsond on Wednesday July 23, 2014 @06:19PM (#8077261)
Wireshark is a good tool for inspecting 802.11 frames, but it's still a pain. If you do go down this path, I highly recommend adding a capture filter for your adapters MAC, so you don't get flooded with management frames. Filter string: wlan addr 00:00:00:00:00:00.
Re:The sad state of Linux Wi-Fi by zercool on Wednesday July 23, 2014 @02:30PM (#8076068)
You're right. This is incredibly frusturating. Are there any good work arounds?
Re:The sad state of Linux Wi-Fi by swinglock on Wednesday July 23, 2014 @06:11PM (#8077221)
I feel the same way on Windows, but I've never attempted to dig deeper.
Re:The sad state of Linux Wi-Fi by jdong on Wednesday July 23, 2014 @03:43PM (#8076535)
>Sometimes I can't enter a text password, it only accepts a fixed-length hexadecimal string (happens on Windows a lot). Again why?

Um, maybe because WEP passphrases are fixed length hexadecimal strings?