From owner-freebsd-net  Tue Mar 20 10:46:53 2001
Delivered-To: freebsd-net@freebsd.org
Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.157])
	by hub.freebsd.org (Postfix) with ESMTP id 6D59537B71A
	for <freebsd-net@FreeBSD.ORG>; Tue, 20 Mar 2001 10:46:48 -0800 (PST)
	(envelope-from yar@comp.chem.msu.su)
Received: (from yar@localhost)
	by comp.chem.msu.su (8.11.1/8.11.1) id f2KIONt12595;
	Tue, 20 Mar 2001 21:24:23 +0300 (MSK)
	(envelope-from yar)
Date: Tue, 20 Mar 2001 21:24:23 +0300
From: Yar Tikhiy <yar@comp.chem.msu.su>
To: Mike Tancsa <mike@sentex.net>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: A few nasty bugs in the networking code
Message-ID: <20010320212422.Q58464@comp.chem.msu.su>
References: <20010319203104.L43447@comp.chem.msu.su> <200103191732.SAA85848@info.iet.unipi.it> <SEN.985024831.955218181@news.sentex.net> <flhebtco6bd2bq3o145k3fl515ofotr471@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <flhebtco6bd2bq3o145k3fl515ofotr471@4ax.com>; from mike@sentex.net on Tue, Mar 20, 2001 at 07:05:58AM -0500
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Mar 20, 2001 at 07:05:58AM -0500, Mike Tancsa wrote:
>
> Do any of the VLAN patches fix the arp -d bug with VLAN interfaces ?
> 
> i.e. arp -d does not work 
> 
> cbackup2# ifconfig vlan0
> vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.112.1 netmask 0xffffff00 broadcast 192.168.112.255
>         ether 00:90:27:25:bf:8b 
>         vlan: 3 parent interface: fxp1
> cbackup2# arp -na | grep 192
> ? (192.168.112.1) at 0:90:27:25:bf:8b permanent
> ? (192.168.112.2) at 0:50:fc:1e:3b:dc
> cbackup2# arp -d 192.168.112.2
> delete: can't locate 192.168.112.2

That bug has to do with /usr/sbin/arp skipping ARP table entries,
which interfaces aren't of one of the following types: IFT_ETHER,
IFT_FDDI, IFT_ISO88023, IFT_ISO88024, IFT_ISO88025. The type of
the vlan interface is IFT_8021_VLAN (that is defined to be equivalent
of IFT_PROPVIRTUAL now), so /usr/sbin/arp just doesn't ``see'' its
entries.

Isn't it better to assign the IFT_ETHER type to the vlan interface?
There might be other places in the code where vlans would behave
unexpectedly because of their type...

SY, Yar

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