All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Higgins <dhiggins@ngenera.com>
To: netfilter@vger.kernel.org
Subject: Re: Troubles doing transparent proxy for virtual machines
Date: Thu, 03 Jun 2010 17:59:02 -0500	[thread overview]
Message-ID: <4C0833B6.3040009@ngenera.com> (raw)
In-Reply-To: <20100603232041.7b18a208@catlap>


On 06/03/2010 04:20 PM, Marek Kierdelewicz wrote:
> Hi,
>
>    
>> I guess what's confusing me is that everything runs on the same box.
>>      
> Yup. Packet traverses nat table when it passes bridge and it cannot
> traverse this table second time entering virbr0 interface.
>
> Try this:
> echo 0>  /proc/sys/net/bridge/bridge-nf-call-iptables
>    

Thanks for the response. I'm beginning to think that my strategy here is 
all wrong to begin with. Here's why:

1. The subnet for my VMs is 192.168.122.0/24. This is created by 
libvirtd when it starts up.

2. I start up Firefox in a VM, then go to google.com.

3. As I watch with tcpdump, I never even see 192.168.122.x in the output.

Maybe libvirtd is doing its own network voodoo before handing off to the 
kernel network stack.  [Shrug]  Should I expect tcpdump to show packets 
coming through a bridge (virbr0 or just br0)?

This is still pretty deep water to me.


  reply	other threads:[~2010-06-03 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 21:01 Troubles doing transparent proxy for virtual machines Dan Higgins
2010-06-03 21:20 ` Marek Kierdelewicz
2010-06-03 22:59   ` Dan Higgins [this message]
2010-06-04  6:27     ` Marek Kierdelewicz
  -- strict thread matches above, loose matches on Subject: below --
2010-05-27 19:39 Dan Higgins

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=4C0833B6.3040009@ngenera.com \
    --to=dhiggins@ngenera.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 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.