Re: NM fails to connect when booting ?? -[SOLVED]
On Thursday 19 March 2009 00:11:19 Richard England wrote: > Mark Haney wrote: > > Timothy Murphy wrote: > >> I wish some guru who understands NM would bring out a variant > >> that just connects on bootup. > >> I'm pretty sure the standard version would rapidly fall into disuse. > > > > But, they have that feature already. It's the way network interfaces > > have started for a decade. Why bother with NM at all when starting the > > interface on boot is what 99% of people need anyway? > > > > As for the arguments about wireless connectivity, how many people > > actually move between wireless connections? If you do it might be only > > between 2, home and work. > > > > NM sucks, everyone knows it, so let's can it and move to something that > > doesn't. I'll throw my .02 cents in here: NM Rocks ! I can connect to most any wireless connection I come across without issues. It auto connects to remembered SSID's on startup as well. The only area I have issues is with trying to setup VPN access via NM. > > NM works fine for me on my laptop and I regularly move between 4 > different wireless connections. > > It may suck for you but it works great for me. "...so let's can [this > thread] and move to something [else more productive]", eh? > > ~~R -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Aaron Konstam wrote: > And the latest NM can be configured to connect on boot. 1. What do you mean by the "latest" NM? I get [...@mary ~]$ grep NetworkManager /var/log/rpmpkgs NetworkManager-0.7.0.99-3.fc10.i386.rpm NetworkManager-glib-0.7.0.99-3.fc10.i386.rpm NetworkManager-gnome-0.7.0.99-3.fc10.i386.rpm NetworkManager-openvpn-0.7.0.99-1.fc10.i386.rpm NetworkManager-vpnc-0.7.0.99-1.fc10.i386.rpm 2. Are you using KDE or Gnome (or something else)? (I am running KDE.) 3. I have checked-in "Activate device when computer starts" in f=>Applications=>Administration=>Network Configuration, on highlighting the device in question (eth1) and clicking on Edit. In fact all the check-boxes on this page are ticked. I notice incidentally that if I go to f=>Applications=>Administration=>Network Device Control, I see that nothing is listed under "The following network interfaces are configured in the active profile". Does one need to change the "active profile"? If so, how? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
William Case venit, vidit, dixit 18.03.2009 18:55: > On Wed, 2009-03-18 at 17:35 +, Matthew Saltzman wrote: >> On Wed, 2009-03-18 at 11:46 -0400, William Case wrote: >>> Hi; >>> >>> On Wed, 2009-03-18 at 14:26 +0200, Antti J. Huhtala wrote: ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > William Case wrote: > >>> >> >> The lack of documentation is regrettable, but I haven't had much trouble >> lately making it do anything I've tried. (Admittedly, I haven't tried >> everything possible. In particular, I haven't tried to start a wireless >> connection at boot, which seems to be the most common problem scenario.) >> >>> I actually think that NM is a great improvement over >>> system-config-network. That is one of the reasons why I have brought >>> any problems I am having with NM to this mailing list. I would rather >>> get NM working for me than return to system-config-network. >>> >>> For ordinary users or users who would rather spend their time on things >>> other than tweaking their wireless or wired network -- keep it >>> simple,stupid (KISS). The problem is, if you want to make some minor >>> changes or alterations you have to dive into the arcane nether world of >>> networking. >>> >>> I would suggest: >>> 1. A button that allows you to disconnect (turn it off) temporarily >>> -- say to the next boot. >> >> Right-click the applet and uncheck Enable Networking or Enable Wireless, >> as appropriate. > > Sorry to everyone. Was trying to disconnect by left-click then clicking > on "System eth0." > >> >>> 2. An "Edit Connections" that actually allows you to edit >>> connections. >> >> All my wireless connections are editable from the applet. The wired >> connections are editable from s-c-network, as mentioned above. >> Apparently Fedora devs think that that's the way to go. >> >>> 3. Tie editing to root, if necessary, with the usual sudo or su - >>> popup. >> >> See s-c-network. It might be nice if nm-applet started s-c-network when >> you tried to edit a "non-editable" connection, but if this is where an >> "ordinary user" would think to >> edit /etc/sysconfig/network-scripts/ifcfg-eth0, then s-c-network the way >> to do it. >> >>> 4. Clearly show in the gui how to turn ONBOOT to yes or no. >> >> See s-c-network. >> >> BTW, I have a desktop with a recent F10 install, fully up to date. It >> has only a wired interface. That interface comes up at boot (before >> login) with no problem using NM, not using the network service. I have >> not made any changes to its /etc/sysconfig/network-scripts/ifcfg-eth0. >> s-c-network shows that it is on at startup and controlled by NM. >> > > Trouble in paradise then. I have two recent F10 installs, fully up to > date. Neither had ifcfg-eth0 BOOTUP=yes. The default depends on your install media: if you didn't use your device during install then anaconda put BOOTUP=no there. Which is why the recent updates break automatic wired connections for existing users who installed from CD/DVD. (NM used to ignore that setting.) > >>> 5. A Default button that returns any adjustments to the default >>> settings. >>> 6. A manual that is useful. >>> >>> And, by the way, what does the "never" that is placed at the end "System >>> eth0" line mean? >> >> Means "Never connected to that interface." Apparently incorrect or >> meaningless for System eth0, but seems to work for wireless. >> > I suppose I am being a bit tentative because I got into a major mixup in > F9 between NM and system-config-network. I just wish Fedora would make > the network connecting completely one or the other. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Mark Haney wrote: Timothy Murphy wrote: I wish some guru who understands NM would bring out a variant that just connects on bootup. I'm pretty sure the standard version would rapidly fall into disuse. But, they have that feature already. It's the way network interfaces have started for a decade. Why bother with NM at all when starting the interface on boot is what 99% of people need anyway? As for the arguments about wireless connectivity, how many people actually move between wireless connections? If you do it might be only between 2, home and work. NM sucks, everyone knows it, so let's can it and move to something that doesn't. NM works fine for me on my laptop and I regularly move between 4 different wireless connections. It may suck for you but it works great for me. "...so let's can [this thread] and move to something [else more productive]", eh? ~~R -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Matthew Saltzman wrote: On Wed, 2009-03-18 at 11:46 -0400, William Case wrote: BTW, I have a desktop with a recent F10 install, fully up to date. It has only a wired interface. That interface comes up at boot (before login) with no problem using NM, not using the network service. I have not made any changes to its /etc/sysconfig/network-scripts/ifcfg-eth0. s-c-network shows that it is on at startup and controlled by NM. My impression is that if the network is connected (and maybe up) during install, that the config file is functional. That's commonly not the case with wireless, or less commonly the case, if you prefer. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Tim wrote: PS: I'm quite sick of gmane news postings to this mailing list that INAPPROPRIATELY set a post-to header to THEIR news server. I have to manually remove the post-to header and manually add the proper to header. It's quite a cheek to act as a gateway to someone else's mailing list, then try and subvert posts to themselves. Tim, it's possible that the site runs a mail to news gateway of their own, and set the group as moderated, with a moderator address of the list submission address. Since you clean it up I can't see the headers to guess, but I would expect your list input software to clean the headers pretty aggressively by default, and not leave you to do it. Sorry to copy the list... -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 18 Mar 2009 15:44:30 -0500 Aaron Konstam wrote: > > NM sucks, everyone knows it, so let's can it and move to something that > > doesn't. > > > Not everyone. I like it. I agree. I use NM on three laptops that regularly use two different wireless access points and one EVDO modem. NM is the real thing for handling networking on those machines. I use static addresses on the laptops but I just added them to the dhcpd.conf on my server so there's no need to horse around on the client side. I also use NM on my Acer Aspire One for doing network testing at customer sites for the cable tv/Internet/phone company that I do some tech work for. Customer says his connection isn't working or runs slow? Connect from there with my Acer. Instant answer to the question: is it the customer's equipment or something else. NM works fine. From my point of view. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Aaron Konstam wrote: On Wed, 2009-03-18 at 09:12 -0400, Mark Haney wrote: Timothy Murphy wrote: I wish some guru who understands NM would bring out a variant that just connects on bootup. I'm pretty sure the standard version would rapidly fall into disuse. But, they have that feature already. It's the way network interfaces have started for a decade. Why bother with NM at all when starting the interface on boot is what 99% of people need anyway? As for the arguments about wireless connectivity, how many people actually move between wireless connections? If you do it might be only between 2, home and work. NM sucks, everyone knows it, so let's can it and move to something that doesn't. Not everyone. I like it. And the latest NM can be configured to connect on boot. There is a checkbox for start on boot, note that as of the current version March 10th, it doesn't work, although the most recent update may have addressed that. There was discussion about anaconda and NM not playing well, perhaps someone finally looked into it. From memory: unless there is an explicit "ONBOOT=yes" the NIC defaults to no. That may be a simplification, I set my wlan0 checkbox to boot at startup and it doesn't. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 15:11 -0600, Joseph L. Casale wrote: > >> NM sucks, everyone knows it, so let's can it and move to something that > >> doesn't. > >> > >Not everyone. I like it. And the latest NM can be configured to connect > >on boot. > > Can you edit your connections? Wireless ones with nm-applet. Wired ones with system-config-network. > > -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Mark Haney wrote: Bill Davidsen wrote: I had actually hoped that the "profiles" stuff might let me have multiple configurations which work at multiple locations. I have three locations needing credentials, and I'd like to have a "Starbucks" configuration which found whatever was available. Doesn't seem to work that way. :-( Thankfully I know how to write scripts and use iwconfig... Yeah, it's a saving grace for those of us who have given up on NM. NM sucks, everyone knows it, so let's can it and move to something that doesn't. The reason people think it sucks is that the documentation is missing, inadequate, or wrong. And when I mentioned this someone told me that writing documentation is not a good use of developer time, and that's hogwash. I've done FOSS and commercial development for over thirty years, and on commercial software there was always a description before the code was written, and someone writing documentation which was checked by QA, or for something I was giving away, I wrote my own because I wanted people to love and use my software. We used to call the NM approach "if it was hard to code it should be hard to use." Actually, the documentation issue isn't why I think it sucks. But you are correct, no/poor/incorrect documentation is BAD. Very bad. I've been a sysadmin for 12 years now professionally and done a great deal of programming, I document /everything/ even in the smallest script. It makes life MUCH easier. The reason I think it sucks is because it's so erratically unstable and buggy. I'm all for open source, but implementing a half-baked app like this for something as important as the network is just foolish. This also coincides with bad documentation, I've not looked at the code, but if they don't document the app, is the code undocumented as well? To me, it seems that that is the case based on the unstable nature of the app. I was looking for an essay I once had, called "Comments are Documentation, Too." It undoubtedly came from my youth, when structured programming was still used. In my search I found a link to "Documentation: Give it up; it won't happen"[1] and "FLOSS Manuals sprints to build quality free documentation."[2] I hate to say it, but "quality-free documentation" comes closer to the case here. The decision to use this is still beyond me... I would would be ashamed if something I wrote was a constant topic on this list, had it's own list on how to avoid it, even had people selling bloody tee shirts which show "NetworkManager" in a circle with a slash through it, and generated opinions like the "everyone knows it" above. Actually I exaggerate, the site was selling iron-on sheets for $4, you had to provide your own shirt, but there must have been some market. I do believe that a scan of this list indicates it's not just a few people frustrated by the lack of documentation. To the person who commented that I "probably never really wrote any ing documentation at all," a number of my articles have been published, you may be able to find the ones I wrote for _SysAdmin_ magazine a few years ago still online. [1] http://www.linuxjournal.com/node/1005775 [2] http://linux.com/feature/155205 -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: NM fails to connect when booting ?? -[SOLVED]
>> NM sucks, everyone knows it, so let's can it and move to something that >> doesn't. >> >Not everyone. I like it. And the latest NM can be configured to connect >on boot. Can you edit your connections? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 09:12 -0400, Mark Haney wrote: > Timothy Murphy wrote: > > > > > I wish some guru who understands NM would bring out a variant > > that just connects on bootup. > > I'm pretty sure the standard version would rapidly fall into disuse. > > > > But, they have that feature already. It's the way network interfaces > have started for a decade. Why bother with NM at all when starting the > interface on boot is what 99% of people need anyway? > > As for the arguments about wireless connectivity, how many people > actually move between wireless connections? If you do it might be only > between 2, home and work. > > NM sucks, everyone knows it, so let's can it and move to something that > doesn't. > Not everyone. I like it. And the latest NM can be configured to connect on boot. > > -- > Frustra laborant quotquot se calculationibus fatigant pro inventione > quadraturae circuli > > Mark Haney > Sr. Systems Administrator > ERC Broadband > (828) 350-2415 > > Call (866) ERC-7110 for after hours support > -- === I hold it, that a little rebellion, now and then, is a good thing... -- Thomas Jefferson === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Bill Davidsen wrote: > I had actually hoped that the "profiles" stuff might let me have > multiple configurations which work at multiple locations. I have three > locations needing credentials, and I'd like to have a "Starbucks" > configuration which found whatever was available. Doesn't seem to work > that way. :-( Thankfully I know how to write scripts and use iwconfig... Yeah, it's a saving grace for those of us who have given up on NM. > >> NM sucks, everyone knows it, so let's can it and move to something that >> doesn't. >> > The reason people think it sucks is that the documentation is missing, > inadequate, or wrong. And when I mentioned this someone told me that > writing documentation is not a good use of developer time, and that's > hogwash. I've done FOSS and commercial development for over thirty > years, and on commercial software there was always a description before > the code was written, and someone writing documentation which was > checked by QA, or for something I was giving away, I wrote my own > because I wanted people to love and use my software. We used to call the > NM approach "if it was hard to code it should be hard to use." Actually, the documentation issue isn't why I think it sucks. But you are correct, no/poor/incorrect documentation is BAD. Very bad. I've been a sysadmin for 12 years now professionally and done a great deal of programming, I document /everything/ even in the smallest script. It makes life MUCH easier. The reason I think it sucks is because it's so erratically unstable and buggy. I'm all for open source, but implementing a half-baked app like this for something as important as the network is just foolish. This also coincides with bad documentation, I've not looked at the code, but if they don't document the app, is the code undocumented as well? To me, it seems that that is the case based on the unstable nature of the app. The decision to use this is still beyond me... > > I would would be ashamed if something I wrote was a constant topic on > this list, had it's own list on how to avoid it, even had people selling > bloody tee shirts which show "NetworkManager" in a circle with a slash > through it, and generated opinions like the "everyone knows it" above. > Actually I exaggerate, the site was selling iron-on sheets for $4, you > had to provide your own shirt, but there must have been some market. I > do believe that a scan of this list indicates it's not just a few people > frustrated by the lack of documentation. > -- Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Mark Haney wrote: Timothy Murphy wrote: I wish some guru who understands NM would bring out a variant that just connects on bootup. I'm pretty sure the standard version would rapidly fall into disuse. But, they have that feature already. It's the way network interfaces have started for a decade. Why bother with NM at all when starting the interface on boot is what 99% of people need anyway? As for the arguments about wireless connectivity, how many people actually move between wireless connections? If you do it might be only between 2, home and work. I had actually hoped that the "profiles" stuff might let me have multiple configurations which work at multiple locations. I have three locations needing credentials, and I'd like to have a "Starbucks" configuration which found whatever was available. Doesn't seem to work that way. :-( Thankfully I know how to write scripts and use iwconfig... NM sucks, everyone knows it, so let's can it and move to something that doesn't. The reason people think it sucks is that the documentation is missing, inadequate, or wrong. And when I mentioned this someone told me that writing documentation is not a good use of developer time, and that's hogwash. I've done FOSS and commercial development for over thirty years, and on commercial software there was always a description before the code was written, and someone writing documentation which was checked by QA, or for something I was giving away, I wrote my own because I wanted people to love and use my software. We used to call the NM approach "if it was hard to code it should be hard to use." I would would be ashamed if something I wrote was a constant topic on this list, had it's own list on how to avoid it, even had people selling bloody tee shirts which show "NetworkManager" in a circle with a slash through it, and generated opinions like the "everyone knows it" above. Actually I exaggerate, the site was selling iron-on sheets for $4, you had to provide your own shirt, but there must have been some market. I do believe that a scan of this list indicates it's not just a few people frustrated by the lack of documentation. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 17:35 +, Matthew Saltzman wrote: > On Wed, 2009-03-18 at 11:46 -0400, William Case wrote: > > Hi; > > > > On Wed, 2009-03-18 at 14:26 +0200, Antti J. Huhtala wrote: > > > ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > > > > William Case wrote: > > > > The lack of documentation is regrettable, but I haven't had much trouble > lately making it do anything I've tried. (Admittedly, I haven't tried > everything possible. In particular, I haven't tried to start a wireless > connection at boot, which seems to be the most common problem scenario.) > > > I actually think that NM is a great improvement over > > system-config-network. That is one of the reasons why I have brought > > any problems I am having with NM to this mailing list. I would rather > > get NM working for me than return to system-config-network. > > > > For ordinary users or users who would rather spend their time on things > > other than tweaking their wireless or wired network -- keep it > > simple,stupid (KISS). The problem is, if you want to make some minor > > changes or alterations you have to dive into the arcane nether world of > > networking. > > > > I would suggest: > > 1. A button that allows you to disconnect (turn it off) temporarily > > -- say to the next boot. > > Right-click the applet and uncheck Enable Networking or Enable Wireless, > as appropriate. Sorry to everyone. Was trying to disconnect by left-click then clicking on "System eth0." > > > 2. An "Edit Connections" that actually allows you to edit > > connections. > > All my wireless connections are editable from the applet. The wired > connections are editable from s-c-network, as mentioned above. > Apparently Fedora devs think that that's the way to go. > > > 3. Tie editing to root, if necessary, with the usual sudo or su - > > popup. > > See s-c-network. It might be nice if nm-applet started s-c-network when > you tried to edit a "non-editable" connection, but if this is where an > "ordinary user" would think to > edit /etc/sysconfig/network-scripts/ifcfg-eth0, then s-c-network the way > to do it. > > > 4. Clearly show in the gui how to turn ONBOOT to yes or no. > > See s-c-network. > > BTW, I have a desktop with a recent F10 install, fully up to date. It > has only a wired interface. That interface comes up at boot (before > login) with no problem using NM, not using the network service. I have > not made any changes to its /etc/sysconfig/network-scripts/ifcfg-eth0. > s-c-network shows that it is on at startup and controlled by NM. > Trouble in paradise then. I have two recent F10 installs, fully up to date. Neither had ifcfg-eth0 BOOTUP=yes. > > 5. A Default button that returns any adjustments to the default > > settings. > > 6. A manual that is useful. > > > > And, by the way, what does the "never" that is placed at the end "System > > eth0" line mean? > > Means "Never connected to that interface." Apparently incorrect or > meaningless for System eth0, but seems to work for wireless. > I suppose I am being a bit tentative because I got into a major mixup in F9 between NM and system-config-network. I just wish Fedora would make the network connecting completely one or the other. -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Hi Mike; On Wed, 2009-03-18 at 04:49 -0500, Mike Chambers wrote: > On Wed, 2009-03-18 at 00:24 -0400, William Case wrote: > > Can't you just right click and uncheck the box that has "Enabled > Networking" to turn it off and then recheck again when want back online? > Not on my applet. Once it is connected, clicking on "Enabled Networking" just has it repeat the connecting process. If it is disconnected, it is only for a second or two. -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On 03/18/2009 08:46:45 AM, William Case wrote: > 1. A button that allows you to disconnect (turn it off) > temporarily > -- say to the next boot. > 2. An "Edit Connections" that actually allows you to edit > connections. > 3. Tie editing to root, if necessary, with the usual sudo or su > - > popup. > 4. Clearly show in the gui how to turn ONBOOT to yes or no. > 5. A Default button that returns any adjustments to the default > settings. > 6. A manual that is useful. > > And, by the way, what does the "never" that is placed at the end > "System > eth0" line mean? It just happens that I discovered at least on use for the "never" -- I noticed it the other day, and then noticed that my sat modem was powered off, so there was no network available. As to the button mentioned in #1 above, granted that's a good idea, but in the meanwhile, what's wrong with: sudo /etc/init.d/NetworkManager stop -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 11:46 -0400, William Case wrote: > Hi; > > On Wed, 2009-03-18 at 14:26 +0200, Antti J. Huhtala wrote: > > ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > > > William Case wrote: > > > > I agree completely. The problem seems to be in the NetworkManager > > > > Applet. First, there is no manual. Secondly, it seems to lack any > > > > ability to affect the function of NetworkManager -- at least at the > > > > simplest level. I can't use it to disconnect, if for some reason I > > > > might want to (eg. tweaking, playing around, etc.). Even when I use the > > > > edit function - "Edit Connections" - all the editable fields are greyed > > > > out. To me that is where an ordinary user would think to alter the > > > > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > > > > which in turn is only a reporting program. > > > > > > "Edit Connections" is for primarily editing per-user settings. I think > > > there's also a plugin for systemwide settings which can be edited at the > > > same place, but Fedora is using a plugin to use the existing > > > system-config-network settings instead, so you have to fire up > > > system-config-network to change systemwide settings. > > > > > > Kevin Kofler > > > > > I wonder if "Edit connections" now works even for per-user settings? A > > few days ago I finally installed F10 from original (Nov -08) x86_64 DVD. > > That version seemed to allow me to edit NM connections at least somehow > > but I didn't do it before downloading some 340 M of updates. After that > > "Edit connections" was useless (greyed out) for ordinary user. > > Because I have a wired cable modem (at eth0) and a NATted Centos 5.2 box > > connected to Internet (via eth1) through the F10 box, I could not make > > NM behave the way I wanted. > > Maybe the original ifcfg-eth0 default of 'ONBOOT=no' is not a bug but it > > surely is a poor choice for someone like me with no wireless devices. > > After struggling a while with NM trying to configure it the way I > > wanted, I had to disable NM altogether and configure the trusty old > > network service like it is in my F9 system. To add insult to injury, it > > is now necessary to install gnome-netstatus applet separately because it > > has been removed from basic F10 installation's 'add-to-panel-gadgets'. > > > > To me it looks like "life is too short for NM". > The lack of documentation is regrettable, but I haven't had much trouble lately making it do anything I've tried. (Admittedly, I haven't tried everything possible. In particular, I haven't tried to start a wireless connection at boot, which seems to be the most common problem scenario.) > I actually think that NM is a great improvement over > system-config-network. That is one of the reasons why I have brought > any problems I am having with NM to this mailing list. I would rather > get NM working for me than return to system-config-network. > > For ordinary users or users who would rather spend their time on things > other than tweaking their wireless or wired network -- keep it > simple,stupid (KISS). The problem is, if you want to make some minor > changes or alterations you have to dive into the arcane nether world of > networking. > > I would suggest: > 1. A button that allows you to disconnect (turn it off) temporarily > -- say to the next boot. Right-click the applet and uncheck Enable Networking or Enable Wireless, as appropriate. > 2. An "Edit Connections" that actually allows you to edit > connections. All my wireless connections are editable from the applet. The wired connections are editable from s-c-network, as mentioned above. Apparently Fedora devs think that that's the way to go. > 3. Tie editing to root, if necessary, with the usual sudo or su - > popup. See s-c-network. It might be nice if nm-applet started s-c-network when you tried to edit a "non-editable" connection, but if this is where an "ordinary user" would think to edit /etc/sysconfig/network-scripts/ifcfg-eth0, then s-c-network the way to do it. > 4. Clearly show in the gui how to turn ONBOOT to yes or no. See s-c-network. BTW, I have a desktop with a recent F10 install, fully up to date. It has only a wired interface. That interface comes up at boot (before login) with no problem using NM, not using the network service. I have not made any changes to its /etc/sysconfig/network-scripts/ifcfg-eth0. s-c-network shows that it is on at startup and controlled by NM. > 5. A Default button that returns any adjustments to the default > settings. > 6. A manual that is useful. > > And, by the way, what does the "never" that is placed at the end "System > eth0" line mean? Means "Never connected to that interface." Apparently incorrect or meaningless for System eth0, but seems to work for wireless. > > > -- Matthew Saltzman Clemson University Math Sciences mjs
Re: NM fails to connect when booting ?? -[SOLVED]
Mark Haney wrote: >> I wish some guru who understands NM would bring out a variant >> that just connects on bootup. >> I'm pretty sure the standard version would rapidly fall into disuse. >> > > But, they have that feature already. It's the way network interfaces > have started for a decade. Why bother with NM at all when starting the > interface on boot is what 99% of people need anyway? Because, sadly, the network service has never worked even reasonably well with WiFi, in my experience. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Thu, 2009-03-19 at 00:48 +1030, Tim wrote: > On Wed, 2009-03-18 at 11:54 +, Timothy Murphy wrote: > > Am I alone in thinking the "per user" paradigm is crazy? > > How many people actually have WiFi laptops used by several people > > who want to connect in different ways? > > How many average users would have a wireless access point that lets them > have different user logons? > > Every one that I've seen has just ONE set of logon credentials for > everything that connects to it. I strikes me that this per-user idea is > being implemented in the wrong way. It could only work for something > beyond the actual wireless connection. Any serious enterprise? WPA with PEAP is standard here. User credentials are checked against a system-wide userid/password directory. Only credentialed employees/students can gain access to the campus network. Guests have a separate, restricted network that is open for anyone. There certainly are reasons to support system-wide, on-boot connections, but per-user connections are a good model for many mobile apps. Now, my laptop doesn't get much use from different users, but I do have to control many different connections: * home (WPA) * office (WPA/PEAP) * Jittery Joe's (NOT Starbucks!) * remote office I visit frequently (currently WPA) * homes of several different friends, family, and colleagues (typically WPA or WEP) * hotels and airports (and Starbucks 8^( ) when I travel (Web-authenticated access) * remote work locations (could be anything). Accessing those on boot doesn't make much sense (how would I choose which connection when multiple ones are visible, and how would I authenticate?), and I don't do much with the laptop that doesn't involve being logged in. I don't think my usage pattern is all that unique. Per-user access controls in NM do have one problem: once I've authenticated, if I log out, the connection stays up and the next user is still authenticated with my credentials. For work, that would be a problem if the machine were actually multi-user and I didn't trust other users, because the network managers expect the logged in user to be the authenticated user. For other locations, it might be a problem if the next user isn't authorized. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wednesday 18 March 2009 14:18:50 Tim wrote: > PS: I'm quite sick of gmane news postings to this mailing list that > INAPPROPRIATELY set a post-to header to THEIR news server. I have to > manually remove the post-to header and manually add the proper to > header. It's quite a cheek to act as a gateway to someone else's > mailing list, then try and subvert posts to themselves. They're actually trying to avoid people "posting" a follow-up that then doesn't get reflected back to the mailing list? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Hi; On Wed, 2009-03-18 at 14:26 +0200, Antti J. Huhtala wrote: > ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > > William Case wrote: > > > I agree completely. The problem seems to be in the NetworkManager > > > Applet. First, there is no manual. Secondly, it seems to lack any > > > ability to affect the function of NetworkManager -- at least at the > > > simplest level. I can't use it to disconnect, if for some reason I > > > might want to (eg. tweaking, playing around, etc.). Even when I use the > > > edit function - "Edit Connections" - all the editable fields are greyed > > > out. To me that is where an ordinary user would think to alter the > > > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > > > which in turn is only a reporting program. > > > > "Edit Connections" is for primarily editing per-user settings. I think > > there's also a plugin for systemwide settings which can be edited at the > > same place, but Fedora is using a plugin to use the existing > > system-config-network settings instead, so you have to fire up > > system-config-network to change systemwide settings. > > > > Kevin Kofler > > > I wonder if "Edit connections" now works even for per-user settings? A > few days ago I finally installed F10 from original (Nov -08) x86_64 DVD. > That version seemed to allow me to edit NM connections at least somehow > but I didn't do it before downloading some 340 M of updates. After that > "Edit connections" was useless (greyed out) for ordinary user. > Because I have a wired cable modem (at eth0) and a NATted Centos 5.2 box > connected to Internet (via eth1) through the F10 box, I could not make > NM behave the way I wanted. > Maybe the original ifcfg-eth0 default of 'ONBOOT=no' is not a bug but it > surely is a poor choice for someone like me with no wireless devices. > After struggling a while with NM trying to configure it the way I > wanted, I had to disable NM altogether and configure the trusty old > network service like it is in my F9 system. To add insult to injury, it > is now necessary to install gnome-netstatus applet separately because it > has been removed from basic F10 installation's 'add-to-panel-gadgets'. > > To me it looks like "life is too short for NM". I actually think that NM is a great improvement over system-config-network. That is one of the reasons why I have brought any problems I am having with NM to this mailing list. I would rather get NM working for me than return to system-config-network. For ordinary users or users who would rather spend their time on things other than tweaking their wireless or wired network -- keep it simple,stupid (KISS). The problem is, if you want to make some minor changes or alterations you have to dive into the arcane nether world of networking. I would suggest: 1. A button that allows you to disconnect (turn it off) temporarily -- say to the next boot. 2. An "Edit Connections" that actually allows you to edit connections. 3. Tie editing to root, if necessary, with the usual sudo or su - popup. 4. Clearly show in the gui how to turn ONBOOT to yes or no. 5. A Default button that returns any adjustments to the default settings. 6. A manual that is useful. And, by the way, what does the "never" that is placed at the end "System eth0" line mean? -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Tom Horsley wrote: > On Wed, 18 Mar 2009 09:12:14 -0400 > Mark Haney wrote: > >> As for the arguments about wireless connectivity, how many people >> actually move between wireless connections? If you do it might be only >> between 2, home and work. > > I'm fairly certain from the empirical evidence that the NM developers > do all their work at different Starbucks (at least that seems to be > the only model NM seems to be designed to support :-). > I agree with you there. I've never seen an app make something straightforward into something so complex it never works the same way twice /and/ breaks the existing method that it's trying to replace. Can anyone explain to me why this is a good idea? -- Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 11:54 +, Timothy Murphy wrote: > Am I alone in thinking the "per user" paradigm is crazy? > How many people actually have WiFi laptops used by several people > who want to connect in different ways? How many average users would have a wireless access point that lets them have different user logons? Every one that I've seen has just ONE set of logon credentials for everything that connects to it. I strikes me that this per-user idea is being implemented in the wrong way. It could only work for something beyond the actual wireless connection. PS: I'm quite sick of gmane news postings to this mailing list that INAPPROPRIATELY set a post-to header to THEIR news server. I have to manually remove the post-to header and manually add the proper to header. It's quite a cheek to act as a gateway to someone else's mailing list, then try and subvert posts to themselves. -- [...@localhost ~]$ uname -r 2.6.27.19-78.2.30.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 18 Mar 2009 09:12:14 -0400 Mark Haney wrote: > As for the arguments about wireless connectivity, how many people > actually move between wireless connections? If you do it might be only > between 2, home and work. I'm fairly certain from the empirical evidence that the NM developers do all their work at different Starbucks (at least that seems to be the only model NM seems to be designed to support :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Timothy Murphy wrote: > > I wish some guru who understands NM would bring out a variant > that just connects on bootup. > I'm pretty sure the standard version would rapidly fall into disuse. > But, they have that feature already. It's the way network interfaces have started for a decade. Why bother with NM at all when starting the interface on boot is what 99% of people need anyway? As for the arguments about wireless connectivity, how many people actually move between wireless connections? If you do it might be only between 2, home and work. NM sucks, everyone knows it, so let's can it and move to something that doesn't. -- Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > William Case wrote: > > I agree completely. The problem seems to be in the NetworkManager > > Applet. First, there is no manual. Secondly, it seems to lack any > > ability to affect the function of NetworkManager -- at least at the > > simplest level. I can't use it to disconnect, if for some reason I > > might want to (eg. tweaking, playing around, etc.). Even when I use the > > edit function - "Edit Connections" - all the editable fields are greyed > > out. To me that is where an ordinary user would think to alter the > > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > > which in turn is only a reporting program. > > "Edit Connections" is for primarily editing per-user settings. I think > there's also a plugin for systemwide settings which can be edited at the > same place, but Fedora is using a plugin to use the existing > system-config-network settings instead, so you have to fire up > system-config-network to change systemwide settings. > > Kevin Kofler > I wonder if "Edit connections" now works even for per-user settings? A few days ago I finally installed F10 from original (Nov -08) x86_64 DVD. That version seemed to allow me to edit NM connections at least somehow but I didn't do it before downloading some 340 M of updates. After that "Edit connections" was useless (greyed out) for ordinary user. Because I have a wired cable modem (at eth0) and a NATted Centos 5.2 box connected to Internet (via eth1) through the F10 box, I could not make NM behave the way I wanted. Maybe the original ifcfg-eth0 default of 'ONBOOT=no' is not a bug but it surely is a poor choice for someone like me with no wireless devices. After struggling a while with NM trying to configure it the way I wanted, I had to disable NM altogether and configure the trusty old network service like it is in my F9 system. To add insult to injury, it is now necessary to install gnome-netstatus applet separately because it has been removed from basic F10 installation's 'add-to-panel-gadgets'. To me it looks like "life is too short for NM". Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Kevin Kofler wrote: > "Edit Connections" is for primarily editing per-user settings. I think > there's also a plugin for systemwide settings which can be edited at the > same place, but Fedora is using a plugin to use the existing > system-config-network settings instead, so you have to fire up > system-config-network to change systemwide settings. Am I alone in thinking the "per user" paradigm is crazy? How many people actually have WiFi laptops used by several people who want to connect in different ways? I would guess it is less that 1%. I wish some guru who understands NM would bring out a variant that just connects on bootup. I'm pretty sure the standard version would rapidly fall into disuse. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
On Wed, 2009-03-18 at 00:24 -0400, William Case wrote: > I agree completely. The problem seems to be in the NetworkManager > Applet. First, there is no manual. Secondly, it seems to lack any > ability to affect the function of NetworkManager -- at least at the > simplest level. I can't use it to disconnect, if for some reason I > might want to (eg. tweaking, playing around, etc.). Even when I use the > edit function - "Edit Connections" - all the editable fields are greyed > out. To me that is where an ordinary user would think to alter the > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > which in turn is only a reporting program. Can't you just right click and uncheck the box that has "Enabled Networking" to turn it off and then recheck again when want back online? -- Mike Chambers Madisonville, KY Fedora Project - Bugzapper, Tester, User, etc.. miketc...@fedoraproject.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
William Case wrote: > I agree completely. The problem seems to be in the NetworkManager > Applet. First, there is no manual. Secondly, it seems to lack any > ability to affect the function of NetworkManager -- at least at the > simplest level. I can't use it to disconnect, if for some reason I > might want to (eg. tweaking, playing around, etc.). Even when I use the > edit function - "Edit Connections" - all the editable fields are greyed > out. To me that is where an ordinary user would think to alter the > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > which in turn is only a reporting program. "Edit Connections" is for primarily editing per-user settings. I think there's also a plugin for systemwide settings which can be edited at the same place, but Fedora is using a plugin to use the existing system-config-network settings instead, so you have to fire up system-config-network to change systemwide settings. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Hi Todd; At the risk of beating a dead horse ... On Tue, 2009-03-17 at 23:25 -0400, Todd Zullinger wrote: > William Case wrote: > > It has been reported by someone else as a medium level bug. See: > > https://bugzilla.redhat.com/show_bug.cgi?id=470477 > > Or see the changelog of NetworkManager-0.7.0.99-3: > > * Mon Mar 09 2009 Dan Williams - 1:0.7.0.99-3 > - Missing ONBOOT should actually mean ONBOOT=yes (rh #489422) > > Bug #489422 is "No network after last NM update" > https://bugzilla.redhat.com/489422 > > > The bug comments gave me the following work around: > > > > The automatic wired network connection can be made to work by doing: > > > > "if and only if the flag ONBOOT in > > /etc/sysconfig/network-scripts/ifcfg-eth0 is set to "yes"" > > > > My ifcfg-eth0 file had ONBOOT=no; I changed it to ONBOOT=yes and now my > > Internet connection is made automatically on boot. > > > > I would think that this is more than a medium level concern, > > particularly for new users of Fedora 10. > > Well, the levels aren't really used my many maintainers (though maybe > they are for RHEL bugs, which 470477 is...). But aside from that, the > NM release on Fedora fixes the bug that a missing ONBOOT parameter is > treated differently in NM than it was by the network service. I can't > see how having ONBOOT=no and NM not starting that device could be > construed as an NM bug though. It's perhaps a bug if some tool is > automatically writing the ONBOOT=no into the ifcfg file when it > shouldn't be. I agree completely. The problem seems to be in the NetworkManager Applet. First, there is no manual. Secondly, it seems to lack any ability to affect the function of NetworkManager -- at least at the simplest level. I can't use it to disconnect, if for some reason I might want to (eg. tweaking, playing around, etc.). Even when I use the edit function - "Edit Connections" - all the editable fields are greyed out. To me that is where an ordinary user would think to alter the ifcfg-eth* script. It seems to be just a front end gui for nm-tools which in turn is only a reporting program. Maybe more is coming in the NetworkManager Applet. -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
William Case wrote: > It has been reported by someone else as a medium level bug. See: > https://bugzilla.redhat.com/show_bug.cgi?id=470477 Or see the changelog of NetworkManager-0.7.0.99-3: * Mon Mar 09 2009 Dan Williams - 1:0.7.0.99-3 - Missing ONBOOT should actually mean ONBOOT=yes (rh #489422) Bug #489422 is "No network after last NM update" https://bugzilla.redhat.com/489422 > The bug comments gave me the following work around: > > The automatic wired network connection can be made to work by doing: > > "if and only if the flag ONBOOT in > /etc/sysconfig/network-scripts/ifcfg-eth0 is set to "yes"" > > My ifcfg-eth0 file had ONBOOT=no; I changed it to ONBOOT=yes and now my > Internet connection is made automatically on boot. > > I would think that this is more than a medium level concern, > particularly for new users of Fedora 10. Well, the levels aren't really used my many maintainers (though maybe they are for RHEL bugs, which 470477 is...). But aside from that, the NM release on Fedora fixes the bug that a missing ONBOOT parameter is treated differently in NM than it was by the network service. I can't see how having ONBOOT=no and NM not starting that device could be construed as an NM bug though. It's perhaps a bug if some tool is automatically writing the ONBOOT=no into the ifcfg file when it shouldn't be. In any case, I'm glad you found the solution. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Problems are opportunity in work clothes. pgpKi1W7vA4wh.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
Hi; For any one else who might have been following this problem: On Mon, 2009-03-16 at 21:36 -0400, William Case wrote: > Hi; > > I now have Fedora 10 on two systems. On both, NetworkManager fails to > connect at bootup + login. If I remember correctly, NM connected > automatically on booting when I first installed Fedora 10 on each > machine. Some time after the major update it stopped connecting. > > It is not a major problem to me. I can just checkmark 'System eth0', > but it shouldn't work that way. > > Is this a reported bug? I didn't see this specifically. It has been reported by someone else as a medium level bug. See: https://bugzilla.redhat.com/show_bug.cgi?id=470477 The bug comments gave me the following work around: The automatic wired network connection can be made to work by doing: "if and only if the flag ONBOOT in /etc/sysconfig/network-scripts/ifcfg-eth0 is set to "yes"" My ifcfg-eth0 file had ONBOOT=no; I changed it to ONBOOT=yes and now my Internet connection is made automatically on boot. I would think that this is more than a medium level concern, particularly for new users of Fedora 10. -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
