# License, or (at your option) any later version. # published by the Free Software Foundation either version 2 of the ![]() # under the terms of the GNU Lesser General Public License as # avahi is free software you can redistribute it and/or modify it Here is the avahi config on the $ cat /etc/avahi/nf I am sharing my WiFi to my Pi by setting the wired connection to "Shared to other computers" (with both IPv4 and IPv6). I connected the raspberry pi with an ethernet cable to my computer (which is using WiFi). I have checked that Avahi is running (same command as on the pi). Ssh: Could not resolve hostname raspberrypi.local: Name or service not known I think the issue might be in my linux system I use to connect to the pi? The hostname is also raspberrypi so that is not the issue. Sep 28 12:31:45 raspberrypi avahi-daemon: Registering new address record for 10.42.0.56 on eth0.IPv4. Sep 28 12:31:45 raspberrypi avahi-daemon: New relevant interface eth0.IPv4 for mDNS. Sep 28 12:31:45 raspberrypi avahi-daemon: Joining mDNS multicast group on interface eth0.IPv4 with address 10.42.0.56. Sep 28 12:31:34 raspberrypi avahi-daemon: Registering new address record for fe80::a3a0:c51a:4fa:5bd0 on eth0.*. Sep 28 12:31:34 raspberrypi avahi-daemon: New relevant interface eth0.IPv6 for mDNS. Sep 28 12:31:34 raspberrypi avahi-daemon: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::a3a0:c51a:4fa:5bd0. Sep 28 12:31:21 raspberrypi avahi-daemon: Interface eth0.IPv4 no longer relevant for mDNS. Sep 28 12:31:21 raspberrypi avahi-daemon: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.42.0.56. Sep 28 12:31:21 raspberrypi avahi-daemon: Withdrawing address record for 10.42.0.56 on eth0. Sep 28 12:31:21 raspberrypi avahi-daemon: Interface eth0.IPv6 no longer relevant for mDNS. Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Mon 12:01:52 CEST 35min agoĬGroup: /system.slice/rvice on the pi, the avahi-deamon is $ service avahi-daemon status I want to ssh into my Pi and I can do it right now with the ip address of the Pi. Moreover, if I leave ssh.service and reboot it also doesn't work. However, if I reboot the device, it stops working again. Moreover, if I then remove ssh.service and run systemctl again, it recognizes that ssh.service is gone, and removes that service, but leaves myservice completely functional. However, and this is where it gets weird: if I copy the default ssh.service over from the avahi documentation and then RERUN the systemctl command above, it recognizes a "change" in the service files, reloads and then BOTH ssh and myservice are published correctly. It just doesn't publish my service (despite the log saying it read my config file). This should work on boot (according to all the documentation I've seen), but doesn't. I added rvice in /etc/avahi/services with the following content: For that I need to add it to a config, so I did just that. It works just fine, but that doesn't configure it to start automatically. It sorta works, but not quite, and I cannot figure out why not.Īvahi-publish -s myservice _mqtt._tcp 1883 I am trying to configure avahi-daemon on my raspberry pi to broadcast the service I just programmed, which needs to be discoverable automatically.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |