From owner-freebsd-bugs  Wed Feb  7 12:50:20 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id BFBFA37B4EC
	for <freebsd-bugs@hub.freebsd.org>; Wed,  7 Feb 2001 12:50:01 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f17Ko1i14815;
	Wed, 7 Feb 2001 12:50:01 -0800 (PST)
	(envelope-from gnats)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 0D08E37B491
	for <freebsd-gnats-submit@FreeBSD.org>; Wed,  7 Feb 2001 12:45:05 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f17Kj5S14377;
	Wed, 7 Feb 2001 12:45:05 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200102072045.f17Kj5S14377@freefall.freebsd.org>
Date: Wed, 7 Feb 2001 12:45:05 -0800 (PST)
From: tburgess@whitley.unimelb.edu.au
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-1.0
Subject: kern/24937: flaky connection through vlan interface
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         24937
>Category:       kern
>Synopsis:       flaky connection through vlan interface
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 07 12:50:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tim Burgess
>Release:        4.2-release
>Organization:
>Environment:
FreeBSD death.whitley.unimelb.edu.au 4.2-RELEASE FreeBSD 4.2-RELEASE #1: Tue Jan 30 11:19:00 EST 2001     root@death.whitley.unimelb.edu.au:/usr/src/sys/compile/DEATH  i386
>Description:
We have three vlans connected to a parent interface rl0, and have had flaky connections through the server since it was set up this way.  After much experimentation, it turns out that disabling the vlan interface and shifting one of the connections to it's own real NIC fixes the problem.  The NIC rl0 is not faulty, as it is still acting as the external connection to the internet (the machine is a firewall/gateway/NAT box).
>How-To-Repeat:
See above.
>Fix:
Buy another NIC until you run out of PCI slots like we have :(


>Release-Note:
>Audit-Trail:
>Unformatted:


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