You are not logged in.
Hi,
I think I'm following the instructions, but having trouble getting these things to do the job of avahi.
I can resolve mDNS requests on the network (servername.local), but networkd doesn't seem to be responding / advertising to requests for this server (cannot connect from another arch box on same switch, nothing showing up with "avahi-browse --all").
Trying to go solo with systemd/resolved/networkd and not use NetworkManager or other tools.
Following these instructions: https://wiki.archlinux.org/index.php/Sy … olved#mDNS
in /etc/systemd/resolved.conf the only line uncommented is:
[Resolve]
MulticastDNS=yes
I've setup the network file as recommended I think:
cat /etc/systemd/network/20-wired.network
[Match]
Name=ens35
[Network]
DHCP=yes
MulticastDNS=yes
I don't have any firewalls on at the moment (very new install).
Must be missing something obvious?
Thanks in advance for any advice someone can offer.
Cheers,
Grant.
Last edited by grant.traynor (2020-12-30 02:54:39)
Offline
For clarity :
you did disable avahi-daemon.service & avahi-daemon.socket ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi @Lone_Wolf,
Thanks for helping out. Appreciate it.
I didn't install avahi, but here's the status of these services.
$ systemctl status avahi-daemon.service
Unit avahi-daemon.service could not be found.
$ systemctl status avahi-daemon.socket
Unit avahi-daemon.socket could not be found.
Cheers,
Grant.
Offline
Edit: Maybe a dnssd service needed: https://www.freedesktop.org/software/sy … dnssd.html I think systemd should respond to a simple hostname query, but...
I suggest you start systemd-resolved with debug logging, that should give you more information about what is happening: https://unix.stackexchange.com/a/432077
Last edited by progandy (2020-12-30 02:29:05)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
That's it! Thanks progandy!
cat /etc/systemd/dnssd/workstation.dnssd
[Service]
Name=%H
Type=_ssh._tcp
Port=22
Can then resolve with %H.local on another machine.
Is it just me or is the documentation a little scant? I'm happy to update the wiki topic if that's going to be useful.
Cheers,
Grant.
Last edited by grant.traynor (2020-12-30 03:06:43)
Offline
For posterity, if you want the "workstation" record to show up:
[Service]
Name=%H
Type=_workstation._tcp
Offline