netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dan Noé" <dpn@isomerica.net>
To: Ignacy Gawedzki <lkml@qult.net>, linux-kernel@vger.kernel.org
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: TUN/TAP hacking
Date: Wed, 23 Jul 2008 22:25:28 -0400	[thread overview]
Message-ID: <4887E818.4020305@isomerica.net> (raw)
In-Reply-To: <20080723235514.GA8992@zenon.in.qult.net>

Ignacy Gawedzki wrote:
> I need some advice from network stack experts, so I hope this is the right
> place to ask.

The Linux kernel networking folks hang out at netdev
(netdev@vger.kernel.org).  I've CC'd them...

> I thought I'd be able to use the TAP interfaces to create some sort of a
> network emulator.  For a start I just "bridged" two tap interfaces, much in
> the same way as the example of br_select.c from http://vtun.sf.net , assigned
> both interfaces different IPv4 addresses (both with a /32 prefix), set them up
> and tried to transmit a UDP packet from one address to the other through the
> bridge.  Both logs from my bridge program and tcpdump tell me that the packets
> are flowing as expected, but somehow the destination process doesn't get the
> packets (despite all correct bind, etc).
> 
> Is it simply that the stack inconditionally drops any packet with the same
> source (IP and/or MAC) address as some local interface?
> 
> As ARP resolution seems not to work either (I had to put permanent entries in
> the neighbor table), I suppose this is the case indeed.
> 
> Could anyone confirm that? (please CC me, I've not subscribed)
> 
> Thanks,
> 
> Ignacy
> 


-- 
                    /--------------- - -  -  -   -   -
                    |  Dan Noé
                    |  http://isomerica.net/~dpn/

       reply	other threads:[~2008-07-24  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080723235514.GA8992@zenon.in.qult.net>
2008-07-24  2:25 ` Dan Noé [this message]
2008-07-24  6:50   ` TUN/TAP hacking Marek Kierdelewicz
2008-07-24  8:34     ` Ignacy Gawedzki

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=4887E818.4020305@isomerica.net \
    --to=dpn@isomerica.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@qult.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).