|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Wireless Questions about wireless networking setup, use, and wireless specific applications |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi,
For a while I have been using ifup instead of network manager; started so that I can use wireless when starting in runlevel 3. I have noticed my connection is faster and doesn't keep being lost and needing to be reconnected as it did with network manager and I wondered why this is? Also network manager used to crash quite often. Has anyone else had similar experiences, maybe the opposite? To me, network manager has become a thing of the past. Everything is so much smoother without it. Do we even need network manager? What does it do? Why is it so unstable? Regards, Barry. |
|
|||
|
I would agree with hcw and in the past have to say I found network manager a bit flaky. Being somewhat "old-school" I too figure "ifup" is the "proper" way to do it !
But in the past few months I've had cause to be "network hopping" and found not only is it so much easier and quicker with network manager, but that network manager has delivered rock-solid stability. So now I've got lazy and use it all the time. SO actually I would say netwrok manager is now very useable and with portable devices also very useful. And isn't that the whole point? Stuff only has a use if it's ueful and useable ! To address the reliability question, I guess that network manager is another layer between the user and the configuration and like with any process, as you add more layers, so you increase the potential for processes to not communicate properly. You write a config to a config file, that's it; you type the same information into a user interface and expect it will communicate through the OS to ultimately write that same config file...but maybe something gets missed in that communication process. Not a very technical analysis I know... IG |
|
||||
|
Barry Nichols wrote:
> Hi, > > For a while I have been using ifup instead of network manager; started > so that I can use wireless when starting in runlevel 3. > > I have noticed my connection is faster and doesn't keep being lost and > needing to be reconnected as it did with network manager and I wondered > why this is? > > Also network manager used to crash quite often. Very true. > > Has anyone else had similar experiences, maybe the opposite? Yes. > > To me, network manager has become a thing of the past. Everything is so > much smoother without it. NetworkManager is the future... oddly enough. > > Do we even need network manager? What does it do? Why is it so > unstable? Poorly written? Makes horrible assumptions? Written to be "like" Microsoft? Who knows? There's also things like wicd that might be an alternative. If ifup works for you, at least it's easy to augment/change... I "think" ifup will stick around. I hate to think of trying to do anything serious with NetworkManager. |
|
|||
|
cjcox wrote:
> Poorly written? Makes horrible assumptions? Written to be > "like" Microsoft? Who knows? > > There's also things like wicd that might be an alternative. > > If ifup works for you, at least it's easy to augment/change... > > I "think" ifup will stick around. I hate to think of trying > to do anything serious with NetworkManager. Try roaming with ifup. NM is much more convenient than editing ifcfg-wlan0 or using the YaST GUI. NM is a work in progress; however, it does work. Note that it has no effect on signal strength of transmit/receive rates. That is a function of the driver and the MAC layer. |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|