All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yavetskiy Yuriy <yavetskiy@kpi.ua>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Re :Re: Re :Re: Re :Re: Bridging LACP (802.3ad)	frames not working
Date: Wed, 20 Jan 2010 18:31:06 +0200	[thread overview]
Message-ID: <4B572FCA.8080905@kpi.ua> (raw)
In-Reply-To: <20100119214451.72637a94rn0biysz@mx.kpi.ua>

Hello.

I solve my problem without ebtables.
Just add to net/bridge/br_input.c next strings (with +):

        if (unlikely(is_link_local(dest))) {
                /* Pause frames shouldn't be passed up by driver anyway */
                if (skb->protocol == htons(ETH_P_PAUSE))
                        goto drop;

+                /* Don't touch SLOW frames (LACP, etc.) */
+               if (skb->protocol == htons(ETH_P_SLOW))
+                        goto forward;

                /* If STP is turned off, then forward */
                if (p->br->stp_enabled == BR_NO_STP && dest[5] == 0)
                        goto forward;

                if (NF_HOOK(PF_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
                            NULL, br_handle_local_finish))
                        return NULL;    /* frame consumed by filter */
                else
                        return skb;     /* continue processing */
        }

and after I've compiled it to kernel 802.3ad frames became pass through 
linux bridge.


yavetskiy@kpi.ua wrote:
> Hello.
>
> I have the same problem with bridging 802.3ad frames.
>
> But rules:
> ebtables -A INPUT -p 0x8809 -j ACCEPT
> ebtables -A FORWARD -p 0x8809 -j ACCEPT
> are not enough to solve this problem, it still doesn't work for me.
> I have vanila kernel 2.6.32 with no patches, Debian squeeze, eth1 and  
> eth2 interfaces in bridge with stp disabled.
> Maybe I've missed something? Do you have any ideas?
> Thank you.
>
>
> --
> WBR
> Yavetkiy Yuriy
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>   


-- 
WBR
Yavetskiy Yuriy
ULTI-RIPE


  reply	other threads:[~2010-01-20 16:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 19:44 [Bridge] Re :Re: Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working yavetskiy
2010-01-20 16:31 ` Yavetskiy Yuriy [this message]
2010-01-20 17:54   ` Stephen Hemminger
2010-01-20 18:14     ` Jean-Michel Hautbois
2010-03-18  9:06       ` Phil Karn
  -- strict thread matches above, loose matches on Subject: below --
2010-01-13 16:53 Jean-Michel Hautbois
2010-01-13 16:55 ` Stephen Hemminger
2010-01-13 17:21   ` Jean-Michel Hautbois
2010-01-13 17:42     ` Jean-Michel Hautbois
2010-01-13 16:30 [Bridge] " Stephen Hemminger
2010-01-13 16:47 ` [Bridge] Re :Re: " jhautbois
2010-01-13 16:49   ` Stephen Hemminger

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=4B572FCA.8080905@kpi.ua \
    --to=yavetskiy@kpi.ua \
    --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 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.