Conversation

Notices

1. Sergey Bugaev (bugaevc@floss.social)'s status on Tuesday, 07-Feb-2023 02:13:09 JST Sergey Bugaev

   in reply to

   I never understood firewalls, and I still don't. If I'm listening on a port, it must be because I'm expecting packets on it, no?

   If I didn't want to receive packets from that network, I wouldn't have bound to that interface. As simple as that.

   Maybe there is a deeper meaning to this, but for me, 'systemctl disable --now firewalld' it is.

   </rant>

   • Sergey Bugaev (bugaevc@floss.social)'s status on Tuesday, 07-Feb-2023 02:13:10 JST Sergey Bugaev

     in reply to

     This is further complicated by how the 'default' network is apparently defined by the system libvirt, while my VMs on the user libvirt are able to use it without explicitly referring to it, by connecting to the bridge interface.

     "It just works", except when it doesn't, and you're on your own trying to make sense of the patchy docs and random forum questions scattered around the web.

     Adrian Cochrane repeated this.
   • Sergey Bugaev (bugaevc@floss.social)'s status on Tuesday, 07-Feb-2023 02:13:11 JST Sergey Bugaev

     Argh, it's been firewalld that prevented my libvirt VMs from accessing the host

     Spent a loooot of time trying to debug this, thinking it was a bug in my Terrible mDNS responder at first. Then when I saw that not only mDNS does not work, but pretty much nothing does, I realized it was something with libvirt networking setup.

     Adrian Cochrane repeated this.