From owner-freebsd-stable  Tue Jun 25 18:19:23 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4837637B401; Tue, 25 Jun 2002 18:19:14 -0700 (PDT)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g5Q1JDf49243;
	Tue, 25 Jun 2002 18:19:13 -0700 (PDT)
	(envelope-from jdp@wall.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.11.6/8.11.0) id g5Q1JDU36770;
	Tue, 25 Jun 2002 18:19:13 -0700 (PDT)
	(envelope-from jdp)
Date: Tue, 25 Jun 2002 18:19:13 -0700 (PDT)
Message-Id: <200206260119.g5Q1JDU36770@vashon.polstra.com>
To: stable@freebsd.org
From: John Polstra <jdp@polstra.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: em/Intel(R) PRO/1000 problems
In-Reply-To: <20020625193510.GA21123@pir.net>
References: <E17MOog-000IXa-00@cse.cs.huji.ac.il> <20020625193510.GA21123@pir.net>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

In article <20020625193510.GA21123@pir.net>,
Peter Radcliffe  <freebsd-stable@FreeBSD.ORG> wrote:
> Danny Braniss <danny@cs.huji.ac.il> probably said:
> > em0: <Intel(R) PRO/1000 Network Connection, Version - 1.2.7> and
> > em0: <Intel(R) PRO/1000 Network Connection, Version - 1.3.8>
> 
> Between the upgrade of em from 1.2.7 to 1.3.8 I started having
> problems with the em card in my desktop box at work.
> 
> I have two tagged vlans over one em interface;
> 
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=3<rxcsum,txcsum>
>         ether 00:02:b3:xx:xx:xx
>         media: Ethernet autoselect (1000baseTX <full-duplex>)
>         status: active
> vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1496
>         inet 130.64.x.xxx netmask 0xffffff00 broadcast 130.64.1.255
>         ether 00:02:b3:xx:xx:xx
>         vlan: 1 parent interface: em0
> vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1496
>         inet 192.168.2.222 netmask 0xffffff00 broadcast 192.168.2.255
>         ether 00:02:b3:xx:xx:xx
>         vlan: 2 parent interface: em0
> 
> With 1.2.7 in -RELEASE this works fine, with 1.3.8 in -STABLE I stop
> seeing arp replies from any Foundry equipment.

The recent em0 upgrade added HW support for VLANs in the driver,
and I'm just wondering if it broke the old non-HW-supported method.
There's an experiment you could try.  Use ifconfig to set "link0" on
both vlan1 and vlan2, then see if it starts working.  Just an idea to
try.  I don't know whether it will make any difference.

John
-- 
  John Polstra
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message