From: Joe Giles <jgiles@windowsproof.com>
To: netfilter@lists.netfilter.org
Subject: Re: ipt_time time match invalid size
Date: Thu, 10 Aug 2006 00:30:23 -0600 [thread overview]
Message-ID: <200608100030.23683.jgiles@windowsproof.com> (raw)
In-Reply-To: <001201c6bc3b$1f60fca0$0101000a@tanjian>
On Wednesday 09 August 2006 11:09 pm, Rob Sterenborg wrote:
> > I finally figured out what I was doing wrong with the P-O-M and the
> > time module.
> >
> > Now, after installing the proper modules and running the following
> > iptables command:
> > IPTABLES = path to iptables
> > $IPTABLES -A INPUT -s 192.168.15.131 -m time --timestart
> > 17:05 --timestop 17:20 --days Wed -j RULE_2
> > $IPTABLES -A FORWARD -s 192.168.15.131 -m time --timestart
> > 17:05 --timestop 17:20 --days Wed -j RULE_2
> >
> > (This was just a test script to see how it worked)
> >
> > It doesn't work and I get this error executing the command from
> > within my script:
> >
> > iptables: Unknown error 4294967295
> > iptables: Unknown error 4294967295
> >
> > And, I get this output in dmesg:
> >
> > ip_tables: time match: invalid size 0 != 16
> > ip_tables: time match: invalid size 0 != 16
> >
> >
> > I used the 20060706 of p-o-m-ng and am using the 2.6.17.8
> > kernel. The 20060706 version of p-o-m is the latest with the
> > time module in it and it compiles just fine with the kernel.
> >
> > Does anyone know how I can resolve this issue?
>
> Did you also recompile iptables?
>
>
> Gr,
> Rob
Thanks for the reply...
I found out that there was some API changes in the 2.6.17 kernel that prevent
it from working properly. I downgraded to a 2.6.15 kernel and it is working
as planned.
Thanks for the reply... I will wait for the maintainers to update via p-o-m at
a later date...
Joe
prev parent reply other threads:[~2006-08-10 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 0:02 ipt_time time match invalid size Joe Giles
2006-08-10 5:09 ` Rob Sterenborg
2006-08-10 6:30 ` Joe Giles [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=200608100030.23683.jgiles@windowsproof.com \
--to=jgiles@windowsproof.com \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox