On 12/4/20 8:53 PM, Samuel Sieb wrote:
> I've never heard of this. I'm not sure, but this seems
like something
> I don't use, at least not explicitly. Is this something that I can
> remove from the system, or at least turn off (so it won't use CPU),
> Or is this "under the hood" of things I do use?
The workstation install has libvirtd enabled by default. If you aren't
going to use VMs, then you can run "systemctl disable libvirtd".
I assume this is not something I use withut knowing it.
-bash.1[~]: systemctl disable libvirtd
Removed /etc/systemd/system/multi-user.target.wants/libvirtd.service.
Removed /etc/systemd/system/sockets.target.wants/virtlogd.socket.
-bash.2[~]:
>> You most likely don't need mdns (Multicast DNS) and can
delete that
>> service. You *may* need dhcpv6-client
>> to properly configure your IPv6 automatically when the system starts.
>
> How do I delete a service (mdns)?
You don't delete it. You can "systemctl disable avahi-daemon". If it
mentions something about socket activation, then you can use "mask"
instead of "disable" to keep it off.
-bash.2[~]: systemctl disable avahi-daemon
Removed /etc/systemd/system/multi-user.target.wants/avahi-daemon.service.
Removed /etc/systemd/system/dbus-org.freedesktop.Avahi.service.
Removed /etc/systemd/system/sockets.target.wants/avahi-daemon.socket.
-bash.3[~]:
> If I understood you and that pdf file correctly, tivoconnect has
> nothing to do with watching youtube videos or online streaming (such
> as Viki, Rakuten, or Zoom). I think I don't use this either. But
> tivoconnect sure shows up a lot in both columns. Is there something I
> should remove from the system (via dnf), or shut off?
You are unlikely to have something running on that port. That number is
most likely just getting used randomly, unless that's one of the ports
that gets scanned for. In which case, there's nothing you can do anyway.
>> Someone in this thread suggested that outgoing traffic should be
>> examined as well as incoming. That does make sense to me. The
>> firewall-cmd commands I did: did those look at both incoming and
>> outgoing, or just incoming?
>
> By default the firewall only blocks incoming, but it's possible to block
> outgoing as well.