Description: Guarddog is a firewall configuration utility for Linux systems. It is aimed at two groups of users. Novice to intermediate users who are not experts in TCP/IP networking and security, and those users who don't want the hastle of dealing with cryptic shell scripts and ipchains/iptables parameters.Last changelog:
Changes compared to 2.2:
* More protocols: Jabber over SSL, PGP key server, Bittorrent, rsync, distcc, gkrellm, Microsoft Media Server protocol.
This is a great iptables (et al.) configurator! It really makes this as easy as OS X's firewall configuration thinger, and it gives you more control than just that. At first I was slightly confused on the zones concept, but once that clicks, everything makes sense.
Well Done, This is a usefull app that I would love at some stage to spend some time on. Alas I can not see that eventuating so I sincerely hope it gets picked up or updated and upgraded reasonably often. Thankyou!
I installed on SuSE 10.1 upgraded from 9.3 and it installed and ran flawlessly.
Good luck for the future
JmOnKeY
I like guarddog, have been using off Debian Sid. This app must be correctly installed and local "clik" type installations may not cut it.
Because of Sid's current problems, I built kde3.5 with konstruct and must now build kde apps to get it all off Sid.
Guarddog and some other compiles fail is this manner:
:guarddog.cpp:(.text+0x3211): undefined reference to `vtable for GuarddogApp'
guarddog.o: In function `GuarddogApp::~GuarddogApp()':guarddog.cpp:(.text+0x331a): undefined reference to `vtable for GuarddogApp'
guarddog.o:guarddog.cpp:(.text+0x3321): more undefined references to `vtable for GuarddogApp' follow
commandrunner.o: In function `CommandRunner::CommandRunner(QWidget*, char const*)':commandrunner.cpp:(.text+0x300): undefined reference to `vtable for CommandRunner'
:commandrunner.cpp:(.text+0x307): undefined reference to `vtable for CommandRunner'
commandrunner.o: In function `CommandRunner::CommandRunner(QWidget*, char const*)':commandrunner.cpp:(.text+0x5a0): undefined reference to `vtable for CommandRunner'
:commandrunner.cpp:(.text+0x5a7): undefined reference to `vtable for CommandRunner'
commandrunner.o: In function `CommandRunner::~CommandRunner()':commandrunner.cpp:(.text+0x7da): undefined reference to `vtable for CommandRunner'
commandrunner.o:commandrunner.cpp:(.text+0x7e1): more undefined references to `vtable for CommandRunner' follow
collect2: ld returned 1 exit status
How might I fix this? (Using previus gcc from Sid as current one needs the new libc6 which is broken).
And solved my problems with VMware and host only networks. My Linux laptop is a SAMBA server for a VMware virtual machine running XP, but a pure client for everything else.
Using GuardDog to configure my firewall for this was easy. And all my previous attempts had resulted in the host only SAMBA server being blocked as well.
Thanks for this wonderful application!
It's really easy to use and has great documentation (although I miss "What's this?" help).
Now my computer is finally secure. Before Guarddog, I did not have a firewall because it was too complicated to set up.
I was wondering, I am currently preparing to switch my OS over to Suse Linux 9.1 Pro (with KDE 3.2) and was hoping that I could get Guarddog to install and work under Suse. Any suggestions?
I love it. I am pretty new to linux and allows me to set up an effective firewall that I otherwise could not do with my current knowledge of iptables. I did notice that after a reboot I have to reapply the guarddog settings. Would it be possible in future releases to have this done automatically? Other than that the program is perfect for my needs. Thank you.
I had the same problem trying to launch compiled guarddog 2.3.0:
> "An error occurred while reading the protocol database. Details: unable to
open the network protocol database XML file."
The solution is here:
When building it (compiling) you need to pass --prefix=/usr or similar to configure. It depends on where you KDE stuff is installed.
It worked fine to me: './configure --prefix=/usr' and then 'make' and 'make install'
linux2.4.20-28.8
redhat8.0
qt3.0.5
KDE3.0.5
I'm not sure what other info would help, but I get this error when 'make install' with ./configure --prefix=/usr
Making install in protocoldb
make[1]: Entering directory `/home/anubis/guarddog-2.2.0/protocoldb'
/usr/bin/xmllint --noout --valid --dtdvalid protocoldb.dtd networkprotocoldb.xml
http://www.simonzone.com/software/protocoldb/1.0/protocoldb.dtd:1: error: Extra content at the end of the document
^
make[1]: *** [dbvalid] Error 1
make[1]: Leaving directory `/home/anubis/guarddog-2.2.0/protocoldb'
make: *** [install-recursive] Error 1
Not giving ./configure any options I still have the same runtime error as well, in a popup:
An error occured while reading the protocol database.
Details: "Unable to open the network protocol database XML file."
and on the command line:
QFile::open: No file name specified
Seems like an error related to something not being installed above, but I've no idea how to fix it. Providing this feedback in case it helps somehow =)
That's a known error in the nvidia driver. NVidia is already aware of this. I can remember to find the official solution for this problem from NVidia by using google.
Ratings & Comments
16 Comments
easy for use and good for advance unser . Works on Mandriva 2009--->looks at ftp.pbone.net for rpm.
This is a great iptables (et al.) configurator! It really makes this as easy as OS X's firewall configuration thinger, and it gives you more control than just that. At first I was slightly confused on the zones concept, but once that clicks, everything makes sense.
Well Done, This is a usefull app that I would love at some stage to spend some time on. Alas I can not see that eventuating so I sincerely hope it gets picked up or updated and upgraded reasonably often. Thankyou! I installed on SuSE 10.1 upgraded from 9.3 and it installed and ran flawlessly. Good luck for the future JmOnKeY
I like guarddog, have been using off Debian Sid. This app must be correctly installed and local "clik" type installations may not cut it. Because of Sid's current problems, I built kde3.5 with konstruct and must now build kde apps to get it all off Sid. Guarddog and some other compiles fail is this manner: :guarddog.cpp:(.text+0x3211): undefined reference to `vtable for GuarddogApp' guarddog.o: In function `GuarddogApp::~GuarddogApp()':guarddog.cpp:(.text+0x331a): undefined reference to `vtable for GuarddogApp' guarddog.o:guarddog.cpp:(.text+0x3321): more undefined references to `vtable for GuarddogApp' follow commandrunner.o: In function `CommandRunner::CommandRunner(QWidget*, char const*)':commandrunner.cpp:(.text+0x300): undefined reference to `vtable for CommandRunner' :commandrunner.cpp:(.text+0x307): undefined reference to `vtable for CommandRunner' commandrunner.o: In function `CommandRunner::CommandRunner(QWidget*, char const*)':commandrunner.cpp:(.text+0x5a0): undefined reference to `vtable for CommandRunner' :commandrunner.cpp:(.text+0x5a7): undefined reference to `vtable for CommandRunner' commandrunner.o: In function `CommandRunner::~CommandRunner()':commandrunner.cpp:(.text+0x7da): undefined reference to `vtable for CommandRunner' commandrunner.o:commandrunner.cpp:(.text+0x7e1): more undefined references to `vtable for CommandRunner' follow collect2: ld returned 1 exit status How might I fix this? (Using previus gcc from Sid as current one needs the new libc6 which is broken).
And solved my problems with VMware and host only networks. My Linux laptop is a SAMBA server for a VMware virtual machine running XP, but a pure client for everything else. Using GuardDog to configure my firewall for this was easy. And all my previous attempts had resulted in the host only SAMBA server being blocked as well.
User defined port ranges, and bittorrent as well.
Guarddog is easy usefull and convenient. One of the best application.
Thanks for this wonderful application! It's really easy to use and has great documentation (although I miss "What's this?" help). Now my computer is finally secure. Before Guarddog, I did not have a firewall because it was too complicated to set up.
I was wondering, I am currently preparing to switch my OS over to Suse Linux 9.1 Pro (with KDE 3.2) and was hoping that I could get Guarddog to install and work under Suse. Any suggestions?
I love it. I am pretty new to linux and allows me to set up an effective firewall that I otherwise could not do with my current knowledge of iptables. I did notice that after a reboot I have to reapply the guarddog settings. Would it be possible in future releases to have this done automatically? Other than that the program is perfect for my needs. Thank you.
Did you save your settings in Guarddog? It seems to work for me, I don't have to reapply it every time I reboot the machine. Hmmm. Strange.
I had the same problem trying to launch compiled guarddog 2.3.0: > "An error occurred while reading the protocol database. Details: unable to open the network protocol database XML file." The solution is here: When building it (compiling) you need to pass --prefix=/usr or similar to configure. It depends on where you KDE stuff is installed. It worked fine to me: './configure --prefix=/usr' and then 'make' and 'make install'
linux2.4.20-28.8 redhat8.0 qt3.0.5 KDE3.0.5 I'm not sure what other info would help, but I get this error when 'make install' with ./configure --prefix=/usr Making install in protocoldb make[1]: Entering directory `/home/anubis/guarddog-2.2.0/protocoldb' /usr/bin/xmllint --noout --valid --dtdvalid protocoldb.dtd networkprotocoldb.xml http://www.simonzone.com/software/protocoldb/1.0/protocoldb.dtd:1: error: Extra content at the end of the document ^ make[1]: *** [dbvalid] Error 1 make[1]: Leaving directory `/home/anubis/guarddog-2.2.0/protocoldb' make: *** [install-recursive] Error 1 Not giving ./configure any options I still have the same runtime error as well, in a popup: An error occured while reading the protocol database. Details: "Unable to open the network protocol database XML file." and on the command line: QFile::open: No file name specified Seems like an error related to something not being installed above, but I've no idea how to fix it. Providing this feedback in case it helps somehow =)
libtool: link: `/usr/lib/libGL.la' is not a valid libtool archive make[2]: *** [guarddog] Error 1 make[2]: Leaving directory `/root/Download/guarddog-2.3.0/guarddog-2.3.0/guarddog' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/Download/guarddog-2.3.0/guarddog-2.3.0' make: *** [all-recursive-am] Error 2
That's a known error in the nvidia driver. NVidia is already aware of this. I can remember to find the official solution for this problem from NVidia by using google.
application ! Easy, convenient. If you do not intend to be a master of iptable rules then Guarddog may be for you.