Hello Guest, if you reading this it means you have not yet registered. Please take a second to Click here to register and in a few simple steps, you will be able to enjoy all the many features of our fine community. Please note that nicknames are prohibited lewd or meaningless (no numbers or letters at random) and introduce yourself in the section for you to meet our community.
NetworkManager
Pokaż wyniki od 1 do 3 z 3

Temat: NetworkManager

  1. #1
    Avatar POL_ED
    POL_ED jest nieaktywny Zbanowany admin
    Mężczyzna
    Dystrybucja: MDV2011-32,Debian Lenny, 64studio
    Dołączył
    Jun 2005
    Skąd
    Tigerland
    Postów
    12,425
    Wątków
    233
    Siła Reputacji
    1274
    Reputacja
    18333

    NetworkManager

    NAME
    NetworkManager.conf - NetworkManager configuration file

    SYNOPSIS
    /etc/NetworkManager/NetworkManager.conf
    or
    <SYSCONFDIR>/NetworkManager/NetworkManager.conf
    where <SYSCONFDIR> depends on your distribution or build.

    DESCRIPTION
    NetworkManager.conf is a configuration file for NetworkManager. It is
    used to set up various aspects of NetworkManager's behavior. The loca‐
    tion of the file may be changed through use of the "--config=" argument
    for NetworkManager (8).

    FILE FORMAT
    The configuration file format is so-called key file (sort of ini-style
    format). It consists of sections (groups) of key-value pairs. Lines
    beginning with a '#' and blank lines are considered comments. Sections
    are started by a header line containing the section enclosed in '[' and
    ']', and ended implicitly by the start of the next section or the end
    of the file. Each key-value pair must be contained in a section.
    Minimal system settings configuration file looks like this:

    [main]
    plugins=keyfile

    Description of sections and available keys follows:

    [main]
    This section is the only mandatory section of the configuration file.

    plugins=plugin1,plugin2, ...
    List system settings plugin names separated by ','. These plug‐
    ins are used to read/write system-wide connection. When more
    plugins are specified, the connections are read from all listed
    plugins. When writing connections, the plugins will be asked to
    save the connection in the order listed here. If the first plug‐
    in cannot write out that connection type, or can't write out any
    connections, the next plugin is tried. If none of the plugins
    can save the connection, the error is returned to the user.

    Available plugins:

    keyfile
    plugin is the generic plugin that supports all the con‐
    nection types and capabilities that NetworkManager has.
    It writes files out in a .ini-style format in /etc/Net‐
    workManager/system-connections. For security, it will
    ignore files that are readable or writeable by any user
    or group other than root since private keys and
    passphrases may be stored in plaintext inside the file.

    ifcfg-rh
    plugin is used on the Fedora and Red Hat Enterprise Linux
    distributions to read and write configuration from the
    standard /etc/sysconfig/network-scripts/ifcfg-* files.
    It currently supports reading wired, WiFi, and 802.1x
    connections, but does not yet support reading or writing
    mobile broadband, PPPoE, or VPN connections. To allow
    reading and writing of these add keyfile plugin to your
    configuration as well.

    ifcfg-mdv
    plugin is used on the Mandriva distribution to read and
    write configuration from the standard files under
    /etc/sysconfig/network-scripts. Additionally wireless
    security information is taken from /etc/wpa_suppli‐
    cant.conf. It currently supports reading wired, WiFi,
    and possibly 802.1x connections, but does not yet support
    reading or writing mobile broadband, PPPoE, or VPN con‐
    nections. To allow reading and writing of these add key‐
    file plugin to your configuration as well.

    ifupdown
    plugin is used on the Debian and Ubuntu distributions,
    and reads connections from /etc/network/interfaces. Since
    it cannot write connections out (that support isn't
    planned), it is usually paired with the keyfile plugin to
    enable saving and editing of new connections. The ifup‐
    down plugin supports basic wired and WiFi connections,
    including WPA-PSK.

    ifcfg-suse
    plugin is only provided for simple backward compatibility
    with SUSE and OpenSUSE configuration. Most setups should
    be using the keyfile plugin instead. The ifcfg-suse plug‐
    in supports reading wired and WiFi connections, but does
    not support saving any connection types.

    dhcp=dhclient | dhcpcd
    This key sets up what DHCP client NetworkManager will use.
    Presently dhclient and dhcpcd are supported. The client config‐
    ured here should be available on your system too. If this key is
    missing, available DHCP clients are looked for in this order:
    dhclient, dhcpcd.

    no-auto-default=<hwaddr>,<hwaddr>,... | *
    Set devices for which NetworkManager shouldn't create default
    wired connection (Auto eth0). NetworkManager creates a default
    wired connection for any wired device that is managed and
    doesn't have a connection configured. List a device in this
    option to inhibit creating the default connection for the
    device.
    When the default wired connection is deleted or saved to a new
    persistent connection by a plugin, the MAC address of the wired
    device is automatically added to this list to prevent creating
    the default connection for that device again. Devices are spec‐
    ified by their MAC addresses, in lowercase. Multiple entries are
    separated by commas. You can use the glob character * instead of
    listing addresses to specify all devices.
    Examples:
    no-auto-default=00:22:68:5c:5d:c4,00:1e:65:ff:aa:ee
    no-auto-default=*

    dns=plugin1,plugin2, ...
    List DNS plugin names separated by ','. DNS plugins are used to
    provide local caching nameserver functionality (which speeds up
    DNS queries) and to push DNS data to applications that use it.

    Available plugins:

    dnsmasq
    this plugin uses dnsmasq to provide local caching name‐
    server functionality.

    [keyfile]
    This section contains keyfile-specific options and thus only has effect
    when using keyfile plugin.

    hostname=<hostname>
    Set a persistent hostname when using the keyfile plugin.

    unmanaged-devices=mac:<hwaddr>;mac:<hwaddr>;...
    Set devices that should be ignored by NetworkManager when using
    the keyfile plugin. Devices are specified in the following for‐
    mat: "mac:<hwaddr>", where <hwaddr> is MAC address of the device
    to be ignored, in hex-digits-and-colons notation. Multiple
    entries are separated by a semicolon. No spaces are allowed in
    the value.
    Example:
    unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C 4

    [ifupdown]
    This section contains ifupdown-specific options and thus only has
    effect when using ifupdown plugin.

    managed=false | true
    Controls whether interfaces listed in the 'interfaces' file are
    managed by NetworkManager. If set to true, then interfaces
    listed in /etc/network/interfaces are managed by NetworkManager.
    If set to false, then any interface listed in /etc/net‐
    work/interfaces will be ignored by NetworkManager. Remember that
    NetworkManager controls the default route, so because the inter‐
    face is ignored, NetworkManager may assign the default route to
    some other interface. When the option is missing, false value
    is taken as default.

    [logging]
    This section controls NetworkManager's logging. Any settings here are
    overridden by the --log-level and --log-domains command-line options.

    level=<level>
    One of [ERR, WARN, INFO, DEBUG]. The ERR level logs only criti‐
    cal errors. WARN logs warnings that may reflect operation.
    INFO logs various informational messages that are useful for
    tracking state and operations. DEBUG enables verbose logging
    for debugging purposes. Subsequent levels also log all messages
    from earlier levels; thus setting the log level to INFO also
    logs error and warning messages.

    domains=<domain1>,<domain2>, ...
    The following log domains are available: [HW, RFKILL, ETHER,
    WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4,
    DNS, VPN, SHARING, SUPPLICANT, AGENTS, SETTINGS, SUSPEND, CORE,
    DEVICE, OLPC, WIMAX, INFINIBAND, FIREWALL, ADSL, BOND, VLAN,
    BRIDGE].
    In addition to them, these special domains can be used: [NONE,
    ALL, DEFAULT, DHCP, IP].

    NONE = when given by itself, logging is disabled
    ALL = all log domains will be switched on
    DEFAULT = default log domains
    DHCP = a shortcut for "DHCP4, DHCP6"
    IP = a shortcut for "IP4, IP6"

    HW = Hardware related operations
    RFKILL = RFKill subsystem operations
    ETHER = Ethernet device operations
    WIFI = Wi-Fi device operations
    BT = Bluetooth
    MB = Mobile Broadband
    DHCP4 = DHCP for IPv4
    DHCP6 = DHCP for IPv6
    PPP = Point-to-point protocol operations
    WIFI_SCAN = Wi-Fi scanning operations
    IP4 = Domain for IPv4 logging
    IP6 = Domain for IPv6 logging
    AUTOIP4 = AutoIP (avahi) operations
    DNS = Domain Name System related operations
    VPN = Virtual Private Network connections and operaions
    SHARING = Connection sharing
    SUPPLICANT = WPA supplicant related operations
    AGENTS = Secret agents operations and communication
    SETTINGS = Settings/config service operations
    SUSPEND = Suspend/resume
    CORE = Core daemon operations
    DEVICE = Activation and general interface operations
    OLPC = OLPC Mesh device operations
    WIMAX = Wimax device operations
    INFINIBAND = InfiniBand device operations
    FIREWALL = FirewallD related operations
    ADSL = ADSL device operations
    BOND = Bonding device operations
    VLAN = VLAN device operations
    BRIDGE = Bridging device operations

    [connectivity]
    This section controls NetworkManager's optional connectivity checking
    functionality. This allows NetworkManager to detect whether or not the
    system can actually access the internet or whether it is behind a cap‐
    tive portal.

    uri=<uri>
    The URI of a web page to periodically request when connectivity
    is being checked. This page should return the header "X-Net‐
    workManager-Status" with a value of "online". Alternatively,
    it's body content should be set to "NetworkManager is online".
    The body content check can be controlled by the response option.
    If this option is blank or missing, connectivity checking is
    disabled.

    interval=<seconds>
    Controls how often connectivity is checked when a network con‐
    nection exists. If set to 0 connectivity checking is disabled.
    If missing, the default is 300 seconds.

    response=<response>
    If set controls what body content NetworkManager checks for when
    requesting the URI for connectivity checking. If missing,
    defaults to "NetworkManager is online"

    SEE ALSO
    http://live.gnome.org/NetworkManager/SystemSettings

    NetworkManager(8), nmcli(1), nm-tool(1), nm-online(1), nm-settings(5).

    17 January 2013 NetworkManager.conf(5)
    Ostatnio edytowane przez POL_ED ; 04.02.2017 o 22:48
    Proszę o używanie przycisków reputacji
    Jak stosować vbcode


    Jabber : [jabber]pol_ed[/jabber]

  2. Panna Google
    Panna Google jest aktywna
    Avatar Panny Google

    Dołączył
    01-05-2004
    Skąd
    Internet
    Postów
    999
    Pochwał
    159

    Nie lubisz reklam? Zarejestrowani ich nie widzą! Rejestracja







  3. #2
    Avatar bolwerk
    bolwerk jest nieaktywny Admin
    Mężczyzna
    Dystrybucja: Debian GNU/Linux Wheez/CyanogenMod-7.0.3
    Dołączył
    Jun 2004
    Skąd
    Small Town: Nowhere
    Wiek
    40
    Postów
    2,809
    Wątków
    41
    Siła Reputacji
    265
    Reputacja
    3451

    Odp: NetworkManager

    Przyznaję się od razu. Nie przeczytałem od początku do końca.

    POL_ED o co chodzi?

    Pozdrawiam...
    Ostatnio edytowane przez bolwerk ; 05.02.2017 o 00:22 Powód: Literówka...

  4. #3
    Avatar POL_ED
    POL_ED jest nieaktywny Zbanowany admin
    Mężczyzna
    Dystrybucja: MDV2011-32,Debian Lenny, 64studio
    Dołączył
    Jun 2005
    Skąd
    Tigerland
    Postów
    12,425
    Wątków
    233
    Siła Reputacji
    1274
    Reputacja
    18333

    Odp: NetworkManager

    Stopniowo będzie przyrastać (o ile starczy mi sił .....)
    O "celowości" systemd - już jest na forum.
    systemd.network + NetworkManager = spore problemy z netem. Zwłaszcza gdy potrzebna konfiguracja statyczna, a nie dynamiczna przez DHCP. A i taką konfiguracją bywają problemy przy aktualizacji OMA...
    Do tego jeszcze systemd-resolved

    Wszytko w swoim czasie. Opisów konfiguracji internetu (i nie tylko) w OMA Lx jak na lekarstwo.


    Kod:
     ---------------------------
            \   ^__^
             \  (oo)\_______
                (__)\       )\/\
                    ||----w |
                    ||     ||
    ===================
    Czysta instalacja OMA Lx 3.01 z DVD.

    Kod:
    cat /etc/sysconfig/network-scripts/ifcfg-eth0
    DEVICE=eth0
    ONBOOT=yes
    NM_CONTROLLED=yes
    BOOTPROTO=dhcp
    Kod:
    ll /etc/resolv.conf
     /etc/resolv.conf -> /var/run/NetworkManager/resolv.conf
    Kod:
    cat /etc/resolv.conf
    # Generated by NetworkManager
    search home
    nameserver 192.168.1.1
    Kod:
    cat /etc/sysconfig/network
    NETWORKING=yes
    Kod:
    ifconfig -a
    enp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            ether 00:01:29:a3:66:xx  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 19  
    
    enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.1.17  netmask 255.255.255.0  broadcast 192.168.1.255
            inet6 fe80::201:29ff:fea3:66:yy  prefixlen 64  scopeid 0x20<link>
            ether 00:01:29:a3:66:ae  txqueuelen 1000  (Ethernet)
            RX packets 7056  bytes 7906529 (7.5 MiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 5864  bytes 652392 (637.1 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 17  
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1  (Local Loopback)
            RX packets 4  bytes 200 (200.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 4  bytes 200 (200.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    Kod:
    dmesg |grep eth
    [2017] sky2 0000:03:00.0 eth0: addr 00:01:29:a3:66:xx
    [2017] sky2 0000:05:00.0 eth1: addr 00:01:29:a3:66:yy
    [2017] sky2 0000:03:00.0 enp3s0: renamed from eth0
    [2017] sky2 0000:05:00.0 enp5s0: renamed from eth1
    Kod:
    systemctl -l status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
       Active: active (running) since 2017 CET; 8min ago
         Docs: man:NetworkManager(8)
     Main PID: 3513 (NetworkManager)
        Tasks: 4 (limit: 4915)
       CGroup: /system.slice/NetworkManager.service
               ├─3513 /usr/sbin/NetworkManager --no-daemon
               └─3807 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp5s0.pid -lf /var/lib/NetworkManager/dhclient-7ae3e730-f297-45f1-bff3-6972a575876a-enp5s0.lease -cf /var/lib/NetworkManager/dhclient-enp5s0.conf enp5s0
    NetworkManager[3513]: <info>  [1486321102.7127] device (enp5s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
    NetworkManager[3513]: <info>  [1486321102.7134] device (enp5s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
    NetworkManager[3513]: <info>  [1486321102.7137] device (enp5s0): state change: secondaries -> activated (reason 'none') [90 100 0]
    NetworkManager[3513]: <info>  [1486321102.7138] manager: NetworkManager state is now CONNECTED_LOCAL
    dhclient[3807]: bound to 192.168.1.17 -- renewal in 40415 seconds.
    NetworkManager[3513]: <info>  [1486321102.9717] manager: NetworkManager state is now CONNECTED_GLOBAL
    NetworkManager[3513]: <info>  [1486321102.9719] policy: set 'enp5s0' (enp5s0) as default for IPv4 routing and DNS
    NetworkManager[3513]: <info>  [1486321103.4000] device (enp5s0): Activation: successful, device activated.
    NetworkManager[3513]: <info>  [1486321107.1771] manager: startup complete
    NetworkManager[3513]: <info>  [1486321322.1564] audit: op="connection-update" uuid="7ae3e730-f297-45f1-bff3-6972a575876a" name="enp5s0" pid=4638 uid=1001 result="success"

    ===========
    Edit:
    Kod:
    cat /etc/X11/xorg.conf
    cat: /etc/X11/xorg.conf: Nie ma takiego pliku ani katalogu
    Ostatnio edytowane przez POL_ED ; 05.02.2017 o 20:32
    Proszę o używanie przycisków reputacji
    Jak stosować vbcode


    Jabber : [jabber]pol_ed[/jabber]

Informacje o wątku

Users Browsing this Thread

Aktualnie 1 użytkownik(ów) przegląda ten wątek. (0 zarejestrowany(ch) oraz 1 gości)

Uprawnienia

  • Nie możesz zakładać nowych wątków
  • Nie możesz pisać wiadomości
  • Nie możesz dodawać załączników
  • Nie możesz edytować swoich postów
  •