All of lore.kernel.org
 help / color / mirror / Atom feed
From: "plamen .." <paco078@abv.bg>
To: xen-devel@lists.xensource.com
Subject: XEN and ipq_read
Date: Tue, 27 Apr 2010 11:31:33 +0300 (EEST)	[thread overview]
Message-ID: <340661326.4879.1272357093666.JavaMail.apache@mail21.abv.bg> (raw)

 Hi all,

I'm using Ubuntu Hardy, Xen version 3.2.1-rc1-pre, Dom0 kernel 2.6.24-27-xen, PV DomU kernel 2.6.24-27-xen. 

I'm setting DomU as a router having iptables 1.3.8. I put an IDS system Snort in inline mode (IPS) on the router, which is configured to retrieve specific packets from kernel (iptables ... -j QUEUE and ip_queue module). At first snort started to report errors on each received packet. After a little bit of debugging and doing a sample application to test ipq_read() I found that raw data sent from kernel contains about 24 bytes more than expected. The additional bytes are in the meta data structure before the real packet content. This breaks raw data parsing. After a little bit of additional debugging I noticed that this happens only on Xen DomU VMs. On Dom0 it work fine, on other servers not running Xen it works also fine. 

Currently I'm about to install rtr DomU as HVM and I think it will work fine, but I don't want to leave it like this in production. 

Is there any reason in xen kernel to break sending packets from kernel to user space through the ip_queue module ? If so is there any way to work around this issue ?

Thanks in advance,
Plamen

             reply	other threads:[~2010-04-27  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  8:31 plamen .. [this message]
2010-04-27  9:05 ` XEN and ipq_read Pasi Kärkkäinen

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=340661326.4879.1272357093666.JavaMail.apache@mail21.abv.bg \
    --to=paco078@abv.bg \
    --cc=xen-devel@lists.xensource.com \
    /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.