Tom Eastep wrote:
> On 05/04/2013 05:21 PM, Dash Four wrote:  
>   
>> That explains it then, though I think this behaviour is wrong - 
>> shorewall should be capable of doing the same checks when a custom 
>> config directory is specified and then make a decision on whether to 
>> compile or not.
>>     
>
> The ability to specify a directory on the command line is intended to be
> used for temporary or test configurations. I disagree that there is any
> need to honor AUTOMAKE for such configurations and, in fact, I think it
> would be a detriment. If I have a special configuration that I use
> infrequently, honoring AUTOMAKE with that configuration would probably
> result in an attempt to restart using the config to be ignored.
>   
I disagree. If I am running shorewall using custom configuration 
directory (as was the case with me for the past 2+ years), then I need 
to specify this and expect all shorewall.conf options to be honoured.

As you know, on all my dmz machines I am running live images, which 
have, essentially, read-only root (including the "default" 
/etc/shorewall) - when any changes, even though preserved in ram for the 
duration of the OS session, are lost on reboot and that is the main 
reason for using custom shorewall config directory.

Anyway, I am getting something odd since I've started using 
shorewall-init - during boot I see this (this is from /var/log/boot.log):

Bringing up loopback interface:  SIOCADDRT: Network is unreachable
SIOCADDRT: Network is unreachable

I can't see any problems accessing the loopback device and the routes in 
'local' seems OK, so I am a bit bemused by this message. Any ideas?

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to