[opensuse] How to make your Linux machines visible to other Linux machines - TechRepublic
I recently came across this article. How does it affect OpenSUSE? I couldn't find that pack name in Yast. https://www.techrepublic.com/article/how-to-make-your-linux-machines-visible-to-other-linux-machines/?ftag=TRE475558a&bhid=12825460 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
W dniu 29.11.2018 o 21:20, James Knott pisze:
I recently came across this article. How does it affect OpenSUSE? I couldn't find that pack name in Yast.
On openSUSE the package is called just "avahi" and on my Tumbleweed system it's installed and running. I didn't touch it, so I think it's like that by default. The only issue I see, is that it has config files for SuSEfirewall2, but not for firewalld. -- Adam Mizerski
On 11/29/2018 03:28 PM, Adam Mizerski wrote:
W dniu 29.11.2018 o 21:20, James Knott pisze:
I recently came across this article. How does it affect OpenSUSE? I couldn't find that pack name in Yast.
On openSUSE the package is called just "avahi" and on my Tumbleweed system it's installed and running. I didn't touch it, so I think it's like that by default.
The only issue I see, is that it has config files for SuSEfirewall2, but not for firewalld.
-- Adam Mizerski
I've found browsing Linux boxes from Windows has often been "iffy". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/11/2018 21.34, James Knott wrote:
On 11/29/2018 03:28 PM, Adam Mizerski wrote:
W dniu 29.11.2018 o 21:20, James Knott pisze:
I recently came across this article. How does it affect OpenSUSE? I couldn't find that pack name in Yast.
On openSUSE the package is called just "avahi" and on my Tumbleweed system it's installed and running. I didn't touch it, so I think it's like that by default.
The only issue I see, is that it has config files for SuSEfirewall2, but not for firewalld.
I've found browsing Linux boxes from Windows has often been "iffy".
Yes, avahi ports has to be opened on the firewall. There have been many posts in the list about killing avahi. /etc/sysconfig/SuSEfirewall2.d/services/avahi: ## Name: Zeroconf/Bonjour Multicast DNS ## Description: Zeroconf/Bonjour Multicast DNS (mDNS) ports for Service Discovery (DNS-SD) # Allow broadcasting on UDP port 5353. # mdnsresponder (5354) port is not used by Avahi UDP="mdns" BROADCAST="mdns" But I think that finding machine names doesn't require avahi, but the samba service that covers bios names, on of the old msdos samba services. I forget which. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 11/29/2018 03:22 PM, Carlos E. R. wrote:
Yes, avahi ports has to be opened on the firewall. There have been many posts in the list about killing avahi.
I have always installed avahi to create a service to allow printing to my laserjet from the iphone. Never noticed any problem with it being too chatty and nothing like the "dreaded dog". -- David C. Rankin, J.D.,P.E.
participants (4)
-
Adam Mizerski -
Carlos E. R. -
David C. Rankin -
James Knott