From: jhautbois@gmail.com
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridging partially (rx eth0 -> tx eth1)
Date: Tue, 15 Dec 2009 09:32:38 +0000 [thread overview]
Message-ID: <001636025d9729a369047ac1127f@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Hi there,
I'm new on the mailing list, but this is not a good reason to be quiet :-).
I'm very interested in the bridging functionnality of the Linux kernel.
I am wondering f it is possible to bridge "partially".
I mean : I would like to have all the traffic from the RX of my eth1 card
directly sent out through the TX of my eth0 card.
But I would like to receive the frames from the RX of eth0 thanks to a
PF_PACKET socket.
Is this possible with the bridging system ?
I don't think so, but I haven't foud out the answer...
Thanks in advance !
Best Regards.
JM
[-- Attachment #2: Type: text/html, Size: 661 bytes --]
next reply other threads:[~2009-12-15 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 9:32 jhautbois [this message]
2009-12-15 16:28 ` [Bridge] Bridging partially (rx eth0 -> tx eth1) richardvoigt
2009-12-15 16:36 ` [Bridge] Re :Re: " jhautbois
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=001636025d9729a369047ac1127f@google.com \
--to=jhautbois@gmail.com \
--cc=bridge@lists.linux-foundation.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