• 19 Posts
  • 66 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • It’s actually surprising how much just having a person in the room can alter the temperature and humidity levels. In my master bathroom, I have my bathroom fan set to activate when the dew point reaches a certain level (I’ve found that dew point produces better results than just humidity); the idea is that the bathroom will be ventilated when someone takes a shower and for however long it takes for the humidity to dissipate after they’re done. The funny thing is that every so often, I’ll take an excessively long poop (lets me honest, I’m scrolling on my phone), and the fan will kick on. Just being in the bathroom will alter the dew point enough that it triggers the fan.

    I also have a room that contains all my server/networking equipment. It’s climate-controlled, and I’m constantly monitoring temperatures. The times that in the room working, I can see a noticeable spike in the temperature graph, even though the only variable that’s changed is that there’s a person in the room.

    So my point is: OP might not have been having fun that night; it’s entirely possible someone just came in and went to bed.



  • There are really two reasons ECC is a “must-have” for me.

    • I’ve had some variant of a “homelab” for probably 15 years, maybe more. For a long time, I was plagued with crashes, random errors, etc. Once I stopped using consumer-grade parts and switched over to actual server hardware, these problems went away completely. I can actually use my homelab as the core of my home network instead of just something fun to play with. Some of this improvement is probably due to better power supplies, storage, server CPUs, etc, but ECC memory could very well play a part. This is just anecdotal, though.
    • ECC memory has saved me before. One of the memory modules in my NAS went bad; ECC detected the error, corrected it, and TrueNAS sent me an alert. Since most of the RAM in my NAS is used for a ZFS cache, this likely would have caused data loss had I been using non-error-corrected memory. Because I had ECC, I was able to shut down the server, pull the bad module, and start it back up with maybe 10 minutes of downtime as the worst result of the failed module.

    I don’t care about ECC in my desktop PCs, but for anything “mission-critical,” which is basically everything in my server rack, I don’t feel safe without it. Pfsense is probably the most critical service, so whatever machine is running it had better have ECC.

    I switched from bare-metal to a VM for largely the same reason you did. I was running Pfsense on an old-ish Supermicro server, and it was pushing my UPS too close to its power limit. It’s crazy to me that yours only pulled 40 watts, though; I think I saved about 150-175W by switching it to a VM. My entire rack contains a NAS, a Proxmox server, a few switches, and a couple of other miscellaneous things. Total power draw is about 600-650W, and jumps over 700W under a heavy load (file transfers, video encoding, etc). I still don’t like the idea of having Pfsense on a VM, though; I’d really like to be able to make changes to my Proxmox server without dropping connectivity to the entire property. My UPS tops out at 800W, though, so if I do switch back to bare-metal, I only have realistically 50-75W to spare.


  • corroded@lemmy.worldtoSelfhosted@lemmy.worldLow Cost Mini PCs
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    3 months ago

    I have a few services running on Proxmox that I’d like to switch over to bare metal. Pfsense for one. No need for an entire 1U server, but running on a dedicated machine would be great.

    Every mini PC I find is always lacking in some regard. ECC memory is non-negotiable, as is an SFP+ port or the ability to add a low-profile PCIe NIC, and I’m done buying off-brand Chinese crop on Amazon.

    If someone with a good reputation makes a reasonably-priced mini PC with ECC memory and at least some way to accept a 10Gb DAC, I’ll probably buy two.


  • This is only true when you have a single transmission medium and a fixed band. Cable internet is a great example; you only have a few MHz of bandwidth to be used for data transmission, in any direction; the rest is used up by TV channels and whatever else. WiFi is also like this; you may have full-duplex communications, but you only have a very small portion of the 2.4Ghz or 5Ghz band that your WiFi router can use.

    Ethernet is not like this. You have two independent transmission lines; each operates in one direction, and each is completely isolated from any other signals outside the transmitter and receiver. If your ethernet hardware negotiates a 10Gb connection, you have 10Gb in one direction and 10Gb in the other. Because the transmission lines are separate, saturating one has absolutely no effect on the other.


  • You are absolutely correct; I phrased that badly. Over any kind of RF link, bandwidth is just bandwidth. I was more referring to modern ethernet standards, all of which assume a separate link for upload and download. As far as I am aware, even bi-directional fiber links still work symmetrically, just different wavelengths over the same fiber.

    If you have a 10GBaseT connection, only using 5Gb in one direction doesn’t give you 15Gb in the other. It’s still 10Gb either way.


  • This is a really good explanation; thank you!

    There is one thing I’m having a hard time understanding, though; I’m going to use my ISP as an example. They primarily serve residential customers and small businesses. They provide VDSL connections, and there isn’t a data center anywhere nearby, so any traffic going over the link to their upstream provider is almost certainly very asymmetrical. Their consumer VDSL service is 40Mb/2Mb, and they own the phone lines (so any restriction on transmit power from the end-user is their own restriction).

    To make the math easy, assume they have 1000 customers, and they’re guaranteeing the full 40Mb even at peak times (this is obviously far from true, but it makes the numbers easy). This means that they have at least a 40Gbit link to their upstream provider. They’re using the full 40Gb on one side of the link, and only 2Gbit on the other. I’ve used plenty of fiber SFP+ modules, and I’ve never seen one that supports any kind of asymmetrical connection.

    With this scenario, I would think that offering their customers a faster uplink would be free money. Yet for whatever reason, they don’t. I’d even be willing to buy whatever enterprise-grade equipment is on the other end of my 40/2 link to get a symmetrical 40/40; still not an option. Bonded DSL, also not an option.

    With so much unused upload bandwidth on the ISP’s part, I would think they’d have some option to upgrade the connection. The only thing I can think is that having to maintain accounts for multiple customers with different service levels costs more than selling some of their unused upload bandwidth.




  • Like several people here, I’ve also been interested in setting up an SSO solution for my home network, but I’m struggling to understand how it would actually work.

    Lets say I set up an LDAP server. I log into my PC, and now my PC “knows” my identity from the LDAP server. Then I navigate to the web UI for one of my network switches. How does SSO work in this case? The way I see it, there are two possible solutions.

    • The switch has some built-in authentication mechanism that can authenticate with the LDAP server or something like Keycloak. I don’t see how this would work as it relies upon every single device on the network supporting a particular authentication mechanism.
    • I log into and authenticate with an HTTP forwarding server that then supplies the username/password to the switch. This seems clunky but could be reasonably secure as long as the username/password is sufficiently complex.

    I generally understand how SSO works within a curated ecosystem like a Windows-based corporate network that uses primarily Microsoft software for everything. I have various Linux systems, Windows, a bunch of random software that needs authentication, and probably 10 different brands of networking equipment. What’s the solution here?


  • If you’re concerned about power, I don’t see any reason it should matter at all where you have your cameras, as long as your PoE switch is rated to supply your cameras. If your NVR has some kind of built-in PoE switch, then you can probably avoid having a second PoE switch for your cameras by co-locating them in the same network closet, but PoE switches are so cheap, I’d say set it up however it’s most convenient for you. To answer your question of “is it possible,” it absolutely is. I’m doing something similar. I have a lot of cameras, but two of them are PoE and are quite a distance away from my NVR server. They feed into a PoE switch that connects to a second switch that acts as the main switch for the building. That switch has a fiber connection to a third switch that lives in my server rack, and that switch has a DAC connection to my DVR server. They work just as well as the ones plugged directly into my rack switch.

    The only real concern I see is bandwidth. If your cameras and NVR are on the same switch, you’d avoid having to pass the data from the cameras out across your network to the switch that has your NVR. For 4 cameras, though (even at 4k), your total bandwidth is going to be far less than what even a 1GB network can handle. It’s very easy to saturate a switch, though, so this is going to depend largely on your network topology and what you’re using your network for.

    I would highly encourage you to keep your IP cameras on a separate VLAN, though. IP cameras all have a tendency to want to “call home,” and while that might just be for something as simple as checking for firmware updates, I don’t want my cameras connecting to anything outside my network without my permission.


  • Got my two CRS310s, set them up, and they’re working well. I’m amazed with how configurable they are in comparison to my old Zyxel switches.

    I’m not sure I’m setting up VLANs correctly, though. There’s an option to set up VLANS under Interface or Bridge. I have several ports that pass more than one tagged VLAN, and as far as I can tell, that’s only possible on the Bridge. So my Interface -> VLAN setup is completely empty, and my Bridge -> VLAN setup contains all my VLAN assignments.

    I’ve researched this a bit, and it seems like I’m doing it the right way, but I’m a bit concerned I’m passing the VLANs off to the CPU instead of the switch chip. This is the first switch I’ve used with this kind of VLAN setup. Am I on the right track?

    Also, my 1GB SFP modules only work if I disable Autonegotiation; then they show as “Up,” with all the lights on, even if no cable is attached. Not a big deal really, but strange. I don’t have this issue with my 10GB SFP+ modules.




  • I had no idea. Microtik is definitely new to me. For a long time, I always used surplus or recycled enterprise-level hardware, and that usually ended up being Dell, HP, or Cisco. When I did my most recent upgrade, I replaced most of that with Trendnet or TP-Link; it just made more sense, and I recognized the brand names.

    The fact that Miktotik has a CLI at all is kind of a plus to me, even if it’s horrible. Regardless, though, my network setup usually consists of Factory Default Settings -> Assign a Static IP -> Configure port-based VLANs. It’s not particularly advanced. Most likely I wouldn’t even need to use anything other than the web-based management interface.

    I really appreciate the suggestion. Microtik makes a few switches that would work perfectly for me, but I had written them off as a “random white-label brand.” I think I’ll probably be replacing my Zyxel switches with Microtik.


  • I haven’t used the Omada switches, but I’ve had good luck with TP-Link in the past.

    Switch fans are almost always going to have some level of noise. The smaller the fan, the faster it has to spin to match whatever the target airflow is. I did a fan swap on one of my Dell switches a few years ago, and while it did help, it took it from “profoundly annoying from behind a closed door” to “it’s not too bad if there’s TV or music on.” The Omada switches look like they might be a good solution, though.


  • I’ve used WiFi routers as switches in the past, but it just kinda makes sense to buy something a little more purpose-built if I’m already buying new hardware anyway.

    Even using a PfSense box, managed switches do matter. While I’m not using any of the routing capability on the switches (if they even have it), I still need to be able to assign switch ports to a specific VLAN. I can connect a “dumb” switch to a VLAN-aware port on a managed switch, and every port on the dumb switch essentially becomes a member of the parent VLAN. In my case, though, the switches I need to replace each have multiple VLANs that need to be assigned to specific ports.


  • I’ve actually seen a few Microtik switches that meet my needs, but to be entirely honest, I’ve never used Microtik before, and I was a bit hesitant based on that. If you’re running one in a location that hits 40c, that’s already far above what I’d be dealing with. My hottest location only gets to about 30c (86f), and I’ve had trouble with my Zyxel switches even lower than that.

    I’d actually prefer a switch with nothing but SFP+ ports. I’m going to wait and see if I get any more feedback, but if you’ve had good experience with Microtik, I may give them a try.


  • Asus RE-BE88

    Not a bad suggestion, but it doesn’t really work for me. I already have a Unifi system for my WiFi, and I use PfSense for routing, so I’d be disabling half of the features. Plus, for the same cost, I can just buy another of my “main” 16-port SFP+ switches, which is kind of what I’m trying to avoid.



  • I’m fortunate enough to be a homeowner, but I rented places for most of my adult live. My current home doesn’t have central AC, and none of my rentals did either.

    Everywhere I’ve lived, the mounting hardware that comes with portable ACs just didn’t work for me. What I found that did work is to throw away the existing window mount and build your own. I’ll take two pieces of plywood, cut them to the space that exists in my window (at one point this was a sliding door), and sandwich a sheet of insulation foam in the middle. Then drill holes for your AC tubes and screw on the mounts that came with your AC.

    Also, if at all possible, avoid the single-hose portable units. You’re wasting cold air. A dual-hose unit uses outdoor air to cool the unit itself, and the hot exhaust gets expelled through the second tube. Do make sure you have a screen on the inlet, though, unless you want to be cleaning out bugs from inside your AC. I have used window units, single-hose portable, and dual-hose portable units. At least in my experience, the window units work best, the dual-hose units are a close second, and the single-hose units are crap.

    As far as HA integration, I recently went through the process of finding a new AC that works with HA. What I found is that everything available either requires internet access and works with proprietary “cloud” access or just doesn’t have any sort of remote connection. Some of the “cloud” solutions have decent integration with HA, but I have a hard-and-fast rule that none of my IoT devices access anything outside my home network. What worked for me is buying a “dumb” portable AC with a remote control and using a Wifi-connected universal remote to provide access to HA.


  • I’ve been an electronics hobbyist for years, and I still don’t own a 3D printer. You can buy premade enclosures in almost every size you can imagine. Then just drill holes to mount IO ports.

    I do want to get a 3D printer exactly for this reason, but I’ve just never gotten around to buying one. They are certainly not a necessity if you want to build your own stuff.


  • One of my favorite automations is my “temperature lamp.” HA takes an average temperature, humidity, and illuminance from various outdoor sensors around my property. I have a template sensor that uses these values, then gives me a “feels-like” outdoor temperature. Another template sensor takes this “feels-like” temperature and converts it to a percentage between 0 (freezing) an 100 (> 120 degrees F). It uses this percentage to calculate a value between blue and red on a perceptually-uniform colorspace (CIELAB) and spits out an RGB value. An automation watches this RGB value and applies it to a RGB light bulb in my living room.

    The result is that I have a light that displays what the temperature “feels like” and changes color in a way that people perceive as matching the temperature. So if the lamp looks “kind of blue” it’s going to feel “kind of cold” outside. If the bulb looks “kind of red,” it’s going to feel “kind of warm.”

    I set this up for fun, but it’s actually ended up being really useful. Before we leave the house, we can just glance over at the lamp and know if we need to put on a sweatshirt or a coat, or maybe leave the outerwear at home.