LINUX.ORG.RU
ФорумAdmin

После create_ap не удаётся подключаться к точкам доступа

 ,


0

2

Накануне пробовал поднять у себя на лэптопе программную точку доступа. Т.к. я пользуюсь Arch, первым же делом полез в арчвики. Оттуда же узнал про скрипт create_ap. После скрипта и инструкций из вики мой арч отказывается подключаться к точкам доступа. Скрипт запускаю следующей командой: create_ap wlp6s0 ppp0 mywifi 123456789 (да, у меня интернет через PPPoE и поэтому использовать бриджи не судьба). Когда пытаюсь подсоединиться, допустим, через wifi-menu пишет следующее:

ob for netctl@wlp6s0\x2dBuriy_PC.service failed because the control process exited with error code.
See "systemctl status "netctl@wlp6s0\\x2dBuriy_PC.service"" and "journalctl -xe" for details.
Выхлоп от systemctl status netctl@wlp6s0\\x2dBuriy_PC.service:
● netctl@wlp6s0\x2dBuriy_PC.service - Networking for netctl profile wlp6s0-Buriy_PC
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2016-12-02 18:04:01 MSK; 20s ago
     Docs: man:netctl.profile(5)
  Process: 13199 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 13199 (code=exited, status=1/FAILURE)

дек 02 18:04:01 localhost systemd[1]: Starting Networking for netctl profile wlp6s0-Buriy_PC...
дек 02 18:04:01 localhost network[13199]: Starting network profile 'wlp6s0-Buriy_PC'...
дек 02 18:04:01 localhost network[13199]: The interface of network profile 'wlp6s0-Buriy_PC' is already up
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Main process exited, code=exited, status=1/FAILURE
дек 02 18:04:01 localhost systemd[1]: Failed to start Networking for netctl profile wlp6s0-Buriy_PC.
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Unit entered failed state.
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Failed with result 'exit-code'.

А вот что в это время происходило с netctl:

[trololo@localhost ~]$ journalctl | grep netctl
дек 02 18:03:07 localhost systemd[1]: Starting Networking for netctl profile wlp6s0-Buriy_PC...
дек 02 18:03:07 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Main process exited, code=exited, status=1/FAILURE
дек 02 18:03:07 localhost systemd[1]: Failed to start Networking for netctl profile wlp6s0-Buriy_PC.
дек 02 18:03:07 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Unit entered failed state.
дек 02 18:03:07 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Failed with result 'exit-code'.
дек 02 18:03:51 localhost polkitd[527]: Operator of unix-process:13069:4896542 successfully authenticated as unix-user:loorke to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.33 [systemctl stop netctl@me.service] (owned by unix-user:loorke)
дек 02 18:03:51 localhost systemd[1]: Stopping Networking for netctl profile me...
дек 02 18:03:51 localhost systemd[1]: Stopped Networking for netctl profile me.
дек 02 18:04:01 localhost systemd[1]: Starting Networking for netctl profile wlp6s0-Buriy_PC...
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Main process exited, code=exited, status=1/FAILURE
дек 02 18:04:01 localhost systemd[1]: Failed to start Networking for netctl profile wlp6s0-Buriy_PC.
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Unit entered failed state.
дек 02 18:04:01 localhost systemd[1]: netctl@wlp6s0\x2dBuriy_PC.service: Failed with result 'exit-code'.
дек 02 18:04:11 localhost konsole[488]: org.kde.kurifilter-ikws: "netctl@wlp6s0\\\\x2dBuriy_PC.service"

Какой адаптер используешь? Дай выхлоп команд lspci, lsusb и iw phy0 info

nickleiten ★★★ ()

Выхлоп lspci:

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
06:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)
08:00.0 3D controller: NVIDIA Corporation GK208M [GeForce 920M] (rev ff)
lsusb:
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 008: ID 0cf3:e005 Qualcomm Atheros Communications 
Bus 002 Device 002: ID 0c45:6712 Microdia 
Bus 002 Device 006: ID 046d:c05f Logitech, Inc. M115 Optical Mouse
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
iw phy0 info: http://pastebin.com/ZyLNzfum (ЛОР ругается что сообщение слишком большое).

zoroaster ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.