public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo iptables problem
Date: Fri, 17 Nov 2006 07:41:30 -0600	[thread overview]
Message-ID: <022b01c70a4e$16d408f0$4ba65c90@vv507j> (raw)
In-Reply-To: <Pine.BSF.4.64.0611170606380.63609@server2.shellworld.net>

Well, I don't know anything about gen2 but it sounds as if the kernel was 
compiled w/o the ip_tables module.  I don't know exactly where that is in 
the kernel config but I would imagine that like any other module, you can 
compile it into the kernel, compile it as a module, or not compile it at 
all. You'd have to check your kernel config.

But you should be able to say 'modinfo ip_tables' and get info about the 
module if it has been built. If modinfo prints a notice that  there is no 
such module, you're going to have to recompile your kernel or download a new 
pre-compiled one.

----- Original Message ----- 
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, November 17, 2006 5:09 AM
Subject: gentoo iptables problem


> running iptables -F in gentoo or any other command so far as I can tell
> other than the help command produces a fatal error claiming the package
> can't find module ip_tables and for that reason iptables can't initialize.
> I got this using using emerge iptables so can't yet figure what's going on
> and why.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jude DaShiell
 ` John Heim [this message]
 Jude DaShiell
 ` Gregory Nowak
   ` John Heim
 Jude DaShiell

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='022b01c70a4e$16d408f0$4ba65c90@vv507j' \
    --to=jheim@math.wisc.edu \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).