From owner-freebsd-net  Thu Mar  1 16:39:23 2001
Delivered-To: freebsd-net@freebsd.org
Received: from mail.andy.de (fw.andy.de [212.8.198.74])
	by hub.freebsd.org (Postfix) with ESMTP id 97AD537B71F
	for <freebsd-net@FreeBSD.org>; Thu,  1 Mar 2001 16:39:21 -0800 (PST)
	(envelope-from andy@andy.de)
Received: from windoze.andy.de (windoze.andy.de [212.8.199.4])
	by mail.andy.de (Postfix) with ESMTP id A2B967CFF1
	for <freebsd-net@FreeBSD.org>; Fri,  2 Mar 2001 01:39:20 +0100 (CET)
Date: Fri, 02 Mar 2001 01:38:22 +0100
From: Andreas Gerstenberg <andy@andy.de>
To: freebsd-net@FreeBSD.org
Subject: Re: vlan panics?
Message-ID: <4244559283.983497102@windoze.andy.de>
In-Reply-To: <3A8C0614.3131FB3@elischer.org>
X-Mailer: Mulberry/2.0.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

-- Julian Elischer <julian@elischer.org> wrote:

> Adrian Chadd wrote:

>> I've discovered that on the fxp, if I ifconfig a vlan up without
>> ifconfig'ing the parent interface (fxp) up, I'll get a panic.
>> I don't have the bt handy at the moment but basically the codepath
>> is bringing the vlan interface up, sending the gratuituous(sp)? arp
>> request out the vlan interface, which sends it out the parent interface.
>> The fxp code doesn't check whether the interface has been initialised
>> when it attempts to queue a packet for outbound, and you get a panic.

I had the same problem yesterday which took some hours to figure out,
whats going wrong. I have opened a PR for this problem (25478), there is
also a backtrace in.

But now I'm reading my freebsd-net archive..I think in the future I'll have
to take a look here before :-)

> there's an fxp-Vlan patch floating around somewhere.

Yes, http://www.euitt.upm.es/~pjlobo/fbsdvlan.html. This patch only helps
you to receive long frames. But the panic described above happens
independent of this patch.

There is a workaround for this problem, but it can take hours to find
out what happens or even to find out that you have to "ifconfig up" the
parent interface before.

regards,
Andy


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