Linux Container Development
 help / color / mirror / Atom feed
From: Jean-Marc Pigeon <jmp-4qkeo2rQ0gg@public.gmane.org>
To: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: iptables in container, wrong log destination, need pointer
Date: Thu, 11 Feb 2010 09:32:26 -0500	[thread overview]
Message-ID: <1265898746.19130.119.camel@Mercier.safe.ca> (raw)

Hello,


	I have containerized syslog, such each container has its
	own syslog.

	Container can have their own set of iptables rules.
	
	I was expecting CONT: iptables log report to be
	send to the CONT: syslog, which is not the case,
	they are rather sent to HOST: syslog.

	This means to me, iptables rules are containerized,
	but the execution is NOT (CONT: rules are checked
	within the HOST: context, not the CONT: context).

	Could somebody give me hint where I should look
	in the code, to have a better understanding about
	what is happening?

-- 
A bientôt
==========================================================================
Jean-Marc Pigeon                                   Internet: jmp@safe.ca
SAFE Inc.                                          Phone: (514) 493-4280
                                                   Fax:   (514) 493-1946
        Clement, 'a kiss solution' to get rid of SPAM (at last)
           Clement' Home base <"http://www.clement.safe.ca">
==========================================================================

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

             reply	other threads:[~2010-02-11 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 14:32 Jean-Marc Pigeon [this message]
     [not found] ` <1265898746.19130.119.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-02-11 17:51   ` iptables in container, wrong log destination, need pointer Serge E. Hallyn

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=1265898746.19130.119.camel@Mercier.safe.ca \
    --to=jmp-4qkeo2rq0gg@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.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