ppptp через NetworkManager

[Lancelot-2M]

Всем доброе время суток.
Вопрос такой не новый - но поиск меня не спас...

Как настроить pppoe через нетворк менеджер?

Что было:
Ubuntu Netbook Remix 9.04
-проводное соединение eth0 - работает, вижу компы локальной сети

Что сделал:
-установил пакет network-manager-openvpn_0.7.1~rc4.1.20090323+bzr27-0ubuntu2_i386
-установил пакет network-manager-pptp_0.7.1~rc4.20090316+bzr23-0ubuntu3_i386
-создал в менеджере соединение типа ppptp - ввёл в него ip шлюза, пользователя, пароль, для всех пользователей, ручной старт.

При попытки соединиться пишет: VPN conection faild because VPN service fail to start.
dmesg про это ничего не знает...

Соответственно соединение идёт через eth0...

Видел варианты без менеджера, но они не подходят - настраиваю для жены - она подключается к разным провайдерам в разных местах по роду службы и оперативно править конфиги не сможет - нужна визуальная настройка...

[tagnupip]

В дополнительных настройках VPN попробуй снять все галки-те что не в окне

[ruPaladin]

PPPoE - это не VPN. PPTP - это VPN. Что именно нужно VPN или PPPoE?

[Lancelot-2M]

ppptp
Извиняюсь, попытаюсь исправить заголовок

[Sam Stone]

VPN conection faild because VPN service fail to start.
dmesg про это ничего не знает...

а syslog и messages?

[Lancelot-2M]

messages как и dmesg говорит eth0 link up

а вот syslog:

Sep 30 08:52:40 7th-lab-windy kernel: [ 9092.891671] r8169: eth0: link up
Sep 30 08:52:40 7th-lab-windy NetworkManager: <info>  (eth0): carrier now ON (device state 2)
Sep 30 08:52:40 7th-lab-windy NetworkManager: <info>  (eth0): device state change: 2 -> 3
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) starting connection 'Wired connection 1'
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  (eth0): device state change: 3 -> 4
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  (eth0): device state change: 4 -> 5
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  (eth0): device state change: 5 -> 7
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  dhclient started with pid 6798
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 30 08:52:54 7th-lab-windy dhclient: Internet Systems Consortium DHCP Client V3.1.1
Sep 30 08:52:54 7th-lab-windy dhclient: Copyright 2004-2008 Internet Systems Consortium.
Sep 30 08:52:54 7th-lab-windy dhclient: All rights reserved.
Sep 30 08:52:54 7th-lab-windy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 30 08:52:54 7th-lab-windy dhclient:
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  DHCP: device eth0 state changed normal exit -> preinit
Sep 30 08:52:54 7th-lab-windy dhclient: Listening on LPF/eth0/00:24:21:6d:92:04
Sep 30 08:52:54 7th-lab-windy dhclient: Sending on   LPF/eth0/00:24:21:6d:92:04
Sep 30 08:52:54 7th-lab-windy dhclient: Sending on   Socket/fallback
Sep 30 08:52:54 7th-lab-windy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 30 08:52:54 7th-lab-windy dhclient: DHCPOFFER of 192.168.0.164 from 192.168.0.1
Sep 30 08:52:54 7th-lab-windy dhclient: DHCPREQUEST of 192.168.0.164 on eth0 to 255.255.255.255 port 67
Sep 30 08:52:54 7th-lab-windy dhclient: DHCPACK of 192.168.0.164 from 192.168.0.1
Sep 30 08:52:54 7th-lab-windy dhclient: bound to 192.168.0.164 -- renewal in 57 seconds.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  DHCP: device eth0 state changed preinit -> bound
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>    address 192.168.0.164
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>    prefix 24 (255.255.255.0)
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>    gateway 192.168.0.1
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>    nameserver '192.168.0.1'
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Sep 30 08:52:54 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Sep 30 08:52:54 7th-lab-windy avahi-daemon[2579]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.164.
Sep 30 08:52:54 7th-lab-windy avahi-daemon[2579]: New relevant interface eth0.IPv4 for mDNS.
Sep 30 08:52:54 7th-lab-windy avahi-daemon[2579]: Registering new address record for 192.168.0.164 on eth0.IPv4.
Sep 30 08:52:55 7th-lab-windy NetworkManager: <info>  (eth0): device state change: 7 -> 8
Sep 30 08:52:55 7th-lab-windy NetworkManager: <info>  Policy set 'Wired connection 1' (eth0) as default for routing and DNS.
Sep 30 08:52:55 7th-lab-windy NetworkManager: <info>  Activation (eth0) successful, device activated.
Sep 30 08:52:55 7th-lab-windy NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  Starting VPN service 'org.freedesktop.NetworkManager.pptp'...
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.pptp' started (org.freedesktop.NetworkManager.pptp), PID 6830
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.pptp' just appeared, activating connections
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  VPN plugin state changed: 1
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  VPN plugin state changed: 3
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  VPN connection 'БИТС' (Connect) reply received.
Sep 30 08:52:59 7th-lab-windy NetworkManager: <WARN>  nm_vpn_connection_connect_cb(): VPN connection 'БИТС' failed to connect: 'No VPN secrets!'.
Sep 30 08:52:59 7th-lab-windy NetworkManager: <info>  Policy set 'Wired connection 1' (eth0) as default for routing and DNS.
Sep 30 08:53:12 7th-lab-windy NetworkManager: <debug> [1254286392.002711] ensure_killed(): waiting for vpn service pid 6830 to exit
Sep 30 08:53:12 7th-lab-windy NetworkManager: <debug> [1254286392.002915] ensure_killed(): vpn service pid 6830 cleaned up


как видим пишет No VPN secrets! - но в /etc/ppp/pap-secrets  у меня есть запись "нужный_пользователь" * "нужный_пароль"

[Psy[H[]]

/etc/ppp/pap-secrets и NM совершенно никак не связаны. Да и соединение по pptp системного уровня в нем не прокатит.
по глюкам NM смотреть тут: https://forum.ubuntu.ru/index.php?topic=50516.msg370632#msg370632

[Lancelot-2M]

не понял про "не стоит делать подключение системным"
"системное" и "не системное" - это как?

[Psy[H[]]

То есть оставить на уровне пользователя.
Есть там галка, называется в нынешней user-friendly формально правильной, но по существу идиотской терминологии "доступно всем пользователям". Вот ее ставить не надо.

[Dixi257]

Надо смотреть syslog строки pptp, pppd ну и  NetworkManager.