Le 04/07/2018 à 11:33, John Hughes a écrit :
On 04/07/18 11:04, Didier Kryn wrote:

    3) network-manager, which is a replacement for the previous, decides of everything, and cannot be configured.
?

man nmcli

    No manual entry for nmcli

    But this is just because I haven't network-manager installed :-)

    To tell the true story, I'm rather happy with net-tools. I just noticed long ago that network-manager was messing up what I configured with net-tools, and it didn't bring any benefit. Therefore it became the first package I systematically removed right after a Debian install.

    I have configured servers with several ethernet interfaces to different LANs, including some with interface bonding. On laptops, I have wifi roaming with many different wifi stations recorded, and automatic connection to the present station, with priority to Ethernet when plugged in. Everything simple, logical, automatic, and the way everyone wants it, and I don't need neither nm nor wicd for that. I can't see any improvement I would need, except a simpler configuration, and except that, as from ASCII, the init script deserves a little hack.

    If somedy finds a system which does as well or even better and/or is easier to configure, I might try it, but, for the moment, I see on this list that nm and wicd are a major source of problems. But, after all, maybe all these complains will find their way upstream and this will help to improve wicd and make it become a good solution.

        Didier


_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to