From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 20 16:30:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7728D08 for ; Thu, 20 Mar 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C58AAC50 for ; Thu, 20 Mar 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2KGU1gb031437 for ; Thu, 20 Mar 2014 16:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2KGU1Bh031436; Thu, 20 Mar 2014 16:30:01 GMT (envelope-from gnats) Date: Thu, 20 Mar 2014 16:30:01 GMT Message-Id: <201403201630.s2KGU1Bh031436@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Karl Pielorz Subject: Re: kern/163803: vlan does not work X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Pielorz List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2014 16:30:01 -0000 The following reply was made to PR kern/163803; it has been noted by GNATS. From: Karl Pielorz To: bug-followup@FreeBSD.org, kes-kes@yandex.ru Cc: Subject: Re: kern/163803: vlan does not work Date: Thu, 20 Mar 2014 16:22:36 +0000 Hi, I stumbled across this PR the other day - having a similar issue setting up VLANs under 10.x in this case. After much head scratching I found, for example on a freshly installed, run up FBSD 10.x box: ifconfig bge1.100 create ifconfig bge1.100 192.168.0.20 netmask 255.255.255.0 [and equivalent on the other side] Doesn't work - you see ARP requests flying around - but no traffic is exchanged. However, doing: ifconfig bge1 up (i.e. Bringing up the 'parent' / underlying NIC on both machines) After a few seconds - everything 'works', and traffic does flow over the VLAN (i.e. ARP requests are answered etc.) Whether this is the same issue, whether it's a "bug" that the interface isn't brought 'up' when the vlan virtual interface is created - who knows. Similar thing happens for LAGG interfaces - unless you have a dummy: ifconfig_bge1="UP" In /etc/rc.conf - LAGG configs don't work either. Anyway, just thought I'd post a followup to this - incase this 'fixes' (or at least sheds light) on the original issue. -Karl