Tim: >> 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. Timothy Murphy: > 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? I mean things like take the laptop home, it automatically joins my network. Take it somewhere else, it automatically joins that network (well, once I've established credentials, it'll automatically join that network, now, and the next visit). And at home I have a wireless network, but I could plug in the cable if I need to do something that way. And Network Manager manages that, I just plug in, or get near enough, and connection just happens. I don't have to fiddle around with bringing some network interface up on the command line, with any GUI, or any sort of list. I don't have to change any settings to suit the different network, Network Manager has handled changes when the network came up (different DNS here, different IP there, etc.). > I'm not sure what you mean. > How do you "customise your DHCP client"? Well, in the olden days, it was done in /etc/dhclient.conf file. Where, you added in overrides that your client should use instead of the information supplied by the server. Such as use some other DNS server than it tells you to. Of course, one problem with that is that people kept on fiddling with their machine configuration, instead of setting up their DHCP server properly. i.e. Put in working DNS server addresses into the DHCP server. Nowadays it ought to be done through some Network Manager options, to customise the particular connection you're using. Again, it's the case of configuring the network properly, rather than trying to bludgeon in settings at a lower level. > 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. I can't answer for that. The same drivers are used. It's just an automation manager that follows a set of rules about what to do. It's worked on anything that I've thrown at it. But then I have a working DHCP server on my LAN. I'm not expecting an automation tool to work without the normal data used for automation. > In my opinion NM software is absurdly complicated, > largely because it is trying to do too much. It's not doing very much at all. Notice a network is available, apply suitable configuration to your network to use it. > And also because no-one has ever documented > exactly what it is meant to be doing. On that I agree. As well as a lack of good documentation, or even explanation, there are some damn fool notices, like this one: NetworkManager: <info> (wlan0): deactivating device (reason: 37). What the hell does that mean? And, since there was no documentation, the only way you could possibly find out would be to get the source code, then reverse engineer the programmer's thought processes. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- 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
