On Fri, Oct 4, 2013 at 5:58 PM, Michael Orlitzky mich...@orlitzky.com wrote:
1. The iptables-restore syntax is uglier and harder to read.
I don't get this - the syntax is *chain and then :tables (with
optional counters) instead of -N, and then a bunch of rules, and then
a COMMIT command (the
On 10/13/2013 06:26 AM, shawn wilson wrote:
On Fri, Oct 4, 2013 at 5:58 PM, Michael Orlitzky mich...@orlitzky.com wrote:
1. The iptables-restore syntax is uglier and harder to read.
I don't get this - the syntax is *chain and then :tables (with
optional counters) instead of -N, and then a
On 10/03/2013 08:27 PM, Grant Edwards wrote:
Let's say you wanted to configure routing of TCP packets based on destination
port like in this example:
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.netfilter.html
[which contains a series of 'ip' and 'iptables' commands to get packets
On 10/03/2013 04:28 PM, Kerin Millar wrote:
The iptables runscript is ideal for persisting the rules. However,
during the initial construction of a non-trivial ruleset, I prefer to
write a script that adds the rules. An elegant way of doing this is to
use iptables-restore with a heredoc.
On Fri, 04 Oct 2013 17:58:14 -0400
Michael Orlitzky mich...@orlitzky.com wrote:
On 10/03/2013 04:28 PM, Kerin Millar wrote:
The iptables runscript is ideal for persisting the rules. However,
during the initial construction of a non-trivial ruleset, I prefer
to write a script that adds
Let's say you wanted to configure routing of TCP packets based on destination
port like in this example:
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.netfilter.html
[which contains a series of 'ip' and 'iptables' commands to get packets
destined for port 25 to use a specific gateway.]
On 03/10/2013 20:27, Grant Edwards wrote:
Let's say you wanted to configure routing of TCP packets based on destination
port like in this example:
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.netfilter.html
[which contains a series of 'ip' and 'iptables' commands to get packets
7 matches
Mail list logo