• 1 Post
  • 50 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.

    Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.

    Run:

    sudo systemctl edit systemd-networkd-wait-online.service

    That adds the override.conf for the service. Add these lines:

    [Service]
    ExecStart=
    ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any
    

    The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.









  • Here’s my messy-cabled 9u rack.

    Image

    It has:

    • Fiber gateway out of view on top of the rack.
    • Switch, which also powers 2 Ruckus APs and 2 other switches.
    • Mikrotik RB5009 router.
    • Raspberry Pi x3 all running Debian Bookworm. I have too many pis right now, running Home Assistant, LibreNMS, Log collection, and a read-only NUT server that orchestrates shutdowns and startups on power loss. I need to consolidate these.
    • 1L PCs. One is on Debian serving media and files. The other is a test server where I’m trying out Immich on openSUSE. I’m considering moving to that and rootless podman for services. To that end I have another of these 1L boxes on my desk trying other options (MicroOS, Fedora IoT, maybe others).
    • HDs. These are backup drives for the 1L server. I keep them powered off except when needed.
    • UPS and a managed, switched PDU.

    Everything is set up for low energy consumption (~90w), remote admin, and recovery from power loss.


  • My favorite French borrowings are gentle, genteel and jaunty. All borrowed from gentil (kind, pleasant, nice), but at different times (13th century, late 16th, and 17th, respectively).

    The French word is from Latin gentilis, meaning “of the Roman clan.” English borrowed that from Latin as gentile.

    So we have 4 English words, all from the same Latin origin. Of them, genteel is probably closest to the Old French pronunciation (but the vowels are still a little bit different).



  • It’s funny that there are two unambiguous alternatives to bimonthly, but they both mean 2x/month: fortnightly and semimonthly.

    Both German and Dutch distinguish their equivalent words with clear prefixes meaning half- and two-. The English word was unclear after 1066 since the French word bimensuel would have been used by the new bosses. And that means 2x/month. English used bimensual for a while before developing a new, worse word with the Latin origin bi- and the Germanic origin -monthly. And it seems to have been ambiguous from the start. So this has probably been messed up for almost 1050 years.

    Maybe we should resurrect the Old English prefix twi- to make a new(old) 1x/2months word twimonthly or more intuitively, twomonthly that we can use in opposition with halfmonthly.




  • That’s all fine, but just be sure you know how much you’re paying them for that service. Before we switched to self-managed a number of years ago our guys were taking 1.4% off the top of the whole account just to pick a bunch of index ETFs. Market goes up 5% and I only see 3.6% of it. Not good. Plus the ETFs they picked had higher expenses than just going with a whole market choice.

    They offered to get us on a plan at 1%. Ha, no thanks.



  • If you’re buying new cameras they’ll be 802.3af PoE. Passive is becoming much less common. So that model router I linked would work great.

    I think if you’re a moderately technically inclined person you would be happy with that solution. If you are intimidated at the idea of writing or adapting some scripts, I would probably recommend a router on one of the other platforms plus a PoE switch.


  • The easiest part of your requirements are the custom DNS records. All of the platforms recommended so far can do this. OpenWRT has the advantage of WiFi capabilities. If you want the router to also be your WiFi access point then it may be your best option. But it sounds like you only need it to be a wired router, which is good.

    As far as the ad blocking, I have done this with pi-hole, and with the built-in DNS and block capabilities of OpenWRT, Mikrotik and OPNSense. They are all fine. The router ones don’t have the fancy web UI like pi-hole. So if you use that a lot you will be disappointed. Mikrotik’s is the most basic and a new feature for them, but they are actively developing it. Plus their current routers can run containers, so you can run pi-hole on the router as a container if you want.

    PoE ports as a requirement is what narrows your options considerably I think. You could get that from a separate switch. If you want that in the router itself then you have very few options.

    Mikrotik has a lot of routers with PoE out. Their newest model in the RB5009 series can do either passive or 802.3af/at PoE out. Many of their older routers have passive PoE only. Make sure you know what your cameras need.

    I had similar requirements as you and got this: https://mikrotik.com/product/rb5009upr_s_in

    It has PoE out available on all 8 Ethernet ports. The default 48v power supply works with 802.3af/at PoE. It is a 96 watt supply, and can support ~76 watts of PoE downstream. If you need passive PoE then you would need to change to a 24v power supply.

    Mikrotik RouterOS requires some learning to use its advanced features, but their quick setup defaults are good. And the platform is super reliable and flexible.

    For DNS you would use their Adlist functionality along with a script similar to the one from BartoszP in this thread to enable DNS name resolution for lan hosts: https://forum.mikrotik.com/viewtopic.php?t=181640. That script is added to the DHCP server config to run when each client gets an address lease. And then you would add static name records in IP / DNS / Static for the other host.domain names you want your lan devices to connect to by name which can’t be resolved via your upstream DNS server.



  • Yeah, I get what you’re saying. Definitely. It’s not complicated for one pair of speakers in one room. For one music source. For one person controlling it.

    There just haven’t been any better cost-effective solutions with multi-room, control from your any phone convenience. And that’s a big plus for how we listen to music. Today there are a few contenders, but many of them are also cloud dependent. Really the small number of good options in this space is proof of how good Sonos was for a long time. Well and also of Spotify causing people ditch the idea of a offline digital music library.

    Edit: And to be clear, aside from the “any computer networks” part, this is what the original Sonos device did. It could work without a home network, but worked best with a shared music library on a PC. Didn’t need cloud anything, internet connection, account, etc. You just hooked your normal speakers to it and it played music.