Korkstand

quote:

---

I have a regular Deco mesh system. I stuck one of the nodes out in my metal shop, 45’ from the other node. It works fine.

Both are interior, but it is a wood framed house.

I was going to run a wire, glad I tried this instead.

---

It's inside the metal shop? Surprised it works alright if so, though 45' is not all that far.

Honestly if all you're doing on the far end is streaming TV or browsing the web occasionally, which probably covers a big majority of cases, a wireless mesh will be good enough most of the time. If you want to do something demanding or end up wanting cameras at the far end, you might run into bandwidth or latency issues.

quote:

---

The reality is most people no longer give a shite about tech, nor do they much need to these days anyway

---

They'd better start giving a shite because if we end up with machines writing all the code and nobody knows what's going on we're fricked.

I don't use Synology either, just figured it was the easy/safe choice for someone starting out.

I'm not about to recommend/explain the path I chose. :lol:

I would replace stuff every 5-6 years anyway just due to technology advances, but as for degrading it's really hard to say what's happening.

It could be environmental as pointed out.

It could be software issues, either bugginess where your specific setup wasn't tested well or digital "cruft" accumulating that a factory reset might remedy.

It could be hardware issues. Consumer networking gear is expected to be silent thus usually have no fans, so they rely on heat sinks attached with thermal paste/adhesive which doesn't last forever. It eventually degrades and chips begin to throttle to manage heat which reduces performance, if they don't fail altogether.

quote:

---

are you sure you have equipment issues and not interference issues? If it is interference, new equipment will have the same problem.

---

I'm leaning toward equipment issues, but interference is definitely a possibility. And not only from your neighbors' wifi, but also nearby comms towers can cause major issues.

I don't know of any stores, but if you can't find one maybe look at the local "maker" groups or try to find a makerspace that might stock a few things. That's something I've had on the back of my mind for a while, starting one on my side of the river.

I usually just order from Amazon though.

quote:

---

It just suddenly exploded out of nowhere.

---

We haven't seen anything yet. We are approaching the singularity.

AI is already being used to write its own code and design its own chips. This will keep snowballing and accelerating.

quote:

---

What was the fundament technological leap that got us here?

---

Probably more like a lot of tiny hops and a lot of money. I think it's been pretty much steady progression that just feels like a big leap because the pace of AI is faster than what we're used to.

quote:

---

I think AI good give you really good answers to these questions.

---

I'll run this through ChatGPT:

quote:

---

The first Deco device is plugged into my BGW210 (BGW210 set into passthrough and being used as a modem only) and is the router. The second Deco device is 50' away and is being used in mesh mode. The third Deco device is 50' away from the second device, 100' from the router, and is being used in mesh mode. I want to wire the system for backhaul. My questions are: Do I need to run an Ethernet cable from the 3rd device all the way back to the router, or can I run it back to the second device? Obviously the second device needs to go back to the router itself. Once the second and third devices are wired for backhaul, do I need to change them to access points or keep them in mesh? If backhaul wiring the Deco devices does not get the WIFI where I want it to be, I am considering buying TP-Link Deco BE25 Dual-Band BE5000 WiFi 7 Mesh (much smaller devices for odd shaped areas). These will probably not be wired, should these be set as APs or mesh?

---

quote:

---

Here’s how to wire and configure your Deco system for best results:

--- ###

1. Wiring the backhaul * **Router ? Second Deco**: You’re right, the second Deco must be wired directly back to the router. That ensures a strong, stable feed. * **Third Deco**: You don’t need to run a cable all the way back to the router. You can wire the third Deco to the second one. TP-Link supports a *daisy chain wired backhaul*. So: * Router ? Deco #2 ? Deco #3 works just fine.

--- ###

2. Mode selection (AP vs Mesh) * **Keep them in Mesh Mode.** * The wired connection will automatically be used for backhaul. * Switching them to AP mode changes the network topology (single flat Wi-Fi with the BGW210 in charge), but since you already set the BGW210 to passthrough and the Deco as router, mesh mode is the right choice. * **No need to manually change modes** when you add Ethernet. Deco will auto-prefer Ethernet for backhaul if present.

--- ###

3. If you add Deco BE25 units (wireless only) * **Use Mesh Mode**, not AP. * Mesh mode lets them coordinate with your main Deco router, handle seamless roaming, and optimize paths. * Access Point mode is only if you want your BGW210 (or another router) to run the whole network, which you don’t.

--- ###

4. Practical tip: * If your Wi-Fi coverage still feels thin after wiring, placement is usually the culprit. Ideally, keep line-of-sight or minimal obstructions between units. * The BE25 units are designed for odd-shaped coverage, so sprinkling them in as wireless mesh satellites should extend coverage nicely. They’ll still handshake with the wired Decos just fine.

---

? Bottom line: * Router ? Deco #2 (wired). * Deco #2 ? Deco #3 (wired). * Keep them in **mesh mode**. * If you add BE25 units wirelessly, also **mesh mode**, not AP. Do you want me to also sketch you a simple diagram of the wired + wireless mesh layout so it’s visually obvious where each cable and role goes?

---

Bump.

I don't know what, exactly, is wrong with me, but I just can't stick with a tool for notes and tasks. I nitpick everything and focus on the annoyances and then I try something else. I wish I could say that I'm a perfectionist, but I absolute am not that. This is the only thing I'm trying to perfect right now in my life. :lol:

With Obsidian the annoyance for me is how heavy it is, and also the fact that there isn't a web client. I've run across SilverBullet so I'm giving that a whirl. It's a self-hosted PKM server and web app. It is very barebones, but also very powerful given that it has an embedded Lua engine. It has its own annoyances, of course, but in my playing around it is growing on me. I love that it's a server and that I can run it myself. I pointed it at my Obsidian data directory and it mostly just works. None of my dataview or other plugin stuff works, of course, but all of my notes are there and it didn't take long to get some task list code working in Lua.

It doesn't have nearly the userbase of Obsidian, so it's lacking in community plugins and scripts, but me & GPT are getting some stuff done. :lol:

So if this is an issue for any of you using Obsidian:

quote:

---

It really is a very powerful tool; however, to really take advantage of the power it provides can be a bit challenging for the non technical.

---

then maybe SilverBullet isn't for you. But if you like the idea of your notes accessible from any device with a browser, programmable notes, and an extremely configurable interface, then give it a try.

quote:

---

So far I am ultra glad that I put Linux on my rig and ditched Windows.

I don't do anything intensive with it, just store stuff, simple word processing stuff, and shitpost on TD. So far, it's dramatically faster than it used to be and so far 100% reliable.

I kinda hate myself for not doing this a long time ago.

---

I switched to Linux 19 years ago and I thank my younger self every day for that.