Tim wrote: > On Fri, 2012-01-13 at 14:26 +0000, Timothy Murphy wrote: >> That's why I wish NM would stick to WiFi. > > It's there to deal with changing networks, such as my laptop being > either wired or wireless, on any LAN, automatically. And it does that > fine, for me. To force it into only dealing with WiFi would make it > useless. Do you mean that your ethernet and WiFi are on different LANs? If they are, wouldn't it be simpler _not_ to use NM on the ethernet LAN? In my case - which I would have thought was normal for home users - both ethernet and WiFi are on the same network, 192.168.2.* . It doesn't make the slightest difference if I plug in ethernet (as I sometimes do, because it seems faster for some things), whether I am using NM or not. > Where I can see Network Manager to be a pain is when users try to use a > badly set up LAN. Such as, half using DHCP, then manually overriding > some of the settings sent out by the DHCP server (all those people > complaining about hosts or resolve.conf files being ignored - who should > really be customising their DHCP client, not directly messing with > networking settings). I'm not sure what you mean. How do you "customise your DHCP client"? NM doesn't work with 2 of my machines - an EeePC and an old machine bought at Lidl. It also doesn't work properly with Orinoco Classic Gold PCMCIA WiFi cards. The network service works on all these. In my opinion NM software is absurdly complicated, largely because it is trying to do too much. And also because no-one has ever documented exactly what it is meant to be doing. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
