Guarddog 1.9.6

[m3rlin]

After installation, i try to run the firewall, and this error appear:
"An Error Ocurred While Reading The Protocol Database
Details: "Unable to open the network protocol database XML file"

And in the shell: Qfile:pen: No file name specified
KCrash: crashing... crashrecursioncounter =2
KCrash: Application name = guarddog path = <unknown> pid = 1184
Unable to start dr.Knoqi

What could be worng here??!
Thanks for all the help

[Ludootje]

I have *exactly* the same problem. I suppose it's because guarddog is written for KDE2, but I'm not sure. I've mailt the author, but he didn't respond. Does anyone else know how to fix this problem, or if guarddog works under KDE3 too?

[razor_01]

There are versions of guarddog that work with KDE2 and KDE3. Make sure that you have the version for your distro and the KDE that you have.

[Ludootje]

Thanks for the info. I just compiled guarddog for KDE3 with these configure options:
./configure --prefix=/usr/bin --with-kde-version=3
However, when I try to start it, I get an error dialog.
I include a screenshot of th errors, in the hope that someone can help me out.

[m3rlin]

well, i downloaded guarddog 2.0, and its working just fine, but i can't seam to install the watchdog, its returning errors while compiling :(

[Ludootje]

Originally posted by m3rlin
well, i downloaded guarddog 2.0, and its working just fine, but i can't seam to install the watchdog, its returning errors while compiling :(
Could you tell me with which configure options you compiled guarddog, on what kde version, and if you run it as root or as normal user?

For watchdog:
from http://www.simonzone.com/software/watchdog:
"24 November, 2001 - No real news, just a note to say that Watchdog doesn't work with Linux 2.4 kernels. Support is planned of course. The Watchdog project is alive, but sleeping. All of my development time is going to Guarddog at the moment. Once Guarddog version 2.0 is released I intend to give Watchdog some much needed attention. - SBE"
In 2001 KDE3 wasn't released yet, so if you use that KDE version I suppose that's the reason. And if you use a 2.4.x kernel, it won't work neither apparently...

[m3rlin]

well i did, ./configure --prefix=/opt/kde2
with the user, and make, and then as root make install
and it worked just fine

to load at startup i edited the /etc/rc.d/boot.local
and wrote this
# Guarddog Startup
if [ -r /etc/rc.firewall ]; then
. /etc/rc.firewall
fi

# End of Guarddog Startup

[Ludootje]

Originally posted by m3rlin
well i did, ./configure --prefix=/opt/kde2
with the user, and make, and then as root make install
and it worked just fine

to load at startup i edited the /etc/rc.d/boot.local
and wrote this
# Guarddog Startup
if [ -r /etc/rc.firewall ]; then
. /etc/rc.firewall
fi

# End of Guarddog Startup
Thanks!
Sorry for asking so much questions, but I really want to get it working :)
Next question: how do you start the GUI to configure the firewall?

[Ludootje]

Guarddog is started using the script /etc/init.d/guarddog (automatically made by guarddog):


#! /bin/sh

PATH=/sbin:/bin:/usr/sbin:/usr/bin
NAME=guarddog

#test -f /etc/rc.firewall || exit 0

if [ ! -f /etc/rc.firewall ]; then
echo "Unable to start guarddog firewall - /etc/rc.firewall does not exist"
exit 0
fi

set -e

case "$1" in
start|restart|reload|force-reload)
echo -n "Setting up guarddog firewall..."
. /etc/rc.firewall
echo "done."
;;
stop)
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|restart|reload|force-reload}" >&2
exit 1
;;
esac

exit 0


and yes, /etc/rc.firewall exists - it's generated by guarddog too apparently, from the top of the file:


#!/bin/bash
# [Guarddog2]
# DO NOT EDIT!
# This firewall script was generated by "Guarddog" by Simon Edwards
# http://www.simonzone.com/software/guarddog/ This script requires Linux
# kernel version 2.2.x and ipchains OR Linux kernel 2.4.x and iptables.


Also, from the messages which are printed on the screen on boot, I know that the guarddog firewall starts just fine. Now all I need is the GUI to configure the firewall.

All the commands with which I can run /etc/init.d/guarddog work fine too, without printing out an error msg:


{root@~} /etc/init.d/guarddog start
Setting up guarddog firewall...done.
{root@~} /etc/init.d/guarddog restart
Setting up guarddog firewall...done.
{root@~} /etc/init.d/guarddog reload
Setting up guarddog firewall...done.
{root@~} /etc/init.d/guarddog force-reload
Setting up guarddog firewall...done.
{root@~}

[m3rlin]

you can run the file "guarddog" as root then all the options will appear, and you can configure the firewall

[Ludootje]

Originally posted by m3rlin
you can run the file "guarddog" as root then all the options will appear, and you can configure the firewall
Well that's the problem I'm having.
See the fourth post of this topic please, it explains the error I get when I try that.

[m3rlin]

Ludootje you are probably using a old version of Guarddog. Try to use the 2.0, it worked for me, no problems with it

[Ludootje]

Nope, I'm using 2.0. My tarball isn't corrupted neither, the md5sum corresponds.
Am I the only one with this problem? The author doesn't reply apparently :(

[m3rlin]

what is your distro?
Did you already read the requierments? and did you installed guarddog with out problems?

did you used the prefix "./configure --prefix=/opt/kde2/include"
this if your using the Kde2 of course!

[Ludootje]

Originally posted by m3rlin
what is your distro?
Did you already read the requierments? and did you installed guarddog with out problems?

did you used the prefix "./configure --prefix=/opt/kde2/include"
this if your using the Kde2 of course!
Libranet (Debian based).
I used this:
./configure --prefix=/usr/bin --with-kde-version=3
I have KDE3 of course. Installing went fine. I'll uninstall it & reinstall it without a prefix in the hope it works, although I seriously doubt about it.

I don't see requirements anywhere on the site.
Reading trough the README at the moment.

There's this:

gawk !!! Attn: Debian Users !!!
-------------------------------
Guarddog needs gawk to be installed in order to operate. Debian installs awk
by default and not gawk. Make sure you install the gawk deb. If you see
an error message like "awk: ... function gensub never defined" then you
forgot to install gawk.

I have gawk installed though.

There's this too:

* Debian:

I have a report that:

make install prefix=/usr

is what you should use.

... which I didn't do. I'll try that now, and hope it works.

BTW I have iptables (v1.2.7a) and a 2.4 kernel (2.4.19).


Thanks a lot for taking the time to help me.
Who knows, maybe the 'make install prefix=/usr' will make it work...

[Ludootje]

IT WORKED!!! with the 'make install --prefix=/usr' it worked just fine!!!

Thanks for all the time you spent helping me.

edit:

Just set up iptables, and I had this output:
---
Using iptables.
Resetting firewall rules.
Loading kernel modules.
modprobe: Can't locate module ip_conntrack_ftp
modprobe: Can't locate module ip_conntrack_irc
Setting kernel parameters.
Configuring firewall rules.
Finished.
---
So it works perfectly :) Just need to compile 2 more modules apparently. I'm so happy :)

[m3rlin]

Please post here the results! Of couse when you use the prefix for the KDE, you must make sure that is pointed to the libs
something like "--prefix=/opt/kde2/include", if you don't point all the path, it won't work.
Hope i can install that, this firewall kicks ***!

[Ludootje]

Originally posted by m3rlin
Please post here the results! Of couse when you use the prefix for the KDE, you must make sure that is pointed to the libs
something like "--prefix=/opt/kde2/include", if you don't point all the path, it won't work.
Hope i can install that, this firewall kicks ***!
Err? What results? Sorry I don't see what you mean...
The prefix doesn't have to be added to ./configure as long as you use the default dirs I think (/opt isn't the default, you shouldn't even have an /opt AFAIK).

[m3rlin]

I ment to say, the results of your installations!

The prefix doesn't have to be added to ./configure as long as you use the default dirs I think (/opt isn't the default, you shouldn't even have an /opt AFAIK).

Im using Suse 7.3 and to install i had to prefix de the directory, just like this "./configure --prefix=/opt/kde2/include"

Only with this prefix i was able to install the Guarddog.You should try it!

[Ludootje]

Originally posted by m3rlin
I ment to say, the results of your installations!

The prefix doesn't have to be added to ./configure as long as you use the default dirs I think (/opt isn't the default, you shouldn't even have an /opt AFAIK).

Im using Suse 7.3 and to install i had to prefix de the directory, just like this "./configure --prefix=/opt/kde2/include"

Only with this prefix i was able to install the Guarddog.You should try it!
Well yes, you needed the prefix because SuSE doesn't use KDE's default install directories in its RPMs.
The results of my installation... well it worked.

I don't understand what guarddog does exactly though - if I block IRC & ICQ, kxicq & xchat can still connect. Does anyone know if guarddog only blocks incoming IRC & ICQ connections when I select those two?

[m3rlin]

quote: Does anyone know if guarddog only blocks incoming IRC & ICQ connections when I select those two?

Guarddog blocks incoming and outgoing, when you execute the guarddog you will see "Zone" here you have "local" and "internet"

if you select internet, and start your configuration, let's say, that you wish to block the irc.In the internet you are blocking your self!all the configs(internet) are protocols served from internet to you(client)

And the Local, is what you want to internet to acess to your computer!Let's say SSH, in the "local" you must allow the SSH protocol so that you can acess your computer from the internet!

[Ludootje]

Originally posted by m3rlin
quote: Does anyone know if guarddog only blocks incoming IRC & ICQ connections when I select those two?

Guarddog blocks incoming and outgoing, when you execute the guarddog you will see "Zone" here you have "local" and "internet"

if you select internet, and start your configuration, let's say, that you wish to block the irc.In the internet you are blocking your self!all the configs(internet) are protocols served from internet to you(client)

And the Local, is what you want to internet to acess to your computer!Let's say SSH, in the "local" you must allow the SSH protocol so that you can acess your computer from the internet!
Thanks!! I thought it was completely different:
'internet' for all incoming and outgoing connections with/from the internet; and 'local' for intranets.
That explains it. Thank you :)

[m3rlin]

:D i thought that too, and i was getting crazy,lol. Enjoy the firewall! No problem man, ask stuff at anytime!
Just like me :)