From owner-freebsd-net@FreeBSD.ORG Fri Jun 6 02:27:32 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4FF21065674 for ; Fri, 6 Jun 2008 02:27:32 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 99C0F8FC0C for ; Fri, 6 Jun 2008 02:27:32 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-179-28.hsd1.fl.comcast.net ([76.108.179.28] helo=[192.168.1.3]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1K4ReY-0000Yu-Lm; Thu, 05 Jun 2008 22:26:06 -0400 Message-ID: <4848A106.9050709@gtcomm.net> Date: Thu, 05 Jun 2008 22:29:26 -0400 From: Paul User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Support (Rudy)" References: <48489F0E.3030203@monkeybrains.net> In-Reply-To: <48489F0E.3030203@monkeybrains.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: vlan oddness X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2008 02:27:32 -0000 Probably still in the routing table and didn't get removed when the interface was destroyed.. do a route get 10.5.43.225 Support (Rudy) wrote: > > I created and destoryed, brought up and down a vlan... now it is not > accepting an IP.... what does the 'File exists' mean? > > #ifconfig vlan9 > vlan9: flags=8843 metric 0 mtu > 1500 > options=3 > ether 00:30:48:5c:ba:9c > media: Ethernet autoselect (1000baseTX ) > status: active > vlan: 9 parent interface: em0 > > # ifconfig vlan9 10.5.43.225/27 > ifconfig: ioctl (SIOCAIFADDR): File exists > > Also, I don't have the IP/net assigned on any IPs: > # ifconfig | grep inet > inet 10.5.40.8 netmask 0xffffff00 > inet 10.5.42.254 netmask 0xffffff80 > inet 64.215.30.154 netmask 0xfffffffc > inet 127.0.0.1 netmask 0xff000000 > inet 10.9.212.1 netmask 0xfffffe00 > inet 10.5.41.1 netmask 0xffffff00 > inet 10.9.2215.225 netmask 0xffffffe0 > inet 10.9.215.9 netmask 0xfffffffc > inet 10.77.0.6 netmask 0xffffff00 > inet 10.5.42.126 netmask 0xffffff80 > inet 10.99.0.1 netmask 0xffffff00 > > probably a reboot will fix it, but if anyone has seen this oddness, > let me know if you found out what caused it. > (Running fresh freebsd 7.0-STABLE) > > Rudy > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >