Bug 24938

Summary:	mandi seems broken with network
Product:	Mageia	Reporter:	w unruh <unruh>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mandi-1.4-3.mga7 Also mandi 1.4-4.mga8	CVE:
Status comment:

Description w unruh 2019-06-10 18:59:09 CEST

Description of problem:
One of mandi's only job is the network-- that seems the only plugin that comes with mandi-- are there others? But it does not do a good job on that.

If I leave the default for /etc/sysconfig/wpa_supplicant which is I believe what mandi reads to start up wpa_supplicant (no DEVICES, no INTERFACES) then Network Center (NC) does not use mandi as far as I can tell, because /lib/libDrake/networking/monitor.pm does not get anything back from the dbus request for the list of scan results. If I put in
INTERFACES="-iwlp58s0"
DRIVERS="-Dnl80211"
(those are the right interface number and driver for my laptop wireless card)
then it seems that mandi does return some addresses but less than half of those
which are there according to iwlist (and in particular not the strongest ones). And sometimes it returns nothing in the list of scan results. So, when mandi does not work it is useless and when it does it is also useless.

Or, I do not know if one should tell wpa_supplicant to Scan first before reporting ScanResults (as in monitor.pm)

Version-Release number of selected component (if applicable):

How reproducible: always.

Steps to Reproduce:
Change /etc/sysconfig/wpa_supplicant to add INTERFACES and DRIVERS appropriate for your wireless card
Reboot
open Network Center and look at the reported access points. I get less than half of those reported by iwlist
(Note that monitor.pm uses iwlist if mandi, or wpa_cli do not work.
iwlist has other problems-- namely does NOT report anything if there are more than 200 access points available. But that is another problem discussed elsewhere)

Comment 1 Marja Van Waes 2019-06-11 11:49:06 CEST

Assigning to the Mageia tools maintainers because the previous upstream (Mandriva) no longer exists

CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 2 w unruh 2022-10-05 18:34:01 CEST

mandi is still flakey.
--
I am running network-center. Especially at work where I use eduroam, network center keeps thinking that the connection is WEP. It is WPA-Enterprise. This both messes up /etc/wpa_supplicant.conf and of course results in a failed connection. This tends to happen especially when I change from home to (Which is WPA-Privatekey) to work. If I open config, it says that the connection type is WEP.
When I do wpa_cli scan  and wpa_cli scan-results, eduroam is listed as WPA_EAP.
But mandi still keeps thinking it is WEP as that is what is reported to network-center. 

It is really unclear to me why mandi exists, when wpa_cli does the job (unfortunately it needs to be running as root to do so-- no idea why so I run draknetcenter via sudo. But of course mandi does not need that and it is what takes over the connection scan.

Someone really really  needs to take draknetcenter in hand and rewrite it, using nl80211 and either iw ( instead of iwlist-- but iw reports are a complete mess, plus the owners of iw refuse to stabilise the output and warns not to screen-scrape, when, as far as I can see, that is the only way of using the output, and its man page is at best a stub. FAr more useful is wpa_cli which unfortunately only works under root.)

It is really a shame that wireless networking is such a mess.

Source RPM: mandi-1.4-3.mga7 => mandi-1.4-3.mga7 Also mandi 1.4-4.mga8
Version: Cauldron => 8