knetfilter
Knetfilter is a KDE frontend to iptables. It is used with Linux 2.4 to manage the functionality of netfilter. Knetfilter lets you set up most common firewall configurations, as well as perform more sophisticated management of a complex firewall. It is also possible to use an integrated interface to tcpdump and nmap.
| Tags | Desktop Environment KDE Networking |
|---|---|
| Licenses | GPL |
Recent releases
- 27 Jul 2006 05:28
Changes: Some typos were corrected.
- 15 Dec 2005 03:49
Changes: This release was tested to compile cleanly with KDE 3.5 and GCC 4.0.
- 26 Apr 2005 03:59
Changes: Icons have been renamed to avoid name collisions.
- 09 Dec 2004 07:02
Changes: Since netfilter modules are now partially autoloaded, the initial checks were updated.
- 30 Aug 2004 08:32
Changes: Support for the SAME target has been implemented in NAT chains. The README.first file has been updated.
- All comments
Recent commentsRHEL4 build problem?
Have knetfilter-3.5.1 on CentOS4.4
unfortunately, when I make
# rpmbuild -tb knetfilter-3.5.1.tar.gz
it makes a lot of errors during creating result package and stops
Could you please fix this spec file?
Re: Problem installing
the user who is compiling knetfilter has not iptables in his path
> When I do ./configure I get the
> following error at the end:
> checking for iptables... not found
> configure: error: No iptables found.
> yet iptables are there (version v1.2.8,
> in /sbin)
> I am using Fedora core 1.
> Do you know what the problem is?
>
Re: Problem installing
solved in 3.3.1 (my mistake, usualli iptables are
somewhere else)
> When I do ./configure I get the
> following error at the end:
> checking for iptables... not found
> configure: error: No iptables found.
> yet iptables are there (version v1.2.8,
> in /sbin)
> I am using Fedora core 1.
> Do you know what the problem is?
>
Problem installing
When I do ./configure I get the following error at the end:
checking for iptables... not found
configure: error: No iptables found.
yet iptables are there (version v1.2.8, in /sbin)
I am using Fedora core 1.
Do you know what the problem is?
Re: documentation...
Actually reverse resolution is not done anymore as default, and it is optional, if users do want it and they know their DNS works for every ip address.
This is the new default I will use for every monitor.
About inserting rules, you should use ip, not hostnames.
> Give users the option to resolve the
> ipnumbers to hostnames with some
> commentary that it can be slow if the
> dns is busy / ofline. Maybe let the user
> set the timeout ?
>
> Greetz
>
> % I do need help for documentation.
> % My first problem is that, not being
> % english, I have difficoulties to
> write
> % some good documentation stuff.
> % My second problem is that as the
> % coder, I am quite busy in updates and
> % bug fixes, and I have difficoulties,
> % since I
> % am quite alone to find the time for
> % user documentation.
> %
> % I am interested about your first
> % remark. I never saw knetfilter stop
> % while executing some command. It
> could
> % take some time to list rules of
> % something else, but this is not a
> % knetfilter bug, since it tries to
> % revolve numeric addresses.
> % Infact I do manage just numeric
> % addresses, but they are resolved to
> give
> % the host names for the rules listing
> or
> % similar. If your DNS cannot resolve
> some
> % address, knetfilter has to timeout to
> go
> % to next rule and so on.
> % Should I avoid this, and give just
> % numeric haddresses?
> %
>
>
>