Important question

[Gene Czarcinski]

On 12/18/2012 03:36 PM, Adam Williamson wrote:
> On Tue, 2012-12-18 at 15:02 -0500, Gene Czarcinski wrote:
>> On 12/18/2012 01:34 PM, Adam Williamson wrote:
>>> On Tue, 2012-12-18 at 11:15 -0500, Gene Czarcinski wrote:
>>>> OK, so maybe I an nuts but it seems to me that there is this 800 pound
>>>> gorilla wondering around the Fedora 18 tent and its name is firewalld!
>>>> Or it with respect to virtual guests and libvirt (since libvirt is a
>>>> critical part of networking support).
>>>>
>>>> Maybe I am missing some critical information as to how to configure
>>>> firewalld so that guests can perform functions which the same guest can
>>>> do on a Fedora 17 host.  She only firewalld configuration I have been
>>>> able to come up with is to configure it disabled.
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=888288
>>> Your report is very general, which makes it hard to get a hold of. I can
>>> confirm the specific problem that a guest does not seem to be able to
>>> ssh to an F18 host (192.168.122.1, usually) in the default NAT
>>> networking config. For me it doesn't work with F17 guest or F18 guest.
>> OK, I set it up and do a range of tests.  For comparison purposes I
>> could compare to F18 with firewalld disabled but it would be lots easier
>> for me to compare against the F17 host.
> Comparing with firewalld disabled would be nice but probably not
> compulsory.
>
>> One more question, I would like to add the libvirt-1.0.01,
>> NetManager-git20121130, and dnsmasq-2.65 updates.  Is this OK or do you
>> want me to stick to what is in F18 only?
> Please stick to the stock F18 package set.
>
>> I am willing to put a bit of effort into this but I need guidance to
>> what information to collect.
>>
>> BTW, there is nothing in syslog.  Is there some extra logging that I can
>> turn on for firewalld?  I do not want to play with the rules to add this
>> logging because I honestly do not understand the firewalld rules.
> Not sure about that, but just precise details on what activities you're
> trying and what's failing would be really useful.
I am moving further info to the bugzilla report