Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Arash Yadegarnia <arash@bluehome.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: FWDing packets from a physical interface to a virtual interface
Date: Wed, 12 Sep 2007 08:45:17 -0300	[thread overview]
Message-ID: <46E7D14D.90603@solutti.com.br> (raw)
In-Reply-To: <1189596770.5995.11.camel@Thinkpad>

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]



    So maybe you'll have to some bridging stuff and not 
netfilter/iptables ones ....

    iptables/netfilter deals basically with Layer 3 (IP) packets and not 
layer 2 frames, which are the ones you're interested.

Arash Yadegarnia escreveu:
> Thanks Jorge,
>
> I'm not using any specific VPN solution, Me and my colleagues are
> developing a secure VPN solution based on kernel TUN/TAP driver.
> Since we have full control over our tap interface we just need to
> redirect the whole traffic coming into the eth0 (from a LAN) into the
> tap interface, so we can read them (I mean Ethernet frames in Layer 2)
> and send them out from the other pysical interface (eth1).
> BTW, Redirecting a single or even multiple ports won't work in my
> situation, because I want whole traffic in layer 2, not a specific port
> number.
>
> Thanks,
> Arash
>   

-- 


	Atenciosamente / Sincerily,
	Leonardo Rodrigues
	Solutti Tecnologia
	http://www.solutti.com.br

	Minha armadilha de SPAM, NÃO mandem email
	gertrudes@solutti.com.br
	My SPAMTRAP, do not email it





[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 5672 bytes --]

      reply	other threads:[~2007-09-12 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 22:36 FWDing packets from a physical interface to a virtual interface Arash Yadegarnia
2007-09-12  1:40 ` Jorge Davila
2007-09-12 11:32   ` Arash Yadegarnia
2007-09-12 11:45     ` Leonardo Rodrigues Magalhães [this message]

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=46E7D14D.90603@solutti.com.br \
    --to=leolistas@solutti.com.br \
    --cc=arash@bluehome.net \
    --cc=netfilter@lists.netfilter.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