I’m using a setup where my Raspberry 3B+ is connecting to the local network over Wifi. As we are still under bullseye, I used Configurer le WiFi sur un Pi manuellement à l'aide de wpa_supplicant.conf
The mDNS resolution on the local network is not working. Could it be that the /etc/yunohost/mdns.yml config is hard-coded on the eth0 ?
I think you’re right, it adds to the correct wlan0 interface
-- Boot 5c2efa41b726499388f1d44474a627ae --
Feb 08 09:17:23 systemd[1]: Started YunoHost mDNS service.
Feb 08 09:17:28 yunomdns[1082]: Adding yunohost.local with addresses ['192.168.5.166'] on interface wlan0
Feb 08 09:17:28 yunomdns[1082]: Adding fan.local with addresses ['192.168.5.166'] on interface wlan0
Feb 08 09:17:28 yunomdns[1082]: Adding influxdb.local with addresses ['192.168.5.166'] on interface wlan0
Feb 08 09:17:28 yunomdns[1082]: Adding nodered.local with addresses ['192.168.5.166'] on interface wlan0
Feb 08 09:17:28 yunomdns[1082]: Adding phpmyadmin.local with addresses ['192.168.5.166'] on interface wlan0
Feb 08 09:17:28 yunomdns[1082]: Registering...
Feb 08 09:17:30 yunomdns[1082]: Registered. Press Ctrl+C or stop service to stop.
Another issue, yunomdns is not starting randomly sometimes. This could be related to the fact that I am connected to the same router over wlan0 and eth0, with 2 fixed DHCP leases.
Now I want to switch back to ethernet connexion and use hotspot_ynh.
The config panel of hotspot is not loading. Could it be related to the initial headless setup ?
Define “not starting”: is there an error in the service logs?
Wild guess, in absence of details: it’s starting fine,but before the interfaces. It might be needed to tweak the systemd configuration file to declare the interfaces dependency.