On Thursday, August 01, 2013 04:02:29 PM johnny bowen wrote: > > IP_FORWARDING=On > > > > in /etc/shorewall/shorewall.conf . > > > > Does this setting over-ride the sysctl setting? > > Or do they have different effects?
> 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. Thanks for the response. But what exactly do you mean by "the setting for ip_forwarding"? Do you mean the sysctl.conf setting? And as a matter of interest, why would the IP_FORWARDING setting change? As it happened, it seemed as though IP forwarding was _not_ working on my CentOS server with IP_FORWARDING=On, even after re-starting shorewall (and powering the router on and off). That was with net.ipv4.ip_forward = 0. But after changing this with sudo sysctl -w net.ipv4.ip_forward=1 the problem seemed to go away. Is that plausible? -- 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
