From owner-freebsd-net@FreeBSD.ORG  Sun Feb  2 02:29:21 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EAD307CC
 for <freebsd-net@freebsd.org>; Sun,  2 Feb 2014 02:29:21 +0000 (UTC)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com
 [IPv6:2a00:1450:4013:c00::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 825CC127B
 for <freebsd-net@freebsd.org>; Sun,  2 Feb 2014 02:29:21 +0000 (UTC)
Received: by mail-ee0-f52.google.com with SMTP id e53so2983147eek.11
 for <freebsd-net@freebsd.org>; Sat, 01 Feb 2014 18:29:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=31DaIaMDR20RJZAyH3oQZR06cytu5zapkBLSJ3itRkU=;
 b=T0DHKkK8B5d6AjFUrhQROt9ZiYmqK+gUZQLBYKgvMTAI4h2Dw/wXPZ0/2XAi+EE+11
 NrQVwirjtYCBDHHgsZXVfkZu5diB8mPMLcGk3J8CAgE6uQPkK8TZukWabvVPYp9hP88L
 JT/GxuUCvRNdpmy1/6rXmX5anxVTFFHw6SM6OPxn+VK7bS876Yc72AN3nWYp7P+d8LiG
 lHdearpXmjNkXzuMhDjOZnaJu4NEtBhw6x3TAlGsO5Vy/8nsOyKIUGNuuSZhtzeRdbbL
 lcyfe6qZBN1tKn184E63tKLUwtIbkMRQ5FQHl4t8LfrFXYGpsdP7ZWHgabPwgyw35Ovd
 xZMQ==
MIME-Version: 1.0
X-Received: by 10.15.43.141 with SMTP id x13mr33772636eev.35.1391308159903;
 Sat, 01 Feb 2014 18:29:19 -0800 (PST)
Received: by 10.14.65.4 with HTTP; Sat, 1 Feb 2014 18:29:19 -0800 (PST)
In-Reply-To: <CALCpEUFLwZ6vismFKgyo1Q_P4iwzxS+jBozTV+O1kvap6U8brQ@mail.gmail.com>
References: <CALCpEUH7YHhG3gw0wrObsJux=PWmJu2K6_tzCbCfXQ21ENYHdw@mail.gmail.com>
 <CALCpEUEuXR7_Q8_zt2TjnsOqt_rYMH5do=UEjssqkj684Xdimg@mail.gmail.com>
 <CALCpEUFLwZ6vismFKgyo1Q_P4iwzxS+jBozTV+O1kvap6U8brQ@mail.gmail.com>
Date: Sat, 1 Feb 2014 18:29:19 -0800
Message-ID: <CALCpEUEDCPWog3sQzhTgL2NFyF1OB7YECxPvEr+LxNvhOOhQtA@mail.gmail.com>
Subject: Re: Errors using span interface on if_bridge(4)
From: hiren panchasara <hiren.panchasara@gmail.com>
To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2014 02:29:22 -0000

On Sat, Feb 1, 2014 at 5:16 PM, hiren panchasara
<hiren.panchasara@gmail.com> wrote:
> I rebuilt the kernel with following change to check failure:
>
> Index: if_bridge.c
> ===================================================================
> --- if_bridge.c (revision 260789)
> +++ if_bridge.c (working copy)
> @@ -2536,6 +2536,7 @@
>         struct bridge_iflist *bif;
>         struct ifnet *dst_if;
>         struct mbuf *mc;
> +       int error = 0;
>
>         if (LIST_EMPTY(&sc->sc_spanlist))
>                 return;
> @@ -2552,7 +2553,9 @@
>                         continue;
>                 }
>
> -               bridge_enqueue(sc, dst_if, mc);
> +               error = bridge_enqueue(sc, dst_if, mc);
> +               if (error)
> +                       printf("%s: bridge_enqueue failed\n", __func__);
>         }
>  }
>
> After this change and reboot, I see packets on ix3 without those
> bad-len errors seen before.

Just an update that it was not this change which was triggering
anything. I reverted it and things are still the same.
I guess reboot caused those bad-len errors to go away.

Trying to find how to narrow down what is causing this checksum errors.

cheers,
Hiren