On my system, the file /usr/lib/NetworkManager/conf.d/nf exists and contains the following directive: Within the three directories, files are parsed in their listed order.
So, I'm struggling on my own to make both proton0 and ipv6leakintrf0 be "managed".įrom what I can piece together from the NetworkManager configuration documentation, NetworkManager configures devices from the following sources, in order: ProtonVPN support has not been able to resolve the issue after working on it for nearly two months, but they did inform me they don't support unmanaged connections. Right now, in the broken state, the two ProtonVPN device profiles proton0 and ipv6leakintrf0 are listed as "unmanaged" and "disconnected", respectively, by nmcli: $ nmcli d Gcc: 7.3.1 Shell: bash v: 4.4.19 inxi: 3.0.This question is a follow-up to this one, which remains unresolved. Info: Processes: 157 Uptime: 7m Memory: 3.72 GiB used: 1.12 GiB (30.1%) Init: systemd Compilers: Sensors: System Temperatures: cpu: 43.0 C mobo: N/A ID-1: /dev/sda model: TOSHIBA_MQ01ABF0 size: 465.76 GiB IF: enp1s0 state: down mac: 2c:fd:a1:aa:88:34Ĭard-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k v: kernel Network: Card-1: Realtek RTLE PCI Express Fast/Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI
PROTONVPN UBUNTU SERIES
OpenGL: renderer: Mesa DRI Intel HD Graphics 505 (Broxton) v: 4.5 Mesa 18.0.3 direct render: YesĪudio: Card-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster driver: snd_hda_intel Graphics: Card-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics driver: i915ĭisplay: x11 server: X.Org 1.19.6 driver: intel unloaded: fbdev,modesetting,vesa Mobo: ASUSTeK model: X541NA v: 1.0 serial: N/A UEFI: American Megatrends v: X541NA.314īattery: ID-1: BAT0 charge: 29.8 Wh condition: 30.6/34.6 Wh (89%) model: ASUSTeK ASUS BatteryĬPU: Topology: Quad Core model: Intel Pentium N4200 bits: 64 type: MCP arch: N/A L2 cache: 1024 KiBįlags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8756 Machine: Type: Laptop System: ASUSTeK product: X541NA v: 1.0 serial: N/A System Info System: Host: akontio Kernel: 4.14.39-1-MANJARO x86_64 bits: 64 compiler: gcc v: 7.3.1ĭesktop: KDE Plasma 5.12.5 tk: Qt 5.10.1 Distro: Manjaro Linux 17.1.10 Hakoila
PROTONVPN UBUNTU HOW TO
Does anyone know what might be causing this or how to fix it? I would really appreciate some help! I have tried disabling IPv6, upon doing which I am told that IPv6 management is REQUIRED for the VPN to function. Not being able to manage IPv6 by protonvpn-cli might cause issues in leaking the system's IPv6 address. Please test the system for the root cause. There are issues in managing IPv6 in the system. I am trying to use the ProtonVPN-cli application ( ), and when trying to connect I am provided with the following error: Connecting.
Using the latest stable release of Manjaro KDE, on 2 different machines I am experiencing the same issue.
0 kommentar(er)
