From: Patrick McHardy <kaber@trash.net>
To: FiloSottile <filosottile.wiki@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Iptables without ipt_state using xt_state
Date: Wed, 13 Jan 2010 09:21:56 +0100 [thread overview]
Message-ID: <4B4D82A4.6000102@trash.net> (raw)
In-Reply-To: <4B4CDEBE.2040304@gmail.com>
FiloSottile wrote:
> Mart Frauenlob ha scritto:
>> what does modprobe -v xt_state say?
>>
> WARNING: Deprecated config file /etc/modprobe.conf, all config files
> belong into /etc/modprobe.d/.
> FATAL: Could not load
> /lib/modules/2.6.18-128.1.1.el5.028stab062.3PAE/modules.dep: No such
> file or directory
> As i said, i am on a OpenVZ VPS, and i cannot modify kernel and modules.
The module needs to be loaded in the initial namespace to
be available in the VPS.
next prev parent reply other threads:[~2010-01-13 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 17:34 Iptables without ipt_state using xt_state FiloSottile
2010-01-12 18:36 ` Mart Frauenlob
2010-01-12 20:42 ` FiloSottile
2010-01-12 22:43 ` Pascal Hambourg
2010-01-13 8:21 ` Patrick McHardy [this message]
2010-01-12 23:02 ` /dev/rob0
-- strict thread matches above, loose matches on Subject: below --
2010-01-13 12:50 FiloSottile
2010-01-16 12:34 ` Mart Frauenlob
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=4B4D82A4.6000102@trash.net \
--to=kaber@trash.net \
--cc=filosottile.wiki@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox