HP Virtual Agent, you're about as useless as the fucking hardware that I'm troubleshooting. What part of fucking "Arch Linux" do you not understand?! Not everyone runs your fucking assumed OS choices - WanBLowS 7, 8 or 10. What's more, the hardware that I'm troubleshooting doesn't even support those bloody operating systems.

Long live HP and its random freezes due to poor thermal management. And long live Intel's fucking wireless drivers, that for no good reason disconnect after half an hour and require me to restart NetworkManager to (hopefully) get shit connected again. And long live those useless fucking "virtual assistants"!!!

So I decided to install Arch on my Vps.
Problem: no connection from Vps to internet.
Info: I have terminal access from my hostings panel.
Solution: basic troubleshooting and Google
Problem: this hosting uses outdated install image with broken systemd-networkd.
Solution: install networkmanager
Problem: no internet
Solution: download networkmanager and dependencies on my laptop
Problem: How do I upload them?
Solution: put them in a tar archive, then base64 it and copy paste it via the panel.
Problem: That base64 is over 30MB. No browser lets me copy and paste so much text.
Solution: Write a quick and dirty Java that reads a .txt file and presses buttons.
Problem: Browser freezes after one second
Solution: Thread.sleep(10) after each character, and Thread.sleep(1000) after 10k characters for the browser to catch up.

It's currently going and I have no idea how long it will take. I'll post an update when it finishes.
And people ask me why I love programming. It can help solve so much problems with so little work.

Edit: according to some quick calculations this will take about 5-6 hours, so I'm cancelling it, sine it's past midnight now. I'll start it up tommorow before going to college

## building my own router

I hoped things would go more smoothly :)
Anyway, my new miniPC easily accepted CentOS 8 - no fuss here. And I've got to say - I love CentOS8 so far! Shell has amazing nifty tricks, UI (gnome3) is also snappy, video/audio/ethernet,.. everything works.

What I did NOT expect is hardware being off. Well okay, the price was low - it was obvious smth is not right. But still.. I decided to build my own router so that I could swap wifi card whenever I want. So that I could run my own network services in there. Turns out - the card swapping is not as easy as one might think.

I got the AX200 WiFi6 card for that very purpose. But once plugged in the OS can only see it's bluetooth module. Weird... What's even weirder is that even though the card is PCIe, the OS uses btusb module to talk to that device. What? USB?? emm.. What??

And there it is. After opening it up again I noticed that the mPCIe area is marked with a label: "USB WIFI / WWAN". USB? Does that mean this PCIe slot is wired into the USB bus? Not impossible I guess.

Googling for a "pcie wifi over usb" or smth like that brought me to one reddit (I think?) where someone wanted to build a DIY wifi mPCIe -> USB adapter and someone else adviced hime that (for some reason) at best he could only get bluetooth working (hey! just like me!). It's got to do smth with pcie channels and USB being too weak to handle all that load, or smth.. IDK, I'm not a HW guy.

Well that sucks then! I have a mPCIe slot that does not work as a PCIe. Shit! So I guess the best I could do is to plug back in the same wifi card that came with the device. It smells like 2003 - supports only g protocol. Fine, let's try that. Maybe I'll find a way to work around this mPCIe limitation later on (USB adapter or smth... except there are no USB WIFI6 dongles yet :( ). So I plug it back in and start turning it into a router. Disable NetworkManager, configure static NCs' settings, install dhcpd, hostapd, bind and others. Looks like all is done! Now it's time to start it all. systemctl start hostapd --> FAILED. wtf? journalctl says it could not initialize a driver. umm okay? Why? Forums say I should airodump-ng check and kill whatever's using that device. Fine. airodumo reveals avahi and wpa_suppl are still using it. kill, kill, GOTTA KILL 'EM ALL!! Starting hostapd again -- same shit... wtf?

iw list

My gawd... That shitty network card does not even support AP mode :( I mean.. My USB wifi dongle for 2€ supports 2x more modes, is faster, has better range and is easier to work with than this old tart!

Yeah. That was an interesting day. When enfironment engineers break my testing environments at work I'm glad I have where to spend my time now.

BTW any ideas how to bypass this mPCIe nonsense? Come on, there are USB GPUs out there.. Why can't they make a USB (or dual-USB if they really need to) mPCIe adapter?

Why is NetworkManager in Ubuntu so buggy? I really hate it. Makes me even miss Windows. Desktop with random freezes and the super intelligent resolvd can't even resolve shit. So I can't connect to VPN to work, so I gotta reboot a damn Linux machine to make it work. Why this Linux Desktop decay? Why?

My desktop pc is suddenly having issues connecting to my home WiFi network, every few minutes it just stops having an internet connection while not showing anything out of the ordinary.

I finally have time to work on some side projects and now THIS happens, weirdly enough it's also just this network, my hotspot seems to work fine.

Now I have a watcher on to keep systemctl restarting the networkmanager, why can stuff just not work for once ? ;_;

I've had this issue since a few months but the failure interval has never been this bad. usually it was just one restart a day

Time to look up the linux mint forums again

Riddle me this: (Arch) Whenever network connection is lost, NetworkManager freezes for a good 10s. Neither nmcli nor nmtui nor client applications get anything back from it during this time. After that 10s, it detects that the connection was lost and continues normal operation.

Anyone had issues with NetworkManger on Kubuntu restarting 66 fucking times on boot? Switching to wicd ffs...

Spent all day trying to fix my intermittently failing Wi-Fi connection on Linux. Error codes for wpa_supplicant are entirely unhelpful. -_-

<rant>
Linux: Manjaro XFCE

I disabled WiFi in the manage networks widget because reasons.

BIG Mistake!

Fuck! Can't enable it anymore.
😱😵😭😭😭😭😭😭😭😭😭

</Rant>
<Info>
More info in case you want to help me:

Widget sais: "Wifi Disabled" in grey letters and not clickable.

Googled around, debug info:

$ip list
wlp3s0 ... State DOWN
$ip link enable wlp3s0
Error: locked by RF-Kill

$rfkill list
....
1: phy0
Soft lock yes
Hard lock no

$ rfkill unblock 1
$ rfkill list
1: phy0
Soft lock no
Hard lock no

WiFi still disabled.

$ip link enable wlp3s0
$ip link
...
wlp3s0 ... Down

WiFi still disabled.

$ cat ..../NetworkManager/NetworkManager.status

....
Wireless ... Disabled.

Restarts case rfkill soft lock again.

The laptop is a 2015 Razer Blade 14 and does not have hardware switches or shortcuts that I know of, that dis or enable wifi, or Bluetooth.

</Info>

I brought my laptop on vacation, but I left my archiso USB drive at home, assuming I wouldn't break anything.

I broke networkmanager. I just added a connection, it worked flawlessly, but for some reason it is now a reason to stop booting. It enters emergency mode, but I can't type anything... Possibly because it doesn't have read/write access or something idk.

But how on Earth would this break my system??? I'm beginning to understand why some people dislike systemd sometimes...

I guess I'll fix it when I come home...

Iwd. IWD. iNetWirelessDaemon. Where have you been? No lag at all. Fast. No dependencies. Lightweight. No layers of abstractions...

Since I switched to Arch on my my computer (4 years ago!), I've had to deal with NetworkManager. What a piece of shit. Don't get me started about wpa_supplicant, the piece of software that did the real lifting.

Thanks, Intel!

Spent days adding cloud-init to a CentOS kickstart script for a baremetal template.
I didn't want to have NetworkManager installed but had network problems.

Turns out you need to explicitly put NM_CONTROLLED=no in the config for the interface to not use NetworkManager.

Because that makes sense.