JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Connecting Systems Using Reactive Network Configuration in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Reactive Network Configuration (Overview)

Highlights of Profile-Managed Network Configuration

What Is Reactive Network Configuration?

When to Use Reactive Network Configuration

Network Profiles and Types

Description of an NCP

Description of the Automatic and User-Defined NCPs

Description of an NCU

Description of a Location Profile

Description of an ENM

Description of a Known WLAN

Profile Activation Policy

NCP Activation Policy

NCU Activation Properties

Examples of an NCP Policy

Location Activation Selection Criteria

Profile Configuration Tasks

How Reactive Network Profiles Work

How Reactive Networking Works With Other Oracle Solaris Networking Technologies

SMF Network Services

Network Configuration Security and Authorizations

Authorizations and Profiles Related to Network Configuration

Authorizations Required to Use the User Interfaces

Where to Find Network Configuration Tasks

2.  Creating and Configuring Reactive Network Profiles (Tasks)

3.  Administering Your Reactive Network Configuration (Tasks)

4.  Using the Network Administration Graphical User Interface

Index

Network Configuration Security and Authorizations

Security for reactive network configuration encompasses the following components:

The netcfgd daemon controls the repository where all of the network configuration information is stored. The netcfg command, the network administration GUI, and the nwamd daemon send requests to the netcfgd daemon to access the repository. These functional components make requests through the network configuration management library, libnwam.

Authorizations and Profiles Related to Network Configuration

The current network configuration implementation uses the following authorizations to perform specific tasks:

These authorizations are registered in the auth_attr database. For more information, see the auth_attr(4) man page.

The solaris.network.autoconf.read authorization is included in the Basic Solaris User rights profile, which is assigned to all users by default. Any user with this authorization is therefore able to view the current network state and the contents of all network profiles.

Two additional rights profiles are provided: Network Autoconf User and Network Autoconf Admin. The Network Autoconf User profile has read, select, and wlan authorizations. The Network Autoconf Admin profile adds the write authorization. The Network Autoconf User profile is assigned to the Console User profile. Therefore, by default, anyone who is logged in to the console can view, enable, and disable profiles. Because the Console User profile is not assigned the solaris.network.autoconf.write authorization, any user with this authorization cannot create or modify NCPs, NCUs, locations, or ENMs. However, the Console User profile can view, create, and modify WLANs.

Authorizations Required to Use the User Interfaces

The netcfg and netadm commands can be used to view network profiles by any user who has the Basic Solaris User rights profile. This profile is assigned to all users by default.

The netadm command can also be used to enable network profiles by any user who has the Network Autoconf User or Console User profile. The Console User profile is automatically assigned to the user who is logged in to the system from /dev/console.

To modify network profiles by using the netcfg command, you need the solaris.network.autoconf.write authorization or the Network Autoconf Admin profile.

You can determine the privileges that are associated with a rights profile by using the profiles command with the profile name. For more information, see the profiles(1) man page.

For example, to determine privileges that are associated with the Console User rights profile, use the following command:

$ profiles -p "Console User" info
Found profile in files repository.
    name=Console User
    desc=Manage System as the Console User
    auths=solaris.system.shutdown,solaris.device.cdrw,solaris.smf.manage.vbiosd,
    solaris.smf.value.vbiosd
    profiles=Suspend To RAM,Suspend To Disk,Brightness,CPU Power Management,
    Network Autoconf User,Desktop Removable Media User
    help=RtConsUser.html

The network administration GUI includes the following components, which are not privileged. These components are granted authorizations, depending on how they are started and the tasks they need to perform.

You can obtain additional authorizations in one of the following ways: