Bug 799143

Summary: Firewall prevented dnsmasq from working with virtual bridge network
Product: [Fedora] Fedora Reporter: Scott Doty <scott>
Component: dnsmasqAssignee: Tomáš Hozza <thozza>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: aquini, dougsland, itamar, veillard
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-19 11:32:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Scott Doty 2012-03-01 21:10:28 UTC
Description of problem:

DHCP functionality didn't work with Windows 8 public beta until firewall rule was removed.  I thought at first this was an interoperability problem, but removing the last INPUT chain firewall rule (the catchall that sends back an icmp access denied) seems to have fixed the problem.

Version-Release number of selected component (if applicable):

dnsmasq-2.58-2.fc16.x86_64

How reproducible:

I used the i686 iso from here:

http://windows.microsoft.com/en-US/windows-8/iso

Steps to Reproduce:
1. install into virt
2. boot virt
  
Actual results:

OS sense out dhcp requests that dnsmasq does not answer.

Expected results:

dnsmasq answering dhcp request, configuring the OS.

Additional info:

I went to re-create the problem & capture the packets with tcpdump -- but this time, it worked.  Only thing different now from when it didn't work is firewall changes.

Comment 1 Fedora Admin XMLRPC Client 2012-10-22 13:21:28 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Tomáš Hozza 2012-11-19 11:32:54 UTC
From the problem description this was a problem with your firewall settings. dnsmasq communication is filtered by firewall settings therefore you should check if there is any firewall rule preventing dnsmasq from receiving/sending packets.

Closing as NOTABUG since this is a firewall settings issue.

If your issue persists, please consider creating a bug for another component (firewall/libvirt/virt-manager).