Yes the setting in shorewall.conf will override the setting in sysctl.conf.
You can set IP_FORWARDING=KEEP so that it will keep whatever the setting is for ip_forwarding. On Thu, Aug 1, 2013 at 3:24 PM, Timothy Murphy <[email protected]> wrote: > I'm running shorewall on two CentOS servers in different countries, > both running shorewall 4.5.4 under CentOS-6.4. > > I noticed today that one of the servers has ip_forward set > [tim@alfred ~]$ sudo sysctl net.ipv4.ip_forward > net.ipv4.ip_forward = 1 > while the other has it unset. > > Both have > IP_FORWARDING=On > in /etc/shorewall/shorewall.conf . > > Does this setting over-ride the sysctl setting? > Or do they have different effects? > > -- > Timothy Murphy > e-mail: gayleard /at/ eircom.net > tel: +353-86-2336090, +353-1-2842366 > School of Mathematics, Trinity College, Dublin 2, Ireland > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
