Freebsd config error device tun is unknown

Модератор: SLEDopit

I have been having some problems with openconnect in my Arch Linux (Antergos to be precise) and I have no idea what’s causing it. (Although I’m used to linux and all, I’m very new to VPNs and openconnect.)

I’m trying to connect to my University’s VPN via 2 methods. I start by following the instructions, which simply say to create a Cisco AnyConnect Compatible VPN and input the name and gateway.

When I do it this way and try to connect via the network-manager applet it doesn’t work. When I flip the VPN switch it simply flips right back immediately and that’s it. No error messages or anything.

The second approach I’m trying is via command line. So I try this

$ sudo openconnect -u myusername my.gateway.edu

(I’m replacing the actual gateway with my.gateway.edu and also the username and blurring relevant IPs from now on)

This is the log I get from that input:

POST https://my.gateway.edu/
Connected to 164.**.**.**:443
SSL negotiation with my.gateway.edu
Server certificate verify failed: signer not found

Certificate from VPN server "my.gateway.edu" failed verification.
Reason: signer not found
To trust this server in future, perhaps add this to your command line:
    --servercert sha256:bb2476a96b88357fe74f28a347ba549a2af4bea8668e30a77e1a8295f466bfdc
Enter 'yes' to accept, 'no' to abort; anything else to view: yes
Connected to HTTPS on my.gateway.edu
Got HTTP response: HTTP/1.1 401 Unauthorized
Error generating GSSAPI response:
gss_init_sec_context(): Unspecified GSS failure.  Minor code may provide more information
gss_init_sec_context(): SPNEGO cannot find mechanisms to negotiate
Server 'my.gateway.edu' requested Basic authentication which is disabled by default
GET https://my.gateway.edu/
Connected to 164.**.**.**:443
SSL negotiation with my.gateway.edu
Server certificate verify failed: signer not found
Connected to HTTPS on my.gateway.edu
Got HTTP response: HTTP/1.1 401 Unauthorized
No more authentication methods to try
GET https://my.gateway.edu/
Please enter your username.
POST https://my.gateway.edu/auth
Please enter your password.
Password:
POST https://my.gateway.edu/auth
Got CONNECT response: HTTP/1.1 200 CONNECTED
CSTP connected. DPD 90, Keepalive 32400
Connected as 169.**.***.**, using SSL
DTLS handshake failed: Resource temporarily unavailable, try again.
Failed to open tun device: No such device
Set up tun device failed
Unknown error; exiting.

I have asked the University’s IT support but they also don’t know what’s happening (I think they’re not very familiar with Arch Linux). I have tried some other things such as using the flag --script /etc/vpnc/vpnc-script but the result is the same.

EDIT

I have recently come across this website via the IT people that says that I have to create a tunnel device before connecting. Even after doing that the results of sudo openconnect -u myusername my.gateway.edu --interface tun1 are still the same.

Проблема оказалась в systemd-resolved.service — Network Name Resolution

Я удалил resolvconf:

sudo apt-get --purge remove resolvconf

Установил openresolv:

apt install openresolv

Выполнил команду результатом которой Active: inactive (dead):

systemctl status systemd-resolved.service

Выполнил вторую команду результатом которой стало Active: active (running):

systemctl enable systemd-resolved.service
systemctl start systemd-resolved.service

Запуск wireguard. После чего wg-client завелся:

sudo wg-quick up wg0-client
———

Но теперь другая проблема. При загрузке системы wg0-client.service выдает ошибку. Он и раньше ее выдавал. Думаю, что wireguard запускается раньше, чем resolved.service. Приходится после загрузки системы делать:

systemctl restart wg-quick@wg0-client.service

Как это исправить?

systemd-analyze blame
213ms wg-quick@wg0-client.service
1.072s systemd-resolved.service

Вот вывод из журнала загрузки:

grep -i wg /var/log/boot.log
[FAILED] Failed to start WireGuard via wg-quick(8) for wg/client.
See 'systemctl status wg-quick@wg-client.service' for details.

systemctl status wg-quick@wg-client.service:

systemctl status wg-quick@wg-client.service
● wg-quick@wg-client.service - WireGuard via wg-quick(8) for wg/client
   Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled)
   Active: **failed** (Result: exit-code) since Tue 2020-06-30 17:10:56 MSK; 2 weeks 1 days ago
     Docs: man:wg-quick(8)
           man:wg(8)
           https://www.wireguard.com/
           https://www.wireguard.com/quickstart/
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8
Main PID: 564 (code=exited, status=1/FAILURE)

Но у меня нет файла конфигурации с таким именем: wg-quick: `/etc/wireguard/wg-client.conf’ does not exist

ls /etc/wireguard
client_private.key  client_public.key  wg0-client.conf
———-
———-
В итоге последнюю проблему удалось решить. По ошибке был создан сервис несуществующего интерфейса :

systemctl stop wg-quick@wg-client.service
systemctl disable wg-quick@wg-client.service
systemctl enable wg-quick@wg0-client.service
systemctl start wg-quick@wg0-client.service

systemctl status wg-quick@wg0-client.service
● wg-quick@wg0-client.service - WireGuard via wg-quick(8) for wg0/client
   Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2020-07-15 18:33:52 MSK; 5s ago
     Docs: man:wg-quick(8)
           man:wg(8)
           https://www.wireguard.com/
           https://www.wireguard.com/quickstart/
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8
  Process: 1544 ExecStart=/usr/bin/wg-quick up wg0-client (code=exited, status=0/SUCCESS)
Main PID: 1544 (code=exited, status=0/SUCCESS)