• 2 Posts
  • 21 Comments
Joined 3 years ago
cake
Cake day: January 20th, 2024

help-circle
  • Hi all, thanks for all your comments and suggestions, here’s a late update:

    I went with option 2 and configured the second VLAN + Wifi with the printer on it. The process was smooth except for half a day troubleshooting why DHCP was not possible (turns out I have to manually tell dnsmasq to listen on the new interface as well…). I set up a static IP address for the printer though. Adding the machine from my other devices involve manually typing out its IP, something I hope to resolve with an avahi daemon on the router later on.

    For Android specifically, printing can be configured through its “Default Print Service” which can be found in Settings. Scanning requires a separate app, and I found ScanBridge to be exactly what I need and also FOSS. The address to type in is http://$PRINTER_IP_ADDRESS/eSCL/ (note the trailing slash). There’s also Mopria Scan, which is proprietary.

    If you use a VPN on the Android, remember to exempt the print service and scan app from the tunnel.


  • Your 1. seems good enough as a starter, yeah. I’ll probably tell my users to ditch the app altogether otoh, so I’m looking forward to the Pi as a long-term solution

    Though, what kind of non-tech nightmares are you referring to? I’d think that if being done properly and with autodiscovery enabled, it would be as seamless as “connect to printer/scanner X on the network” which is the Pi itself. But I probably haven’t understood enough


  • Damn, I didn’t know devices do these dynamic MACs, but yeah it’s not a trusted field to begin with.

    By IPP autodiscovery, do you mean mDNS? If so, does the router needs to install avahi as well for single-network discovery to work? Or just the client?

    Avahi on the router for multi VLAN discovery seem to be a nice idea, I’ll look into it and maybe try to hook it up to solution 2. I’ve thought users could just manually input the IP addresses (and the non-tech users will just simply be onboarded by me anyways), but having it advertised by default may just be less of a hassle for them.





  • So what are the alternatives that work with both Alpine and Debian?

    My opinion is that you’d be better off sticking to the OOTB init system that these distros provide, and hop to an entirely different distro that supports the init system you want/need. And for distros that do support multiple, stick to their guides carefully. Would save from a lot of incompat quirks and unsupported bugs, since these things can be as integrated into the main system as the package manager, if not more.

    Conceptually though systemd can be a bunch. The s6 dev put out these definitions for the way he conceptually breaks down the entire init/service ecology into small pieces so have a look (ou may be interested in his full post explaining the motivation behind s6/s6-manager too). And since you’re on Alpine, see their plans for a future init system.

    With that said you may wanna try out dinit on Chimera Linux. They’re one of the unique distros that offers this and some other cool things


  • If you have the WireGuard config from Mullvad already, just edit your wg.conf files on client devices to route all traffic via the Mullvad servers. Basically replace all the values of the [Peer] block with Mullvad values.

    If you can share your Mullvad wg config file and your wireguard-server config file here, we can sort this out together

    Edit: actually since your only goal is to increase the Mullvad device limits, why not just use Mullvad-provided confs directly in your client WireGuard apps? Should be straightforward to do






  • Might look into Gotosocial considering it’s more lightweight.

    Other than that I wonder whether it’s better for the uni/department to register on another instance, similar to how fosstodon is home for many FOSS projects. An inter-unis, academic-focused Fediverse server might be a good club project, and could allow more donation sources to sustain too (although this is pretty above-scope from what you’re asking).




  • Assuming you just want file sync and storage, if you can live without External Storage (having another SFTP/WebDAV/whatever backend), then I think oCIS is great for you. It also expect an OIDC auth provider by default - this guide helped me through. Note that you have to configure the S3 storage driver in oCIS and properly backup your buckets and metadata.

    For Talk you can setup an internal Matrix and TURN server too. I recommend conduwuit if you want something lightweight, or Synapse (quite heavy) if you need OIDC integration.