friend_of_satan @ friend_of_satan @lemmy.world

Posts

1

Comments

1,021

Joined

2 yr. ago

He is another victim of his decisions.

This definitely gave me "Well, well, well, if it isn't the consequences of my own actions" vibes too.

Look at this visualization of how much money Jeff Bezos has, and then tell me that it is reasonable and justifiable.

https://mkorostoff.github.io/1-pixel-wealth/

We can be heroes. https://i.imgur.com/hdT6mQm.mp4

I don't think I've ever seen that kind of bloat with Linux.

The gateway device should definitely be up at all times, but in the real world, things don't always go as planned.

If you only use the internet, then maybe having your AP go down when your gateway goes down is fine. For us avid self-hosters, that is unacceptable behavior.

Interesting, but at $160 the GL-MT600 is nearly twice the price of the OpenWrt One.

Good to know about though! My whole reason for asking for alternatives is I've had a great experience with dd-wrt in the past, and I'm sick of ubiquiti, so I'm looking ahead for my next router.

Personally I'd get standalone AP's and hang them off a standalone switch so that if the internet gateway goes down the LAN experience is not interrupted.

Turris Omnia is 4x the price of the OpenWrt One.

with far more than 4 devices plugged in

Even more important, I don't want layer 1 dropping on my devices just because my internet gateway rebooted, especially if I'm using DHCP.

What other hardware at this price point would you consider for running openwrt?

s/subnets/vlans/

It's not a great idea to have multiple layer 3's sharing the same layer 2.

How did you like it? I'm like 10 hours in and so far it seems ok, but I'm not seeing the super amazing game that my friends raved about. For instance last night while playing I thought about how Bioshock was much more immersive and gripping, and it came out the same year.

Mass Effect. First time through the trilogy.

From my understanding, it only checks DNS when it initially connects, and so if the public IP changes the connection just stops working.

This is pretty standard TCP network behavior for long duration connections. The client queries dns for the IP address, opens a socket, and leaves it open as long as needed.

One thing that would help here is some kind of keepalive feature, like a client to server TCP connect or SYN, or better yet a higher level protocol signal. Check your client to see if there is some tunable keepalive. It may be set so something long like 1h.

One time as a kid I took a southern Baptist church trip to Central America. When I got back my racist uncle said "y'all look like a bunch of foreigners." Mind you that at the time I was blond enough to be a Hitler Youth poster boy, but heaven forbid my skin was brown from being in the sun. 🙄

Shoot, you're right. I thought MX used Ubuntu as upstream but it uses Debian.

But this is Trump we're talking about!

It's funny and awesome that the two top distro are Ubuntu remixes that remove snap.

Edit: I'm wrong. MX uses Debian as upstream, not Ubuntu, which removes any snap related tech from the picture entirely.

Rawlsian veil of ignorance strikes again would once again be awesome to use.

Imagine that one side gets no background checks, and the other does, but you don't know which side gets what. Do you agree to that?