On 11/17/19 5:07 PM, Tom H wrote:
On Sun, Nov 17, 2019 at 1:49 AM Ed Greshko
<ed.greshko(a)greshko.com> wrote:
> On 11/17/19 8:35 AM, Ed Greshko wrote:
>> On 11/17/19 2:48 AM, Patrick O'Callaghan wrote:
>>> But from the guest:
>>> [poc@fedora30 ~]$ showmount -e bree
>>> clnt_create: RPC: Unable to receive
>>>
>>> What am I missing?
>> OK, I put up an nfs server on the host and get the same error.
>>
>> If I disable the firewall on the host, it succeeds.
>>
>> Strangely, looking at wireshark output it seems port 111 is
>> unreachable. Even if I explicitly enable that port the problem
>> persists.
> OK, I fixed it....
>
> I put the interface virbr0 in the FW zone libvirt.
Wow. Weird that virbr0 is firewalled, but good to know. Thanks.
Yep, and as my other post states I think it always was there. If one reads the
description in
/usr/lib/firewalld/zones/libvirt.xml they'd see.
<description>
The default policy of "ACCEPT" allows all packets to/from
interfaces in the zone to be forwarded, while the (*low priority*)
reject rule blocks any traffic destined for the host, except those
services explicitly listed (that list can be modified as required
by the local admin). This zone is intended to be used only by
libvirt virtual networks - libvirt will add the bridge devices for
all new virtual networks to this zone by default.
</description>
I wrote
https://bugzilla.redhat.com/show_bug.cgi?id=1773273 as the GUI sent me down
the wrong path.
--
The key to getting good answers is to ask good questions.