Ostatnio zmieniłem operatora na Netie, ze względu na oferowanie internetu po ETTH, co pozwala wyeliminować totalnie urządzenie od dostawcy (a nie jak w przypadku np. UPC/Play po DOCSIS gdzie trzeba przestawić ich wspaniałego connectboxa w tryb bridge). Według instrukcji na internecie, również powinienem bez problemu otrzymać dane PPPoE.

W moim przypadku (prawdopodobnie że jest to sieć internetia?), w portalu netiaonline nie miałem podanych danych logowania PPPoE (tak jak to powinno być według instrukcji). Instalator również nie miał przy sobie na umowie tych danych, oraz po sprawdzeniu przez siebie w portalu, również nie mógł uzyskać tych danych. Po kontakcie na infolinii, jedyne co dostałem SMSem, to nieprzydatne dla mnie informacje co do ustawień ADSL, nadal bez danych do logowania.

Recently i faced an interesting issue - after enabling Cloudflare proxy on domain hosted on Plesk (with Litespeed webserver, but that is not important), the domain returned Plesk default page instead of the domain, even through in domain logs i could see the requests.

Some time ago I decided to setup seperate homelab network in my house, as my previous homelab server is more like a production homeserver which I don’t want to disrupt. It is not much, but I wanted to build something small, energy-efficient and from the parts I already had.

But back to the topic that made me curious - I kinda needed some persistent storage for pods in lab. Then I remembered that the Mikrotik (RB951G-2HnD) router i’m using have a USB port and I saw an option in winbox to create SMB share. I think you can image where it is going.

I’m still using my chromebook with coreboot as a portable thinclient. Due to small built-in storage (only 16GB), i’m also using microSD card as a secondary storage for larger files and project. However i was strugeling with microSD card not being mounted at boot (waiting for device), my solution was to just physically eject and insert the card at boot, but it is pretty inconvient and is probably destroying the card pins.

Recently, I was trying to upgrade my toy K3s cluster using System Upgrade Plans operator. Applied example manifest, control-plane upgraded without issues, but pod for upgrading worker node was constantly restarting with error in logs exec /bin/upgrade.sh: exec format error. I would kinda expect that issue on ARM system (although we come a long way in the last couple of years!), but my nodes are running on x86 CPU, so what is happening?