On 1/28/19 9:24 PM, Patrick O'Callaghan wrote:
On Mon, 2019-01-28 at 19:52 +0800, Ed Greshko wrote:
Actually, vnet0, wasn't even there initially until I manually added it to "public". Originally the line read
interfaces: enp2s0 wlp4s0
What zone was it in, as a matter of interest?
Oh, I thought I posted this earlier, public.
[egreshko@meimei ~]$ sudo firewall-cmd --info-zone=public [sudo] password for egreshko: public (active) target: default icmp-block-inversion: no interfaces: enp2s0 wlp4s0 sources: services: dhcpv6-client dns kde-connect mdns ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
I've reverted to this condition.
Have you tried with the FW stopped?
Well I stopped firewalld, though I don't think that actually stops the FW itself, i.e. iptables in the kernel.
Makes no difference.
Well, good news and bad news. The good news is that I think I've been able to reproduce the problem. The bad news is that it is late in my day and I've had a bit of a "night cap".
But, do this, with the firewall stopped reboot the guest. Then see if it works. When I reproduced the problem it was necessary to reboot the guest to get it working.
I'll do more in my AM.