Still a flawed KnetworkManager in the released 11.3.
No user control for cabled 10/100 lan ports. Yast config for the eth0 says it can have usercontrol by networkmanager. Oh no it doesn’t !!!
It seems to cater for wi-fi users only who get a “enable wireless” tickbox and “manage connections”. At least you can stop and start it.
Meanwhile cable users who might have a taskbar display for lan traffic can see stuff pouring in, or out and if it’s something they don’t want they can’t do anything about it unless they pull the plug.
Great work, opensuse developers, or should that be opensource.
Oh, do NOT post with reminders about “ifup/down” in a terminal.
On 07/24/2010 06:36 AM, skoco wrote:
>
> Still a flawed KnetworkManager in the released 11.3.
>
> No user control for cabled 10/100 lan ports. Yast config for the eth0
> says it can have usercontrol by networkmanager. Oh no it doesn’t !!!
>
> It seems to cater for wi-fi users only who get a “enable wireless”
> tickbox and “manage connections”. At least you can stop and start it.
>
> Meanwhile cable users who might have a taskbar display for lan traffic
> can see stuff pouring in, or out and if it’s something they don’t want
> they can’t do anything about it unless they pull the plug.
>
> Great work, opensuse developers, or should that be opensource.
>
> Oh, do NOT post with reminders about “ifup/down” in a terminal.
I find that kNetworkManager works fine here. My wired port is configured to come
on when plugged, NOT ON BOOT. When I plug in a wire, NM switches to the wired
connection immediately. When I unplug it, back to wireless. That is exactly what
I want, as do most users. As you seem to want something else, you need to take
that up with the NetworkManager developers at networkmanager-list@gnome.org. You will need to describe exactly what yoou want,
and it would be best if you lose the attitude.
The tone of your posting suggest to me that you are on a desktop with a permanent wired connection and do not use wireless. If that is the case, why use networkmanager at all? Rather, just plug it in and use ifup.
If I am wrong and you do occasionally need wireless, then I would go with what hcvv said.
The tone of your posting suggest to me that you are on a desktop with a permanent wired connection and do not use wireless. If that is the case, why use networkmanager at all? Rather, just plug it in and use ifup.
yes indeed, a cable
Quite probably, as others suggested, I should have let off steam in a different Forum. Whatever “attitude” I have is applicable to many other areas and basically stems from being a happy user of some part of a favoured product that previously worked in an efficient, ergonomic manner and now, under the same name in a newer version, does not.
If people think what they have now is better than they had before and are loathe to criticise, or frown on criticism, then… Emperor’s new clothes and all that.
I know exactly how you feel. I’ve had nothing but problems since I installed 11.3 on this laptop. People on the forums have helped me fix most of it but I haven’t had this many problems since I first started using SUSE.
My wired port is configured to come
on when plugged, NOT ON BOOT. When I plug in a wire, NM switches to the wired
connection immediately. When I unplug it, back to wireless. That is exactly what
I want, as do most users.
YES, so do I. How do I do that, once my WLAN is working?
On 07/25/2010 03:06 PM, hgeis wrote:
>
> My wired port is configured to come
> on when plugged, NOT ON BOOT. When I plug in a wire, NM switches to the
> wired
> connection immediately. When I unplug it, back to wireless. That is
> exactly what
> I want, as do most users.
>
> YES, so do I. How do I do that, once my WLAN is working?
If using NM, switch to ifup control temporarily (with YaST, or course). The set
your wired connection to connect when plugged and your wireless to come on at
boot. At that point, go back to control with NM.
