FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 04-03-2008, 10:14 PM
Mike Chambers
 
Default Network Manager Summary

Ok, I want to make sure I understand how this works, or at least see if
Dan or someone can help explain what/when to use this tool exactly.

Soo, is network manager *only* (or at least currently) used on
wireless/wired systems (such as laptops obviously) for connecting back
and forth? Or is/can/should it be able to be used normally on just a
wired desktop system as well with no wireless connection? And if so,
does it start up in the proper place, so the proper services will start
up and can be used without errors?

I know this topic sort of has/is being discussed, but mainly on various
topics/problems/bugs. But thought might give Dan an opp. to do a quick
run down on what services to have on/off to get it working, and
what/will work currently with NM starting on boot, in place of
(conjunction with?) normal networking as before.

Dan, any chance of a quick summary for us for wireless users and just
wired (laptops and desktops) so we can get a better understanding on who
can use this and who can't?

--
Mike Chambers
Fedora Project - Ambassador, Bug Zapper, Tester, User, etc..
mikec302@fedoraproject.org

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-03-2008, 10:37 PM
Owen Taylor
 
Default Network Manager Summary

On Thu, 2008-04-03 at 17:14 -0500, Mike Chambers wrote:
> Ok, I want to make sure I understand how this works, or at least see if
> Dan or someone can help explain what/when to use this tool exactly.

Disclaimer: I'm not Dan though I sit a few feet from him and have
discussed this stuff with him a fair bit. Hopefully he'll follow
up and correct me where I'm wrong.

> Soo, is network manager *only* (or at least currently) used on
> wireless/wired systems (such as laptops obviously) for connecting back
> and forth? Or is/can/should it be able to be used normally on just a
> wired desktop system as well with no wireless connection?

NetworkManager is certainly intended to handle all systems with a
Desktop running on them. It probably could also handle many server
systems, but for now that's not an explicit target.

> And if so, does it start up in the proper place, so the proper services
> will start up and can be used without errors?

This solution for start order problems are two pronged:

A) There's no reason NetworkManager can't be moved earlier (though
starting NetworkManager is as far as I know async, it's not going to
wait until DHCP completes before moving on in the in the init
scripts. Waiting for DHCP can be a pretty big bottleneck in
system startup, so that's probably a good thing, all in all.)

Moving NetworkManager earlier may require moving D-BUS earlier
as well.

B) But the system generally should be fixed so that it can deal
with the network coming up later. After all, if I boot my
desktop and the network cable unplugged, I shouldn't have to reboot
or mount -a to get my network filesystems, should I?
(Using the problem in
https://bugzilla.redhat.com/show_bug.cgi?id=439242 as an example.)

> I know this topic sort of has/is being discussed, but mainly on various
> topics/problems/bugs. But thought might give Dan an opp. to do a quick
> run down on what services to have on/off to get it working, and
> what/will work currently with NM starting on boot, in place of
> (conjunction with?) normal networking as before.

Services:

NetworkManager: on

network: off. It is possible to mark interfaces
in /etc/sysconfig/network to be skipped by NetworkManager
(you add something like NMCONTROL=off, though that's not the exactly
the right option) and have a hybrid NM + network system, but there's
little point. In the normal case NetworkManager starts everything
including lo.

wpa_supplicant: off (harmless if on, probably will be on in upgraded
systems. It's currently activated by NetworkManager on demand
via D-BUS.)

- Owen

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-03-2008, 10:43 PM
Harald Hoyer
 
Default Network Manager Summary

Owen Taylor wrote:

Services:

NetworkManager: on

network: off. It is possible to mark interfaces
in /etc/sysconfig/network to be skipped by NetworkManager
(you add something like NMCONTROL=off, though that's not the exactly

the right option) and have a hybrid NM + network system, but there's
little point. In the normal case NetworkManager starts everything
including lo.


use
/etc/sysconfig/network-scripts/ifcfg-*
not
/etc/sysconfig/network

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-03-2008, 10:52 PM
José Matos
 
Default Network Manager Summary

On Thursday 03 April 2008 23:14:27 Mike Chambers wrote:
>
> Dan, any chance of a quick summary for us for wireless users and just
> wired (laptops and desktops) so we can get a better understanding on who
> can use this and who can't?

Without wanting to steal the thread and because this issue is related I have
another question. If I click on the applet with the right mouse I have one
option called "Edit Connections..."

I get a dialog with all the types of connection supported by NM that have
been used. So far so good. :-)

For each connection I have three options, add, edit and delete. For me using
KDE only the last option is available, the other two are greyed out. Is this
normal, a bug or some sloppiness from me? :-)

I saw a picture on Dan's blog where those options where active...

--
José Abílio

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-03-2008, 11:02 PM
Mike Chambers
 
Default Network Manager Summary

On Thu, 2008-04-03 at 23:52 +0100, José Matos wrote:
> On Thursday 03 April 2008 23:14:27 Mike Chambers wrote:
> >
> > Dan, any chance of a quick summary for us for wireless users and just
> > wired (laptops and desktops) so we can get a better understanding on who
> > can use this and who can't?
>
> Without wanting to steal the thread and because this issue is related I have
> another question. If I click on the applet with the right mouse I have one
> option called "Edit Connections..."
>
> I get a dialog with all the types of connection supported by NM that have
> been used. So far so good. :-)
>
> For each connection I have three options, add, edit and delete. For me using
> KDE only the last option is available, the other two are greyed out. Is this
> normal, a bug or some sloppiness from me? :-)
>
> I saw a picture on Dan's blog where those options where active...

I also called up that UI and I had *NO* listings in there, yet I have
eth0 and worked fine with the "network" service. I think maybe there
was dns issue when trying to use network manager,and either/neither eth0
was discovered, or dns didn't work? But *all* of the buttons were
grayed out for me on that UI.

--
Mike Chambers
Fedora Project - Ambassador, Bug Zapper, Tester, User, etc..
mikec302@fedoraproject.org

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 06:36 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org