• Find my social media feed over here: @sebastianspaeth@social.hamburg

  • Sorry, another technical post, mainly as notes for myself. But perhaps it is useful.

    My work laptop is a MacBook Tahoe 26.6.2. I have to endure a crappy Cisco AnyConnect VPN program and would like to have my central university drives automounted when I access them (which only works once the VPN is active). According to Uni Hamburg instructions, the drive is mounted as a CIFS drive. OK, this is how I managed it after failing spectactular with AppleScript and Shortcuts and such. The best part is that everything is already built in and nothing needs to be installed. Much of my knowledge came from these useful notes.

    These are the steps that I took (with lots of diversions cut out):

    1. Create a new Mountpoint at the disk root
    2. Add the automount configuration
    3. Set my credentials in the keychain, so the correct password/username is being used.

    Create a new Mountpount at the disk root

    There is a nifty small service that automatically creates a mount point at the root of your disk, linking to some other place. This makes it much easier to find. As root, I had to create the file /etc/synthetic.conf (permission rw-r–r–) with the content:

    UHH /System/Volumes/Data/UHH

    Note, that the part between UHH and /System is a literal tabulator character (TAB). I have read reports that your Mac might refuse to boot if you use spaces! So be careful there and check twice! After a reboot, the directiory /UHH will now point to the real directory /System/Volumes/Data/UHH (which is a directory that I simply created with the mkdir command).

    Add the automount configuration

    We use the Mac service autofs to automount the CIFS drive when the directory is accessed. The file /etc/auto_master should already exist. We add the configuration to mount CIFS/smb drives in a separate config file, so add the line

    /- auto_smb -nosuid,noowners

    as a separate line to the config file. This makes autofs look for the config file /etc/auto_smb. This time, spaces between the columns are fine.

    As root, create the file /etc/auto_smb and add your mount points. In my case, it is:

    #/mount/music -fstype=smbfs,soft,noowners,nosuid,rw ://username:password@ip-address:/music
    /System/Volumes/Data/UHH -fstype=smbfs,soft,noowners,nosuid,noatime,rw ://uhhdisk.uni-hamburg.de:/daten/wiso

    (The first line is just a commented out example). A couple of things to note: The first column is my mount point, in my case /System/Volumes/Data/UHH which will then automatically also be visible and mounted if I access /UHH. The second column are the mount options, they should be fine as is. The third column is the DRIVE location, prefixed with a : (don’t ask me why!), and also with a : between the host and the path. Now, you CAN add username and password directly here (see the commented out first line as example), but it has 2 drawbacks: 1) it is readable for all admins on your computer (potentially even more, if you don’t set file permissions carefully), and 2) it seems only to work for “simply” usernames and passwords without special characters. I have a @ in my username, and could never get it to work. The good news is that the password can be stored in the Apple keychain and your Mac looks it up automagically (thanks, I would never have found out on my own!).

    If you need to restart autofs without rebooting your computer: sudo automount -cv seems to do the trick AND outputs a bit of helpful debug information.

    Set my credentials in the keychain

    Hit APPLE-Space, type “keychain” (in my German box, the app is called Schlüsselbundverwaltung) and start it. The Mac helpfully offered to open the news app “Passwords” which I politely declined and opened the keychain anyway. (I don’t know whether Passwords would work). I then added a new entry in the “passwords” tab.

    I guess, important are the “Account” (the username) and the location (including the path). After a reboot, my Mac is now automounting!

    Fediverse Reactions
  • Welcome to another technical post with my take on an area with lots of confusion: matrix VOIP and turn. First: Which VOIP standards does matrix support and second, what with that TURN server in livekit. Please skip if that is not of interest to you.

    Matrix VOIP

    Legacy calls: In the beginning, there was direct WebRTC between participants, potentially using a TURN server that was configured in the matrix synapse configuration. This is now called legacy calls and while some very obsolete clients are still supporting it (yes, Element classic), newer ones typically don’t (Element X and others). One of the problems with this style of calls is, that media needs to be streamed directly to all participants and received from all participants, which makes that n*(n-1) streams. This is OK for 1:1, but does not scale when more than a handfull people participates in a call.

    Jitsi: Some Element clients (mostly Element Web/Desktop) are able to embed web widgets. This was used to embed external jitsi servers, so that one could organize jitsi calls from within a matrix room. I don’t think other clients ever supported this. It worked, but always felt a bit like a bandaid.

    MatrixRTC: The new style calls as defined in MSC 4143 and define signalling and call membership over Matrix communication channels, but leave the media transport to pluggable backends. Currently, the only usable backend is Livekit, this is defined in MSC 4195. Alternative backends are planned, e.g. a direct WebRTC mesh (potentially using TURN servers). I refer to MSC 3401 for that. But for now, it is livekit or nothing. Because there is often confusion around that: MatrixRTC calls using livekit can both be group calls and “direct” 1:1 calls (DM).

    TURN and Livekit

    So…., one of the most frequent annoyances, is that people try hard to set up their Matrix voip, install livekit and all that (which is tricky enough). And then they either get told in a support room, or come up with the plan of their own, to get the livekit TURN working or to install a separate coturn TURN server.

    I’d just like to interject for a moment. NOOO, YOU MOST LIKELY DO NOT NEED TO GET THE INTERNAL LIVEKIT TURN SERVER RUNNING AND YOU MOST LIKELY DO NOT NEED TO SETUP A SEPERATE COTURN SERVER!!!

    In order to argue my case, let me explain briefly what a turn server is for, and then turn (HAHA) to livekit, the SFU (selective forwarding unit).

    If there were not firewalls, and NATs, everyone could reach everyone. VOIP would be easy and no TURN servers would be needed. But the fact is, there are many firewalls, preventing incoming connections to random ports. And NATs make participants unreachable from the outside. So a turn server is a bandaid, relaying media traffic in a way, that actors only have outgoing connections and no incoming connections when they cannot receive any. Traffic with a TURN server kind of looks like:

    Alice ---------> TURN relay <----------- Bob

    Now, livekit is a SFU, it receives, combines and distributes media streams from VOIP participants. It can do so over TCP and UDP connections. Traffic using the livekit SFU kind of looks like (simplified):

    Alice ---------> livekit SFU <----------- Bob

    Uhh, ohh, that looks pretty similar, right? Right! The livekit SFU effectively performs like a TURN server, and can take over that functionality. So, in normal cases, there is NO turn needed. So what is the internal livekit turn server for (or an alternative coturn server that one already had set up)?

    There are very restricted network environments (public hotspots, corporate firewalls, censoring governments) where not only incoming connections are hindered, but also outgoing connections might be prevented. The internal livekit TURN server (at least the TCP part) ONLY EVER announces port 443 via TLS (src code) instead of whatever port you might have configured as turn: TLSPort:, so it is for use cases where you are only allowed to reach other HTTPS web sites (trying to hide your media traffic as regular website https traffic). It helps in no other case! And the UDP part of the turn server is pretty much useless, as the SFU is already able to use a whole bunch of UDP ports to do its turnish thing anyway.

    As a result: I have disabled the livekit internal TURN server and not set up another coturn server and am doing my matrixRTC voip calls happily every after.

    Fediverse Reactions
  • Last weekend, Oliver and I participated at the “little” Hamburg , which involves walking 50km within 12(?) hours. To cut a long story short, we made it in less than 10h, including breaks. But it was more exhausting than I thought.

    Yes, we got a few blisters (quite a few actually), but more annoying where the last 10km which just took as long as the previous 40km. We made it and took a Taxi/Moia home, not in the mood for more partying.

    Still, a nice adventure with Oliver.

    Fediverse Reactions
  • Dear Stefanie Remmer, it was a pleasure to moderate your oral defense and witness you becoming a real doctor! Welcome to the club, we’ll teach you the secret handshake next…

    https://www.wiso.uni-hamburg.de/fachbereich-sozoek/professuren/gilbert/team/remmer-stefanie.html

    Fediverse Reactions
  • Eine Pyramide aus sechs Glàsern Frühjahrshonig. Im Hintergrund ist unscharf ein Bienenstock im Garten zu sehen
    (Ein Teil des) ersten Frühjahrshonigs aus unserem Garten den wir ernten konnten.
    Fediverse Reactions
  • Ein Misthaufen im Vordergrund mit einem altmodischen "Herzhausen-Plumpsklo" im Hintergrund. Das ganze Photo ist monochrom in sepiafarben gehalten.
    Ein nordeutsches Backsteinhaus mit einem altmodischen Schild "Emmis Krämerladen". Davor lehnen 4 hölzerne Wagenräder and der Wand.
    Im ist die Zeit stehen geblieben.
    Fediverse Reactions
  • If you want a musical escape room, you could also just listen to me playing the flute. You’ll escape in seconds!!!

    Fediverse Reactions
  • Fediverse Reactions
  • Schön wars ein paar Tage übers Wochenende mit der @Volksdorf@feuerwehr.social (und meiner Tochter Johanna) nach Boltenhagen zu fahren und den Teamgeist ein bisschen zu stärken. Danke!

    Das Schiff "Assistent" in Boltenhagen im Hafen
    Das Segelschiff “Assistent”, das in Boltenhagen im Hafen liegt