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> In-Reply-To: <flhebtco6bd2bq3o145k3fl515ofotr471@4ax.com>; from mike@sentex.net on Tue, Mar 20, 2001 at 07:05:58AM -0500 References: <20010319203104.L43447@comp.chem.msu.su> <200103191732.SAA85848@info.iet.unipi.it> <SEN.985024831.955218181@news.sentex.net> <flhebtco6bd2bq3o145k3fl515ofotr471@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010320212422.Q58464>