netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: "Yigal Reiss (yreiss)" <yreiss@cisco.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] brouted packet identified as PACKET_OTHERHOST blocked by higher protocol
Date: Tue, 14 Jul 2015 13:05:01 +0200	[thread overview]
Message-ID: <20150714110501.GC25674@breakpoint.cc> (raw)
In-Reply-To: <3167EFAB95044A4EB6B134B9A39AA98A055B5DBE@xmb-rcd-x05.cisco.com>

Yigal Reiss (yreiss) <yreiss@cisco.com> wrote:
> The problem I'm trying to solve is that when packets being sent from one bridged interface to the other are "brouted" they get dropped by the IP layer. The reason is that the packet being raised has pkt_type of type PACKET_OTHERHOST.

No, thats not the problem you're trying to solve.

If you want to move OTHERHOST skbs, don't (b)route them?

Whats the real issue that you're trying to solve?

  reply	other threads:[~2015-07-14 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 10:37 [PATCH] brouted packet identified as PACKET_OTHERHOST blocked by higher protocol Yigal Reiss (yreiss)
2015-07-14 11:05 ` Florian Westphal [this message]
2015-07-14 11:18   ` Yigal Reiss (yreiss)
2015-07-14 11:35     ` Florian Westphal
2015-07-14 11:52       ` Yigal Reiss (yreiss)
2015-07-14 11:59         ` Florian Westphal

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=20150714110501.GC25674@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=yreiss@cisco.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 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).