From: Gerry Reno <greno@verizon.net>
To: netfilter@vger.kernel.org
Subject: Re: fwknop: use with Fedora?
Date: Sat, 22 Sep 2007 23:01:46 -0400 [thread overview]
Message-ID: <46F5D71A.1050901@verizon.net> (raw)
In-Reply-To: <46F5C161.7090908@verizon.net>
Gerry Reno wrote:
> Well, I'm just forging ahead. Hopefully someone can answer my
> original question about user chains.
>
> Right now I tried starting the fwknop daemon and was greeted with
> these errors:
>
> # service fwknop start
> Starting the fwknop daemons: Can't load
> '/usr/lib/fwknop/i386-linux-thread-multi/auto/Net/Pcap/Pcap.so' for
> module Net::Pcap: libpcap.so.0.9.4: cannot open shared object file: No
> such file or directory at
> /usr/lib/perl5/5.8.8/i386-linux-thread-multi/DynaLoader.pm line 230.
> at /usr/sbin/fwknopd line 47
> Compilation failed in require at /usr/sbin/fwknopd line 47.
> BEGIN failed--compilation aborted at /usr/sbin/fwknopd line 47.
>
>
> What I have installed is the latest rpm from CipherDyne:
> fwknop-1.8.2-1.i386.rpm
> <http://www.cipherdyne.org/fwknop/download/fwknop-1.8.2-1.i386.rpm>
> and I guess this rpm either doesn't have the right dependencies and
> did not perform something necessary during %post.
>
> help...
>
> Gerry
Well, I found out that the problem is that Fedora 7 has libpcap 0.9.5
installed and fwknop is looking specifically for libpcap 0.9.4. So I
just created a symlink from 0.9.5 to 0.9.4 in /usr/lib. We'll see if
this will work.
----------------------------------
So then we get to the next error:
# service fwknop start
Starting the fwknop daemons: [*] /etc/fwknop/access.conf: source ANY
missing PORT_OFFSET, defaulting to 61000. at /usr/sbin/fwknopd line 2911.
[FAILED]
Ok, so it defaulted to 61000 but then why not start at this point?
----------------------------------
next try:
put in a PORT_OFFSET
# service fwknop start
Starting the fwknop daemons: [*] /etc/fwknop/access.conf: source ANY
missing KNOCK_INTERVAL, defaulting to 60. at /usr/sbin/fwknopd line 2973.
[FAILED]
----------------------------------
next try:
put in a KNOCK_INTERVAL
# service fwknop start
Starting the fwknop daemons: [ OK ]
Finally!
But, when I check the log I see this:
Sep 22 21:57:48 grp-01-00-50 fwknopd: starting fwknopd
Sep 22 21:57:50 grp-01-00-50 fwknopd: flushing existing iptables
IPT_AUTO_CHAIN chains
Sep 22 21:57:50 grp-01-00-50 fwknopd: warning, could not find iptables
state tracking rules in INPUT chain <------- here I think it is
confused about RH/Fedora iptables structure
Sep 22 21:57:50 grp-01-00-50 fwknopd: imported access directives (1
SOURCE definitions).
Sep 22 21:57:50 grp-01-00-50 kernel: device eth0 entered promiscuous mode
Sep 22 21:57:52 grp-01-00-50 setroubleshoot: SELinux is preventing
/sbin/iptables (iptables_t) "write" to /var/log/fwknop/fwknopd.iptout
(var_log_t). For complete SELinux messages. run sealert -l
13ca6c50-c04a-4602-9464-9a01ec6a0ba5
I tried to restorecon -v the file but no luck, still same error.
# ls -l /var/log/fwknop/
total 16
dr-x------ 2 root root 4096 2007-09-22 21:57 errs
-rw-r--r-- 1 root root 0 2007-09-22 22:22 fwknopd.ipterr
-rw-r--r-- 1 root root 0 2007-09-22 22:22 fwknopd.iptout
????
prev parent reply other threads:[~2007-09-23 3:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 0:48 fwknop: use with Fedora? Gerry Reno
2007-09-23 1:29 ` Gerry Reno
2007-09-23 2:27 ` Gerry Reno
2007-09-23 4:30 ` Michael Rash
2007-09-23 12:33 ` Gerry Reno
2007-09-23 12:40 ` Gerry Reno
2007-09-23 13:28 ` Gerry Reno
2007-09-23 13:47 ` Gerry Reno
2007-09-23 13:53 ` Gerry Reno
2007-09-23 14:17 ` Gerry Reno
2007-09-23 15:17 ` Gerry Reno
2007-09-24 0:43 ` Michael Rash
2007-09-23 16:26 ` Gerry Reno
2007-09-23 23:50 ` Gerry Reno
2007-09-24 1:44 ` Gerry Reno
2007-09-24 2:47 ` Gerry Reno
2007-09-24 0:16 ` Michael Rash
2007-09-24 0:10 ` Michael Rash
2007-09-23 3:01 ` Gerry Reno [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46F5D71A.1050901@verizon.net \
--to=greno@verizon.net \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.