Here is the rule that i have. it seems to work for me and it slightly different from yours.
# cat direct.xml <?xml version="1.0" encoding="utf-8"?> <direct> <rule priority="0" table="filter" ipv="ipv4" chain="INPUT">-m mac --mac-source 00:18:DD:03:B6:8A -j ACCEPT</rule> </direct>
of course you got to use your own mac address. sam
On 10/03/2014 12:10 PM, Geoffrey Leach wrote:
First, let it be known that I am completely ignorant of the principles of operation of firewallD, and hope to remain so.
that said, I have a device (known to wok Silicon Dust HD Home Run) that is hard-wired to the ethernet port on another system. Installing Fedora 19 has interfered with this.
In order to open the firewall to this connection, I have followed the advice of Michael Hannon (https://lists.fedoraproject.org/pipermail/users/2013-December/444034.html) and have constructed /etc/firewalld/direct.xml as follows:
<?xml version="1.0" encoding="utf-8"?>
<direct> <passthrough ipv="ipv4">-t filter -A IN_internal_allow -m mac --mac-source 00:18:DD:01:4A:E7 j ACCEPT</passthrough> </direct>
This did not suddenly fix the connection problem :-), but it would be nice to be able to validate this. Using firewall-cmd to reload firewalld resulted in no errors but what do I know?
So, the intended function of this code is to open the firewall to connections involving the device with MAC address 00:18:DD:01:4A:E7. Is that correct?
Should I be able to find this somewhere in the firewall-config menus?
Thanks. _______________________________________________ firewalld-users mailing list firewalld-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/firewalld-users