Executes wpa_supplicant in too verbose mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Fix Released
|
Undecided
|
Unassigned | ||
network-manager (Debian) |
Fix Released
|
Unknown
|
|||
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Alexander Sack |
Bug Description
Binary package hint: network-manager
I'm using
alexander@
ii network-manage 0.6.2-0ubuntu7 network management framework (daemon)
ii network-manage 0.6.2-0ubuntu7 network management framework (GNOME Frontend
on Dapper. I found that wpa_supplicant gets executed by nm like this:
alexander@
root 9441 1 0 20:57 ? 00:00:00 /sbin/wpa_
Because of the "-dd", an *EXTREMELY* awful lot of messages are generated by wpa_supplicant, making it hard to spot important messages. Put differently: The way network manager executes wpa_supplicant, wpa_supplicant floods syslog with (to me) unimportant messages.
As that's the default way of wpa_supplicant being executed, I'm filing a bug. I'm also unable to find a way to configure how wpa_supplicant gets executed - where's the configuration item?
Changed in network-manager: | |
importance: | Untriaged → Wishlist |
status: | Unconfirmed → Confirmed |
Changed in network-manager: | |
status: | Unknown → Unconfirmed |
Changed in network-manager: | |
status: | New → Fix Released |
Changed in network-manager: | |
status: | New → Fix Released |
status: | Confirmed → Fix Released |
I would agree that it is really quite spammy, but I would imagine it's because it's still very new and the debugging information is useful to collect when it goes wrong.
Having said that, it would be great to be able to get more control about how wpa_supplicant is run and also when - I seem to get little pauses in my network traffic every few minutes while it scans for Access Points, even though I am already connected to one (the only one in range, as it happens).