[Mageia-dev] Mageia 3 specifications

[JA Magallón]

On 06/05/2012 11:41 PM, Olav Vitters wrote:
> On Tue, Jun 05, 2012 at 10:44:31PM +0200, Guillaume Rousse wrote:
>> Le 05/06/2012 16:20, Olav Vitters a écrit :
>>> Also, with latest NetworkManager, it seems you can do pretty advanced
>>> network configurations (lacks UI). The UI is planned for GNOME 3.6.
>>> However, seems that loads of Mageia users have issues with
>>> NetworkManager, so not sure what to do. Perhaps safer to wait a year and
>>> hope that other distributions solve the bugs?
>> Approximatively 50% of those problems come from the coexistence with
>> drakxtools and sysinit, conflicting for the control of the
>> interface, rather than actual problems in NM code. Waiting for them
>> to magically disapear won't help much...
>
> Ah ok, but shouldn't that all be fixed now that the patch is back to
> make NetworkManager properly ignore stuff that it should ignore?
>

I tink it is _lot_ easier even for drakxtools to write a file into
/etc/NetworkManager/system-connections that to mess with ifcfg-* files.

And NM is the only sane way to have, in my case, 4 or 5 WiFi configurations
for the same interface and let it pick the right one depending on my
location. It is just marvelous, and without any ifcfg-* file rewriting
on the fly.

And I suppose it can also be done, but I never managed to do without NM:
let my linux in the far corner of the house boot and connect to wifi
without any user logged in...

So in my case, a big +1 for NM and kill all sysvinit files for network.

I acknowledge that I never tried to do bonding with NM, for example...

> meaning: only look for USE_NM/NM_CONTROLLED (I forgot which), not demand
> more than that.
>
>
> But ideally it would be nice if there was only one way to setup a
> network.. and for me that means NetworkManager :). But drakxtools was
> more advanced IIRC, so first NetworkManager needs to get more advanced,
> more documentation, etc.
>
> Cool possibilities with just NetworkManager:
> http://fedoraproject.org/wiki/Features/NMEnterpriseNetworking
>
> https://bugzilla.gnome.org/show_bug.cgi?id=677148:
> (all one bugzilla.gnome.org, seem duplicates, but there is a bug per
>   product, so bug for maybe gnome-control-center, gnome-shell, etc)
>
> 677144: network: make sure bridged devices are handled
> 677145: network: make sure bridged devices are handled
> 677146: network: make sure bonded devices are handled
> 677147: network: make sure bonded devices are handled
> 677148: network: make sure vlans are handled
> 677149: network: make sure vlans are handled
> 677150: network: make sure ipoib is handled
> 677151: network: make sure ipoib is handled
>
> I had to lookup what ipoib (IP over infiniband) meant, article is here:
> http://www.ietf.org/wg/concluded/ipoib.html
>
>
> GNOME shell specific:
> https://bugzilla.gnome.org/show_bug.cgi?id=677142: multiple nics (NM can
> handle it, GNOME shell not)
>    677142: network: make sure multiple nics are handled ok
>    677143: network: make sure multiple nics are handled ok
>
> Note: The support is in NetworkManager. The GNOME bugs are to ensure it
> is shown/exposed in the UI properly. Not sure if available in stuff like
> KNetworkManager, but NM is not specific to GNOME.
>
> All bugs above are really server like things. I thought drakxtools still
> was better at setting up Wifi; and I think that is more important to get
> right than vlan/bridging/etc.
>


-- 
J.A. Magallon <jamagallon()ono!com>        \               Winter is coming...