¡ɹǝpun uʍop ɯoɹɟ ʎɐppᴉפ

  • 1 Post
  • 26 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle
  • I use LMS and it is fantastic. However not knowing your setup in detail, I cannot help you more.

    1. LMS can stream to multiple devices, separately. (Different music in different rooms/devices).
    2. LMS can stream simultaneously to multiple devices. (Same music across several devices).
    3. Yes, it can chromecast (chromecast bridge extension). There is also an Airbridge extension.
    4. Yes, there is a plugin to stream from YouTube (I don’t use it, so I don’t know if this includes or excludes YT music)

    I looked through my extensions and I cannot see a ‘spotcast bridge’ option, but doesn’t mean it doesn’t exist. You’d have to look about, maybe github.

    Finally, like you have ‘snapclient’ on the RPi’s you can/could change them to ‘chrome clients’ (different project but same deal as the snapclient). When checking, it seems the solutions that exist are pretty out of date, and there are comments that google has locked down on the ‘chromecast api’ that check the client is legit or not, through signed certificates. So everything is fine if you have legit chromecasts, but it might not be so successful with an emulated cc, such as VLC client or omxplayer.

    More finally though, Logitech Media Server, is designed to be that - the central server of your music. Ideally you would have all your music locally, rather than on other services. So it probably isn’t what you are looking for.




  • It was only a few weeks ago (maybe 4). Systems are all kept up to date with ansible. Most are Debian but there are few Ubuntu. The two that failed were both Debian.

    Granted both that failed have high [virtual] disk usage compared to the other VM’s. I cannot remember the failure now, but lots of searching confirmed that it was likely unrecoverable (they could boot, but only into read only). None of the btrfs-check “dangerous” commands could recover it, spitting out tons of errors about mismatching somethings (again, forgotten the error).


  • My setup is different to yours but not totally different. I run ESXi 8, and I started to use BTRFS on some of my VM’s.

    I had a power failure, that was longer than the UPS could handle. Most of the system shutdown safely, a few VM’s did not. All of the EXT4 VM’s were easily recovered (including another one that was XFS). TWO of the BTRFS systems crashed into a non recoverable state.

    Nothing I could do to fix them, they were just toast. I had no choice but to recover using backups. This made me highly aware that BTRFS is still not a reliable FS.

    I am migrating everything from BTRFS to something more stable and reliable like EXT4. It’s simply not worth the headache.




  • I find Joplin perfect for my needs. Markdown, embedding images, links etc. I sync to my selfhosted nextcloud.

    I like tags, I would like them to add a “directory tree” type of view to help sort “folders” (the thing they call “notebooks”) but only because I am more used to just filesystem type structured filing. But the notebooks and tagging idea works for me too.

    I strictly use it for notes/note keeping, in particular “HOWTO’s” and specific topic notes. So I dont even do a great deal of markdown in my notes, but I love the ability to add screen captures etc to them for clarity.

    And being on nextcloud, I can access those notes anywhere on any device, PC, Android, Raspberry Pi!! Joplin has an app for all of them


  • Its in several more kernels than that.

    That patch was backported into known (and probably more): v5.10.202, v5.15.140, v6.1.64

    ext4 data corruption in 6.1 stable tree (was Re: [PATCH 5.15 000/297] 5.15.140-rc1 review

    So I’ve got back to this and the failure is a subtle interaction between iomap code and ext4 code. In particular that fact that commit 936e114a245b6 (“iomap: update ki_pos a little later in iomap_dio_complete”) is not in stable causes that file position is not updated after direct IO write and thus we direct IO writes are ending in wrong locations effectively corrupting data. The subtle detail is that before this commit if ->end_io handler returns non-zero value (which the new ext4 ->end_io handler does), file pos doesn’t get updated, after this commit it doesn’t get updated only if the return value is < 0.

    The commit got merged in 6.5-rc1 so all stable kernels that have 91562895f803 (“ext4: properly sync file size update after O_SYNC direct IO”) before 6.5 are corrupting data - I’ve noticed at least 6.1 is still carrying the problematic commit. Greg, please take out the commit from all stable kernels before 6.5 as soon as possible, we’ll figure out proper backport once user data are not being corrupted anymore. Thanks!

    https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/




  • Thats not how it works.

    You have a LAN and hopefully you have a firewall that shields your LAN from WAN. Your fw is probably handing out DHCP lease IP (like 192.168.x.y)

    When you “bridge” your VM looks like an independant device on you LAN. Nothing at this point has allowed it to the public. Your dhcp can even give it an IP (but its probably better to set a static ip). In bridge mode, a "fake mac is spoofed alongside you nic’s real mac, and only for said VM)

    At that point the VM id accessible likr any other device on the LAN.

    if you then want to use vpn, just connect to your LAN however that works(vpn to computer or vpn to firewall/vpn server) and access.

    if you want to access from WAN without vpn, then you need to understand reverse proxying and youll need a full proper firewall\gateway device at the front of your network (like OPNsense).



  • I run iRedMail (a collection of dovecot, postfix etc, plus sogo and roundcube web clients and managed by a nice web frontend, all open source and runs on any linux.

    I’ve run for about 8 years, no dramas other than my isp technocally doesnt allow it. But they don’t block anything and occasionally they submit their ip ranges for customers to places like spamhaus, so i just script check every month to see if they added my ip back, then i just submit removal, it takes all of 30sec. (IP is semi static, probably changes once every 9 months or so, so not a drama to update dkim on my domain registrar.)



  • the biggest issue with N.switch is that it requires static outgoing ports.

    i have not used pf in years (opnsense here so should be same) but what you need to do is set hybrid outgoing NAT, designate a static IP to the switch, and then tell outgoing NAT for that IP to use static ports, outgoing.

    by default pf\opn randomises the outgoing NAT port and that messes up the Nswitch royally. (especially online like MK8deluxe)

    most of what is being posted about uPNP and N.switch is not correct. As long as your firewall rules allow the switch to get out (lock ports if you want to, but its a console, so … why?)

    Nintendo servers simply do not like you joining a game lobby on outgoing 34567, and then starting the game on 23456, and then turning a corner on lap 2 switching to outgoing port 18845.