Caddy reverse proxy

caddy, Geekiness, pihole, proxmox, Raspberry Pi

I was using Caddy with no problems but it suddenly stopped working after I switched my pihole 6 installation from a proxmox lxc (where it was lagging horribly) to a bare metal Pi3. I put it down to the DNS, and maybe that was the cause but the solution was to remove the wildcard at the top of the Caddyfile.

I was using a wildcard *.local certificate but Firefox rejected it because it didn’t match dns.local.

Removing the *.local section from the Caddyfile fixed it once I had installed the root.crt in Firefox. I use a proxmox script for the caddy installation and it puts the certificates in 

/var/lib/caddy/.local/share/caddy/pki/authorities/local/

Ethernet Speed

Debian, Geekiness

https://serverfault.com/questions/207474/how-do-i-verify-the-speed-of-my-nic

Thanks to serverfault I found how to check link speed between two debian machines – iperf3

You can see the expected max speed using ethtool:

# assuming eth0 is the interface we care about
~$ sudo ethtool eth0 | grep Speed
        Speed: 10000Mb/s

To see real-time speeds install iperf3, then run one machine as server and one as client:

# on both machines
apt install iperf3 -y
# say no to the install at startup - this is just for occasional testing

# on machine A, which is 192.168.1.3
iperf3 -s

# on machine B - reach out to machine A's IP address
iperf3 -c 192.168.1.3

I got 250 Mb/s whilst doing a backup on the cabling I installed myself 25 years ago (before gigabit was a thing) to a USB ethernet 25m away from the switch, so I will take that.

WSL2, Docker Desktop and Shared Drives

docker, Geekiness

A pain in the bum but I got there.

I was trying to share a NFS share with an immich docker container to have a play with importing videos. The Debian could see it but the Image could not. I am not sure if it is to do with the limit on the omv NFS IP address range or something but I knew if my Windows machine could see it then the damn WSL2 should be able to see it too, natively!

In PowerShell wsl --list --verbose lists which WSL are in use, and confusingly it gives two but the * suggested that this was the one to work with. 

  NAME              STATE           VERSION
* Debian            Running         2
  docker-desktop    Running         2

I tried and tried to mount the NFS share there, but though the Debian could see it, the Docker image could not. I share the same folder using SMB so was able to get that in to WSL using:

wsl -d Debian
sudo mkdir /mnt/p
sudo mount -t drvfs P: /mnt/p

This makes the p: drive appear on /mnt/p which I could then get working in the yaml with:

    volumes:
      - /mnt/p:/mnt/p_drive

This worked so nicely that I couldn’t think why the NFS share worked so went back and tried it all over again. It immediately worked!

Argh.

samba machine visible on Windows Network

docker, Geekiness, samba, ,

This has bothered me for ages, but today I worked it out.

I am using a docker image for samba (dperson/samba) and that works fine after a bit of work, but it always bothered me that I could not see the computer in the home network. I know it is more secure not to, but sometimes convenience wins.

I finally found the answer, and it is wsdd

I found an undocumented, wsdd docker image image with 500k downloads in docker hub but no documentation at all. This yaml was enough to allow me to call it what I wanted rather than it’s rather prosaic name and it came up INSTANTLY:

  wsdd:
    image: viniciusleterio/wsdd
    container_name: wsdd
    network_mode: host
    restart: always
    command: >
      -i eth0
      -n MyServerName