Please support VectorLinux!

Author Topic: Firewall Not Working in VL6.0  (Read 1984 times)

Martin109

  • Vectorite
  • ***
  • Posts: 290
Firewall Not Working in VL6.0
« on: October 02, 2010, 09:26:14 am »
I've used VASM to try and set up the firewall, and I did this by ensuring that firewall was selected under Services for runlevels 4 & 5.

However, when booting up VL6.0, the on-screen message 'Starting the Firestarter firewall: failure' scrolls up.

When I power down the computer, I get the message 'Stopping the Firestarter filewall: success!'

What is happening?
Compaq Armada E500, i686 Pentium III, 512Mb RAM, 3.2 Gb HDD, running Vector Linux 5.9 Standard

Fujitsu Lifebook, i686 Pentium M, 1.7 GHz, 1028Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Compaq Evo, i686 Pentium M, 1.4 GHz, 512Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

bigpaws

  • Vectorian
  • ****
  • Posts: 1868
Re: Firewall Not Working in VL6.0
« Reply #1 on: October 02, 2010, 10:46:23 am »
As root look at /var/log/syslog /var/log/messages they may give you
a clue to the problem.

You can check to see if iptables is running. Open a console, and type:

ps -e | grep iptables

You can look at your iptables rules by using a console and log in as root then type:

iptables -L

HTH

Bigpaws

Martin109

  • Vectorite
  • ***
  • Posts: 290
Re: Firewall Not Working in VL6.0
« Reply #2 on: October 02, 2010, 12:32:02 pm »
As root look at /var/log/syslog /var/log/messages they may give you
a clue to the problem.

You can check to see if iptables is running. Open a console, and type:

ps -e | grep iptables

You can look at your iptables rules by using a console and log in as root then type:

iptables -L

HTH

Bigpaws

Thanks, BP.

Searching the output of /var/log/syslog and /var/log/messages for the strings 'firewall', 'fire' & 'iptables' drew a blank.

Typing ps -e | grep iptables produced no output.

Typing iptables -L gave the following output, which looks like a blank template:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Compaq Armada E500, i686 Pentium III, 512Mb RAM, 3.2 Gb HDD, running Vector Linux 5.9 Standard

Fujitsu Lifebook, i686 Pentium M, 1.7 GHz, 1028Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Compaq Evo, i686 Pentium M, 1.4 GHz, 512Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Martin109

  • Vectorite
  • ***
  • Posts: 290
Re: Firewall Not Working in VL6.0
« Reply #3 on: October 03, 2010, 05:39:27 am »
I see that under 'Menu'>'System', Firestarter is listed.

If I click on this and enter root password, a window opens up, showing 'Firewall Status Active', but whatever I've been doing online during the session, the Inbound and Outbound Events totals stay at zero.
Compaq Armada E500, i686 Pentium III, 512Mb RAM, 3.2 Gb HDD, running Vector Linux 5.9 Standard

Fujitsu Lifebook, i686 Pentium M, 1.7 GHz, 1028Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Compaq Evo, i686 Pentium M, 1.4 GHz, 512Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Martin109

  • Vectorite
  • ***
  • Posts: 290
Re: Firewall Not Working in VL6.0
« Reply #4 on: November 25, 2010, 12:43:18 pm »
Still not got anywhere with this.
Compaq Armada E500, i686 Pentium III, 512Mb RAM, 3.2 Gb HDD, running Vector Linux 5.9 Standard

Fujitsu Lifebook, i686 Pentium M, 1.7 GHz, 1028Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Compaq Evo, i686 Pentium M, 1.4 GHz, 512Mb RAM, 40 Gb HDD, running Vector Linux 6.0 Standard

Andy Price

  • Packager
  • Vectorite
  • ****
  • Posts: 237
Re: Firewall Not Working in VL6.0
« Reply #5 on: November 26, 2010, 03:17:48 am »
Hi. I'm not sure if the grep command is correct as I get no output as a user and an error message as root.

I get lots of output when I run iptables -L, so, as you say, your minimal output suggests that iptables has no rules configured.

Perhaps you can manually add some rules to see if this will kick things into life. See this thread: http://forum.vectorlinux.com/index.php?topic=6040

Andy