Re: Firewalld/nftable/libvirt...

2020-05-08 Thread Nathanael D. Noblet
On Fri, 2020-05-08 at 22:08 +0200, Igor Raits wrote:
> 
> I would guess that some ip_forward or something like this is not set.
> I'd report this against firewalld component on 
> https://bugzilla.redhat.com.
> 

Thanks Igor,

  In attempting to file the bug I found that a bug has been filed
already. https://bugzilla.redhat.com/show_bug.cgi?id=1832723.

Much appreciated.
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Firewalld/nftable/libvirt...

2020-05-08 Thread Igor Raits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Fri, 2020-05-08 at 13:34 -0600, Nathanael D. Noblet wrote:
> Hello,
> 
>   I upgraded to F32 Beta, and then final when it came out. In the
> last
> few days I've got an issue that I'm 99% sure I'm not the cause of but
> I
> don't know what component to report it on.
> 
>   I've had this workstation for years and it has a number of VMs that
> I
> manage with virt-manager/libvirt. eth0 is part of a bridge, "bridge0"
> every VM uses that bridge as its network interface to get an IP on my
> local network. It has worked like this for years, upgrading sometimes
> messed up the bridge configuration. This upgrade there were no issues
> until recently. 
> 
>   Now my VMs can't get an IP address via DHCP unless I temporarily
> stop
> firewalld. I wondered if it was the change from iptables to nftables.
> However I changed it to use iptables and that didn't fix it.
> 
>   So, seeing as I didn't change the firewall rules and I don't know
> why
> this is no longer working I'm kinda thinking its a bug but not sure
> where to report it? 

I would guess that some ip_forward or something like this is not set.
I'd report this against firewalld component on 
https://bugzilla.redhat.com.

> Thoughts?
> -- 
> Nathanael
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
- -- 
Igor Raits 
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEcwgJ58gsbV5f5dMcEV1auJxcHh4FAl61vC8ACgkQEV1auJxc
Hh499hAAogC0WSPDQ2A2Ut2ggJqQg3PrEjCQB78ORyJZZSJn5ZQTCehvfVMdRWtM
GUegmam24ZBvpXKab+ILLDak84vAajr3KjjlvcUYiJfRrZCvHXSl9PF/xmyT3+be
l/DCQSvKqHwbXlQCvGyZrrXCO6RlEs2QwYuXjKpUtO38vdD8YpbCcwhJiCz1bHGv
QT/6/gG3vVDOBPR62owNfQpx9PSG+DbIWlnHEfsX6y+4aECpmZF2HjzuLXCKCIld
ihbKbpVEa+FNkTxeiWFFYYgVYPEDG6xexQG4qvc0n0aelTbhlZwSDhcDJXMCUiwT
UHyqp1Gz4InSPLURHIN/uuWy8EpkSv3lcP+uVSwHnC77ntOQibft87JBZZzyLBcV
KdmYk3TW46lULD7amMzVPMhnk8a+Qs8kC5vUW6Q+d+78XAJrttkwx9Tut29U8bqW
gK0sUW84Tvc9rDqPc7EFiEDfsIeK0hmvX9eEYCFl3wPksvAguXFgyKsR2Inr8Gh8
GdSVIdjgnynNtm4QZJW1gSYYUy1DIphhezcbMp//hmaQcH4eFX1E6dF5iWrkg1sN
6UZKBHBhBNYi854CPhzhqcOEDvQkRWEkL5d2QciozqG1rH6mL6bUaRyR1e6zhqhX
46bUt0Jblyagsp+4zSnKzY7uktpv7eYJfisMtduY+Bquj1/jowY=
=Cy3f
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Firewalld/nftable/libvirt...

2020-05-08 Thread Nathanael D. Noblet
Hello,

  I upgraded to F32 Beta, and then final when it came out. In the last
few days I've got an issue that I'm 99% sure I'm not the cause of but I
don't know what component to report it on.

  I've had this workstation for years and it has a number of VMs that I
manage with virt-manager/libvirt. eth0 is part of a bridge, "bridge0"
every VM uses that bridge as its network interface to get an IP on my
local network. It has worked like this for years, upgrading sometimes
messed up the bridge configuration. This upgrade there were no issues
until recently. 

  Now my VMs can't get an IP address via DHCP unless I temporarily stop
firewalld. I wondered if it was the change from iptables to nftables.
However I changed it to use iptables and that didn't fix it.

  So, seeing as I didn't change the firewall rules and I don't know why
this is no longer working I'm kinda thinking its a bug but not sure
where to report it? 

Thoughts?
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org