Elektroda.pl
Elektroda.pl
X

Search our partners

Find the latest content on electronic components. Datasheets.com
Please add exception to AdBlock for elektroda.pl.
If you watch the ads, you support portal and users.

Mandriva 2014.1 Brak WiFi po wczorajszej aktualizacji...logi z konsoli

kopawel 16 Mar 2016 20:16 2556 24
  • #1
    kopawel
    Level 14  
    Witam.
    Wczoraj wieczorem zrobiłem aktualizacje systemu, laptop bym włączony całą noc, rano WiFi jeszcze działało i laptopa wyłączyłem. Dziś go uruchamiam a WiFi nie działa...tzn...widzi dostępne sieci, przy nazwie mojej napisane jest ''Ustawianie interfejsu'', ale nie chce się z nią połączyć i wyskakuje okno do wpisania hasła do sieci. Na tym samym laptopie mam też Win7 i tu jest ok. Na innych domowych urządzeniach internet także działa. Szukam po necie ale wszystko na te Ubuntu.
    Nie wiem od czego zacząć.

    Dzięki za pomoc.

    Dodano po 19 [minuty]:

    Oto wyniki z konsoli, widziałem że pytają o takie rzeczy...

    lspci
    Code:

    [root@localhost pawel]# lspci
    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
    00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
    00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
    01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce 610M] (rev a1)
    02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10)
    02:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10)
    02:00.2 System peripheral: Broadcom Corporation BCM57765/57785 MS Card Reader (rev 10)
    02:00.3 System peripheral: Broadcom Corporation BCM57765/57785 xD-Picture Card Reader (rev 10)
    03:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)


    lspci -nv
    Code:

    [root@localhost pawel]# lspci -nv
    00:00.0 0600: 8086:0104 (rev 09)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0
    Capabilities: [e0] Vendor Specific Information: Len=0c <?>

    00:01.0 0604: 8086:0101 (rev 09) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    I/O behind bridge: 00002000-00002fff
    Memory behind bridge: d0000000-d10fffff
    Prefetchable memory behind bridge: 00000000a0000000-00000000b1ffffff
    Capabilities: [88] Subsystem: 1025:0504
    Capabilities: [80] Power Management version 3
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [a0] Express Root Port (Slot+), MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [140] Root Complex Link
    Kernel driver in use: pcieport

    00:02.0 0300: 8086:0126 (rev 09) (prog-if 00 [VGA controller])
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 27
    Memory at d1400000 (64-bit, non-prefetchable) [size=4M]
    Memory at c0000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 3000 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [d0] Power Management version 2
    Capabilities: [a4] PCI Advanced Features
    Kernel driver in use: i915

    00:16.0 0780: 8086:1c3a (rev 04)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 28
    Memory at d1a04000 (64-bit, non-prefetchable)
    Capabilities: [50] Power Management version 3
    Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Kernel driver in use: mei_me

    00:1a.0 0c03: 8086:1c2d (rev 04) (prog-if 20 [EHCI])
    Subsystem: 1025:0504
    Flags: bus master, medium devsel, latency 0, IRQ 16
    Memory at d1a0a000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci-pci

    00:1b.0 0403: 8086:1c20 (rev 04)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 29
    Memory at d1a00000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
    Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [130] Root Complex Link
    Kernel driver in use: snd_hda_intel

    00:1c.0 0604: 8086:1c10 (rev b4) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
    Memory behind bridge: 9fb00000-9fbfffff
    Prefetchable memory behind bridge: 00000000d1800000-00000000d18fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: 1025:0504
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

    00:1c.1 0604: 8086:1c12 (rev b4) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
    Memory behind bridge: d1900000-d19fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: 1025:0504
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

    00:1d.0 0c03: 8086:1c26 (rev 04) (prog-if 20 [EHCI])
    Subsystem: 1025:0504
    Flags: bus master, medium devsel, latency 0, IRQ 23
    Memory at d1a09000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci-pci

    00:1f.0 0601: 8086:1c49 (rev 04)
    Subsystem: 1025:0504
    Flags: bus master, medium devsel, latency 0
    Capabilities: [e0] Vendor Specific Information: Len=0c <?>
    Kernel driver in use: lpc_ich

    00:1f.2 0106: 8086:1c03 (rev 04) (prog-if 01 [AHCI 1.0])
    Subsystem: 1025:0504
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 25
    I/O ports at 3098 [size=8]
    I/O ports at 30bc [size=4]
    I/O ports at 3090 [size=8]
    I/O ports at 30b8 [size=4]
    I/O ports at 3060 [size=32]
    Memory at d1a08000 (32-bit, non-prefetchable) [size=2K]
    Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [70] Power Management version 3
    Capabilities: [a8] SATA HBA v1.0
    Capabilities: [b0] PCI Advanced Features
    Kernel driver in use: ahci



    00:1f.3 0c05: 8086:1c22 (rev 04)
    Subsystem: 1025:0504
    Flags: medium devsel, IRQ 19
    Memory at d1a06000 (64-bit, non-prefetchable) [size=256]
    I/O ports at 3040 [size=32]

    01:00.0 0300: 10de:0dea (rev a1) (prog-if 00 [VGA controller])
    Subsystem: 1025:0505
    Flags: bus master, fast devsel, latency 0, IRQ 26
    Memory at d0000000 (32-bit, non-prefetchable) [size=16M]
    Memory at a0000000 (64-bit, prefetchable) [size=256M]
    Memory at b0000000 (64-bit, prefetchable) [size=32M]
    I/O ports at 2000 [size=128]
    Expansion ROM at d1000000 [disabled] [size=512K]
    Capabilities: [60] Power Management version 3
    Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [78] Express Endpoint, MSI 00
    Capabilities: [b4] Vendor Specific Information: Len=14 <?>
    Capabilities: [100] Virtual Channel
    Capabilities: [128] Power Budgeting <?>
    Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
    Kernel driver in use: nouveau

    02:00.0 0200: 14e4:16b5 (rev 10)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 16
    Memory at d1830000 (64-bit, prefetchable) [size=64K]
    Memory at d1840000 (64-bit, prefetchable) [size=64K]
    Expansion ROM at 9fb00000 [disabled] [size=2K]
    Capabilities: [48] Power Management version 3
    Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
    Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
    Capabilities: [ac] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [13c] Device Serial Number 00-00-dc-0e-a1-20-5f-c4
    Capabilities: [150] Power Budgeting <?>
    Capabilities: [160] Virtual Channel
    Kernel driver in use: tg3

    02:00.1 0805: 14e4:16bc (rev 10) (prog-if 01)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at d1800000 (64-bit, prefetchable) [size=64K]
    Capabilities: [48] Power Management version 3
    Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [ac] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [150] Power Budgeting <?>
    Capabilities: [160] Virtual Channel
    Kernel driver in use: sdhci-pci

    02:00.2 0880: 14e4:16be (rev 10)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 7
    Memory at d1810000 (64-bit, prefetchable) [size=64K]
    Capabilities: [48] Power Management version 3
    Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [ac] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [150] Power Budgeting <?>
    Capabilities: [160] Virtual Channel

    02:00.3 0880: 14e4:16bf (rev 10)
    Subsystem: 1025:0504
    Flags: bus master, fast devsel, latency 0, IRQ 7
    Memory at d1820000 (64-bit, prefetchable) [size=64K]
    Capabilities: [48] Power Management version 3
    Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [ac] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [150] Power Budgeting <?>
    Capabilities: [160] Virtual Channel

    03:00.0 0280: 168c:002e (rev 01)
    Subsystem: 105b:e034
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at d1900000 (64-bit, non-prefetchable) [size=64K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [60] Express Legacy Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
    Capabilities: [170] Power Budgeting <?>
    Kernel driver in use: ath9k


    lsusb
    Code:

    [root@localhost pawel]# lsusb
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 058f:b002 Alcor Micro Corp. Acer Integrated Webcam
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    uname -r
    Code:

    [root@localhost pawel]# uname -r
    4.1.15-nrjQL-desktop-1omv


    rpm -qa|grep kernel
    Code:

    [root@localhost pawel]# rpm -qa|grep kernel
    kernel-nrjQL-desktop-3.13.6-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.13.11-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.14.9-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.15.6-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.15.7-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.15.8-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.15.10-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.15.10-2omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.5-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.10-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.11-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-devel-3.15.10-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.12-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-laptop-3.18.12-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.14-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.14-2omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-3.18.16-2omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-4.1.3-3omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-devel-4.1.3-3omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-devel-4.1.9-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-4.1.9-1omv-1-1-omv2014.0.x86_64
    lib64kplatokernel14-2.9.10-0.1-omv2014.0.x86_64
    kernel-firmware-extra-20160106-0.1-omv2014.0.noarch
    kernel-headers-4.1.15-1-omv2014.0.x86_64
    kernel-firmware-20160106-0.1-omv2014.0.noarch
    kernel-nrjQL-desktop-4.1.15-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-latest-4.1.15-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-devel-4.1.15-1omv-1-1-omv2014.0.x86_64
    kernel-nrjQL-desktop-devel-latest-4.1.15-1-omv2014.0.x86_64


    ifconfig -a
    Code:

    [root@localhost pawel]# ifconfig -a
    eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether dc:0e:a1:20:5f:c4 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 16

    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 0 (Local Loopback)
    RX packets 412 bytes 33476 (32.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 412 bytes 33476 (32.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether 64:27:37:4c:ec:e7 txqueuelen 1000 (Ethernet)
    RX packets 8 bytes 1004 (1004.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 36 bytes 25081 (24.4 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    iwconfig
    Code:

    [root@localhost pawel]# iwconfig
    eth0 no wireless extensions.

    wlan0 IEEE 802.11bgn ESSID:off/any
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=15 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off
    Encryption key:off
    Power Management:off

    lo no wireless extensions.


    iwlist wlan0 scan
    Code:
    [root@localhost pawel]# iwlist wlan0 scan
    
    wlan0 Scan completed :
    Cell 01 - Address: 36:23:87:70:36:A5
    Channel:1
    Frequency:2.412 GHz (Channel 1)
    Quality=60/70 Signal level=-50 dBm
    Encryption key:on
    ESSID:"DIRECT-RG-BRAVIA"
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
    36 Mb/s; 48 Mb/s; 54 Mb/s
    Mode:Master
    Extra:tsf=000000073f7bc2a6
    Extra: Last beacon: 35ms ago
    IE: Unknown: 00104449524543542D52472D425241564941
    IE: Unknown: 01080C1218243048606C
    IE: Unknown: 030101
    IE: Unknown: 2A0100
    IE: Unknown: 2D1AAC0102FFFF000000000000000000000000000000000000000000
    IE: Unknown: 3D1601000000000000000000000000000000000000000000
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
    IE: Unknown: DD8B0050F204104A0001101044000102103B0001031047001000000000000010108000D8D43CCBC4C710210010536F6E7920436F72706F726174696F6E1023000B536F6E7920425241564941102400013010420001301054000800070050F204000110110012425241564941204B444C2D35305738313542100800020000103C0001011049000600372A000120
    Cell 02 - Address: 7C:4C:A5:D6:E0:A9
    Channel:1
    Frequency:2.412 GHz (Channel 1)
    Quality=57/70 Signal level=-53 dBm
    Encryption key:on
    ESSID:"SKY414B9"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
    Mode:Master
    Extra:tsf=00000035f439bcfd
    Extra: Last beacon: 35ms ago
    IE: Unknown: 0008534B593431344239
    IE: Unknown: 010882848B962430486C
    IE: Unknown: 030101
    IE: Unknown: 0706444520010D14
    IE: Unknown: 200100
    IE: Unknown: 23021100
    IE: Unknown: 2A0104
    IE: Unknown: 2F0104
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    IE: Unknown: 32040C121860
    IE: Unknown: 0B050400370000
    IE: Unknown: 2D1ABC181BFFFF000000000000000000000000000000000000000000
    IE: Unknown: 3D1601080400000000000000000000000000000000000000
    IE: Unknown: 7F080400080000000040
    IE: Unknown: DD800050F204104A0001101044000102103B0001031047001021DA9B393CB0C6CA9FCDE8FBBFD8013C1021000842726F6164636F6D1023000842726F6164636F6D1024000631323334353610420004313233341054000800060050F20400011011000A42726F6164636F6D415010080002200C103C0001011049000600372A000120
    IE: Unknown: DD090010180204000C0000
    IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
    IE: Unknown: 46057200010000
    Cell 03 - Address: 00:07:26:AB:0F:2D
    Channel:1
    Frequency:2.412 GHz (Channel 1)
    Quality=53/70 Signal level=-57 dBm
    Encryption key:on
    ESSID:"BTHomeSpot-K8H"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
    9 Mb/s; 12 Mb/s; 18 Mb/s
    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
    Mode:Master
    Extra:tsf=0000026f4156eefc
    Extra: Last beacon: 35ms ago
    IE: Unknown: 000E4254486F6D6553706F742D4B3848
    IE: Unknown: 010882848B960C121824
    IE: Unknown: 030101
    IE: Unknown: 0706474220010D14
    IE: Unknown: 200100
    IE: Unknown: 2A0100
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    IE: Unknown: 32043048606C
    IE: Unknown: 2D1A2C0103FF00000000000000000000000000000000000000000000
    IE: Unknown: 331A2C0103FF00000000000000000000000000000000000000000000
    IE: Unknown: 3D1601080000000000000000000000000000000000000000
    IE: Unknown: 341601080000000000000000000000000000000000000000
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    IE: Unknown: DD180050F2020101030003A4000027A4000042435E0062322F00
    IE: Unknown: DD0900037F01010000FF7F
    IE: Unknown: DD8A0050F204104A0001101044000102103B0001031047001000000000000010000000000726AB0F2D102100092241746865726F732210230010225750535F484F53544150445F4150221024000A223031323334353637221042000A223031323334353637221054000800060050F20400011011000B2241746865726F73415022100800020084103C000103
    Cell 04 - Address: C4:EA:1D:58:D2:9B
    Channel:11
    Frequency:2.462 GHz (Channel 11)
    Quality=40/70 Signal level=-70 dBm
    Encryption key:on
    ESSID:"TNCAP58D29B"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
    Mode:Master
    Extra:tsf=0000001a32d8fada
    Extra: Last beacon: 35ms ago
    IE: Unknown: 000B544E434150353844323942
    IE: Unknown: 010882848B962430486C
    IE: Unknown: 03010B
    IE: Unknown: 2A0104
    IE: Unknown: 2F0104
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    IE: Unknown: 32040C121860
    IE: Unknown: 2D1A1C181BFFFF000000000000000000000000000000000000000000
    IE: Unknown: 3D160B080000000000000000000000000000000000000000
    IE: Unknown: DD9B0050F204104A0001101044000102103B000103104700107052E57276B35C15B6982CFC223361011021000B546563686E69636F6C6F721023000E546563686E69636F6C6F72205447102400043538326E10420010346133343038376632376137313264331054000800060050F204000110110012546563686E69636F6C6F722054473538326E100800020004103C0001011049000600372A000120
    IE: Unknown: DD090010180202000C0000
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : TKIP
    Authentication Suites (1) : PSK
    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
    Cell 05 - Address: 90:72:40:23:C1:14
    Channel:11
    Frequency:2.462 GHz (Channel 11)
    Quality=22/70 Signal level=-88 dBm
    Encryption key:on
    ESSID:"Prince of Persia 2"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
    Mode:Master
    Extra:tsf=000002b1a4a1c470
    Extra: Last beacon: 35ms ago
    IE: Unknown: 00125072696E6365206F66205065727369612032
    IE: Unknown: 010882848B962430486C
    IE: Unknown: 03010B
    IE: Unknown: 0706474220010D14
    IE: Unknown: 200100
    IE: Unknown: 23021000
    IE: Unknown: 2A0100
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    IE: Unknown: 32040C121860
    IE: Unknown: 2D1AAD1917FFFFFF0000000000000000000000000000000000000000
    IE: Unknown: 3D160B080400000000000000000000000000000000000000
    IE: Unknown: 7F080000000000000040
    IE: Unknown: DD0B0017F20100010100000007
    IE: Unknown: DD0700039301780320
    IE: Unknown: DD0E0017F2070001010690724023C115
    IE: Unknown: DD090010180201001C0000
    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
    IE: Unknown: 46050200010000
    Cell 06 - Address: 00:8A:AE:9C:4B:9A
    Channel:9
    Frequency:2.452 GHz (Channel 9)
    Quality=25/70 Signal level=-85 dBm
    Encryption key:on
    ESSID:"BTHub5-GRKM"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
    9 Mb/s; 12 Mb/s; 18 Mb/s
    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
    Mode:Master
    Extra:tsf=000000395ec45949
    Extra: Last beacon: 35ms ago
    IE: Unknown: 000B4254487562352D47524B4D
    IE: Unknown: 010882848B960C121824
    IE: Unknown: 030109
    IE: Unknown: 0706474220010D14
    IE: Unknown: 2A0100
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    IE: Unknown: 32043048606C
    IE: Unknown: 2D1AAC011BFFFF000000000000000000008000000000000000000000
    IE: Unknown: 3D1609080000000000000000000000000000000000000000
    IE: Unknown: 4A0E14000A002C01C800140005001900
    IE: Unknown: 7F080100000000000040
    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
    IE: Unknown: DD0900037F01010000FF7F
    IE: Unknown: DD8E0050F204104A000110104400010210570001001041000100103B00010310470010284826427B245F6B95FE5BE26C0B738010210002425410230005487562203510240009425420487562203541104200122B3036383334332B4E5134303531313831381054000800060050F204000110110010425420486F6D652048756220352E3041100800020084103C000101
    Cell 07 - Address: 5A:B6:86:B3:9D:C0
    Channel:6
    Frequency:2.437 GHz (Channel 6)
    Quality=26/70 Signal level=-84 dBm
    Encryption key:off
    ESSID:"BTWiFi-with-FON"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
    Mode:Master
    Extra:tsf=000000167cd70180
    Extra: Last beacon: 35ms ago
    IE: Unknown: 000F4254576946692D776974682D464F4E
    IE: Unknown: 010882848B962430486C
    IE: Unknown: 030106
    IE: Unknown: 2A0104
    IE: Unknown: 2F0104
    IE: Unknown: 32040C121860
    IE: Unknown: 2D1AFC181BFFFF000000000000000000000000000000000000000000
    IE: Unknown: 3D1606000400000000000000000000000000000000000000
    IE: Unknown: DD090010180208F0040000
    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
  • #3
    kopawel
    Level 14  
    Niestety nie jestem w stanie teraz powiedziec z jakiego programu do łączenia się z internetem uzywam...jestem w pracy. Próbowałem zapomnieć sieć I skonfigurować połączenie na nowo ale nic to nie pomoglo.
  • #4
    kopawel
    Level 14  
    Narzędzia jakie mam zainstalowane do sieci to drakx-net oraz networkmanager-applet...
  • #5
    kopawel
    Level 14  
    Witam. Zrobiłem tak jak w podanym powyżej linku, punkt po punkcie.

    Problemy nastąpiły w punkcie 2/3. Jest tu w nawiasie informacja że wlan jest UP, ale coś jest także DOWN.
    Dla pewnosci więc wprowadziłem polecenie włączenia karty ale nic to nie zmieniło. Wciąż jakieś urządzenie jest DOWN.
    W punktach 4 i 5 wszystko przebiegało u mnie dokładnie jak w poradniku. Doszedlem do punktu 6 i pojawił sie problem z
    komendą
    ''wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf'' a nastepnie po komendzie ''iw wlan0 link'' okazało się ze wlan0 jest nie połączony z siecią.
    Nie wiem co robic dalej...ktoś ma jakies pomysły ?

    Paweł.


    Punkt 3/4:
    ''Step 3: Bring up the WiFi interface – WiFi network from command line

    Use the following command to bring up the WiFI interface
    Code:

    root@kali:~# ip link set wlan0 up


    Note: If you’re using Ubuntu, Linux Mint, CentOS, Fedora etc. use the command with ‘sudo’ prefix

    Connect to WiFi network in Linux from command line - Bring device up - blackMORE Ops-3

    If you run the show link command again, you can tell that wlan1 is now UP.
    Code:

    root@kali:~# ip link show wlan0
    4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
        link/ether 00:60:64:37:4a:30 brd ff:ff:ff:ff:ff:ff
    root@kali:~#


    Step 4: Check the connection status – WiFi network from command line

    You can check WiFi network connection status from command line using the following command
    Code:

    root@kali:~# iw wlan0 link
    Not connected.
    root@kali:~#

    Connect to WiFi network in Linux from command line - Check device connection - blackMORE Ops-4

    The above output shows that you are not connected to any network.''

    A u mnie...
    Code:

    [root@localhost pawel]# ip link show wlan0
    3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
        link/ether 64:27:37:4c:ec:e7 brd ff:ff:ff:ff:ff:ff
    [root@localhost pawel]#
    [root@localhost pawel]# ip link set wlan0 up
    [root@localhost pawel]#
    [root@localhost pawel]# ip link show wlan0
    3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
        link/ether 64:27:37:4c:ec:e7 brd ff:ff:ff:ff:ff:ff
    [root@localhost pawel]#






    Punkt6:
    ''Step 6: Generate a wpa/wpa2 configuration file – WiFi network from command line

    Now we will generate a configuration file for wpa_supplicant that contains the pre-shared key (“passphrase”) for the WiFi network.
    Code:

    root@kali:~# wpa_passphrase blackMOREOps >> /etc/wpa_supplicant.conf
    abcd1234
    root@kali:~#

    (where 'abcd1234' was the Network password)

    wpa_passphrase uses SSID as a string, that means you need to type in the passphrase for the WiFi network blackMOREOps after you run the command.

    Connect to WiFi network in Linux from command line - Connect to WPA WPA2 WiFi network - blackMORE Ops - 6

    Note: If you’re using Ubuntu, Linux Mint, CentOS, Fedora etc. use the command with ‘sudo’ prefix

    wpa_passphrase will create the necessary configuration entries based on your input. Each new network will be added as a new configuration (it wont replace existing configurations) in the configurations file /etc/wpa_supplicant.conf.
    Code:

    root@kali:~# cat /etc/wpa_supplicant.conf
    # reading passphrase from stdin
    network={
     ssid="blackMOREOps"
     #psk="abcd1234"
     psk=42e1cbd0f7fbf3824393920ea41ad6cc8528957a80a404b24b5e4461a31c820c
    }
    root@kali:~#

    ''
    U mnie...

    Code:

    [root@localhost pawel]# cat /etc/wpa_supplicant.conf                                       


    blob-base64-exampleblob={
    SGVsbG8gV29ybGQhCg==
    }


    # Wildcard match for SSID (plaintext APs only). This example select any
    # open AP regardless of its SSID.
    # network={
    #       key_mgmt=NONE
    # }


    network={
        psk="URYTECFE"
        priority=1
        scan_ssid=0
        ssid="SKY414B9"
    }
    # reading passphrase from stdin
    network={
            ssid="SKY414B9"
            #psk="URYTECFE"
            psk=f12d9b790efae3d6733c6227279a9bbf3e2a21b37f935cd95952819e16c4eb96
    }
    [root@localhost pawel]# wpa_supplicant.conf -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf                 
    bash: wpa_supplicant.conf: nie znaleziono polecenia
    [root@localhost pawel]# wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf     
    Successfully initialized wpa_supplicant
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ctrl_iface exists and seems to be in use - cannot override it
    Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
    Failed to initialize control interface '/var/run/wpa_supplicant'.
    You may have another wpa_supplicant process already running or the file was
    left by an unclean termination of wpa_supplicant in which case you will need
    to manually remove this file before starting wpa_supplicant again.

    [root@localhost pawel]# in wlan0 link
    bash: błąd składni przy nieoczekiwanym znaczniku `in'
    [root@localhost pawel]# iw wlan0 link
    Not connected.
  • #6
    Epic
    Level 29  
    1.W "wpa_supplicant.conf" twojemu ssid odpowiadają 2 wpisy. usuń pozostałe lub korzystaj z innego pliku.
    2.
    Code:
    ctrl_iface exists and seems to be in use - cannot override it
    
    Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
    Failed to initialize control interface '/var/run/wpa_supplicant'.
    You may have another wpa_supplicant process already running or the file was
    left by an unclean termination of wpa_supplicant in which case you will need
    to manually remove this file before starting wpa_supplicant again.

    To sprawdziłeś? Wygląda na to że w systemie działa drugi wpa_supplicant, najpewniej ten uruchomiony na potrzeby networkManagera. Wyłącz go na potrzeby testów.

    3. Spróbuj też dodać nl80211 jako sterownik(opcja po '-D') do wpa_supplicant
    Code:
    wpa_supplicant -D nl80211,wext -i wlan0 -c > ...
  • #7
    kopawel
    Level 14  
    Tak, to rozumiem tylko nie wiem jak to wyłączyc. Teraz tak myślę czy może by inaczej nazwać plik np. ''wpa_supplicant1.conf''. Ale co najważniejsze, w tej chwili jestem podłączony do innej sieci poprzez LAN bo WiFi tez nie chodzi, Czy do każdej sieci będę musiał sie lączyć w ten sposób ?...poprzez terminal...
  • #8
    Epic
    Level 29  
    Co nie wiesz jak wyłączyć?

    1. Usuń pozostałe wpisy w wpa_supplicant.conf to zwykły plik tekstowy używany do uruchomienia wpa_supplicant programu służącego do łączenia się z zabezpieczonymi sieciami wifi. I tylko do tego.
    2. Nie, nie będziesz się musiał zawsze łączyć za pomocą terminala chodzi tylko o zdiagnozowanie problemu. Na razie jest nim bez wątpienie pkt 1. i drugi proces wpa.
  • #9
    kopawel
    Level 14  
    W /etc/ posiadam pliki ''wpa_suplicant.conf'' oraz ''wpa_suplicant.conf.rpmnew''.
    Niestety żadnego z nich nie moge usunąć. Rozumiem że pierwszy musi być usunięty ale mam wątpliwości co do drugiego...
  • #10
    Epic
    Level 29  
    Wykonaj polecenia i wklej wyniki:
    Code:
    ps -eF | grep wpa


    Code:
    # diff /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.rpmnew


    I czytaj ze zrozumieniem, chodziło o usunięcie wpisów w pliku, a nie samego pliku.

    Wpisu czyli np:
    Code:
    network={
    
     ssid="blackMOREOps"
     #psk="abcd1234"
     psk=42e1cbd0f7fbf3824393920ea41ad6cc8528957a80a404b24b5e4461a31c820c
    }


    Tak jak pisałem możesz zostawić obydwa pliki i uruchomić wpa_supplicant korzystając z innego pliku .conf, który tworzysz samodzielnie. Ważne żeby tylko jeden program wpa_supplicant był uruchomiony.
  • #11
    kopawel
    Level 14  
    Oto wyniki z terminala:
    Code:

    [root@localhost pawel]# ps -eF | grep wpa
    root      3553     1  0  4748  6260   1 08:20 ?        00:00:06 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid
    root      7626     1  0  4747  3144   2 08:21 ?        00:00:48 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
    root     22239 22202  0  7396  2268   0 15:10 pts/2    00:00:00 grep --color wpa
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]# # diff /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.rpmnew
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]#



    Pliku wpa_supplicant.conf nie moge nawet otworzyć. Mandriva 2014.1 Brak WiFi po wczorajszej aktualizacji...logi z konsoli

    Widzę że nie mam uprawnień ale nawet jeżeli je zmienię to i tak automatycznie wracają do tych wcześniejszych.

    Napisałeś :''ważne żeby tylko jeden program supplicant był uruchomiony''...ja nie wiem jak go wyłączyć abym mogł uruchomić inny.
  • #12
    Epic
    Level 29  
    1. wpa_supplicant.conf zawiera hasła do twojego wifi może być odczytywany/edytowany tylko i wyłącznie przez roota. Z sudo możesz to robić w GUI, ale najlepiej w terminalu korzystając z dowolnego edytora.
    2. Jak widać w systemie działają 2 procesy wpa_supplicant. Zabij obydwa procesy np.
    Code:
    #kill 'identyfikator procesu'

    3. Plik wpa_supplicant.conf.rpmnew to nowa wersja konfiguracji utworzona przez aktualizacje najpewniej możesz ją usunąć. Ale wykonaj najpierw jeszcze raz komendę diff, bez znaczka '#' na początku gdyż się nie wykonała.
  • #13
    kopawel
    Level 14  
    Code:
    [root@localhost pawel]# diff /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.rpmnew  
    
    83a84,85
    > # Note: When using MACsec, eapol_version shall be set to 3, which is
    > # defined in IEEE Std 802.1X-2010.
    99a102,103
    > #    Note: macsec_qca driver is one type of Ethernet driver which implements
    > #    macsec feature.
    106a111,114
    > # Note: ap_scan=2 should not be used with the nl80211 driver interface (the
    > # current Linux interface). ap_scan=1 is optimized work working with nl80211.
    > # For finding networks using hidden SSID, scan_ssid=1 in the network block can
    > # be used with nl80211.
    112a121,144
    > # MPM residency
    > # By default, wpa_supplicant implements the mesh peering manager (MPM) for an
    > # open mesh. However, if the driver can implement the MPM, you may set this to
    > # 0 to use the driver version. When AMPE is enabled, the wpa_supplicant MPM is
    > # always used.
    > # 0: MPM lives in the driver
    > # 1: wpa_supplicant provides an MPM which handles peering (default)
    > #user_mpm=1
    >
    > # Maximum number of peer links (0-255; default: 99)
    > # Maximum number of mesh peering currently maintained by the STA.
    > #max_peer_links=99
    >
    > # Timeout in seconds to detect STA inactivity (default: 300 seconds)
    > #
    > # This timeout value is used in mesh STA to clean up inactive stations.
    > #mesh_max_inactivity=300
    >
    > # cert_in_cb - Whether to include a peer certificate dump in events
    > # This controls whether peer certificates for authentication server and
    > # its certificate chain are included in EAP peer certificate events. This is
    > # enabled by default.
    > #cert_in_cb=1
    >
    130a163,172
    > # OpenSSL cipher string
    > #
    > # This is an OpenSSL specific configuration option for configuring the default
    > # ciphers. If not set, "DEFAULT:!EXP:!LOW" is used as the default.
    > # See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation
    > # on cipher suite configuration. This is applicable only if wpa_supplicant is
    > # built to use OpenSSL.
    > #openssl_ciphers=DEFAULT:!EXP:!LOW
    >
    >
    216a259,279
    > # Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing
    > # The vendor attribute contents to be added in M1 (hex string)
    > #wps_vendor_ext_m1=000137100100020001
    >
    > # NFC password token for WPS
    > # These parameters can be used to configure a fixed NFC password token for the
    > # station. This can be generated, e.g., with nfc_pw_token. When these
    > # parameters are used, the station is assumed to be deployed with a NFC tag
    > # that includes the matching NFC password token (e.g., written based on the
    > # NDEF record from nfc_pw_token).
    > #
    > #wps_nfc_dev_pw_id: Device Password ID (16..65535)
    > #wps_nfc_dh_pubkey: Hexdump of DH Public Key
    > #wps_nfc_dh_privkey: Hexdump of DH Private Key
    > #wps_nfc_dev_pw: Hexdump of Device Password
    >
    > # Priority for the networks added through WPS
    > # This priority value will be set to each network profile that is added
    > # by executing the WPS protocol.
    > #wps_priority=0
    >
    223a287,298
    > # Automatic scan
    > # This is an optional set of parameters for automatic scanning
    > # within an interface in following format:
    > #autoscan=<autoscan module name>:<module parameters>
    > # autoscan is like bgscan but on disconnected or inactive state.
    > # For instance, on exponential module parameters would be <base>:<limit>
    > #autoscan=exponential:3:300
    > # Which means a delay between scans on a base exponential of 3,
    > # up to the limit of 300 seconds (3, 9, 27 ... 300)
    > # For periodic module, parameters would be <fixed interval>
    > #autoscan=periodic:30
    > # So a delay of 30 seconds will be applied between each scan
    229a305,399
    > # Password (and passphrase, etc.) backend for external storage
    > # format: <backend name>[:<optional backend parameters>]
    > #ext_password_backend=test:pw1=password|pw2=testing
    >
    >
    > # Disable P2P functionality
    > # p2p_disabled=1
    >
    > # Timeout in seconds to detect STA inactivity (default: 300 seconds)
    > #
    > # This timeout value is used in P2P GO mode to clean up
    > # inactive stations.
    > #p2p_go_max_inactivity=300
    >
    > # Passphrase length (8..63) for P2P GO
    > #
    > # This parameter controls the length of the random passphrase that is
    > # generated at the GO. Default: 8.
    > #p2p_passphrase_len=8
    >
    > # Extra delay between concurrent P2P search iterations
    > #
    > # This value adds extra delay in milliseconds between concurrent search
    > # iterations to make p2p_find friendlier to concurrent operations by avoiding
    > # it from taking 100% of radio resources. The default value is 500 ms.
    > #p2p_search_delay=500
    >
    > # Opportunistic Key Caching (also known as Proactive Key Caching) default
    > # This parameter can be used to set the default behavior for the
    > # proactive_key_caching parameter. By default, OKC is disabled unless enabled
    > # with the global okc=1 parameter or with the per-network
    > # proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but
    > # can be disabled with per-network proactive_key_caching=0 parameter.
    > #okc=0
    >
    > # Protected Management Frames default
    > # This parameter can be used to set the default behavior for the ieee80211w
    > # parameter. By default, PMF is disabled unless enabled with the global pmf=1/2
    > # parameter or with the per-network ieee80211w=1/2 parameter. With pmf=1/2, PMF
    > # is enabled/required by default, but can be disabled with the per-network
    > # ieee80211w parameter.
    > #pmf=0
    >
    > # Enabled SAE finite cyclic groups in preference order
    > # By default (if this parameter is not set), the mandatory group 19 (ECC group
    > # defined over a 256-bit prime order field) is preferred, but other groups are
    > # also enabled. If this parameter is set, the groups will be tried in the
    > # indicated order. The group values are listed in the IANA registry:
    > # http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
    > #sae_groups=21 20 19 26 25
    >
    > # Default value for DTIM period (if not overridden in network block)
    > #dtim_period=2
    >
    > # Default value for Beacon interval (if not overridden in network block)
    > #beacon_int=100
    >
    > # Additional vendor specific elements for Beacon and Probe Response frames
    > # This parameter can be used to add additional vendor specific element(s) into
    > # the end of the Beacon and Probe Response frames. The format for these
    > # element(s) is a hexdump of the raw information elements (id+len+payload for
    > # one or more elements). This is used in AP and P2P GO modes.
    > #ap_vendor_elements=dd0411223301
    >
    > # Ignore scan results older than request
    > #
    > # The driver may have a cache of scan results that makes it return
    > # information that is older than our scan trigger. This parameter can
    > # be used to configure such old information to be ignored instead of
    > # allowing it to update the internal BSS table.
    > #ignore_old_scan_res=0
    >
    > # scan_cur_freq: Whether to scan only the current frequency
    > # 0:  Scan all available frequencies. (Default)
    > # 1:  Scan current operating frequency if another VIF on the same radio
    > #     is already associated.
    >
    > # MAC address policy default
    > # 0 = use permanent MAC address
    > # 1 = use random MAC address for each ESS connection
    > # 2 = like 1, but maintain OUI (with local admin bit set)
    > #
    > # By default, permanent MAC address is used unless policy is changed by
    > # the per-network mac_addr parameter. Global mac_addr=1 can be used to
    > # change this default behavior.
    > #mac_addr=0
    >
    > # Lifetime of random MAC address in seconds (default: 60)
    > #rand_addr_lifetime=60
    >
    > # MAC address policy for pre-association operations (scanning, ANQP)
    > # 0 = use permanent MAC address
    > # 1 = use random MAC address
    > # 2 = like 1, but maintain OUI (with local admin bit set)
    > #preassoc_mac_addr=0
    242,246c412,418
    < # Home Realm for Interworking
    < #home_realm=example.com
    <
    < # Username for Interworking network selection
    < #home_username=user
    ---
    > # Automatic network selection behavior
    > # 0 = do not automatically go through Interworking network selection
    > #     (i.e., require explicit interworking_select command for this; default)
    > # 1 = perform Interworking network selection if one or more
    > #     credentials have been configured and scan did not find a
    > #     matching network block
    > #auto_interworking=0
    248,255c420,595
    < # Password for Interworking network selection
    < #home_password=secret
    <
    < # CA certificate for Interworking network selection
    < #home_ca_cert=/etc/cert/ca.pem
    <
    < # IMSI in <MCC> | <MNC> | '-' | <MSIN> format
    < #home_imsi=232010000000000
    ---
    > # credential block
    > #
    > # Each credential used for automatic network selection is configured as a set
    > # of parameters that are compared to the information advertised by the APs when
    > # interworking_select and interworking_connect commands are used.
    > #
    > # credential fields:
    > #
    > # temporary: Whether this credential is temporary and not to be saved
    > #
    > # priority: Priority group
    > #     By default, all networks and credentials get the same priority group
    > #     (0). This field can be used to give higher priority for credentials
    > #     (and similarly in struct wpa_ssid for network blocks) to change the
    > #     Interworking automatic networking selection behavior. The matching
    > #     network (based on either an enabled network block or a credential)
    > #     with the highest priority value will be selected.
    > #
    > # pcsc: Use PC/SC and SIM/USIM card
    > #
    > # realm: Home Realm for Interworking
    > #
    > # username: Username for Interworking network selection
    > #
    > # password: Password for Interworking network selection
    > #
    > # ca_cert: CA certificate for Interworking network selection
    > #
    > # client_cert: File path to client certificate file (PEM/DER)
    > #     This field is used with Interworking networking selection for a case
    > #     where client certificate/private key is used for authentication
    > #     (EAP-TLS). Full path to the file should be used since working
    > #     directory may change when wpa_supplicant is run in the background.
    > #
    > #     Alternatively, a named configuration blob can be used by setting
    > #     this to blob://blob_name.
    > #
    > # private_key: File path to client private key file (PEM/DER/PFX)
    > #     When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
    > #     commented out. Both the private key and certificate will be read
    > #     from the PKCS#12 file in this case. Full path to the file should be
    > #     used since working directory may change when wpa_supplicant is run
    > #     in the background.
    > #
    > #     Windows certificate store can be used by leaving client_cert out and
    > #     configuring private_key in one of the following formats:
    > #
    > #     cert://substring_to_match
    > #
    > #     hash://certificate_thumbprint_in_hex
    > #
    > #     For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
    > #
    > #     Note that when running wpa_supplicant as an application, the user
    > #     certificate store (My user account) is used, whereas computer store
    > #     (Computer account) is used when running wpasvc as a service.
    > #
    > #     Alternatively, a named configuration blob can be used by setting
    > #     this to blob://blob_name.
    > #
    > # private_key_passwd: Password for private key file
    > #
    > # imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format
    > #
    > # milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN>
    > #     format
    > #
    > # domain: Home service provider FQDN(s)
    > #     This is used to compare against the Domain Name List to figure out
    > #     whether the AP is operated by the Home SP. Multiple domain entries can
    > #     be used to configure alternative FQDNs that will be considered home
    > #     networks.
    > #
    > # roaming_consortium: Roaming Consortium OI
    > #     If roaming_consortium_len is non-zero, this field contains the
    > #     Roaming Consortium OI that can be used to determine which access
    > #     points support authentication with this credential. This is an
    > #     alternative to the use of the realm parameter. When using Roaming
    > #     Consortium to match the network, the EAP parameters need to be
    > #     pre-configured with the credential since the NAI Realm information
    > #     may not be available or fetched.
    > #
    > # eap: Pre-configured EAP method
    > #     This optional field can be used to specify which EAP method will be
    > #     used with this credential. If not set, the EAP method is selected
    > #     automatically based on ANQP information (e.g., NAI Realm).
    > #
    > # phase1: Pre-configure Phase 1 (outer authentication) parameters
    > #     This optional field is used with like the 'eap' parameter.
    > #
    > # phase2: Pre-configure Phase 2 (inner authentication) parameters
    > #     This optional field is used with like the 'eap' parameter.
    > #
    > # excluded_ssid: Excluded SSID
    > #     This optional field can be used to excluded specific SSID(s) from
    > #     matching with the network. Multiple entries can be used to specify more
    > #     than one SSID.
    > #
    > # roaming_partner: Roaming partner information
    > #     This optional field can be used to configure preferences between roaming
    > #     partners. The field is a string in following format:
    > #     <FQDN>,<0/1 exact match>,<priority>,<* or country code>
    > #     (non-exact match means any subdomain matches the entry; priority is in
    > #     0..255 range with 0 being the highest priority)
    > #
    > # update_identifier: PPS MO ID
    > #     (Hotspot 2.0 PerProviderSubscription/UpdateIdentifier)
    > #
    > # provisioning_sp: FQDN of the SP that provisioned the credential
    > #     This optional field can be used to keep track of the SP that provisioned
    > #     the credential to find the PPS MO (./Wi-Fi/<provisioning_sp>).
    > #
    > # Minimum backhaul threshold (PPS/<X+>/Policy/MinBackhauldThreshold/*)
    > #     These fields can be used to specify minimum download/upload backhaul
    > #     bandwidth that is preferred for the credential. This constraint is
    > #     ignored if the AP does not advertise WAN Metrics information or if the
    > #     limit would prevent any connection. Values are in kilobits per second.
    > # min_dl_bandwidth_home
    > # min_ul_bandwidth_home
    > # min_dl_bandwidth_roaming
    > # min_ul_bandwidth_roaming
    > #
    > # max_bss_load: Maximum BSS Load Channel Utilization (1..255)
    > #     (PPS/<X+>/Policy/MaximumBSSLoadValue)
    > #     This value is used as the maximum channel utilization for network
    > #     selection purposes for home networks. If the AP does not advertise
    > #     BSS Load or if the limit would prevent any connection, this constraint
    > #     will be ignored.
    > #
    > # req_conn_capab: Required connection capability
    > #     (PPS/<X+>/Policy/RequiredProtoPortTuple)
    > #     This value is used to configure set of required protocol/port pairs that
    > #     a roaming network shall support (include explicitly in Connection
    > #     Capability ANQP element). This constraint is ignored if the AP does not
    > #     advertise Connection Capability or if this constraint would prevent any
    > #     network connection. This policy is not used in home networks.
    > #     Format: <protocol>[:<comma-separated list of ports]
    > #     Multiple entries can be used to list multiple requirements.
    > #     For example, number of common TCP protocols:
    > #     req_conn_capab=6,22,80,443
    > #     For example, IPSec/IKE:
    > #     req_conn_capab=17:500
    > #     req_conn_capab=50
    > #
    > # ocsp: Whether to use/require OCSP to check server certificate
    > #     0 = do not use OCSP stapling (TLS certificate status extension)
    > #     1 = try to use OCSP stapling, but not require response
    > #     2 = require valid OCSP stapling response
    > #
    > # sim_num: Identifier for which SIM to use in multi-SIM devices
    > #
    > # for example:
    > #
    > #cred={
    > #     realm="example.com"
    > #     username="user@example.com"
    > #     password="password"
    > #     ca_cert="/etc/wpa_supplicant/ca.pem"
    > #     domain="example.com"
    > #}
    > #
    > #cred={
    > #     imsi="310026-000000000"
    > #     milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82"
    > #}
    > #
    > #cred={
    > #     realm="example.com"
    > #     username="user"
    > #     password="password"
    > #     ca_cert="/etc/wpa_supplicant/ca.pem"
    > #     domain="example.com"
    > #     roaming_consortium=223344
    > #     eap=TTLS
    > #     phase2="auth=MSCHAPV2"
    > #}
    257,258c597,598
    < # Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN> format
    < #home_milenage=90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82581:000000000123
    ---
    > # Hotspot 2.0
    > # hs20=1
    277,278c617,620
    < # ssid: SSID (mandatory); either as an ASCII string with double quotation or
    < #     as hex string; network name
    ---
    > # ssid: SSID (mandatory); network name in one of the optional formats:
    > #     - an ASCII string with double quotation
    > #     - a hex string (two characters per octet of SSID)
    > #     - a printf-escaped ASCII string P"<escaped string>"
    305,307c647,650
    < # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
    < # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). WPA-None requires
    < # following network block options:
    ---
    > # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) and
    > # WPA-PSK (with proto=RSN). In addition, key_mgmt=WPA-NONE (fixed group key
    > # TKIP/CCMP) is available for backwards compatibility, but its use is
    > # deprecated. WPA-None requires following network block options:
    328a672,697
    > # This can also be set on the outside of the network block. In this case,
    > # it limits the frequencies that will be scanned.
    > #
    > # bgscan: Background scanning
    > # wpa_supplicant behavior for background scanning can be specified by
    > # configuring a bgscan module. These modules are responsible for requesting
    > # background scans for the purpose of roaming within an ESS (i.e., within a
    > # single network block with all the APs using the same SSID). The bgscan
    > # parameter uses following format: "<bgscan module name>:<module parameters>"
    > # Following bgscan modules are available:
    > # simple - Periodic background scans based on signal strength
    > # bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>:
    > # <long interval>"
    > # bgscan="simple:30:-45:300"
    > # learn - Learn channels used by the network and try to avoid bgscans on other
    > # channels (experimental)
    > # bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>:
    > # <long interval>[:<database file name>]"
    > # bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan"
    > # Explicitly disable bgscan by setting
    > # bgscan=""
    > #
    > # This option can also be set outside of all network blocks for the bgscan
    > # parameter to apply for all the networks that have no specific bgscan
    > # parameter.
    > #
    343a713,722
    > # ieee80211w: whether management frame protection is enabled
    > # 0 = disabled (default unless changed with the global pmf parameter)
    > # 1 = optional
    > # 2 = required
    > # The most common configuration options for this based on the PMF (protected
    > # management frames) certification program are:
    > # PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256
    > # PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256
    > # (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used)
    > #
    369c748,749
    < # 8 and 63 characters (inclusive).
    ---
    > # 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
    > # be used to indicate that the PSK/passphrase is stored in external storage.
    375a756,760
    > # mem_only_psk: Whether to keep PSK/passphrase only in memory
    > # 0 = allow psk/passphrase to be stored to the configuration file
    > # 1 = do not store psk/passphrase to the configuration file
    > #mem_only_psk=0
    > #
    381,382c766,775
    < # Note: When using wired authentication, eapol_flags must be set to 0 for the
    < # authentication to be completed successfully.
    ---
    > # Note: When using wired authentication (including macsec_qca driver),
    > # eapol_flags must be set to 0 for the authentication to be completed
    > # successfully.
    > #
    > # macsec_policy: IEEE 802.1X/MACsec options
    > # This determines how sessions are secured with MACsec. It is currently
    > # applicable only when using the macsec_qca driver interface.
    > # 0: MACsec not in use (default)
    > # 1: MACsec enabled - Should secure, accept key server's advice to
    > #    determine whether to use a secure session or not.
    392c785
    < # 0 = disabled (default)
    ---
    > # 0 = disabled (default unless changed with the global okc parameter)
    430c823,824
    < #     identity, e.g., EAP-TTLS)
    ---
    > #     identity, e.g., EAP-TTLS). This field can also be used with
    > #     EAP-SIM/AKA/AKA' to store the pseudonym identity.
    438c832,833
    < #     variable length PSK.
    ---
    > #     variable length PSK. ext:<name of external password field> format can
    > #     be used to indicate that the password is stored in external storage.
    501a897,900
    > #     Note: Since this is a substring match, this cannot be used securily to
    > #     do a suffix match against a possible domain name in the CN entry. For
    > #     such a use case, domain_suffix_match or domain_match should be used
    > #     instead.
    509a909,932
    > # domain_suffix_match: Constraint for server domain name. If set, this FQDN is
    > #     used as a suffix match requirement for the AAAserver certificate in
    > #     SubjectAltName dNSName element(s). If a matching dNSName is found, this
    > #     constraint is met. If no dNSName values are present, this constraint is
    > #     matched against SubjectName CN using same suffix match comparison.
    > #
    > #     Suffix match here means that the host/domain name is compared one label
    > #     at a time starting from the top-level domain and all the labels in
    > #     domain_suffix_match shall be included in the certificate. The
    > #     certificate may include additional sub-level labels in addition to the
    > #     required labels.
    > #
    > #     For example, domain_suffix_match=example.com would match
    > #     test.example.com but would not match test-example.com.
    > # domain_match: Constraint for server domain name
    > #     If set, this FQDN is used as a full match requirement for the
    > #     server certificate in SubjectAltName dNSName element(s). If a
    > #     matching dNSName is found, this constraint is met. If no dNSName
    > #     values are present, this constraint is matched against SubjectName CN
    > #     using same full match comparison. This behavior is similar to
    > #     domain_suffix_match, but has the requirement of a full match, i.e.,
    > #     no subdomains or wildcard matches are allowed. Case-insensitive
    > #     comparison is used, so "Example.com" matches "example.com", but would
    > #     not match "test.Example.com".
    537a961,970
    > #
    > #     For wired IEEE 802.1X authentication, "allow_canned_success=1" can be
    > #     used to configure a mode that allows EAP-Success (and EAP-Failure)
    > #     without going through authentication step. Some switches use such
    > #     sequence when forcing the port to be authorized/unauthorized or as a
    > #     fallback option if the authentication server is unreachable. By default,
    > #     wpa_supplicant discards such frames to protect against potential attacks
    > #     by rogue devices, but this option can be used to disable that protection
    > #     for cases where the server/authenticator does not need to be
    > #     authenticated.
    540c973,998
    < #     "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
    ---
    > #     "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS). "mschapv2_retry=0" can be
    > #     used to disable MSCHAPv2 password retry in authentication failure cases.
    > #
    > # TLS-based methods can use the following parameters to control TLS behavior
    > # (these are normally in the phase1 parameter, but can be used also in the
    > # phase2 parameter when EAP-TLS is used within the inner tunnel):
    > # tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the
    > #     TLS library, these may be disabled by default to enforce stronger
    > #     security)
    > # tls_disable_time_checks=1 - ignore certificate validity time (this requests
    > #     the TLS library to accept certificates even if they are not currently
    > #     valid, i.e., have expired or have not yet become valid; this should be
    > #     used only for testing purposes)
    > # tls_disable_session_ticket=1 - disable TLS Session Ticket extension
    > # tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used
    > #     Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS
    > #     as a workaround for broken authentication server implementations unless
    > #     EAP workarounds are disabled with eap_workaround=0.
    > #     For EAP-FAST, this must be set to 0 (or left unconfigured for the
    > #     default value to be used automatically).
    > # tls_disable_tlsv1_0=1 - disable use of TLSv1.0
    > # tls_disable_tlsv1_1=1 - disable use of TLSv1.1 (a workaround for AAA servers
    > #     that have issues interoperating with updated TLS version)
    > # tls_disable_tlsv1_2=1 - disable use of TLSv1.2 (a workaround for AAA servers
    > #     that have issues interoperating with updated TLS version)
    > #
    553,555c1011,1016
    < #     authentication server certificate.
    < # altsubject_match2: Substring to be matched against the alternative subject
    < #     name of the authentication server certificate.
    ---
    > #     authentication server certificate. See subject_match for more details.
    > # altsubject_match2: Semicolon separated string of entries to be matched
    > #     against the alternative subject name of the authentication server
    > #     certificate. See altsubject_match documentation for more details.
    > # domain_suffix_match2: Constraint for server domain name. See
    > #     domain_suffix_match for more details.
    563a1025,1035
    > # ocsp: Whether to use/require OCSP to check server certificate
    > #     0 = do not use OCSP stapling (TLS certificate status extension)
    > #     1 = try to use OCSP stapling, but not require response
    > #     2 = require valid OCSP stapling response
    > #
    > # openssl_ciphers: OpenSSL specific cipher configuration
    > #     This can be used to override the global openssl_ciphers configuration
    > #     parameter (see above).
    > #
    > # erp: Whether EAP Re-authentication Protocol (ERP) is enabled
    > #
    589a1062,1169
    > # Station inactivity limit
    > #
    > # If a station does not send anything in ap_max_inactivity seconds, an
    > # empty data frame is sent to it in order to verify whether it is
    > # still in range. If this frame is not ACKed, the station will be
    > # disassociated and then deauthenticated. This feature is used to
    > # clear station table of old entries when the STAs move out of the
    > # range.
    > #
    > # The station can associate again with the AP if it is still in range;
    > # this inactivity poll is just used as a nicer way of verifying
    > # inactivity; i.e., client will not report broken connection because
    > # disassociation frame is not sent immediately without first polling
    > # the STA with a data frame.
    > # default: 300 (i.e., 5 minutes)
    > #ap_max_inactivity=300
    >
    > # DTIM period in Beacon intervals for AP mode (default: 2)
    > #dtim_period=2
    >
    > # Beacon interval (default: 100 TU)
    > #beacon_int=100
    >
    > # MAC address policy
    > # 0 = use permanent MAC address
    > # 1 = use random MAC address for each ESS connection
    > # 2 = like 1, but maintain OUI (with local admin bit set)
    > #mac_addr=0
    >
    > # disable_ht: Whether HT (802.11n) should be disabled.
    > # 0 = HT enabled (if AP supports it)
    > # 1 = HT disabled
    > #
    > # disable_ht40: Whether HT-40 (802.11n) should be disabled.
    > # 0 = HT-40 enabled (if AP supports it)
    > # 1 = HT-40 disabled
    > #
    > # disable_sgi: Whether SGI (short guard interval) should be disabled.
    > # 0 = SGI enabled (if AP supports it)
    > # 1 = SGI disabled
    > #
    > # disable_ldpc: Whether LDPC should be disabled.
    > # 0 = LDPC enabled (if AP supports it)
    > # 1 = LDPC disabled
    > #
    > # ht40_intolerant: Whether 40 MHz intolerant should be indicated.
    > # 0 = 40 MHz tolerant (default)
    > # 1 = 40 MHz intolerant
    > #
    > # ht_mcs:  Configure allowed MCS rates.
    > #  Parsed as an array of bytes, in base-16 (ascii-hex)
    > # ht_mcs=""                                   // Use all available (default)
    > # ht_mcs="0xff 00 00 00 00 00 00 00 00 00 "   // Use MCS 0-7 only
    > # ht_mcs="0xff ff 00 00 00 00 00 00 00 00 "   // Use MCS 0-15 only
    > #
    > # disable_max_amsdu:  Whether MAX_AMSDU should be disabled.
    > # -1 = Do not make any changes.
    > # 0  = Enable MAX-AMSDU if hardware supports it.
    > # 1  = Disable AMSDU
    > #
    > # ampdu_factor: Maximum A-MPDU Length Exponent
    > # Value: 0-3, see 7.3.2.56.3 in IEEE Std 802.11n-2009.
    > #
    > # ampdu_density:  Allow overriding AMPDU density configuration.
    > #  Treated as hint by the kernel.
    > # -1 = Do not make any changes.
    > # 0-3 = Set AMPDU density (aka factor) to specified value.
    >
    > # disable_vht: Whether VHT should be disabled.
    > # 0 = VHT enabled (if AP supports it)
    > # 1 = VHT disabled
    > #
    > # vht_capa: VHT capabilities to set in the override
    > # vht_capa_mask: mask of VHT capabilities
    > #
    > # vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8
    > # vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8
    > #  0: MCS 0-7
    > #  1: MCS 0-8
    > #  2: MCS 0-9
    > #  3: not supported
    >
    > ##### Fast Session Transfer (FST) support #####################################
    > #
    > # The options in this section are only available when the build configuration
    > # option CONFIG_FST is set while compiling hostapd. They allow this interface
    > # to be a part of FST setup.
    > #
    > # FST is the transfer of a session from a channel to another channel, in the
    > # same or different frequency bands.
    > #
    > # For detals, see IEEE Std 802.11ad-2012.
    >
    > # Identifier of an FST Group  the interface belongs to.
    > #fst_group_id=bond0
    >
    > # Interface priority within the FST Group.
    > # Announcing a higher priority for an interface means declaring it more
    > # preferable for FST switch.
    > # fst_priority is in 1..255 range with 1 being the lowest priority.
    > #fst_priority=100
    >
    > # Default LLT value for this interface in milliseconds. The value used in case
    > # no value provided during session setup. Default is 50 msec.
    > # fst_llt is in 1..4294967 range (due to spec limitation, see 10.32.2.2
    > # Transitioning between states).
    > #fst_llt=100
    >
    836c1416,1428
    < # IBSS/ad-hoc network with WPA-None/TKIP.
    ---
    > # IBSS/ad-hoc network with RSN
    > # network={
    > #     ssid="ibss-rsn"
    > #     key_mgmt=WPA-PSK
    > #     proto=RSN
    > #     psk="12345678"
    > #     mode=1
    > #     frequency=2412
    > #     pairwise=CCMP
    > #     group=CCMP
    > # }
    >
    > # IBSS/ad-hoc network with WPA-None/TKIP (deprecated)
    847a1440,1456
    > # open mesh network
    > # network={
    > #     ssid="test mesh"
    > #     mode=5
    > #     frequency=2437
    > #     key_mgmt=NONE
    > # }
    >
    > # secure (SAE + AMPE) network
    > # network={
    > #     ssid="secure mesh"
    > #     mode=5
    > #     frequency=2437
    > #     key_mgmt=SAE
    > #     psk="very secret passphrase"
    > # }
    >
    922a1532,1538
    > # Example configuration blacklisting two APs - these will be ignored
    > # for this network.
    > # network={
    > #     ssid="example"
    > #     psk="very secret passphrase"
    > #     bssid_blacklist=02:11:22:33:44:55 02:22:aa:44:55:66
    > # }
    924,935c1540,1566
    < network={
    <     psk="URYTECFE"
    <     priority=1
    <     scan_ssid=0
    <     ssid="SKY414B9"
    < }
    < # reading passphrase from stdin
    < network={
    <       ssid="SKY414B9"
    <       #psk="URYTECFE"
    <       psk=f12d9b790efae3d6733c6227279a9bbf3e2a21b37f935cd95952819e16c4eb96
    < }
    ---
    > # Example configuration limiting AP selection to a specific set of APs;
    > # any other AP not matching the masked address will be ignored.
    > # network={
    > #     ssid="example"
    > #     psk="very secret passphrase"
    > #     bssid_whitelist=02:55:ae:bc:00:00/ff:ff:ff:ff:00:00 00:00:77:66:55:44/00:00:ff:ff:ff:ff
    > # }
    >
    > # Example config file that will only scan on channel 36.
    > freq_list=5180
    > # network={
    > #     key_mgmt=NONE
    > # }
    >
    >
    > # Example MACsec configuration
    > #network={
    > #     key_mgmt=IEEE8021X
    > #     eap=TTLS
    > #     phase2="auth=PAP"
    > #     anonymous_identity="anonymous@example.com"
    > #     identity="user@example.com"
    > #     password="secretr"
    > #     ca_cert="/etc/cert/ca.pem"
    > #     eapol_flags=0
    > #     macsec_policy=1
    > #}
    [root@localhost pawel]#
  • Helpful post
    #14
    Epic
    Level 29  
    Plik wpa_supplicant.conf.rpmnew możesz usunąć. Plik wpa_supplicant.conf wystarczy jak wyczyścisz z wpisów uprzednio zabijając procesy programu.
  • #15
    kopawel
    Level 14  
    Sorry ale ja wciąż nie wiem jak mam zastosowaą komendę
    #kill 'identyfikator procesu'

    Skad mam wziaźć identyfikator procesu ?

    Pliku wpa_supplicant.conf.rpmnew nie mogę usunąć przez brak uprawnień. Zmieniam uprawnienia w opcjach właściwości pliku, klikam OK, a uprawnienia i tak wracają do tych wcześniejszych.
    Pliku wpa_supplicant.conf nie mogę otworzyć np w kwrite bo niby brak uprawnień...czy mam sie zalogować na root-a czy co ?

    Dodano po 25 [minuty]:

    Usunąłem plik wpa_supplicant.conf.rpmnew przez terminal komendą
    Code:
     rm /etc/wpa_supplicant.conf.rpmnew


    Próbuje jeszcze dostać sie do wpa_supplicant.conf.....nie za bardzo wychodzi...
  • Helpful post
    #16
    Epic
    Level 29  
    root ze względów bezpieczeństwa nie może się logować do GUI. Możesz użyć "kdesu kwrite". Ale lepiej edytować plik w jednym z konsolowych edytorów, choćby nano.

    Code:
    nano -w /etc/wpa_supplicant.conf


    Identyfikator procesu (PID) bierzesz z monitora systemowego albo:
    Code:
    [root@localhost pawel]# ps -eF | grep wpa
    
    root      3553     1  0  4748  6260   1 08:20 ?        00:00:06 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid
    root      7626     1  0  4747  3144   2 08:21 ?        00:00:48 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
    root     22239 22202  0  7396  2268   0 15:10 pts/2    00:00:00 grep --color wpa

    pierwsza kolumna to użytkownik druga to właśnie identyfikator procesu, zmienia się przy każdym uruchomieniu procesu.

    Do usuwania również korzystaj z konsoli, wszelkie programy graficzne(menadżer plików itp) nie mają odpowiednich uprawnień do takich operacji jak usuwanie/edycja wpa_supplicant.conf
  • #17
    kopawel
    Level 14  
    Nie wiem czy dobrze to zrobiłem, wpisując te 4 cyfry za komendą kill, bo niby zabija jakiś proces ale tworzą sie w te miejsce inne....

    Code:
    [root@localhost pawel]# ps -eF | grep wpa
    
    root      3525     1  0  4748  6412   1 20:06 ?        00:00:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid
    root      7154     1  0  4747  3220   0 20:07 ?        00:00:02 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
    root     32077 26260  0  7396  2176   2 20:28 pts/2    00:00:00 grep --color wpa
    [root@localhost pawel]# kill 3525
    [root@localhost pawel]# ps -eF | grep wpa
    root      1394     1  0  4748  6452   3 20:30 ?        00:00:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid
    root      1397 26260  0  7395  2288   0 20:30 pts/2    00:00:00 grep --color wpa
    root      7154     1  0  4747  3220   1 20:07 ?        00:00:02 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
    [root@localhost pawel]# kill 7154
    [root@localhost pawel]# ps -eF | grep wpa                                                                                                           
    root      1394     1  0  4748  6452   0 20:30 ?        00:00:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid                                                                                                                                                   
    root      1952 26260  0  7395  2272   2 20:31 pts/2    00:00:00 grep --color wpa
    [root@localhost pawel]# kill 1394
    [root@localhost pawel]# ps -eF | grep wpa                                                                                                           
    root      2232     1  0  4748  6432   0 20:31 ?        00:00:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid                                                                                                                                                   
    root      2235 26260  0  7395  2240   0 20:31 pts/2    00:00:00 grep --color wpa
    [root@localhost pawel]#             


    Dodano po 2 [minuty]:

    Czyli mam usuwać wszystkie jak leci, nawet te co pojawią się na nowo ? Nie będzie to trwało w nieskończoność ?

    Dodano po 2 [minuty]:

    Komenda z nano niestety nie działa:

    Code:
    [root@localhost pawel]# 
    
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]# nano -w /etc/wpa_supplicant.conf
    bash: nano: nie znaleziono polecenia
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]#


    Zadziałalo
    Code:

    [root@localhost pawel]# kwrite /etc/wpa_supplicant.conf

    Otworzył sie plik...
  • Helpful post
    #18
    Epic
    Level 29  
    Najpewniej winny jest NetworkManager, który uruchamia od nowa wpa_supplicant. Możesz go potraktować podobnie jak wyżej( ...grep NetworkManager). Ale najpewniej da się go też wyłączyć klikając w okienkach lub choćby dekonfigurując sieć wifi.

    wpa_supplicant.conf wyczyściłeś?
  • #19
    kopawel
    Level 14  
    Jedyny wpis jaki znalazłem to :
    Code:
    network={
    
        psk="URYTECFE"
        priority=1
        scan_ssid=0
        ssid="SKY414B9"
    }
    # reading passphrase from stdin
    network={
       ssid="SKY414B9"
       #psk="URYTECFE"
       psk=f12d9b790efae3d6733c6227279a9bbf3e2a21b37f935cd95952819e16c4eb96
    }


    Usunąłem go i zapisałem plik...działą WiFI :D:D.

    Dzieki...ale czy jeszcze coś mam zrobić ?
    Czy jeżeli bede chaiał sie teraz połączyć z siecią SKY414B9 to bede miał problemy ??

    I dlaczego wyskakuje mi :
    ''Nie udało się podziękować użytkownikowi Podaruj punkty! '' ??
  • #20
    Epic
    Level 29  
    No i git. Najpewniej z powodu aktualizacji zostały dodane do pliku dodatkowe wpisy tej samej sieci(ssid) i gryzły się. Przez co wifi nie działało.

    Jeżeli wifi łączy się poprawnie, również przy uruchomianiu systemu nic już nie musisz robić.
  • #21
    kopawel
    Level 14  
    No niestety po zrrestartowaniu laptopa znów nie łączy mnie w WiFi...:/....komedia jakaś...

    Dodano po 1 [minuty]:

    Tak wygląda mój plik wpa_supplicant.conf
    Code:
    ##### Example wpa_supplicant configuration file ###############################
    
    #
    # This file describes configuration file format and lists all available option.
    # Please also take a look at simpler configuration examples in 'examples'
    # subdirectory.
    #
    # Empty lines and lines starting with # are ignored

    # NOTE! This file may contain password information and should probably be made
    # readable only by root user on multiuser systems.

    # Note: All file paths in this configuration file should use full (absolute,
    # not relative to working directory) path in order to allow working directory
    # to be changed. This can happen if wpa_supplicant is run in the background.

    # Whether to allow wpa_supplicant to update (overwrite) configuration
    #
    # This option can be used to allow wpa_supplicant to overwrite configuration
    # file whenever configuration is changed (e.g., new network block is added with
    # wpa_cli or wpa_gui, or a password is changed). This is required for
    # wpa_cli/wpa_gui to be able to store the configuration changes permanently.
    # Please note that overwriting configuration file will remove the comments from
    # it.
    #update_config=1

    # global configuration (shared by all network blocks)
    #
    # Parameters for the control interface. If this is specified, wpa_supplicant
    # will open a control interface that is available for external programs to
    # manage wpa_supplicant. The meaning of this string depends on which control
    # interface mechanism is used. For all cases, the existence of this parameter
    # in configuration is used to determine whether the control interface is
    # enabled.
    #
    # For UNIX domain sockets (default on Linux and BSD): This is a directory that
    # will be created for UNIX domain sockets for listening to requests from
    # external programs (CLI/GUI, etc.) for status information and configuration.
    # The socket file will be named based on the interface name, so multiple
    # wpa_supplicant processes can be run at the same time if more than one
    # interface is used.
    # /var/run/wpa_supplicant is the recommended directory for sockets and by
    # default, wpa_cli will use it when trying to connect with wpa_supplicant.
    #
    # Access control for the control interface can be configured by setting the
    # directory to allow only members of a group to use sockets. This way, it is
    # possible to run wpa_supplicant as root (since it needs to change network
    # configuration and open raw sockets) and still allow GUI/CLI components to be
    # run as non-root users. However, since the control interface can be used to
    # change the network configuration, this access needs to be protected in many
    # cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
    # want to allow non-root users to use the control interface, add a new group
    # and change this value to match with that group. Add users that should have
    # control interface access to this group. If this variable is commented out or
    # not included in the configuration file, group will not be changed from the
    # value it got by default when the directory or socket was created.
    #
    # When configuring both the directory and group, use following format:
    # DIR=/var/run/wpa_supplicant GROUP=wheel
    # DIR=/var/run/wpa_supplicant GROUP=0
    # (group can be either group name or gid)
    #
    # For UDP connections (default on Windows): The value will be ignored. This
    # variable is just used to select that the control interface is to be created.
    # The value can be set to, e.g., udp (ctrl_interface=udp)
    #
    # For Windows Named Pipe: This value can be used to set the security descriptor
    # for controlling access to the control interface. Security descriptor can be
    # set using Security Descriptor String Format (see http://msdn.microsoft.com/
    # library/default.asp?url=/library/en-us/secauthz/security/
    # security_descriptor_string_format.asp). The descriptor string needs to be
    # prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
    # DACL (which will reject all connections). See README-Windows.txt for more
    # information about SDDL string format.
    #
    ctrl_interface=/var/run/wpa_supplicant

    # IEEE 802.1X/EAPOL version
    # wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
    # EAPOL version 2. However, there are many APs that do not handle the new
    # version number correctly (they seem to drop the frames completely). In order
    # to make wpa_supplicant interoperate with these APs, the version number is set
    # to 1 by default. This configuration value can be used to set it to the new
    # version (2).
    eapol_version=1

    # AP scanning/selection
    # By default, wpa_supplicant requests driver to perform AP scanning and then
    # uses the scan results to select a suitable AP. Another alternative is to
    # allow the driver to take care of AP scanning and selection and use
    # wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
    # information from the driver.
    # 1: wpa_supplicant initiates scanning and AP selection; if no APs matching to
    #    the currently enabled networks are found, a new network (IBSS or AP mode
    #    operation) may be initialized (if configured) (default)
    # 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
    #    parameters (e.g., WPA IE generation); this mode can also be used with
    #    non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
    #    APs (i.e., external program needs to control association). This mode must
    #    also be used when using wired Ethernet drivers.
    # 2: like 0, but associate with APs using security policy and SSID (but not
    #    BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
    #    enable operation with hidden SSIDs and optimized roaming; in this mode,
    #    the network blocks in the configuration file are tried one by one until
    #    the driver reports successful association; each network block should have
    #    explicit security policy (i.e., only one option in the lists) for
    #    key_mgmt, pairwise, group, proto variables
    # When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
    # created immediately regardless of scan results. ap_scan=1 mode will first try
    # to scan for existing networks and only if no matches with the enabled
    # networks are found, a new IBSS or AP mode network is created.
    ap_scan=1

    # EAP fast re-authentication
    # By default, fast re-authentication is enabled for all EAP methods that
    # support it. This variable can be used to disable fast re-authentication.
    # Normally, there is no need to disable this.
    fast_reauth=1

    # OpenSSL Engine support
    # These options can be used to load OpenSSL engines.
    # The two engines that are supported currently are shown below:
    # They are both from the opensc project (http://www.opensc.org/)
    # By default no engines are loaded.
    # make the opensc engine available
    #opensc_engine_path=/usr/lib/opensc/engine_opensc.so
    # make the pkcs11 engine available
    #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
    # configure the path to the pkcs11 module required by the pkcs11 engine
    #pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so

    # Dynamic EAP methods
    # If EAP methods were built dynamically as shared object files, they need to be
    # loaded here before being used in the network blocks. By default, EAP methods
    # are included statically in the build, so these lines are not needed
    #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
    #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so

    # Driver interface parameters
    # This field can be used to configure arbitrary driver interace parameters. The
    # format is specific to the selected driver interface. This field is not used
    # in most cases.
    #driver_param="field=value"

    # Country code
    # The ISO/IEC alpha2 country code for the country in which this device is
    # currently operating.
    #country=US

    # Maximum lifetime for PMKSA in seconds; default 43200
    #dot11RSNAConfigPMKLifetime=43200
    # Threshold for reauthentication (percentage of PMK lifetime); default 70
    #dot11RSNAConfigPMKReauthThreshold=70
    # Timeout for security association negotiation in seconds; default 60
    #dot11RSNAConfigSATimeout=60

    # Wi-Fi Protected Setup (WPS) parameters

    # Universally Unique IDentifier (UUID; see RFC 4122) of the device
    # If not configured, UUID will be generated based on the local MAC address.
    #uuid=12345678-9abc-def0-1234-56789abcdef0

    # Device Name
    # User-friendly description of device; up to 32 octets encoded in UTF-8
    #device_name=Wireless Client

    # Manufacturer
    # The manufacturer of the device (up to 64 ASCII characters)
    #manufacturer=Company

    # Model Name
    # Model of the device (up to 32 ASCII characters)
    #model_name=cmodel

    # Model Number
    # Additional device description (up to 32 ASCII characters)
    #model_number=123

    # Serial Number
    # Serial number of the device (up to 32 characters)
    #serial_number=12345

    # Primary Device Type
    # Used format: <categ>-<OUI>-<subcateg>
    # categ = Category as an integer value
    # OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
    #       default WPS OUI
    # subcateg = OUI-specific Sub Category as an integer value
    # Examples:
    #   1-0050F204-1 (Computer / PC)
    #   1-0050F204-2 (Computer / Server)
    #   5-0050F204-1 (Storage / NAS)
    #   6-0050F204-1 (Network Infrastructure / AP)
    #device_type=1-0050F204-1

    # OS Version
    # 4-octet operating system version number (hex string)
    #os_version=01020300

    # Config Methods
    # List of the supported configuration methods
    # Available methods: usba ethernet label display ext_nfc_token int_nfc_token
    #   nfc_interface push_button keypad virtual_display physical_display
    #   virtual_push_button physical_push_button
    # For WSC 1.0:
    #config_methods=label display push_button keypad
    # For WSC 2.0:
    #config_methods=label virtual_display virtual_push_button keypad

    # Credential processing
    #   0 = process received credentials internally (default)
    #   1 = do not process received credentials; just pass them over ctrl_iface to
    #   external program(s)
    #   2 = process received credentials internally and pass them over ctrl_iface
    #   to external program(s)
    #wps_cred_processing=0

    # Maximum number of BSS entries to keep in memory
    # Default: 200
    # This can be used to limit memory use on the BSS entries (cached scan
    # results). A larger value may be needed in environments that have huge number
    # of APs when using ap_scan=1 mode.
    #bss_max_count=200


    # filter_ssids - SSID-based scan result filtering
    # 0 = do not filter scan results (default)
    # 1 = only include configured SSIDs in scan results/BSS table
    #filter_ssids=0


    # Interworking (IEEE 802.11u)

    # Enable Interworking
    # interworking=1

    # Homogenous ESS identifier
    # If this is set, scans will be used to request response only from BSSes
    # belonging to the specified Homogeneous ESS. This is used only if interworking
    # is enabled.
    # hessid=00:11:22:33:44:55

    # Home Realm for Interworking
    #home_realm=example.com

    # Username for Interworking network selection
    #home_username=user

    # Password for Interworking network selection
    #home_password=secret

    # CA certificate for Interworking network selection
    #home_ca_cert=/etc/cert/ca.pem

    # IMSI in <MCC> | <MNC> | '-' | <MSIN> format
    #home_imsi=232010000000000

    # Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN> format
    #home_milenage=90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82581:000000000123

    # network block
    #
    # Each network (usually AP's sharing the same SSID) is configured as a separate
    # block in this configuration file. The network blocks are in preference order
    # (the first match is used).
    #
    # network block fields:
    #
    # disabled:
    #   0 = this network can be used (default)
    #   1 = this network block is disabled (can be enabled through ctrl_iface,
    #       e.g., with wpa_cli or wpa_gui)
    #
    # id_str: Network identifier string for external scripts. This value is passed
    #   to external action script through wpa_cli as WPA_ID_STR environment
    #   variable to make it easier to do network specific configuration.
    #
    # ssid: SSID (mandatory); either as an ASCII string with double quotation or
    #   as hex string; network name
    #
    # scan_ssid:
    #   0 = do not scan this SSID with specific Probe Request frames (default)
    #   1 = scan with SSID-specific Probe Request frames (this can be used to
    #       find APs that do not accept broadcast SSID or use multiple SSIDs;
    #       this will add latency to scanning, so enable this only when needed)
    #
    # bssid: BSSID (optional); if set, this network block is used only when
    #   associating with the AP using the configured BSSID
    #
    # priority: priority group (integer)
    # By default, all networks will get same priority group (0). If some of the
    # networks are more desirable, this field can be used to change the order in
    # which wpa_supplicant goes through the networks when selecting a BSS. The
    # priority groups will be iterated in decreasing priority (i.e., the larger the
    # priority value, the sooner the network is matched against the scan results).
    # Within each priority group, networks will be selected based on security
    # policy, signal strength, etc.
    # Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
    # using this priority to select the order for scanning. Instead, they try the
    # networks in the order that used in the configuration file.
    #
    # mode: IEEE 802.11 operation mode
    # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
    # 1 = IBSS (ad-hoc, peer-to-peer)
    # 2 = AP (access point)
    # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
    # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). WPA-None requires
    # following network block options:
    # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
    # both), and psk must also be set.
    #
    # frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
    # 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
    # channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
    # In addition, this value is only used by the station that creates the IBSS. If
    # an IBSS network with the configured SSID is already present, the frequency of
    # the network will be used instead of this configured value.
    #
    # scan_freq: List of frequencies to scan
    # Space-separated list of frequencies in MHz to scan when searching for this
    # BSS. If the subset of channels used by the network is known, this option can
    # be used to optimize scanning to not occur on channels that the network does
    # not use. Example: scan_freq=2412 2437 2462
    #
    # freq_list: Array of allowed frequencies
    # Space-separated list of frequencies in MHz to allow for selecting the BSS. If
    # set, scan results that do not match any of the specified frequencies are not
    # considered when selecting a BSS.
    #
    # proto: list of accepted protocols
    # WPA = WPA/IEEE 802.11i/D3.0
    # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
    # If not set, this defaults to: WPA RSN
    #
    # key_mgmt: list of accepted authenticated key management protocols
    # WPA-PSK = WPA pre-shared key (this requires 'psk' field)
    # WPA-EAP = WPA using EAP authentication
    # IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
    #   generated WEP keys
    # NONE = WPA is not used; plaintext or static WEP could be used
    # WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
    # WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
    # If not set, this defaults to: WPA-PSK WPA-EAP
    #
    # auth_alg: list of allowed IEEE 802.11 authentication algorithms
    # OPEN = Open System authentication (required for WPA/WPA2)
    # SHARED = Shared Key authentication (requires static WEP keys)
    # LEAP = LEAP/Network EAP (only used with LEAP)
    # If not set, automatic selection is used (Open System with LEAP enabled if
    # LEAP is allowed as one of the EAP methods).
    #
    # pairwise: list of accepted pairwise (unicast) ciphers for WPA
    # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
    # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
    # NONE = Use only Group Keys (deprecated, should not be included if APs support
    #   pairwise keys)
    # If not set, this defaults to: CCMP TKIP
    #
    # group: list of accepted group (broadcast/multicast) ciphers for WPA
    # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
    # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
    # WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
    # WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
    # If not set, this defaults to: CCMP TKIP WEP104 WEP40
    #
    # psk: WPA preshared key; 256-bit pre-shared key
    # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
    # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
    # generated using the passphrase and SSID). ASCII passphrase must be between
    # 8 and 63 characters (inclusive).
    # This field is not needed, if WPA-EAP is used.
    # Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
    # from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
    # startup and reconfiguration time can be optimized by generating the PSK only
    # only when the passphrase or SSID has actually changed.
    #
    # eapol_flags: IEEE 802.1X/EAPOL options (bit field)
    # Dynamic WEP key required for non-WPA mode
    # bit0 (1): require dynamically generated unicast WEP key
    # bit1 (2): require dynamically generated broadcast WEP key
    #    (3 = require both keys; default)
    # Note: When using wired authentication, eapol_flags must be set to 0 for the
    # authentication to be completed successfully.
    #
    # mixed_cell: This option can be used to configure whether so called mixed
    # cells, i.e., networks that use both plaintext and encryption in the same
    # SSID, are allowed when selecting a BSS from scan results.
    # 0 = disabled (default)
    # 1 = enabled
    #
    # proactive_key_caching:
    # Enable/disable opportunistic PMKSA caching for WPA2.
    # 0 = disabled (default)
    # 1 = enabled
    #
    # wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
    # hex without quotation, e.g., 0102030405)
    # wep_tx_keyidx: Default WEP key index (TX) (0..3)
    #
    # peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
    # allowed. This is only used with RSN/WPA2.
    # 0 = disabled (default)
    # 1 = enabled
    #peerkey=1
    #
    # wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
    # enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
    #
    # Following fields are only used with internal EAP implementation.
    # eap: space-separated list of accepted EAP methods
    #   MD5 = EAP-MD5 (unsecure and does not generate keying material ->
    #         cannot be used with WPA; to be used as a Phase 2 method
    #         with EAP-PEAP or EAP-TTLS)
    #       MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
    #      as a Phase 2 method with EAP-PEAP or EAP-TTLS)
    #       OTP = EAP-OTP (cannot be used separately with WPA; to be used
    #      as a Phase 2 method with EAP-PEAP or EAP-TTLS)
    #       GTC = EAP-GTC (cannot be used separately with WPA; to be used
    #      as a Phase 2 method with EAP-PEAP or EAP-TTLS)
    #   TLS = EAP-TLS (client and server certificate)
    #   PEAP = EAP-PEAP (with tunnelled EAP authentication)
    #   TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
    #          authentication)
    #   If not set, all compiled in methods are allowed.
    #
    # identity: Identity string for EAP
    #   This field is also used to configure user NAI for
    #   EAP-PSK/PAX/SAKE/GPSK.
    # anonymous_identity: Anonymous identity string for EAP (to be used as the
    #   unencrypted identity with EAP types that support different tunnelled
    #   identity, e.g., EAP-TTLS)
    # password: Password string for EAP. This field can include either the
    #   plaintext password (using ASCII or hex string) or a NtPasswordHash
    #   (16-byte MD4 hash of password) in hash:<32 hex digits> format.
    #   NtPasswordHash can only be used when the password is for MSCHAPv2 or
    #   MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
    #   EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
    #   PSK) is also configured using this field. For EAP-GPSK, this is a
    #   variable length PSK.
    # ca_cert: File path to CA certificate file (PEM/DER). This file can have one
    #   or more trusted CA certificates. If ca_cert and ca_path are not
    #   included, server certificate will not be verified. This is insecure and
    #   a trusted CA certificate should always be configured when using
    #   EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
    #   change when wpa_supplicant is run in the background.
    #
    #   Alternatively, this can be used to only perform matching of the server
    #   certificate (SHA-256 hash of the DER encoded X.509 certificate). In
    #   this case, the possible CA certificates in the server certificate chain
    #   are ignored and only the server certificate is verified. This is
    #   configured with the following format:
    #   hash:://server/sha256/cert_hash_in_hex
    #   For example: "hash://server/sha256/
    #   5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
    #
    #   On Windows, trusted CA certificates can be loaded from the system
    #   certificate store by setting this to cert_store://<name>, e.g.,
    #   ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
    #   Note that when running wpa_supplicant as an application, the user
    #   certificate store (My user account) is used, whereas computer store
    #   (Computer account) is used when running wpasvc as a service.
    # ca_path: Directory path for CA certificate files (PEM). This path may
    #   contain multiple CA certificates in OpenSSL format. Common use for this
    #   is to point to system trusted CA list which is often installed into
    #   directory like /etc/ssl/certs. If configured, these certificates are
    #   added to the list of trusted CAs. ca_cert may also be included in that
    #   case, but it is not required.
    # client_cert: File path to client certificate file (PEM/DER)
    #   Full path should be used since working directory may change when
    #   wpa_supplicant is run in the background.
    #   Alternatively, a named configuration blob can be used by setting this
    #   to blob://<blob name>.
    # private_key: File path to client private key file (PEM/DER/PFX)
    #   When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
    #   commented out. Both the private key and certificate will be read from
    #   the PKCS#12 file in this case. Full path should be used since working
    #   directory may change when wpa_supplicant is run in the background.
    #   Windows certificate store can be used by leaving client_cert out and
    #   configuring private_key in one of the following formats:
    #   cert://substring_to_match
    #   hash://certificate_thumbprint_in_hex
    #   for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
    #   Note that when running wpa_supplicant as an application, the user
    #   certificate store (My user account) is used, whereas computer store
    #   (Computer account) is used when running wpasvc as a service.
    #   Alternatively, a named configuration blob can be used by setting this
    #   to blob://<blob name>.
    # private_key_passwd: Password for private key file (if left out, this will be
    #   asked through control interface)
    # dh_file: File path to DH/DSA parameters file (in PEM format)
    #   This is an optional configuration file for setting parameters for an
    #   ephemeral DH key exchange. In most cases, the default RSA
    #   authentication does not use this configuration. However, it is possible
    #   setup RSA to use ephemeral DH key exchange. In addition, ciphers with
    #   DSA keys always use ephemeral DH keys. This can be used to achieve
    #   forward secrecy. If the file is in DSA parameters format, it will be
    #   automatically converted into DH params.
    # subject_match: Substring to be matched against the subject of the
    #   authentication server certificate. If this string is set, the server
    #   sertificate is only accepted if it contains this string in the subject.
    #   The subject string is in following format:
    #   /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
    # altsubject_match: Semicolon separated string of entries to be matched against
    #   the alternative subject name of the authentication server certificate.
    #   If this string is set, the server sertificate is only accepted if it
    #   contains one of the entries in an alternative subject name extension.
    #   altSubjectName string is in following format: TYPE:VALUE
    #   Example: EMAIL:server@example.com
    #   Example: DNS:server.example.com;DNS:server2.example.com
    #   Following types are supported: EMAIL, DNS, URI
    # phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
    #   (string with field-value pairs, e.g., "peapver=0" or
    #   "peapver=1 peaplabel=1")
    #   'peapver' can be used to force which PEAP version (0 or 1) is used.
    #   'peaplabel=1' can be used to force new label, "client PEAP encryption",
    #   to be used during key derivation when PEAPv1 or newer. Most existing
    #   PEAPv1 implementation seem to be using the old label, "client EAP
    #   encryption", and wpa_supplicant is now using that as the default value.
    #   Some servers, e.g., Radiator, may require peaplabel=1 configuration to
    #   interoperate with PEAPv1; see eap_testing.txt for more details.
    #   'peap_outer_success=0' can be used to terminate PEAP authentication on
    #   tunneled EAP-Success. This is required with some RADIUS servers that
    #   implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
    #   Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
    #   include_tls_length=1 can be used to force wpa_supplicant to include
    #   TLS Message Length field in all TLS messages even if they are not
    #   fragmented.
    #   sim_min_num_chal=3 can be used to configure EAP-SIM to require three
    #   challenges (by default, it accepts 2 or 3)
    #   result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
    #   protected result indication.
    #   'crypto_binding' option can be used to control PEAPv0 cryptobinding
    #   behavior:
    #    * 0 = do not use cryptobinding (default)
    #    * 1 = use cryptobinding if server supports it
    #    * 2 = require cryptobinding
    #   EAP-WSC (WPS) uses following options: pin=<Device Password> or
    #   pbc=1.
    # phase2: Phase2 (inner authentication with TLS tunnel) parameters
    #   (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
    #   "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
    # Following certificate/private key fields are used in inner Phase2
    # authentication when using EAP-TTLS or EAP-PEAP.
    # ca_cert2: File path to CA certificate file. This file can have one or more
    #   trusted CA certificates. If ca_cert2 and ca_path2 are not included,
    #   server certificate will not be verified. This is insecure and a trusted
    #   CA certificate should always be configured.
    # ca_path2: Directory path for CA certificate files (PEM)
    # client_cert2: File path to client certificate file
    # private_key2: File path to client private key file
    # private_key2_passwd: Password for private key file
    # dh_file2: File path to DH/DSA parameters file (in PEM format)
    # subject_match2: Substring to be matched against the subject of the
    #   authentication server certificate.
    # altsubject_match2: Substring to be matched against the alternative subject
    #   name of the authentication server certificate.
    #
    # fragment_size: Maximum EAP fragment size in bytes (default 1398).
    #   This value limits the fragment size for EAP methods that support
    #   fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
    #   small enough to make the EAP messages fit in MTU of the network
    #   interface used for EAPOL. The default value is suitable for most
    #   cases.
    #
    # EAP-FAST variables:
    # pac_file: File path for the PAC entries. wpa_supplicant will need to be able
    #   to create this file and write updates to it when PAC is being
    #   provisioned or refreshed. Full path to the file should be used since
    #   working directory may change when wpa_supplicant is run in the
    #   background. Alternatively, a named configuration blob can be used by
    #   setting this to blob://<blob name>
    # phase1: fast_provisioning option can be used to enable in-line provisioning
    #         of EAP-FAST credentials (PAC):
    #         0 = disabled,
    #         1 = allow unauthenticated provisioning,
    #         2 = allow authenticated provisioning,
    #         3 = allow both unauthenticated and authenticated provisioning
    #   fast_max_pac_list_len=<num> option can be used to set the maximum
    #      number of PAC entries to store in a PAC list (default: 10)
    #   fast_pac_format=binary option can be used to select binary format for
    #      storing PAC entries in order to save some space (the default
    #      text format uses about 2.5 times the size of minimal binary
    #      format)
    #
    # wpa_supplicant supports number of "EAP workarounds" to work around
    # interoperability issues with incorrectly behaving authentication servers.
    # These are enabled by default because some of the issues are present in large
    # number of authentication servers. Strict EAP conformance mode can be
    # configured by disabling workarounds with eap_workaround=0.

    # Example blocks:

    # Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
    # network={
    #    ssid="simple"
    #    psk="very secret passphrase"
    #    priority=5
    # }

    # Same as previous, but request SSID-specific scanning (for APs that reject
    # broadcast SSID)
    # network={
    #    ssid="second ssid"
    #    scan_ssid=1
    #    psk="very secret passphrase"
    #    priority=2
    # }

    # Only WPA-PSK is used. Any valid cipher combination is accepted.
    # network={
    #    ssid="example"
    #    proto=WPA
    #    key_mgmt=WPA-PSK
    #    pairwise=CCMP TKIP
    #    group=CCMP TKIP WEP104 WEP40
    #    psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
    #    priority=2
    # }

    # WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
    # network={
    #    ssid="example"
    #    proto=WPA
    #    key_mgmt=WPA-PSK
    #    pairwise=TKIP
    #    group=TKIP
    #    psk="not so secure passphrase"
    #    wpa_ptk_rekey=600
    # }

    # Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
    # or WEP40 as the group cipher will not be accepted.
    # network={
    #    ssid="example"
    #    proto=RSN
    #    key_mgmt=WPA-EAP
    #    pairwise=CCMP TKIP
    #    group=CCMP TKIP
    #    eap=TLS
    #    identity="user@example.com"
    #    ca_cert="/etc/cert/ca.pem"
    #    client_cert="/etc/cert/user.pem"
    #    private_key="/etc/cert/user.prv"
    #    private_key_passwd="password"
    #    priority=1
    # }

    # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
    # (e.g., Radiator)
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=PEAP
    #    identity="user@example.com"
    #    password="foobar"
    #    ca_cert="/etc/cert/ca.pem"
    #    phase1="peaplabel=1"
    #    phase2="auth=MSCHAPV2"
    #    priority=10
    # }

    # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
    # unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=TTLS
    #    identity="user@example.com"
    #    anonymous_identity="anonymous@example.com"
    #    password="foobar"
    #    ca_cert="/etc/cert/ca.pem"
    #    priority=2
    # }

    # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
    # use. Real identity is sent only within an encrypted TLS tunnel.
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=TTLS
    #    identity="user@example.com"
    #    anonymous_identity="anonymous@example.com"
    #    password="foobar"
    #    ca_cert="/etc/cert/ca.pem"
    #    phase2="auth=MSCHAPV2"
    # }

    # WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
    # authentication.
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=TTLS
    #    # Phase1 / outer authentication
    #    anonymous_identity="anonymous@example.com"
    #    ca_cert="/etc/cert/ca.pem"
    #    # Phase 2 / inner authentication
    #    phase2="autheap=TLS"
    #    ca_cert2="/etc/cert/ca2.pem"
    #    client_cert2="/etc/cer/user.pem"
    #    private_key2="/etc/cer/user.prv"
    #    private_key2_passwd="password"
    #    priority=2
    # }

    # Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
    # group cipher.
    # network={
    #    ssid="example"
    #    bssid=00:11:22:33:44:55
    #    proto=WPA RSN
    #    key_mgmt=WPA-PSK WPA-EAP
    #    pairwise=CCMP
    #    group=CCMP
    #    psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
    # }

    # Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
    # and all valid ciphers.
    # network={
    #    ssid=00010203
    #    psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
    # }


    # EAP-SIM with a GSM SIM or USIM
    # network={
    #    ssid="eap-sim-test"
    #    key_mgmt=WPA-EAP
    #    eap=SIM
    #    pin="1234"
    #    pcsc=""
    # }


    # EAP-PSK
    # network={
    #    ssid="eap-psk-test"
    #    key_mgmt=WPA-EAP
    #    eap=PSK
    #    anonymous_identity="eap_psk_user"
    #    password=06b4be19da289f475aa46a33cb793029
    #    identity="eap_psk_user@example.com"
    # }


    # IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
    # EAP-TLS for authentication and key generation; require both unicast and
    # broadcast WEP keys.
    # network={
    #    ssid="1x-test"
    #    key_mgmt=IEEE8021X
    #    eap=TLS
    #    identity="user@example.com"
    #    ca_cert="/etc/cert/ca.pem"
    #    client_cert="/etc/cert/user.pem"
    #    private_key="/etc/cert/user.prv"
    #    private_key_passwd="password"
    #    eapol_flags=3
    # }


    # LEAP with dynamic WEP keys
    # network={
    #    ssid="leap-example"
    #    key_mgmt=IEEE8021X
    #    eap=LEAP
    #    identity="user"
    #    password="foobar"
    # }

    # EAP-IKEv2 using shared secrets for both server and peer authentication
    # network={
    #    ssid="ikev2-example"
    #    key_mgmt=WPA-EAP
    #    eap=IKEV2
    #    identity="user"
    #    password="foobar"
    # }

    # EAP-FAST with WPA (WPA or WPA2)
    # network={
    #    ssid="eap-fast-test"
    #    key_mgmt=WPA-EAP
    #    eap=FAST
    #    anonymous_identity="FAST-000102030405"
    #    identity="username"
    #    password="password"
    #    phase1="fast_provisioning=1"
    #    pac_file="/etc/wpa_supplicant.eap-fast-pac"
    # }

    # network={
    #    ssid="eap-fast-test"
    #    key_mgmt=WPA-EAP
    #    eap=FAST
    #    anonymous_identity="FAST-000102030405"
    #    identity="username"
    #    password="password"
    #    phase1="fast_provisioning=1"
    #    pac_file="blob://eap-fast-pac"
    # }

    # Plaintext connection (no WPA, no IEEE 802.1X)
    # network={
    #    ssid="plaintext-test"
    #    key_mgmt=NONE
    # }


    # Shared WEP key connection (no WPA, no IEEE 802.1X)
    # network={
    #    ssid="static-wep-test"
    #    key_mgmt=NONE
    #    wep_key0="abcde"
    #    wep_key1=0102030405
    #    wep_key2="1234567890123"
    #    wep_tx_keyidx=0
    #    priority=5
    # }


    # Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
    # IEEE 802.11 authentication
    # network={
    #    ssid="static-wep-test2"
    #    key_mgmt=NONE
    #    wep_key0="abcde"
    #    wep_key1=0102030405
    #    wep_key2="1234567890123"
    #    wep_tx_keyidx=0
    #    priority=5
    #    auth_alg=SHARED
    # }


    # IBSS/ad-hoc network with WPA-None/TKIP.
    # network={
    #    ssid="test adhoc"
    #    mode=1
    #    frequency=2412
    #    proto=WPA
    #    key_mgmt=WPA-NONE
    #    pairwise=NONE
    #    group=TKIP
    #    psk="secret passphrase"
    # }


    # Catch all example that allows more or less all configuration modes
    # network={
    #    ssid="example"
    #    scan_ssid=1
    #    key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
    #    pairwise=CCMP TKIP
    #    group=CCMP TKIP WEP104 WEP40
    #    psk="very secret passphrase"
    #    eap=TTLS PEAP TLS
    #    identity="user@example.com"
    #    password="foobar"
    #    ca_cert="/etc/cert/ca.pem"
    #    client_cert="/etc/cert/user.pem"
    #    private_key="/etc/cert/user.prv"
    #    private_key_passwd="password"
    #    phase1="peaplabel=0"
    # }

    # Example of EAP-TLS with smartcard (openssl engine)
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=TLS
    #    proto=RSN
    #    pairwise=CCMP TKIP
    #    group=CCMP TKIP
    #    identity="user@example.com"
    #    ca_cert="/etc/cert/ca.pem"
    #    client_cert="/etc/cert/user.pem"
    #
    #    engine=1
    #
    #    # The engine configured here must be available. Look at
    #    # OpenSSL engine support in the global section.
    #    # The key available through the engine must be the private key
    #    # matching the client certificate configured above.
    #
    #    # use the opensc engine
    #    #engine_id="opensc"
    #    #key_id="45"
    #
    #    # use the pkcs11 engine
    #    engine_id="pkcs11"
    #    key_id="id_45"
    #
    #    # Optional PIN configuration; this can be left out and PIN will be
    #    # asked through the control interface
    #    pin="1234"
    # }

    # Example configuration showing how to use an inlined blob as a CA certificate
    # data instead of using external file
    # network={
    #    ssid="example"
    #    key_mgmt=WPA-EAP
    #    eap=TTLS
    #    identity="user@example.com"
    #    anonymous_identity="anonymous@example.com"
    #    password="foobar"
    #    ca_cert="blob://exampleblob"
    #    priority=20
    # }

    blob-base64-exampleblob={
    SGVsbG8gV29ybGQhCg==
    }


    # Wildcard match for SSID (plaintext APs only). This example select any
    # open AP regardless of its SSID.
    # network={
    #    key_mgmt=NONE
    # }



  • #22
    Epic
    Level 29  
    Czy w /etc znajdują się też pliki wpa_supplicant.conf.rpmnew lub .rpmsave?

    Próbowałeś ponownie skonfigurować siec w Network Managerze czyli w okienkach?
  • #23
    kopawel
    Level 14  
    W /etc nie ma żadnego z podanych plików.
    Gdy system się załadował, nie było połączenia ani z LAN (kabel odłączony) ani z Wifi.
    Klikam w opcje sieci WiFI i wybieram swoją sieć do połączenia, wyskakuje okno pytające o hasło więc je wpisuje i za chwilę znów wyskakuje te samo okno z zapytaniem o hasło a z siecią się nie łączy...
  • #24
    Epic
    Level 29  
    1. Wykonaj próbę połączenia z siecią wifi, następnie wklej wynik:
    Code: bash
    Log in, to see the code


    2. Wklej zawartość pliku: "/etc/NetworkManager/NetworkManager.conf"

    3. Wykonaj:
    Code: bash
    Log in, to see the code

    I ponownie spróbuj połączyć z siecią wifi za pomocą GUI.
  • #25
    kopawel
    Level 14  
    Witam.

    Oto polecenia z konsoli. Wciąż mam ten problem ale zawsze łącze się z internetem przez WiFi wyłączając wcześniej jeden proces...i tak zawsze przy włączaniu komputera.

    Code:

    [root@localhost pawel]# tail -10 /var/log/syslog
    tail: nie można otworzyć „/var/log/syslog” do czytania: Nie ma takiego pliku ani katalogu
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]# echo "update_config=1" > /etc/wpa_supplicant.conf
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]# ps -eF | grep wpa
    root      3542     1  0  4748  6356   1 11:09 ?        00:00:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u -P /var/run/wpa_supplicant.pid
    root      6912     1  0  4746  3092   0 11:09 ?        00:00:00 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
    root     12368  9944  0  7396  2256   0 11:12 pts/2    00:00:00 grep --color wpa
    [root@localhost pawel]# kill 6912
    [root@localhost pawel]#
    [root@localhost pawel]#
    [root@localhost pawel]# tail -10 /var/log/syslog
    tail: nie można otworzyć „/var/log/syslog” do czytania: Nie ma takiego pliku ani katalogu
    [root@localhost pawel]#




    A to zawartość pliku "/etc/NetworkManager/NetworkManager.conf" :
    Code:

    [main]
    plugins=ifcfg-rh,keyfile




    Chciałem zrobić jakąś aktualizacje systemu ale wchodze w ''Menu -> Narzędzia -> Narzędzia Systemowe ->Konfiguracja komputera -> wyskakuje okienko do wpisania hasla root-a, wpisuje je, okienko znika i nic się nie dzieje.