All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: "Alessandro Suardi" <alessandro.suardi@gmail.com>
Cc: "Maurice Volaski" <mvolaski@aecom.yu.edu>,
	"Harald Welte" <laforge@netfilter.org>,
	linux-kernel@vger.kernel.org
Subject: Re: iptables is complaining with bogus unknown error 18446744073709551615
Date: Sat, 22 Apr 2006 12:59:59 +0100	[thread overview]
Message-ID: <200604221259.59503.nick@linicks.net> (raw)
In-Reply-To: <5a4c581d0604211705k6fa253at658fe8c321f1bc13@mail.gmail.com>

On Saturday 22 April 2006 01:05, Alessandro Suardi wrote:
> On 4/21/06, Nick Warne <nick.warne@gmail.com> wrote:
> > I also ask the same - this 'config' problem/option has been posted on
> > the list previously, I believe.
> >
> > I was about to update my gateway box to 2.6.16.9 this weekend, and I
> > do not build modules on that - so what do I need to do to ensure this
> > xt_tcpudp is built in?
> >
> > Is '> make oldconfig' enough to pull this in?
> >
> > Nick
>
> Hmm, let's see:
>
> [asuardi@donkey src]$ grep tcpudp
> linux-2.6.17-rc1-git4/net/netfilter/Makefile
> obj-$(CONFIG_NETFILTER_XTABLES) += x_tables.o xt_tcpudp.o
>
> OK, I recall configuring this a while ago when still using FC3,
>  as I was bitten too by iptables complaining with the bogus
>  error code which I eventually tracked back to the XTABLES
>  stuff (no - make oldconfig didn't do it for me and I had to go
>  through the config options by hand enabling what I thought
>  was useful). That was since...
>
> [asuardi@donkey src]$ grep -i XTABLES /fc3/usr/src/.config-2.6.1[0-7]*
> /fc3/usr/src/.config-2.6.15-git10:CONFIG_NETFILTER_XTABLES=m
> /fc3/usr/src/.config-2.6.15-git11:CONFIG_NETFILTER_XTABLES=m
> /fc3/usr/src/.config-2.6.16-rc1-git4:CONFIG_NETFILTER_XTABLES=m
> /fc3/usr/src/.config-2.6.16-rc2-git7:CONFIG_NETFILTER_XTABLES=m

OK, to confirm, 'make oldconfig' did indeed pull in the new XTABLES stuff 
without modules.  I presume this will work OK, as my 233MHz box is still 
building (and will be for a few hours yet)...

Nick

-- 
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb

  reply	other threads:[~2006-04-22 20:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  6:21 iptables is complaining with bogus unknown error 18446744073709551615 Maurice Volaski
2006-04-21 11:15 ` Harald Welte
2006-04-21 11:15   ` Harald Welte
2006-04-21 14:22   ` Maurice Volaski
2006-04-21 14:22     ` Maurice Volaski
     [not found]   ` <a06230913c06e96f75f32@129.98.90.227>
2006-04-21 18:26     ` Nick Warne
2006-04-22  0:05       ` Alessandro Suardi
2006-04-22 11:59         ` Nick Warne [this message]
     [not found] <200604210738.k3L7cBGO010103@mailgw.aecom.yu.edu>
2006-04-27  1:12 ` Maurice Volaski
2006-04-27 13:51   ` Harald Welte
2006-04-27 15:41     ` Maurice Volaski
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13 23:19 Maurice Volaski
     [not found] <200604111452.k3BEpxdo019103@mailgw.aecom.yu.edu>
2006-04-11 17:14 ` Maurice Volaski
     [not found] ` <a06230909c06193cea962@129.98.90.227>
     [not found]   ` <876ef97a0604111146m742d75f0gb8240e82ba7426f1@mail.gmail.com>
2006-04-11 19:13     ` Maurice Volaski

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=200604221259.59503.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=alessandro.suardi@gmail.com \
    --cc=laforge@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvolaski@aecom.yu.edu \
    /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.