Bug 1120450 - iptables rules of NetworkManager are not customizable
Summary: iptables rules of NetworkManager are not customizable
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 19
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-17 00:53 UTC by Rafael
Modified: 2015-02-18 11:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-18 11:46:51 UTC

Attachments (Terms of Use)

Description Rafael 2014-07-17 00:53:02 UTC
Description of problem:
Hello !

I redirect all traffic of my iface to first LOG, and then ACCEPT or DROP.
Recently, i have added a new connection in NM. A shared wifi connection.

To make things "transparent to the user", NM creates itself the necessary rules and add then to iptables. 

The problem is. They are preconfigured rules. I can't modify it to LOG, or do some custom actions.

But NM has support for scripts. Why these rules aren't implemented by scripts ?
The user will get the option to customize these iptables rules.

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

How reproducible:
add a shared wireless connection

Steps to Reproduce:

Actual results:
NM adds fixed rules to iptables. 

Expected results:
I don't know what put here.
But as suggestion, NM may use script capability to hold these rules. Will be a matter of choice, customize these rules or not.

Additional info:
If this is not the correct place to report this, just sorry.
You may (or not) point me the right direction.

Comment 1 Fedora End Of Life 2015-01-09 21:27:31 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-18 11:46:51 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.