From owner-freebsd-net@freebsd.org Thu Jun 23 12:40:39 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2936DA7A1C5 for ; Thu, 23 Jun 2016 12:40:39 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7C85274D for ; Thu, 23 Jun 2016 12:40:38 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213] (may be forged)) (authenticated bits=0) by smtp.krpservers.com (8.15.2/8.15.2) with ESMTPSA id u5NCeZ2G063090 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jun 2016 13:40:36 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Thu, 23 Jun 2016 13:40:27 +0100 From: Karl Pielorz To: Michael Gmelin cc: freebsd-net@FreeBSD.org Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? Message-ID: In-Reply-To: <5DA0293A-B07A-4975-A347-3DE91C5A6116@grem.de> References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]> <5DA0293A-B07A-4975-A347-3DE91C5A6116@grem.de> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2016 12:40:39 -0000 --On 23 June 2016 14:30 +0200 Michael Gmelin wrote: > I don't think having an IP address on an interface that also has vlan > interfaces is a good idea. What kind of traffic are you expecting on > lagg1? Hi, This has worked for 'quite a while' (i.e. >year). lagg1 is connected to an HP switch that has on the two ports that are the lagg: - Untagged traffic (i.e. frames presented to the host with no VLAN tag, and frames expected back again with no VLAN tag). - Tagged VLAN30 - which is presented to the host tagged as VLAN30, and the switch expects to get frames back tagged with VLAN30 already. - Tagged VLAN35 - ditto but for VLAN35 The HP's don't seem to have an issue with it - and it worked before. The way rc.conf is interpreted at the moment means we end up without an IP on lagg1 anyway. If you do a manual 'ifconfig lagg1 inet 172.16.50.1 netmask 255.255.255.0' to fix this - it works (although the lagg1.30/35 VLAN's still don't work). In fact, as I just noticed before - if I do 'ifconfig lagg1 promisc' - it all works as it used to (on 10.1-R). -Kp