Random Discussion - IT version

Post Reply New Topic

For IT-related stuff that doesn't need dedicated threads

Lemme start...
I checked today that Android 15 (GrapheneOS) on my Pixel 8 takes 'bout 4.9GB idling, excluding caches.
It is about
- 3x Ubuntu, which is pretty bloated Linux distro (1.7GB idling)
- 5x Linux mint, which idles on roughly 1GB (at least LMDE 6 does)
- 12x Debian 12 with XFCE (400-500MB idle)
- 45x Windows XP (~110MB idle)
- 50x NetBSD w/ CTWM (~90MB idle)
- 78x the RAM my dumbphone snappily runs on (64MB)
And that's without Google Play installed.
Optimized software, yay!

My dumbphone went faulty and goes to warranty service. It's fourth phone (in a row!) from that brand (MyPhone / Hammer) that crapped out in some way, likely I'm not going back on it to have it break yet again.
So refitted my Pixel with SIM and back on Androcrap again :/ I could search for another dumbphone but I'm genuinely fed up with all of this searching and phonehopping. They are always screwed up in some way, software or hardware...
The plus is at least I can check WP while on apprenticeship like right now.

I can touch type very fast
i think 3.122 seconds to type the alphabet
I think that's cool

^ It takes me 3x longer on keyboard and even bit longer on touch so yeah, that's neat!

Router's DHCP decided to forcibly reassign my server's IP address as my desktop's, making server unreachable and making my desktop vulnerable by exposing it to internet. After some messing I've returned it to normal state, but twas irritating nonetheless.
In other words, router basically parked a car (desktop) on already occupied parking spot (IP address), pushing occupying car (server) outta it.

I love crappy network appliances.

Hm, I'm sure I titled this thread bit differently...

That sounds like a misconfiguration issue.

I assume that you have a "server" and the router is forwarding the traffic for whatever port it needs to the IP address that was at some point assigned to the "server". A router shouldn't normally "forcibly reassign" the IP address -- it just doesn't work that way -- but if everything powered down (power outage?) then it might start over on assigning addresses.

So what you should do is:
1) set up an address pool for DHCP. For example, 192.168.1.2 to 192.168.1.20.
2) choose an address outside of that pool, say 192.168.1.99, and manually set it as the IP address for the server.
3) configure the router to forward the traffic to 192.168.1.99 or whatever address you chose.
4) problem solved.

Depending on how you did it, reassigning the address shouldn't have created any kind of a security issue. If, for example, your server is doing http and https, then you should just be forwarding those two ports (80 and 443). Presumably, your computer wouldn't have those two ports open and so there would be nothing there for an attacker to attack.

^ Also SMTP + (submission ports), IMAP as well as SSH (albeit on non-default) and some auxiliary ports primarily for testing stuff. So that's a bunch of them...

But it's what it basically did. Server was running for week maybe on one particular IP, then I powered up my daily driver it somehow crapped out, which turned out to be router assigning already taken address. It was not reserved on router itself (was set on server only), but nonetheless DHCP shouldn't assign already occupied addresses. There was no power outage in meantime.

Are you blocking pings on the server?

Before assigning an IP address, the router should ping the address to make sure it is available. If the server is not answering pings, then that means that the router can assign that address to someone else.

Blocking pings is useless anyway. Many people think that it enhances security, but it really just makes network management more difficult. Disable them at your own peril. If the router doesn't know the IP address is taken because you are blocking pings, then that is a self inflicted wound.

Don't configure a router to pass everything to your server. You should only pass those ports to the server that you want the server to handle.

For what it's worth, you should keep your statically assigned IP addresses out of your address pool anyway.

Nah I don't block pings and never did so, I often use it for internet / link troubleshooting. I can't see how it can "enhance" security either.

It doesn't, only ports I've mentioned. Better have two firewalls than one


True, tho it's one of my "should be done but since it's not that critical never did it"

On an iPad, using Safari browser, locked in landscape mode, at 115% zoom level... this is a decent mobile-esque experience on this forum.

I'm nuking FreeBSD 14.2 install on my main rig in favor of Gentoo today. FreeBSD is just flimsy utter mess, and after year of daily-driving I still can't make it lean or at least not prone to constant breaking. Other BSDs ain't an option as I currently can rely on wireless only. Too bad, given how well-structured both NetBSD or OpenBSD are (And well, I have NetBSD on my auxiliary netbook and it rocks).

I'm interested how it turns out, it's my first time trying Gentoo.

Witty characterization of AI:
"This whole AI thing is like being in a restaurant with a fancy waiter who has one of those giant pepper shakers, only it's full of bird poop and anthrax and he keeps asking "would miss like a little AI on her pasta?" with every dish that comes out... and when you say "NO" he starts grinding anyway and won't stop until you physically knock him over."
https://sauropods.win/@futurebird/114661148972246791

Good one.

I have an OpenWRT router I'm rather fond of. Has wifi 6, GbE ports.