Hello: In January Per Jessen wrote the following, see http://lists.opensuse.org/opensuse/2016-01/msg00252.html: Per Jessen írta:

Istvan Gabor wrote:

...

Hello:

In openSUSE 13.2 the traditional network setup (ifup in yast) was removed

Despite that, it still works quite well.

...

and wicd (??) was introduced which I didn't like when I tried.

I'm not sure there is much to try - wicked runs your network. WHether the interface is ifup or networkmanager.

...

Along with ifup kinternet/qinternet and related packages, eg smpppd (SuSE Meta PPP Daemon, the back-end for kinternet) have been removed too. I am curious how network manager independent network setup occurs in leap 42.1? Does it have kinternet on something similar?

YaST / ifup. Works perfectly fine.

I again installed openSUSE 13.2 and would like to configure network in the traditional way (ie not network manager). I am puzzled by the above statements like "Despite that, it still works quite well. " and "YaST / ifup. Works perfectly fine." I want to be able to disconnect/reconnect the network by one click, like kinternet made it possible in < 13.2 versions. I could not find kinternet/qinternet and smpppd packages either in 13.2 or leap 42 repo. Isn't it possible anymore to control network connection by user by simple clicking? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor wrote:

Hello:

In January Per Jessen wrote the following, see http://lists.opensuse.org/opensuse/2016-01/msg00252.html:

Per Jessen írta:

...

Istvan Gabor wrote:

...

Hello:

In openSUSE 13.2 the traditional network setup (ifup in yast) was removed

Despite that, it still works quite well.

...

and wicd (??) was introduced which I didn't like when I tried.

I'm not sure there is much to try - wicked runs your network. WHether the interface is ifup or networkmanager.

...

Along with ifup kinternet/qinternet and related packages, eg smpppd (SuSE Meta PPP Daemon, the back-end for kinternet) have been removed too. I am curious how network manager independent network setup occurs in leap 42.1? Does it have kinternet on something similar?

YaST / ifup. Works perfectly fine.

I again installed openSUSE 13.2 and would like to configure network in the traditional way (ie not network manager). I am puzzled by the above statements like "Despite that, it still works quite well. " and "YaST / ifup. Works perfectly fine."

That was sarcasm - it continues to work very well because it was never removed. I installed a new 13.2 test system only last week I think, works quite well.

I want to be able to disconnect/reconnect the network by one click, like kinternet made it possible in < 13.2 versions. I could not find kinternet/qinternet and smpppd packages either in 13.2 or leap 42 repo. Isn't it possible anymore to control network connection by user by simple clicking?

Sounds like you want NetworkManager. -- Per Jessen, Zürich (16.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

15.06.2016 22:51, Istvan Gabor пишет:

What I want is this: - To set up network connection as root - I want that regular users cannot edit configured network connection in any way, cannot add, remove or change existing connections - I want that regular users can start and stop connections configured by root.

Is this possible with network manager? Can I configure network manager that it wouldn't let a user add new connection at all? How?

I think that suitable polkit configuration for actions org.freedesktop.NetworkManager.settings.modify.own, org.freedesktop.NetworkManager.settings.modify.system and org.freedesktop.NetworkManager.network-control should do it. You won't be able to prevent user from explicitly editing files under /etc/NetworkManager using su/sudo, but then you cannot do it with ifup either. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Jun 16, 2016 at 8:45 AM, Roger Oberholtzer wrote:

On Wed, Jun 15, 2016 at 10:27 PM, Andrei Borzenkov wrote:

...

15.06.2016 22:51, Istvan Gabor пишет:

...

What I want is this: - To set up network connection as root - I want that regular users cannot edit configured network connection in any way, cannot add, remove or change existing connections - I want that regular users can start and stop connections configured by root.

Is this possible with network manager? Can I configure network manager that it wouldn't let a user add new connection at all? How?

I would love a NetworkManager that only allowed access to a class of devices. In my case, where all wired interfaces (PCI cards) are handled the traditional way and cannot be modified by NetworkManager, but things like wireless or USB are available in NetworkManager.

You can exclude interfaces from NM control using unmanaged-devices in NetworkManager.conf. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Jun 15, 2016 at 11:27 PM, Andrei Borzenkov wrote:

15.06.2016 22:51, Istvan Gabor пишет:

...

What I want is this: - To set up network connection as root - I want that regular users cannot edit configured network connection in any way, cannot add, remove or change existing connections - I want that regular users can start and stop connections configured by root.

Is this possible with network manager? Can I configure network manager that it wouldn't let a user add new connection at all? How?

I think that suitable polkit configuration for actions org.freedesktop.NetworkManager.settings.modify.own, org.freedesktop.NetworkManager.settings.modify.system and org.freedesktop.NetworkManager.network-control should do it. You won't be able to prevent user from explicitly editing files under /etc/NetworkManager using su/sudo, but then you cannot do it with ifup either.

To elaborate a bit. network-control already should be allowed for active users without additional authentication; modify.system is already restricted to root by default; so you only need to restrict or completely deny modify.own to prevent users from creating own connections. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/15/2016 03:51 PM, Istvan Gabor wrote:

...

...

...

...

...

>YaST / ifup. Works perfectly fine.

I again installed openSUSE 13.2 and would like to configure network in the traditional way (ie not network manager). I am puzzled by the above statements like "Despite that, it still works quite well. " and "YaST / ifup. Works perfectly fine."

That was sarcasm - it continues to work very well because it was never removed. I installed a new 13.2 test system only last week I think, works quite well. Still don't understand. I can't find ifup method in yast, I see wicked method instead. Why do you say it wasn't removed?

I think you misinterpreted the "/" in "YaST / ifup. Works perfectly fine". It does NOT mean ... invoke Yast, use the menu item 'ifup under the networking tab' it means that there is capability for this in yast, or, alternatively, you can use the shell command 'ifup', as root, which, of course, has been around for about as long as Linux has had networking" Sometimes people complain about my verbosity, all those clauses in commas (or even my use of parenthetical subclauses), but I think this example shows how brevity can be misinterpreted. Some people seem obsessed with minimizing keystrokes (or mouse clicks); that has never made any sense to me. OK, I'm a dinosaur; I think in terms of ifconfig and ifup and would have to, slowly and ponderously, step though it myself to answer a yast question. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org