From owner-freebsd-net@freebsd.org Wed Apr 20 00:56:58 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 1D2CEB13E80 for ; Wed, 20 Apr 2016 00:56:58 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCF3A12FD for ; Wed, 20 Apr 2016 00:56:57 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-io0-x231.google.com with SMTP id u185so37229485iod.3 for ; Tue, 19 Apr 2016 17:56:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=9mr5df1nm5el98UwQdF7VqtQD1FSobaRG25RLTBXuZo=; b=S0Qy8Bjgke8as9cL6uw7kpvSi9S4TUvsWKe3GTZBFxos1hvrHtf4fq2ElnvE9Qb7oM DZEjR0G8zPGMNKC9w8vmrK20iKpMD7+Lmel8nybIx0NsCXz79JUW7pDC9J20f2AQalkr 5vSX9GzZFL08BdS4npJwpD4egZKGIa8VXziDWrs7z75+HbijT9QwIg1ZgWY8Rk/QToOq 6IbuW0RF9god0uamwFxwGArdZ4E3niXEWzSPJ+A70ntNn+i+3/uO8kdM1ZNrvqT3UXVT 4T4iCn/Ig4Okw/XwKOVKi4UdotlEn2V4C9+U9HN6tcppDgWEZbrVaD7ekz8SSyhUM3cO uGEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=9mr5df1nm5el98UwQdF7VqtQD1FSobaRG25RLTBXuZo=; b=RN7aNHe4WdH7y6pYrzHce4jEPF8L9OvvUExf4VEUKLmqC++jDzHJbQC1H1IbN3oAUt PawuodGdBG7u+m51cWK6kPNLLyK3S0GHQnke2IsCuTNLbn6MdQxYe32sHkQuv69cwL/7 EkXm+FM7mGHGMQt1MtXJ9rkMftuga1e12VeWSdDffGzTzc/q5KjRaSVc5q3HmHcEUMGo 2h42AqzX9oQ89rndCAxShAfoitBtxo30a5eWHK6gV2vWcOAMmr/p+7NnPtbYfFUjW7lC EWnsWJmcP3h+DKUsCjhfUg0PxQMXUQ0sPt6lmHG6ZjqAEeVKpvZsDC4mnhb1Qj+jsNp0 RT2g== X-Gm-Message-State: AOPr4FUyweSvI/zc9cFMspEOCn/7I4bjT/ypFilIpFoxgLkIxCIGNRvHpQYaLSj9CEtt/N5G1neqpoxtn1bsNw== MIME-Version: 1.0 X-Received: by 10.107.37.12 with SMTP id l12mr6324106iol.138.1461113817336; Tue, 19 Apr 2016 17:56:57 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.6.166 with HTTP; Tue, 19 Apr 2016 17:56:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 17:56:57 -0700 X-Google-Sender-Auth: gJZoPYdjQ2J-WrXPmZsI0uc4vTQ Message-ID: Subject: Re: aliases & netmasks, WAS: Issues with ixl(4) From: "K. Macy" To: Dustin Marquess Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 00:56:58 -0000 On Tue, Apr 19, 2016 at 2:52 PM, Dustin Marquess wrote: > Okay, interestingly, I just updated the AMD machine (the ix one) to the > latest version of -CURRENT last night, and now it's acting strangeish > also. So maybe it's not ixl(4) afterall. > > What's obviously "broken" is that the config that is supposed to work: > > ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0" > ifconfig_bridge0_aliases="inet 192.168.1.11/32" > > The alias doesn't work from outside that subnet at least. However the > config that shouldn't work: > > ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0" > ifconfig_bridge0_aliases="inet 192.168.1.11/24" > > Does. Eg, changing the subnet mask on the alias from /32 (which the docs > say it should be) to /24 (which the docs say it shouldn't be), seems to > "fix" it. Although I did seem to lose SSH connectivity to the main IP > sometime after this change. I have a bad feeling that changing the network > mask on the alias is causing other issues. > > Was there some recent change in -CURRENT that would have caused this? Try disabling inpcb route caching.I was afraid that this would happen. -M > > Thanks! > -Dustin > > On Mon, Apr 18, 2016 at 11:06 PM, Dustin Marquess > wrote: > >> I'm having some strange issues with ixl(4) and a X710-DA4 card in a >> new-ish Intel-based server. I'm pretty much replicating an existing setup >> from an older AMD machine that used 2 x X520-DA2 cards and ixgbe(4). This >> is all on -CURRENT. >> >> It's meant to be a bhyve server, so the 4x10GE ports are put into a >> LACP-based lagg(4), then vlan(4) interfaces are bound to the lagg, and then >> if_bridge(4) interfaces are created to bind the vlan and tap interfaces >> together. >> >> The X710-DA4 is running the latest NVM from Intel (5.02): >> >> dev.ixl.3.fw_version: nvm 5.02 etid 80002284 oem 0.0.0 >> dev.ixl.2.fw_version: nvm 5.02 etid 80002284 oem 0.0.0 >> dev.ixl.1.fw_version: nvm 5.02 etid 80002284 oem 0.0.0 >> dev.ixl.0.fw_version: nvm 5.02 etid 80002284 oem 0.0.0 >> >> I've tried both the ixl driver that comes with -CURRENT (1.4.3?) and the >> 1.4.27 driver from Intel and am having the same problem. The problem is >> this exactly (sorry it's taken me so long to get to it!): >> >> Using just one interface, one interface + VLANs, the lagg without VLANs, >> etc, everything works perfectly fine. As soon as I combine >> lagg+vlan+bridge, all hell breaks loose. One machine can ping one alias on >> the server but not the other while other machines can. The server itself >> can't ping the DNS server nor the default route, but can ping things >> through the default route, etc. The behavior is very unpredictable. ssh >> can take a few times to get in, and then once it, "svn update" will work >> for a few seconds and then bomb out, etc. >> >> He is the working config from the X520-DA2 system: >> >> ifconfig_ix0="-lro -tso -txcsum up" >> ifconfig_ix1="-lro -tso -txcsum up" >> ifconfig_ix2="-lro -tso -txcsum up" >> ifconfig_ix3="-lro -tso -txcsum up" >> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2" >> ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 laggport ix2 >> laggport ix3" >> ifconfig_vlan1="vlan 1 vlandev lagg0" >> ifconfig_vlan2="vlan 2 vlandev lagg0" >> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0" >> ifconfig_bridge1="addm vlan2 addm tap1" >> defaultrouter="192.168.1.1" >> >> Here is the "broken" config from the X710-DA4 system: >> >> ifconfig_ixl0="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter >> -vlanhwtso -vlanhwcsum up" >> ifconfig_ixl1="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter >> -vlanhwtso -vlanhwcsum up" >> ifconfig_ixl2="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter >> -vlanhwtso -vlanhwcsum up" >> ifconfig_ixl3="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter >> -vlanhwtso -vlanhwcsum up" >> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2" >> ifconfig_lagg0="laggproto lacp laggport ixl0 laggport ixl1 laggport ixl2 >> laggport ixl3" >> ifconfig_vlan1="vlan 1 vlandev lagg0" >> ifconfig_vlan2="vlan 2 vlandev lagg0" >> ifconfig_bridge0="inet 192.168.1.101/24 addm vlan1 addm tap0" >> ifconfig_bridge1="addm vlan2 addm tap1" >> defaultrouter="192.168.1.1" >> >> I've changed the various flags in the ifconfig_ixl# lines without any >> obvious differences. Both machines are connected to the same HPe 5820X >> switch with the same exact config, so I don't believe it's a switch issue. >> >> Any ideas? Has anybody seen something like this before? >> >> Thanks! >> -Dustin >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"