Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 24915
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Martin Holzer (RETIRED) <mholzer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Roger Luethi <rl@hellgate.ch>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 24915 depends on: Show dependency tree
Bug 24915 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-07-20 13:44 0000
guarddog uses some shell scripting to determine whether to
use ipchains or iptables. The relevant code in /etc/rc.firewall
looks like this:

if [ -e /proc/sys/kernel/osrelease ]; then
  KERNEL_VERSION=`sed "s/^\([0-9][0-9]*\.[0-9][0-9]*\).*\$/\1/" < /proc/sys/kern
el/osrelease`
  if [ $KERNEL_VERSION == "2.5" ]; then
    KERNEL_VERSION="2.4"
  fi;
  if [ $KERNEL_VERSION == "2.4" ]; then
    if [ -e /sbin/iptables ]; then
      FILTERSYS=2
    fi;
    if [ -e /usr/sbin/iptables ]; then
      FILTERSYS=2
    fi;
    if [ -e /usr/local/sbin/iptables ]; then
      FILTERSYS=2
    fi;
  fi;
fi;

Obviously, this doesn't work for the recent 2.6.0-test1 kernel.

Reproducible: Always
Steps to Reproduce:
1. start guarddog
2. set some rules
3. hit "Apply" button

Actual Results:  
ERROR Can't determine the firewall command! (Is ipchains or iptables installed?)

------- Comment #1 From Martin Schlemmer (RETIRED) 2003-07-21 08:41:49 0000 -------
Hopefully you actually use this, as you commited last few versions Martin.

------- Comment #2 From Roger Luethi 2003-07-29 01:22:16 0000 -------
It's getting fixed upstream.

------- Comment #3 From Roger Luethi 2003-08-11 01:13:39 0000 -------
2.1.7 was just released and has it fixed (according to the announcement).

------- Comment #4 From Martin Holzer (RETIRED) 2003-08-11 12:31:22 0000 -------
added, thx

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug