On 10/31/14 09:04, jd1008 wrote: > > On 10/30/2014 05:12 PM, Ed Greshko wrote: >> On 10/31/14 02:11, Tom Horsley wrote: >>> On Thu, 30 Oct 2014 12:00:28 -0600 >>> jd1008 wrote: >>> >>>> Why is this taking place? >>> Lots of things fiddle with iptables rules. >>> >>> If you have the new firewalld service running, God knows what it >>> does. Also the default libvirtd service starts a bunch of >>> networking things for providing a default network that includes >>> some firewall tinkering (or used to, anyway). >> FWIW, I'm working on a fresh install at the moment....doing some >> "experimenting". >> >> Using firewalld, ports 53 (DNS) and 67 (bootp) are not open. Additionally, >> after install of the bind and dhcp packages they remain not open. >> >> It is only when specifically configured to be opened are they. Also, when >> configured by the firewall-config GUI, udp/tcp is open for port 53 but only >> udp is open for 67. >> > Well, I have done nothing to cause this "recent" change. > By "recent" I mean within the last few (4-5) days. > > So, something is doing this, but have no idea how to track it down. >
Are you running iptables or firewalld? systemctl status iptables.service systemctl status firewalld.service will tell you/us. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
