aug 30 18:05:37 popa-20384 NetworkManager[874]: <info> [1598799937.4050] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "TP-Link_F09E"
Wifi is working, but here it is timed out:
aug 30 18:06:33 popa-20384 systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlp9s0.
aug 30 18:06:33 popa-20384 systemd[1]: Dependency failed for WPA supplicant daemon (interface-specific version).
aug 30 18:06:33 popa-20384 systemd[1]: wpa_supplicant@wlp9s0.service: Job wpa_supplicant@wlp9s0.service/start failed with result 'dependency'.
aug 30 18:06:33 popa-20384 systemd[1]: sys-subsystem-net-devices-wlp9s0.device: Job sys-subsystem-net-devices-wlp9s0.device/start failed with result 'timeout'.
aug 30 18:06:33 popa-20384 systemd[1]: Reached target Network.
aug 30 18:06:33 popa-20384 systemd[1]: Reached target Network is Online.
The NetworkManager says:
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.3597] settings: Loaded settings plugin: keyfile (internal)
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.6439] device (lo): carrier: link connected
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.6446] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.6462] manager: (enp8s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.6474] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
aug 30 18:05:32 popa-20384 ModemManager[922]: <info> ModemManager (version 1.14.2) starting in system bus...
aug 30 18:05:32 popa-20384 kernel: Generic FE-GE Realtek PHY r8169-800:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
aug 30 18:05:32 popa-20384 kernel: r8169 0000:08:00.0 enp8s0: Link is Down
aug 30 18:05:32 popa-20384 systemd-networkd[398]: enp8s0: Link UP
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.8582] device (wlan0): driver supports Access Point (AP) mode
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.8603] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
aug 30 18:05:32 popa-20384 NetworkManager[874]: <info> [1598799932.8624] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
aug 30 18:05:33 popa-20384 systemd-networkd[398]: wlan0: Link UP
aug 30 18:05:33 popa-20384 systemd-networkd[398]: wlan0: Link DOWN
aug 30 18:05:33 popa-20384 NetworkManager[874]: <info> [1598799933.5394] device (wlan0): set-hw-addr: set MAC address to FE:92:D1:61:7A:0F (scanning)
Your wired connection gets renamed:
aug 30 18:05:15 popa-20384 kernel: r8169 0000:08:00.0 enp8s0: renamed from eth0
but not your wlan0 to wlp9s0.
I thing the network manager tries to start wlan0, this is this is the wrong name. It is wlp9s0. And there we have the interface-specific version Dependency error.
Could you post the output of:
ip a
Did you configure the WIFI somehow manually instead of using the network-manager? Is wlan0 set there or wlp9s0 as device?
No, it still doesn’t work. I can connect and it shows as connected but it doesn’t get me online. And if I disconnect the wired connection and reconnect it, I cannot go online.
What other custom configurations have you created? Without knowing from what documentation you got them, so we have context, things might get misinterpreted.
From what i gathered is about a Lenovo Z50-75
Can’t tell is some kernel boot parameters will help or not.
See here:
It is great if you play with your system - learning the inner workings - keep going.
timeshift is a fantastic tool
Make notes - so you can back trace your changes and revert if not working. Do not make many changes at once - small steps.
And when you end up like this you need to revert every change you made to your configuration and start fresh.
Please remove the files
/etc/udev/rules.d/70-persistent-net.rules
/etc/sysconfig/network-scripts/ifcfg-eth1
$ whois 1.1.1.2
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '1.1.1.0 - 1.1.1.255'
% Abuse contact for '1.1.1.0 - 1.1.1.255' is 'abuse@apnic.net'
inetnum: 1.1.1.0 - 1.1.1.255
netname: APNIC-LABS
descr: APNIC and Cloudflare DNS Resolver project
descr: Routed globally by AS13335/Cloudflare
descr: Research prefix for APNIC Labs
....
You cannot assign a cloudflare IP to a local interface - this will break your network connection - as I assume your resolv.conf also looks for cloudflare dns.
Watchdog messages can be ignored.
In configuration files you need to use the correct interface names.
Manjaro uses systemd and systemd names interfaces from their system location (their connection point either system board slot or USB hub and port number. This approach creates a predictable but can be annoying to handle.
You can get interface names using various commands e.g.
ip a | grep ' state UP' | cut -d' ' -f2 | cut -d':' -f1
If you really want to change your interface names to the old names - just create the following symlink and restart
I recently played with changing the mentioned systemd behaviour and found that moving around the interface I could make scripts which depended on a specific interface fail (No - I won’t go into details - but it is possible).
I known of the proton vpn gui - but the last time I checked you could make bad decisions in the gui.
EDIT: use the command
sudo protonvpn configure
If you have changed the defaults for option 4-5-6 please purge your config to the defaults.
ProtonVPN is a paid service with their own priority support. Please contact them if your issues continue.
If you have enabled the killswitch be aware that this will produce results like you have described earlier - you interface shows as connected but you can access nothing.