On 6/16/10 9:14 PM, John Brendler wrote: > > I would be appreciative of any insight into what is going on here. >
First of all, you can most likely work around this problem by executing
this command:
shorewall show -f capabilities > /etc/shorewall/capabilities
After that, 'shorewall start' should work.
As to what is going wrong here, nothing you included in your post gives
me a clue.
- I personally use ipsets under Shorewall 4.4.10 and it works fine.
- Since 4.2.11, we've added an IPSET option in shorewall.conf; please
try setting that to the path to your ipset binary and see if that
corrects the problem.
- If that doesn't work then you will need to do a little debugging:
shorewall check -d
The Perl debugger will prompt you; at the prompt, enter:
b Shorewall::Config::IPSet_Match
then
c
When the debugger prompts again, enter 'n' at each prompt until
the IPSET_Match subroutine is exited; then enter 'c'.
Capture the debugging session via copy/paste and send it to me.
Thanks,
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
