summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-August/007191.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-August/007191.html')
-rw-r--r--zarb-ml/mageia-dev/2011-August/007191.html253
1 files changed, 253 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-August/007191.html b/zarb-ml/mageia-dev/2011-August/007191.html
new file mode 100644
index 000000000..30dd6b2c9
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-August/007191.html
@@ -0,0 +1,253 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Drakxnet, drakroam and Draknetcenter : let's fix it or throw it.
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakxnet%2C%0A%09drakroam%20and%20Draknetcenter%20%3A%20let%27s%20fix%20it%20or%20throw%20it.&In-Reply-To=%3C201108022220.49601.maarten.vanraes%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="007189.html">
+ <LINK REL="Next" HREF="007146.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Drakxnet, drakroam and Draknetcenter : let's fix it or throw it.</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakxnet%2C%0A%09drakroam%20and%20Draknetcenter%20%3A%20let%27s%20fix%20it%20or%20throw%20it.&In-Reply-To=%3C201108022220.49601.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] Drakxnet, drakroam and Draknetcenter : let's fix it or throw it.">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Tue Aug 2 22:20:49 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007189.html">[Mageia-dev] Drakxnet, drakroam and Draknetcenter : let's fix it or throw it.
+</A></li>
+ <LI>Next message: <A HREF="007146.html">[Mageia-dev] new samba-squid subpackage proporsal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7191">[ date ]</a>
+ <a href="thread.html#7191">[ thread ]</a>
+ <a href="subject.html#7191">[ subject ]</a>
+ <a href="author.html#7191">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op dinsdag 02 augustus 2011 17:29:35 schreef Buchan Milne:
+&gt;<i> On Monday, 1 August 2011 20:21:21 Maarten Vanraes wrote:
+</I>&gt;<i> &gt; Op maandag 01 augustus 2011 11:42:26 schreef Thomas Lottmann:
+</I>&gt;<i> &gt; &gt; Hello,
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; I should have written this mail much sooner, but finally, I am totally,
+</I>&gt;<i> &gt; &gt; completely and starting to be hatefully fed up of these tools.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; The Mandriva/Mageia tools that manage the network on computers,
+</I>&gt;<i> &gt; &gt; especially the wireless networks are completely dysfunctional. While
+</I>&gt;<i> &gt; &gt; the Network Center does not seem to even communicate with the system
+</I>&gt;<i> &gt; &gt; tools to know what is happening during the link setup, it does not
+</I>&gt;<i> &gt; &gt; auto-refresh network lists properly.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Since 2010.1 now even mixes up itself in it's own network scripts (the
+</I>&gt;<i> &gt; &gt; ones stored in wireless.d). This maxes it wrongly detect numerous
+</I>&gt;<i> &gt; &gt; wireless points (he seen WPA2 Enterperise hotspots as opened or WEP, or
+</I>&gt;<i> &gt; &gt; more nerving, becomes incapable or storing the right authentication
+</I>&gt;<i> &gt; &gt; information).
+</I>&gt;<i>
+</I>&gt;<i> My &quot;production&quot; laptop is still currently running Mandriva 2010.x, and I
+</I>&gt;<i> don't have problems like this. Work networks run WPA2-Enterprise with
+</I>&gt;<i> EAP-PEAP- MSCHAPv2, home runs WPA2-Personal. In the cases I have seen
+</I>&gt;<i> this, it is typically a buggy AP (and in some cases, other platforms have
+</I>&gt;<i> also mis- detected the network details). In some cases, upgrading the AP
+</I>&gt;<i> firmware has resolved the problem.
+</I>&gt;<i>
+</I>&gt;<i> But, these are *specific* issues, and need bug reports with detailed
+</I>&gt;<i> information.
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; A tool that breaks itself is a complete shame!
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; The GUI is also appalling. Despite it's numerous possibilities, it is a
+</I>&gt;<i> &gt; &gt; mess and 60% of it cannot be used by something else than the system or
+</I>&gt;<i> &gt; &gt; a network expert.
+</I>&gt;<i>
+</I>&gt;<i> There are some deficiencies, but in many cases it does at least work. And
+</I>&gt;<i> at least my network comes up regardless of how I boot, where I booted to,
+</I>&gt;<i> whether a user is logged in to a desktop or not (which is not the case on
+</I>&gt;<i> e.g. Fedora).
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; The code itself is undocumented and it extremely difficult to read.
+</I>&gt;<i>
+</I>&gt;<i> The few times I looked at the code, it was quite readable. Unfortunately,
+</I>&gt;<i> the pieces I wanted to do something about ended up requiring changes in
+</I>&gt;<i> non-perl parts.
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; These tools are getting really bad and not working properly anyway
+</I>&gt;<i> &gt; &gt; since a long time now. So either we fix it and improve it (recoding?),
+</I>&gt;<i> &gt; &gt; either we definitely switch to Network Manager.
+</I>&gt;<i>
+</I>&gt;<i> Please no. The biggest frustrations I personally have have nothing to do
+</I>&gt;<i> with net_applet vs NM. My current biggest frustrations are:
+</I>&gt;<i>
+</I>&gt;<i> 1)That wpa_supplicant doesn't return different results on incorrect (WPA2-
+</I>&gt;<i> Enterprise EAP-PEAP) passwords:
+</I>&gt;<i> <A HREF="http://hostap.epitest.fi/bugz/show_bug.cgi?id=399">http://hostap.epitest.fi/bugz/show_bug.cgi?id=399</A>
+</I>&gt;<i>
+</I>&gt;<i> 2)That net_applet doesn't prompt for passwords if wpa_supplicant says it
+</I>&gt;<i> needs a password. I filed a bug for this against Mandriva:
+</I>&gt;<i> <A HREF="https://qa.mandriva.com/show_bug.cgi?id=51705">https://qa.mandriva.com/show_bug.cgi?id=51705</A>
+</I>&gt;<i>
+</I>&gt;<i> Implementing the required dbus communication would allow a number of other
+</I>&gt;<i> improvements (e.g. not having to restart wpa_supplicant for configuration
+</I>&gt;<i> changes, possibly avoid manual parsing/writing of the configuration etc.).
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; I am ready to participate if
+</I>&gt;<i> &gt; &gt; necessary (despite my lack of competence), but I do not want to see
+</I>&gt;<i> &gt; &gt; these tools 'as is' on my computer anymore, and no longer want to see
+</I>&gt;<i> &gt; &gt; these issues that down Mageia's reputation in comparison to other
+</I>&gt;<i> &gt; &gt; popular projects here such as Arch, Fedora or Ubuntu, who do have
+</I>&gt;<i> &gt; &gt; proper tools delivered by default.
+</I>&gt;<i>
+</I>&gt;<i> I disagree with your statement. For example, while Fedora may seem to have
+</I>&gt;<i> &quot;proper tools&quot;, there are many use cases that aren't considered, and a
+</I>&gt;<i> number of issues are still experienced (at least according to my
+</I>&gt;<i> colleagues reports).
+</I>&gt;<i>
+</I>&gt;<i> Allowing NM or non-NM, and having both improved would be win-win.
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; This is not the first time I complain about this tool. We should not
+</I>&gt;<i> &gt; &gt; leave this unchanged. It is far too annoying and pushing to so much
+</I>&gt;<i> &gt; &gt; loss of time.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Yours sincerely,.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Thomas.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; personally, alot of problems could likely be attributed to using all
+</I>&gt;<i> &gt; those several of those apps together.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; imho, the network tools should be redesigned a bit, according to good
+</I>&gt;<i> &gt; usability, but mostly, either they should all be nicely integrated which
+</I>&gt;<i> &gt; each other, or we should just have one that does all nicely.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; personally, i find the netapplet the best working and use that
+</I>&gt;<i> &gt; exclusively to avoid issues.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; but sadly, even netapplet is far from complete.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; as some kind of start, we should have an app that exists in drakconf, but
+</I>&gt;<i> &gt; also accessible via an applet, but again, perhaps we should have multiple
+</I>&gt;<i> &gt; applets, with one for each connection.
+</I>&gt;<i>
+</I>&gt;<i> I don't think this is necessary, the 'Network Center' does an adequate job
+</I>&gt;<i> (taking into account some limitations in the network scripts).
+</I>&gt;<i>
+</I>&gt;<i> &gt; eg: a wifi access link, 2 network connections (one of which goes to
+</I>&gt;<i> &gt; internet), and 3 openvpn tunnels (as an example) it would even be better,
+</I>&gt;<i> &gt; if bluetooth networking could also be included.
+</I>&gt;<i>
+</I>&gt;<i> Bluetooth networking *can* be included, but there is an artificial
+</I>&gt;<i> limitation on only one ppp connection, so you wouldn't be able to have a
+</I>&gt;<i> Bluetooth SPP- based ppp connection as well as a
+</I>&gt;<i> mobile-broadband-dongle-based connection (or ADSL).
+</I>
+why would there be only 1 possible ppp connection? that sounds odd.
+
+&gt;<i> For bluetooth ppp over SPP, the bluetooth configuration only needs to be
+</I>&gt;<i> done once ever (if done correctly), the rfcomm connections will be
+</I>&gt;<i> established when necessary.
+</I>&gt;<i>
+</I>&gt;<i> (Or, are you referring to PAN?).
+</I>
+i think i was, yes, but i'm not too clear on how this sort of thing works
+
+&gt;<i> &gt; (this would also allow for
+</I>&gt;<i> &gt; multiple internet connections at a later time with some advanced routing)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; at the same time, people could tell at a glance if they accidentally use
+</I>&gt;<i> &gt; more than one internet access method.
+</I>&gt;<i>
+</I>&gt;<i> You can see this in Network Center.
+</I>
+yes, but i'm not really a fan of network center, and the whole point of the
+net_applet is that you can always see it, in your systray area. which is where
+i'd like to have all current networking connections separately, so you can
+have 3 openvpn connection and 3 icons, it can more easily show you which are
+working and which aren't.
+
+each of those icons should be 4 state, off-state (but present), on-state, fail-
+state and gateway-state (this connection is use as one of the default routes.)
+
+(incidentally, i'd also like for most connections to set up default route and
+having some small advanced routing that would at least enforce symmetrical
+routing.
+
+eg: each such icon could have as right click menu:
+ - enable/disable
+ - reconnect (?)
+ - use for internet (default route)
+ - delete
+-------------------
+ - add new connection (wizard with several types: vpn, virtual interfaces,
+bonds, bridges, etc... )
+ - firewall ----&gt; (firewall options)
+---------------
+ - network center
+ - help
+ - exit
+
+ie: no more &quot;followed interface, and the like options, because they only
+confuse people.
+
+in drakconf there should then be a network center which is the same thing if
+you click on the net_applet on network center.
+
+the network center should also be an extension of net_applet, the same icons
+should be shown, but bigger with the same states and same right click menu,.
+
+
+iow: i would like them all to be nicely integrated with eachother.
+
+
+&gt;<i> &gt; about openvpn, some of those are user-related (even though they have
+</I>&gt;<i> &gt; effects on global routing), especially password related things,
+</I>&gt;<i> &gt; personally, i think it'd be better if these can only be controlled
+</I>&gt;<i> &gt; through the applet by the user it's from (with perhaps an option to
+</I>&gt;<i> &gt; allow any user to control this too)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; again with openvpn, it would be usefull if there was some kind of way to
+</I>&gt;<i> &gt; know it's not only running, but also if it's essentially active or not,
+</I>&gt;<i> &gt; and if it's used as a internet gateway.
+</I>&gt;<i>
+</I>&gt;<i> Well, the general feedback provided to users (also with e.g. ppp
+</I>&gt;<i> connections) could be improved.
+</I>&gt;<i>
+</I>&gt;<i> &gt; These are some things which i have noticed over the years of using it and
+</I>&gt;<i> &gt; listening to end-user problems.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; perhaps the above can be used as a starting point for a usability scheme.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Thomas, since you feel this strongly, are you willing to spend some time
+</I>&gt;<i> &gt; on this?
+</I>&gt;<i>
+</I>&gt;<i> Regards,
+</I>&gt;<i> Buchan
+</I></PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="007189.html">[Mageia-dev] Drakxnet, drakroam and Draknetcenter : let's fix it or throw it.
+</A></li>
+ <LI>Next message: <A HREF="007146.html">[Mageia-dev] new samba-squid subpackage proporsal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7191">[ date ]</a>
+ <a href="thread.html#7191">[ thread ]</a>
+ <a href="subject.html#7191">[ subject ]</a>
+ <a href="author.html#7191">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>