@moderators Do you have any idea what could be the solution here? I see a possible problem, but I don’t know how it can be solved. Thanks.
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:
Have a read here about that wifi model:
and even tho this is older, still has some valuable information there
https://bbs.archlinux.org/viewtopic.php?id=208472
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
ln -sf /dev/null /etc/udev/rules.d/80-net-setup-link.rules
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).
rtl8723be
enp8s0
wlan0
Having both enp8s0 and wlan0 name types is confusing - go with one or another.
Don’t implement guides found on the internet unless you really understand what you are doing - and be prepared to roll back any change you make.
I’ve reinstalled manjaro and it only works with the wired connection.
Then you need to check the search result from the archived forum mentioned in above comment on rtl8723be - as it is known to create issues.
Ok, right now I am not connected to protonvpn but the internet works fine on wifi. I have no idea what is happening…
But where did protonvpn come from?
Why haven’t you mentioned protonvpn before? Has the this been a factor the whole time?
You are getting somewhere 
Now you know that your connection issue is related to the changes protonvpn makes to your dns and routing.
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.