não pode configurar uma conexão vpnc com o network-manager no Kubuntu 15.04

2

Minha conexão VPN não está funcionando para mim em uma instalação limpa do Kubuntu 15.04, e foi em 14.10 e versões anteriores. Eu posso configurar uma conexão através do "editor de conexão", mas quando eu quero conectá-lo pisca uma janela que é provavelmente onde eu deveria digitar as senhas (mas se foi imediatamente, então eu não posso dizer). Depois de dizer por um tempo que está conectando, desiste. O syslog se parece com isso:

grep NetworkManager /var/log/syslog
Jul  9 15:12:11 hostname NetworkManager[811]: <info> Starting VPN service 'vpnc'...
Jul  9 15:12:11 hostname NetworkManager[811]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 2136
Jul  9 15:12:11 hostname NetworkManager[811]: <info> VPN service 'vpnc' appeared; activating connections
Jul  9 15:12:15 hostname ureadahead[307]: ureadahead:NetworkManager_new.1445: Ignored relative path
Jul  9 15:12:15 hostname ureadahead[307]: ureadahead:NetworkManager: Ignored relative path
Jul  9 15:12:15 hostname ureadahead[307]: message repeated 3 times: [ ureadahead:NetworkManager: Ignored relative path]
Jul  9 15:12:15 hostname ureadahead[307]: ureadahead:NetworkManager_new.1490: Ignored relative path
Jul  9 15:12:15 hostname ureadahead[307]: ureadahead:NetworkManager: Ignored relative path
Jul  9 15:12:15 hostname ureadahead[307]: message repeated 2 times: [ ureadahead:NetworkManager: Ignored relative path]
Jul  9 15:14:11 hostname NetworkManager[811]: <error> [1436447651.584396] [vpn-manager/nm-vpn-connection.c:1778] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.

Criar uma conexão com as senhas na configuração não ajudou:     Jul 9 16:46:17 Nome de host NetworkManager [811]: [1436453177.020663] [vpn-manager / nm-vpn-conexão.c: 1778] get_secrets_cb (): Falha ao solicitar segredos de VPN # 2: (6) Nenhum agente estava disponível para este pedido.

Eu tentei criar manualmente um arquivo conf, que parecia ser parcialmente bem-sucedido. ifconfig tinha um item extra chamado tun0 , eu podia fazer ping de sites usando URLs, mas não conseguia carregar nenhum site no meu navegador. Isso pode ser uma indicação de que o meu problema é semelhante ao este , mas não é bem assim, porque não ter sites funcionando é uma restrição. Foi o que eu fiz lá:

user@hostname:~$ sudo vpnc-connect /etc/vpnc/my_vpn_config.conf
[sudo] password for user: 
Enter IPSec secret for [email protected]: 
Enter password for [email protected]:
VPNC started in background (pid: 19663)...
user@hostname:~$ ping askubuntu.com
PING askubuntu.com (122.122.122.122) 56(84) bytes of data.
64 bytes from 122.122.122.122: icmp_seq=1 ttl=59 time=51.1 ms
user@hostname:~$ sudo vpnc-disconnect
Terminating vpnc daemon (pid: 19663)

o syslog para esta conexão é assim:

Jul  9 16:15:54 hostname NetworkManager[811]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): carrier is OFF
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): new Tun device (driver: 'unknown' ifindex: 6)
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): exported as /org/freedesktop/NetworkManager/Devices/5
Jul  9 16:15:54 hostname NetworkManager[811]: <info> devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
Jul  9 16:15:54 hostname NetworkManager[811]: <info> device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): link connected
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) starting connection 'tun0'
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 1 of 5 (Device Prepare) scheduled...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 1 of 5 (Device Prepare) started...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 2 of 5 (Device Configure) scheduled...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 1 of 5 (Device Prepare) complete.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 2 of 5 (Device Configure) starting...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 2 of 5 (Device Configure) successful.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 2 of 5 (Device Configure) complete.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 3 of 5 (IP Configure Start) started...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 3 of 5 (IP Configure Start) complete.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 5 of 5 (IPv4 Commit) started...
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) Stage 5 of 5 (IPv4 Commit) complete.
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> (tun0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jul  9 16:15:54 hostname NetworkManager[811]: <info> Activation (tun0) successful, device activated.
Jul  9 16:17:49 hostname NetworkManager[811]: <info> (tun0): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
Jul  9 16:17:49 hostname NetworkManager[811]: <info> (tun0): deactivating device (reason 'removed') [36]
Jul  9 16:17:49 hostname NetworkManager[811]: <info> devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)

kvpncerror: Timeout while connecting to 123.123.123.123. vpnc connect process will be killed. O ping do gateway retorna dentro de 50 ms.

Não tenho muita certeza do que mais tentar. Outras opções (pptp, openconnect, openvpn) parecem exigir um certificado de CA, o que eu não tenho, então eu suponho que estou preso com o vpnc. Espero que alguém tenha algumas ideias?

Editar: parece ser uma variante do este bug , embora a correção não tenha funcionado para mim.

    
por craq 09.07.2015 / 17:19

0 respostas