That’s quite the lesson you just laid down.

It’s actually made things a lot more clear for me. To put it as tersely as I can, UTC is the international time, GMT is a timezone, which also happens to be UTC+0.

So GMT is a place/zone/region of earth, and UTC is a time coordination, with no physical location (beyond the prime meridian, which is where it is tracking the time of).

Awesome.

IMO, the biggest problem with timezones is that the people who initially created them were fairly short sighted.

That and there have been way too many changes to who lives in what timezone. The one that boggles my mind is that apparently there’s a country in two timezones, not like, split down the middle or anything, but two active timezones across the entire country depending on which culture you’re a part of, or something. It’s wild.

I still don’t know if there’s any difference between GMT and UTC. I couldn’t find one. They both have the same time, same offset (+0), and represent the same time zone area.

I use UTC because I’m in tech, and I can’t stand time formats, so I exclusively use ISO 8601, with a 24 hour clock. Usually in my local time zone, via UTC. We have DST here which I’m not a fan of, but I have to abide by because everyone else does.

My biggest issues with time and timezones is that everyone uses different standards. It drives me nuts when software doesn’t let me set the standard for how the time and date is displayed, and doesn’t follow the system settings. It’s more common in web apps, but it happens a lot. I put in a lot of effort to try to get everything displaying in a standard format then some crudely written website is just mm/dd/yy with 12h clock and no timezone info, and there’s nothing you can do about it.

I’m generally more of a Debian user, when I use Linux at least, so anything red hat based doesn’t even occur to me to recommend. I generally don’t get involved in distro discussions though.

My main interaction with Linux is Ubuntu server, and that’s where my knowledge generally is. I can’t really fix issues in redhat, so if someone is using it, I’m mostly lost on how to fix it.

There’s enough difference in how redhat works compared to Debian distributions that I would need to do a lot of work to understand what’s happening and fix any problems.

I dunno if I’d say any distro of Linux is really beginner friendly.

It takes quite a bit of learning the ins and outs of operating systems before Linux makes sense in any capacity.

If you’re just looking to run a few basic apps like discord/slack/teams/zoom, and run a browser, then sure, just about every distro can do that without trouble, and can be configured to be as “friendly” as Windows, with a few exceptions.

But anybody who wants to do intermediate/advanced stuff with little to no prior Linux knowledge? I’m not sure any distro is much easier than others. Again, with a few exceptions.

The exceptions are distros that are almost intentionally difficult to use, or that require a high level of competency with Linux before you can attempt to use it.

There’s always a learning curve, that learning curve is pretty much always pretty steep.

I’ve been using Linux for dedicated servers for a while and I don’t use Linux as a desktop environment, in no small part because despite having a fairly high level of competency with Linux, I don’t feel like I know enough to make Linux work for me instead of the other way around.

AI in the current state of technology will not and cannot replace understanding the system and writing logical and working code.

GenAI should be used to get a start on whatever you’re doing, but shouldn’t be taken beyond that.

Treat it like a psychopathic boiler plate.

It depends. If you’re forwarding a lot of ports then maybe, but just a home gaming server? Probably not a big deal.

Just don’t forward ports for remote control and you’ll be fine, especially RDP (3389 IIRC), and SSH…

The banks are borderline criminally negligent because they exclusively use SMS for 2FA.

Simply, it is insufficient.

I get that they want the SMS information on file, and that’s understandable, but give people another option at least, Holy hell. It gives my inner IT secops brain an aneurysm.

It’s improvement.

But you can also polish a turd, and that’s also improvement. It’s still a turd. Taking 1990’s tech and overlaying rich text services onto it, is just polish for the same 90’s tech that should have been left behind.

IMO, it’s still worlds away from what you can get with a purely digital instant messaging system.

Also, it seems idiotic to me that nearly all of your communications can go up in smoke by accidentally dropping your phone into a wood chipper, and you’ll be SOL until you replace it because everything is hairpinned through your cellphones SMS capability. Battery dead? Out of your providers service area? Ha ha, get fucked.

Just dumb.

All I’m going to say to this is…

You people still use SMS?

I’ve explicitly told people not to send me text messages. The protocols are old and shit compared to other instant messengers. I’m on Google chat, telegram, signal, discord, slack, teams… Find another app to talk to me with. I generally don’t care which one, but I actively refuse to sign up for or into any Facebook/meta/Zuckerberg properties. If you use something I don’t that isn’t owned by the zuck, I’ll probably sign up so we can keep touch, but for the love of God, not SMS.

Look, SMS was great when phones didn’t have internet on them. It was a quick and easy way to send updates and chat while away from your cable/DSL/dialup (whatever you had at the time). Now that data is the primary use for a mobile phone plan, just use a more robust IM app.

I also have about six or seven phone numbers, which I give out to different groups of people for different reasons, plus a phone number on my mobile which nearly nobody knows. All my other lines (all VoIP lines) ring my cellphone number. Texting from my VoIP line is not fun, but it does work. Multimedia messages generally get lost and RCS is just encouraging the use of something that should have been killed off.

I’m partial to Telegram and signal since they mainly operate by phone numbers, but I can make “voice” and video calls over data rather than having to use my cellphone directly; which allows me to call from my computer, laptop, phone, tablet… Literally any device that can run the program. So if my phone is lost/damaged/stolen/whatever (unavailable for any reason), I can still send messages to you and call if needed.

If everything is tied to your cellphone number, and that number becomes unavailable for any reason, well… Get fucked I guess. Your SIM stops working, your phone dies/breaks/gets stolen, your provider decides to fuck your account up or charge you a fortune for no good reason and cuts you off, your provider has a major malfunction and stops servicing clients in your area… Literally anything goes wrong with the one system you use and all your SMS bullshit goes away. Stop. Using. SMS.

I’ll just leave this here:

https://kdeconnect.kde.org/

Yep, I’m sure they do.

Realistically, does any average consumer know what’s on which circuit?

Spanning the split phase will screw you up, across breakers won’t be fun but shouldn’t pose any serious problems, as long as it’s not in different sides of the split phase.

I’m pretty sure they say this because actually explaining what will work and what won’t either requires significant prior knowledge of power systems, or a couple of paragraphs of explainers before you can get a rough picture of what the hell they’re driving at.

Everyone I know who has used powerline, just plug it in and see if it works. Those who were lucky, say it’s great and works without issue, etc. Those who were not lucky say the opposite.

I’m just over here watching the fireworks, eating popcorn.

I’ve been doing IT work for more than a decade, I was a nerd/“computer guy” well before that. I’ve had a focus on networking in the past 15-20 years. You learn a few things.

I try to be humble and learn what I can where I can, I know that I definitely do not know everything about it, and at the same time I try to be generous and share what I’ve learned when I can.

So if you have questions, just ask. I either already know, or I can at least point you in the right direction.

It definitely sounds like you have some challenges ahead. I personally prefer MoCA over wireless, simply because you can control what devices are able to be a part of the network, and reduce the overall interference from external sources and connections.

With WiFi, being half duplex, only one station can transmit at a time (with come caveats). Whether that station is a part of your network, or it is simply operating on the same frequency/channel, doesn’t matter. So in high density environments, you can kind of get screwed by neighbors.

MoCA is also half duplex (at least it was the last time I checked) so having a 2.5G MoCA link, to a 1GbE connection (on the ethernet side) should provide similar, or the same experience as pure ethernet (1G full duplex)… The “extra” bandwidth on the MoCA will allow for each station to send and receive at approximately 1Gbps without stepping on eachother so much that you have degraded performance.

However, it really depends on your situation to say what should or shouldn’t be setup. I don’t know your bandwidth requirements, so I can’t really say. The nice thing about ethernet is that it on switched networks (which is what you’ll be using for gigabit), the. Ethernet kind of naturally defaults to the shortest path, unless you’re doing something foolish with it (like intentionally messing with STP to push traffic in a particular direction). The issue with that is that ethernet doesn’t really scale beyond a few thousand nodes. Not an issue for even a fairly large LAN, but that’s the reason we don’t use it for internet (wan side) traffic routing. But now I’m off topic.

Given the naturally shortest-path behavior of ethernet, of you have a switch in your office and you only really use your NAS from your office PC, you’ll have a full speed experience. If nothing else needs high-speed access to the NAS, you’ll be fine.

Apart from the NAS or any other LAN resources, the network should be sufficient to fully saturate your internet connection. So the average WiFi speeds should be targeted towards something faster than your internet link (again, half duplex factors in here). I don’t know your internet speed so I’m not going to even guess what the numbers should be, but I personally aim for double my internet speed for maximum throughput on my WiFi as much as I can. The closer you can get to doubling your internet speed here, the better. Anything more than that will likely be wasted.

There’s a ton to say about WiFi and performance optimization, but I’ll leave it alone unless you ask about it further.

Good luck.

It can be faster, it really depends on whether you have a clear-ish channel for the mesh, which is why I would recommend something on the higher end, hopefully with a dedicated radio for mesh, so it can be on a different channel with (hopefully) less interference.

If the mesh radio is shared with client access, or if it’s on a busy channel, it may be much, much slower than some options.

Hello friend.

You can get 2.5gbps MoCA now. You may want to consider upgrading.

Nice username btw

Depending on where you live and what your power circuits look like (not the outlets, the circuits that power them), you may have a great, or very poor experience.

I’d need to know what country you live in to know more, since power wiring standards vary from country to country. In the USA and Canada (I’m in Canada and the USA is the same), we use split phase and crossing the split phase will severely hinder the ability for powerline to perform.

It’s a viable option, not my favorite option, I’d recommend MoCA (coax) over powerline, but it’s ultimately up to you.

IMO, powerline is going to depend on a lot of factors including what kind of power you use, which varies from country to country. Where I am in North America, we use 240v split phase, and the powerline adapters are 120v (half phase), so if one unit ends up on one side of the phase, and one ends up on the other side of the phase, you’re going to have a bad time, if it links at all… So knowing which “side” of the split phase your powerline is on becomes critical, which is not something most people know about their power situation. As a result, it’s basically a crap shoot whether it will work well or not.

I have three suggestions for you.

Easy mode: find a triple radio mesh wifi system and get at least two nodes. Generally the LAN Jack on the satellite nodes will bridge to the LAN over WiFi. Just add a switch and use it normally. This will harm your overall speeds when connecting to the NAS from other wired LAN systems that are not on the same switch. I’m not sure if that’s important. As long as your internet speed is less than half of your WiFi speed, you shouldn’t really notice a difference.

Medium mode: buy MoCA adapters and use coax. Just be sure to get relatively new ones. They’re generally all 1G minimum, but usually half duplex, so there’s still sacrifice there, but MoCA is generally better than WiFi. The pinch is making sure you stop the MoCA signal from exiting your premise. You don’t want to tap into someone else’s MoCA network, nor have them tap into yours. There are cable filters that will accomplish this, or you can air gap the coax. I’m not sure how much control you have for the ingress/egress of your coax lines. You can yolo it and just hope for the best, but I can’t recommend that.

Hard mode: do ethernet anyways. Usually in rentals, nobody can complain with holes in the walls the size you would get from nails to hand pictures, not much larger than a picture hanging nail, is a cup hook. What I did at my old place, which was a rental, was to buy large cup hooks, and put them every ~18" down the hallway, and load it with ethernet cables. I used adhesive cable runners to go down walls near doors and ran the cables under doors to get from room to room. I got lucky that two adjacent rooms shared a phone jack and I replaced the faceplate with a quad port Keystone faceplate on each side. One Keystone was wired to the phone line to keep existing functionality, the rest were connected to eachother though the wall as ethernet, and I just patched one side to the other (on one side was the core switch for my network). That was my experience, obviously your experience will be different. I used white ethernet to try to blend it in with the ceiling/walls which were off-white. In my situation, I was on DSL and used the phone jack in one of the bedrooms for my internet connection, that bedroom was used as an office and it neighbored my bedroom where I used the jack to jack connections through the wall to feed my TV and other stuff in the bedroom. The ethernet on the cup hooks went from the office to the living room where I put a second access point (first ap was on the office) and TV and other stuff. Inbetween the bedrooms and the living room was the kitchen and the wet wall was basically RF blocking, so I needed an access point on either side, so one in the office near the bedroom and bathroom, and one in the living room, provided plenty of coverage for the ~900sqft apartment we were renting. Most everything was on wired ethernet, and the WiFi was used mainly by laptops and cellphones.

I live by the philosophy of wired when you can, wireless when you have to. Mainly to save WiFi channels and bandwidth for devices that don’t have an easy alternative option like mobile phones and portable computers.

I don’t think you’re in a bad spot OP, and any of these choices should be adequate for your needs, but that will vary depending on what speed internet you have, and how much speed you need for the LAN (to the NAS and between systems).

Good luck.

Oh yeah, I’ve seen that. People hit the most minor roadblock and just stop working until someone else fixes their shit.

It’s an attitude of “we’ve tried nothing and we’re out of ideas!”

I don’t like those people either.

I dunno about OP, but I am, and I have definitely prioritized tickets based on how interesting they sound.

User setup for a new hire that is already here and waiting? Meh. Weird network problem with no apparent solution which will likely require days of investigation? Sounds good.