I'm running a Debian (sid) box, with shorewall & shorewall6

When I boot (or bounce an interface) I'm seeing the following error:
/usr/share/shorewall/lib.base: line 182: /lib.common: No such file or directory

It appears to happen on any interface.

An example:
        $ sudo ifdown eth2
        /usr/share/shorewall/lib.base: line 182: /lib.common: No such file or 
directory
        Shorewall6 down triggered by eth2
        Shorewall6 attempting restart
        /usr/share/shorewall/lib.base: line 182: /lib.common: No such file or 
directory
        Shorewall6 down triggered by eth2
        Shorewall6 attempting restart

(The message is nearly identical when I ifup the interface)

The "obvious" problem to me was that shorewall couldn't find lib.common 
- but it is there on my filesystem:
        $ locate lib.common
        /home/ttelford/src/shorewall/Shorewall-core/lib.common
        /usr/share/shorewall/lib.common

The odd thing is I'm not seeing any problems when I run 'shorewall 
restart' or 'shorewall6 restart'

I'm using the following version of shorwall (including package versions):
        ii  shorewall                            4.4.27.2-1
        ii  shorewall-doc                        4.4.27-1
        ii  shorewall-init                       4.4.27.2-1
        ii  shorewall6                           4.4.27.2-1

I've also tried re-installing the packages (in case there was file 
corruption).  There was no effect when I reinstalled the packages.

Any ideas?
-- 
Troy Telford



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to