From owner-freebsd-net@freebsd.org Sun Jul 12 21:00:18 2015 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 3822399B155 for ; Sun, 12 Jul 2015 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12F12166B for ; Sun, 12 Jul 2015 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6CL0Hgr052011 for ; Sun, 12 Jul 2015 21:00:17 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201507122100.t6CL0Hgr052011@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 12 Jul 2015 21:00:17 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 21:00:18 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 197535 | [re] [panic] if_re (Realtek 8168) causes memory w Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t 3 problems total for which you should take action. From owner-freebsd-net@freebsd.org Mon Jul 13 08:33:50 2015 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 DEDF799BC12 for ; Mon, 13 Jul 2015 08:33:50 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id AE8FB19B3 for ; Mon, 13 Jul 2015 08:33:49 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t6D8XfDG014163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jul 2015 09:33:42 +0100 (BST) Date: Mon, 13 Jul 2015 09:33:42 +0100 From: Karl Pielorz To: John-Mark Gurney cc: freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: In-Reply-To: <20150710180627.GA8523@funkthat.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <20150710180627.GA8523@funkthat.com> 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.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 08:33:51 -0000 --On 10 July 2015 11:06 -0700 John-Mark Gurney wrote: > Try bumping the MTU on the root em's by 4 (1504) before creating the > lagg... I had thought of that - but didn't want to try it (on the basis that out of all the other example config's I've seen - no one else has to, and it will break the lagg MTU). Anyway I tried it, by: - Bump the MTU on the em interfaces before creating the lagg to 1504 - The lagg created, inherits this 1504 MTU That breaks the untagged IP on lagg0 - i.e. I end up with: " lagg0: flags=8843 metric 0 mtu 1504 options=4019b ether 68:05:ca:08:1d:3b inet x.x.x.x netmask 0xffffff00 broadcast y.y.y.y " That MTU of 1504 is going to break lagg0 for untagged traffic :( - However, the VLAN's setup on the lagg still default to 1496 MTU (despite the underlying interface lagg0 being MTU 1504) If I 'manually' bump the MTU on the individual lagg0.x VLAN interfaces - they will go to 1500, but traffic is still 'broken'. I can't 'reduce' the bad MTU on lagg0 either - i.e. 'ifconfig lagg0 mtu 1500' (to try to put it back to 1500) fails with an ioctl error. So sadly, I'm still stuck :( Something is lopping 4 bytes off the MTU when it shouldn't need to. None of the example configs I could find were from 10.1-R (or with exactly the same cards) - but obviously this is just bread & butter lagg/VLAN stuff, so it should work? -Karl From owner-freebsd-net@freebsd.org Mon Jul 13 08:51:46 2015 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 963873349 for ; Mon, 13 Jul 2015 08:51:46 +0000 (UTC) (envelope-from steve.read@stormshield.eu) Received: from work.netasq.com (gwlille.netasq.com [91.212.116.1]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE3C1901 for ; Mon, 13 Jul 2015 08:51:44 +0000 (UTC) (envelope-from steve.read@stormshield.eu) Received: from work.netasq.com (localhost.localdomain [127.0.0.1]) by work.netasq.com (Postfix) with ESMTP id A5DFF2706088 for ; Mon, 13 Jul 2015 10:51:42 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by work.netasq.com (Postfix) with ESMTP id 87B4D2706079 for ; Mon, 13 Jul 2015 10:51:42 +0200 (CEST) Received: from work.netasq.com ([127.0.0.1]) by localhost (work.netasq.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PdvA6zuxcBuR for ; Mon, 13 Jul 2015 10:51:42 +0200 (CEST) Received: from stever.netasq.com (unknown [10.2.39.1]) by work.netasq.com (Postfix) with ESMTPA id 628D52705BD5 for ; Mon, 13 Jul 2015 10:51:42 +0200 (CEST) Message-ID: <55A37C1E.90804@stormshield.eu> Date: Mon, 13 Jul 2015 10:51:42 +0200 From: Steve Read User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> In-Reply-To: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 08:51:46 -0000 On 10.07.2015 15:04, Karl Pielorz wrote: > > The MTU on lagg0.10 has shrunk by 4 (size of VLAN tag). Is there a way > of avoiding that? No. Think about what it means. The MTU on the lagg0 interface is the largest packet it can send for you or for its VLAN interfaces. The MTU on the lagg0.10 (VLAN) interface is the largest packet *it* can send for you. The VLAN tag is added to the packet that you give to lagg0.10, and so the MTU of lagg0.10 must be smaller than the MTU of lagg0. Crudely speaking, the sequence is: * The TCP/IP layers create a packet of N bytes (starting with an IP header), and give them to the "ethernet" layer (lagg0.10) which adds 14 bytes of MAC/ethertype, for a total of N+14. This must fit into the the MTU of lagg0.10. * lagg0.10 then adds four more bytes between the MAC/ethertype and the IP packet, for a total of N+14+4. This must fit into the MTU of lagg0. * lagg0 then sends the packet. Note that the packet given to lagg0 is four bytes bigger than the packet given to lagg0.10, and this is always true. If you make the MTU of lagg0.10 equal to the MTU of lagg0, then lagg0.10 will end up generating packets that are oversize for lagg0, and you don't want that. -- Steve Read From owner-freebsd-net@freebsd.org Mon Jul 13 09:11:54 2015 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 4D3C53AC4 for ; Mon, 13 Jul 2015 09:11:54 +0000 (UTC) (envelope-from technical@at-hacker.in) Received: from mail.at-hacker.in (mail.at-hacker.in [82.146.54.71]) by mx1.freebsd.org (Postfix) with ESMTP id 0BC1B1898; Mon, 13 Jul 2015 09:11:53 +0000 (UTC) (envelope-from technical@at-hacker.in) Received: from [192.168.1.14] (broadband-5-228-79-227.nationalcablenetworks.ru [5.228.79.227]) by mail.at-hacker.in (Postfix) with ESMTPSA id 5E3812ADC85; Mon, 13 Jul 2015 12:11:44 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=at-hacker.in; s=mail; t=1436778704; bh=WjhHyfQSpRIxi2VuGQ7ZFSNgkxbnuPTUYhvQvrGwZEg=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=mJI03dwdtfS+euo9fyzaAzt9BqatMC5py9+OLQeZ8XP+OY+kjXihZVLCeTUyEUOdP zO3oazS6AbxyJAsS4nZNCBRJjrjV5nrtg2o4XdXK+HuEPw6F9pinubJ/mt0ULFkv9U SNfvaTYvU3Acd9tpDySd8cE3bAdMMzKN5Ynxyi1k= Message-ID: <55A380CF.2030503@at-hacker.in> Date: Mon, 13 Jul 2015 12:11:43 +0300 From: Alexey Pereklad User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Kristof Provost CC: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.3: Looks like a bug in pf NAT while translating ICMP packets of type 3 References: <559BC04F.70107@at-hacker.in> <20150707123320.GF3135@vega.codepro.be> In-Reply-To: <20150707123320.GF3135@vega.codepro.be> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 09:11:54 -0000 Hi. I checked if I can reproduce this issue with -CURRENT. Well, -CURRENT has the same problem. Here is my test lab: # uname -a FreeBSD test-BSD-01.hyperv.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r285351: Fri Jul 10 14:49:08 MSK 2015 root@test-BSD-01.hyperv.local:/usr/obj/usr/src/sys/GENERIC amd64 Here is dump on LAN interface: # tcpdump -npi hn1 host 172.16.129.18 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on hn1, link-type EN10MB (Ethernet), capture size 262144 bytes 11:43:25.506775 IP 172.16.129.18.29490 > 208.67.220.220.53: 9125+ A? freebsd.org. (29) 11:43:25.570851 IP 208.67.220.220.53 > 172.16.129.18.29490: 9125 1/0/0 A 8.8.178.110 (45) 11:43:25.571635 IP 172.16.129.18 > 208.67.220.220: ICMP 172.16.129.18 udp port 29490 unreachable, length 36 Dump on external WAN interface at the same moment: # tcpdump -npi hn0 \(udp and port 53\) or icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on hn0, link-type EN10MB (Ethernet), capture size 262144 bytes 11:43:25.741672 IP 213.208.xx.yy.55677 > 208.67.220.220.53: 1319+ A? ya.ru. (23) 11:43:25.795961 IP 208.67.220.220.53 > 213.208.xx.yy.55677: 1319 3/0/0 A 93.158.134.3, A 213.180.193.3, A 213.180.204.3 (71) 11:43:25.796700 IP 172.16.129.18 > 208.67.220.220: ICMP 213.208.xx.yy udp port 55677 unreachable, length 36 So I've created bugreport: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201519 07.07.2015 15:33, Kristof Provost пишет: > On 2015-07-07 15:04:31 (+0300), technical account wrote: >> I have an issue with pf in FreeBSD 9.3. Looks there is something wrong >> with pf's NAT while processing ICMP packets of type 3 (destination >> unreachable). >> > Can you check if this also happens on CURRENT? > > If so, please create a bug on bugs.freebsd.org/bugzilla and cc me > (kp@FreeBSD.org). > You've already gathered the information required for a good bug report. > > I'll try to take a look at it when I find some time. > From owner-freebsd-net@freebsd.org Mon Jul 13 09:15:23 2015 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 425863C04 for ; Mon, 13 Jul 2015 09:15:23 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 099E11C2C for ; Mon, 13 Jul 2015 09:15:23 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [192.168.18.125] (unknown [81.83.8.162]) by venus.codepro.be (Postfix) with ESMTPSA id 1428213EF1; Mon, 13 Jul 2015 11:15:19 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: FreeBSD 9.3: Looks like a bug in pf NAT while translating ICMP packets of type 3 From: Kristof Provost In-Reply-To: <55A380CF.2030503@at-hacker.in> Date: Mon, 13 Jul 2015 11:15:51 +0200 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <559BC04F.70107@at-hacker.in> <20150707123320.GF3135@vega.codepro.be> <55A380CF.2030503@at-hacker.in> To: Alexey Pereklad X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 09:15:23 -0000 Thanks. I=E2=80=99ve added it to my todo list. (No promises about when = I=E2=80=99ll have time though.) Regards, Kristof > On 13 Jul 2015, at 11:11, Alexey Pereklad = wrote: >=20 > Hi. >=20 > I checked if I can reproduce this issue with -CURRENT. Well, -CURRENT = has the same problem. Here is my test lab: >=20 > # uname -a > FreeBSD test-BSD-01.hyperv.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1 = r285351: Fri Jul 10 14:49:08 MSK 2015 = root@test-BSD-01.hyperv.local:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > Here is dump on LAN interface: >=20 > # tcpdump -npi hn1 host 172.16.129.18 > tcpdump: verbose output suppressed, use -v or -vv for full protocol = decode > listening on hn1, link-type EN10MB (Ethernet), capture size 262144 = bytes > 11:43:25.506775 IP 172.16.129.18.29490 > 208.67.220.220.53: 9125+ A? = freebsd.org. (29) > 11:43:25.570851 IP 208.67.220.220.53 > 172.16.129.18.29490: 9125 1/0/0 = A 8.8.178.110 (45) > 11:43:25.571635 IP 172.16.129.18 > 208.67.220.220: ICMP 172.16.129.18 = udp port 29490 unreachable, length 36 >=20 > Dump on external WAN interface at the same moment: >=20 > # tcpdump -npi hn0 \(udp and port 53\) or icmp > tcpdump: verbose output suppressed, use -v or -vv for full protocol = decode > listening on hn0, link-type EN10MB (Ethernet), capture size 262144 = bytes > 11:43:25.741672 IP 213.208.xx.yy.55677 > 208.67.220.220.53: 1319+ A? = ya.ru. (23) > 11:43:25.795961 IP 208.67.220.220.53 > 213.208.xx.yy.55677: 1319 3/0/0 = A 93.158.134.3, A 213.180.193.3, A 213.180.204.3 (71) > 11:43:25.796700 IP 172.16.129.18 > 208.67.220.220: ICMP 213.208.xx.yy = udp port 55677 unreachable, length 36 >=20 > So I've created bugreport: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201519 >=20 > 07.07.2015 15:33, Kristof Provost =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> On 2015-07-07 15:04:31 (+0300), technical account = wrote: >>> I have an issue with pf in FreeBSD 9.3. Looks there is something = wrong >>> with pf's NAT while processing ICMP packets of type 3 (destination >>> unreachable). >>>=20 >> Can you check if this also happens on CURRENT? >>=20 >> If so, please create a bug on bugs.freebsd.org/bugzilla and cc me >> (kp@FreeBSD.org). >> You've already gathered the information required for a good bug = report. >>=20 >> I'll try to take a look at it when I find some time. >>=20 >=20 From owner-freebsd-net@freebsd.org Mon Jul 13 09:29:49 2015 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 8B3663FAC for ; Mon, 13 Jul 2015 09:29:49 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5A04110D4 for ; Mon, 13 Jul 2015 09:29:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t6D9TlFE017703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jul 2015 10:29:48 +0100 (BST) Date: Mon, 13 Jul 2015 10:29:48 +0100 From: Karl Pielorz To: Steve Read , freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: In-Reply-To: <55A37C1E.90804@stormshield.eu> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <55A37C1E.90804@stormshield.eu> 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.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 09:29:49 -0000 --On 13 July 2015 10:51 +0200 Steve Read wrote: > Think about what it means. The MTU on the lagg0 interface is the > largest packet it can send for you or for its VLAN interfaces. The MTU > on the lagg0.10 (VLAN) interface is the largest packet *it* can send for > you. The VLAN tag is added to the packet that you give to lagg0.10, and > so the MTU of lagg0.10 must be smaller than the MTU of lagg0. Ok, I understand all that (despite a bad cold!) - but looking at other peoples ifconfig outputs found on google, they show: - Underlying interface, MTU 1500 - LAGG interface, MTU 1500 - VLAN sub interface, MTU 1500 I don't get that - from the same ifconfig-uration I get: - Underlying interface, MTU 1500 - LAGG interface, MTU 1500 - VLAN sub interface, MTU 1496 I thought if cards natively support VLAN's the VLAN tag was handled 'behind the scenes' - e.g. if I go setup em3.10 - I wouldn't see the MTU drop to 1496. In fact, I've just done this with em3 on that machine... ifconfig em3.10 create ifconfig em3.10 inet 10.12.13.1 netmask 255.255.255.0 ifconfig em3 inet 10.13.14.1 netmask 255.255.255.0 ifconfig em3 em3: flags=8c02 metric 0 mtu 1500 ifconfig em3.10 em3.10: flags=8843 metric 0 mtu 1500 I realise the packets sent by em3.10 will now be 1504 bytes MTU - and if your switch doesn't support VLAN's (and/or can only cope with strict 1500 byte packets you're probably in trouble) - but the above is doing what I'd "expect" to happen for the LAGG case. I could understand losing the 4 bytes maybe if the card didn't support native VLAN's (or having to do it if your switch can't cope with 1500+4 byte frames) - but not if they're supported. > Note that the packet given to lagg0 is four bytes bigger than the packet > given to lagg0.10, and this is always true. If you make the MTU of > lagg0.10 equal to the MTU of lagg0, then lagg0.10 will end up generating > packets that are oversize for lagg0, and you don't want that. Yes, I get that - but as I said I thought 'native VLAN' tagging was handled differently - as shown by the example above with em3. afaik - Lagging interfaces has no effect on MTU, but something behind the scenes is treating lagg0.10 differently from, say em0.10 as far as MTU configuration goes? Ultimately the question is - why are other people running the same ifconfig (admittedly on different FreeBSD versions / cards) and getting what I'd expect [a working system], but I don't? -Karl From owner-freebsd-net@freebsd.org Mon Jul 13 08:25:24 2015 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 B273C99BA2D; Mon, 13 Jul 2015 08:25:24 +0000 (UTC) (envelope-from alexl@mellanox.com) Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0097.outbound.protection.outlook.com [157.56.112.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DC0A1448; Mon, 13 Jul 2015 08:25:23 +0000 (UTC) (envelope-from alexl@mellanox.com) Received: from AM3PR05MB532.eurprd05.prod.outlook.com (10.242.244.146) by AM3PR05MB0950.eurprd05.prod.outlook.com (10.161.33.27) with Microsoft SMTP Server (TLS) id 15.1.213.14; Mon, 13 Jul 2015 08:25:21 +0000 Received: from AM3PR05MB529.eurprd05.prod.outlook.com (10.242.243.155) by AM3PR05MB532.eurprd05.prod.outlook.com (10.242.244.146) with Microsoft SMTP Server (TLS) id 15.1.207.19; Mon, 13 Jul 2015 08:25:20 +0000 Received: from AM3PR05MB529.eurprd05.prod.outlook.com ([10.242.243.155]) by AM3PR05MB529.eurprd05.prod.outlook.com ([10.242.243.155]) with mapi id 15.01.0207.004; Mon, 13 Jul 2015 08:25:20 +0000 From: Alex Liptsin To: "'freebsd-net@freebsd.org'" <'freebsd-net@freebsd.org'>, "'freebsd-questions@freebsd.org'" <'freebsd-questions@freebsd.org'> Subject: VLAN priority Thread-Topic: VLAN priority Thread-Index: AdC9RXQR95/kDOflT5CRzcPN9W+DiA== Date: Mon, 13 Jul 2015 08:25:20 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none; x-originating-ip: [193.47.165.251] x-microsoft-exchange-diagnostics: 1; AM3PR05MB532; 5:GwfwArgzunUXmOBwhTXrVXj61aegSPqfQmh3oa9YjvNvCmkJGeFygem8HEEZzcZWp1Ud6nxtNaU0nAXKDzR2Xvr9w8CmYgUiLTfFe4avsK3azquYxE3M5087JIiNSFdSNdACrl7ZGXHtGoQahLAA+w==; 24:1HJUm9cAR/8Vy/3ksGjDM12QAWww9rcAaDdGVxI9Ht2W9x4MQEIpYYClHAwhSwwSD1Ckb4lLQvPHqS+EnAnMiWQevpDI7eP5Hc0vmkC8/vY=; 20:bXEcXNDK5buTaxgX18rppOjfOxq7ca2rU6d2YFvW4Ol6c5wtTBXU3jZ2Hat15Uxg1JRKpU6oqXMaiA46vyb6Hg== x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR05MB532; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR05MB0950; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(108003899814671); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:AM3PR05MB532; BCL:0; PCL:0; RULEID:; SRVR:AM3PR05MB532; x-forefront-prvs: 0636271852 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(164054003)(229853001)(87936001)(19625215002)(221733001)(189998001)(46102003)(2900100001)(5002640100001)(62966003)(5001960100002)(109986003)(66066001)(450100001)(77096005)(19300405004)(19580395003)(15975445007)(77156002)(33656002)(86362001)(122556002)(2656002)(76576001)(107886002)(5001920100001)(110136002)(40100003)(102836002)(5003600100002)(558084003)(50986999)(16236675004)(92566002)(54356999)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR05MB532; H:AM3PR05MB529.eurprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jul 2015 08:25:20.5188 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR05MB532 X-Microsoft-Exchange-Diagnostics: 1; AM3PR05MB0950; 2:qU2MigwtSA4BCfXpoLSalcG6/a7mdFNOLWaXzTxQIMQjhNcL3NALAzMxm3uUH6F1; 3:rqQIkGH2IjYcWM9e4hEixdiODCwgqrK9oy8oIfFuHUGvcGfzx5/ubiCXvlnZQThkAoiK8ls3MuLTZ/zp2BNeCAwItOKnkFt4fg056WukQ3MEnZghmC1XILBAkSUocF5g5OHdY9FKW9dBS7BirNvQtA==; 25:cIYr6u9HFXWJ/gfMsm7FjumeRdNTD3pMLrGTmg8XX80dK0aZwJGca0bqxxkNSgN6fTgY6IMRW+e6ft/TRKoKlksQK5i80Fseehm5NVSei3iqdj5qaOJDLHdbtuUbo36eJbZs0MspZEZ+Il8Z8uvsQTvUgMFiIbAQdLP9wYdJHJv6B6u0l//4Q+B+W/xFfp3+C+hYg/9f1TK3EXwxsRS1j4ixBZ84KMfGKRw1XBYVKw+B7lU4vwcdUgVc50eQC80T; 23:pKc/lSlDN8hUwyEXeOp2MJl1mHdPeFt6yyvScqsEmzzR+6p2GtgaGyQllmfCGrHmO85HUVuZtRWDlofhJ7yIIGMlj6qHuedSmEz7vF7qlEatfTE2DdbGRpusuRxDfxP3t0uYHqJqQKxM4wr/uNdyrcSqSWQ4B+5RN5Yehy7eOi0m3PlX9aTtEMfQqXDnIUsoQL/I8MEZpsiIeApibOo+LZxTrTtmm07FkZpe9fuoVLvloAqC798JFlaeI0vgscAQ X-OriginatorOrg: Mellanox.com X-Mailman-Approved-At: Mon, 13 Jul 2015 11:47:17 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 08:25:24 -0000 Hi. How can I configure VLAN priority on FreeBSD10-STABLE or FreeBSD11-CURRENT= ? Thanks, Alex. From owner-freebsd-net@freebsd.org Mon Jul 13 12:06:55 2015 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 E0499999338 for ; Mon, 13 Jul 2015 12:06:54 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C7B51920 for ; Mon, 13 Jul 2015 12:06:54 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZEcVX-000Alw-1y; Mon, 13 Jul 2015 13:06:51 +0100 Date: Mon, 13 Jul 2015 13:06:51 +0100 From: Gary Palmer To: Karl Pielorz Cc: Steve Read , freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: <20150713120651.GA68542@in-addr.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <55A37C1E.90804@stormshield.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 12:06:55 -0000 On Mon, Jul 13, 2015 at 10:29:48AM +0100, Karl Pielorz wrote: > > > --On 13 July 2015 10:51 +0200 Steve Read wrote: > > > Think about what it means. The MTU on the lagg0 interface is the > > largest packet it can send for you or for its VLAN interfaces. The MTU > > on the lagg0.10 (VLAN) interface is the largest packet *it* can send for > > you. The VLAN tag is added to the packet that you give to lagg0.10, and > > so the MTU of lagg0.10 must be smaller than the MTU of lagg0. > > Ok, I understand all that (despite a bad cold!) - but looking at other > peoples ifconfig outputs found on google, they show: > > - Underlying interface, MTU 1500 > - LAGG interface, MTU 1500 > - VLAN sub interface, MTU 1500 > > I don't get that - from the same ifconfig-uration I get: > > - Underlying interface, MTU 1500 > - LAGG interface, MTU 1500 > - VLAN sub interface, MTU 1496 > > I thought if cards natively support VLAN's the VLAN tag was handled 'behind > the scenes' - e.g. if I go setup em3.10 - I wouldn't see the MTU drop to > 1496. > > In fact, I've just done this with em3 on that machine... > > ifconfig em3.10 create > ifconfig em3.10 inet 10.12.13.1 netmask 255.255.255.0 > ifconfig em3 inet 10.13.14.1 netmask 255.255.255.0 > > ifconfig em3 > em3: flags=8c02 metric 0 mtu 1500 > > ifconfig em3.10 > em3.10: flags=8843 metric 0 mtu 1500 > > I realise the packets sent by em3.10 will now be 1504 bytes MTU - and if > your switch doesn't support VLAN's (and/or can only cope with strict 1500 > byte packets you're probably in trouble) - but the above is doing what I'd > "expect" to happen for the LAGG case. > > I could understand losing the 4 bytes maybe if the card didn't support > native VLAN's (or having to do it if your switch can't cope with 1500+4 > byte frames) - but not if they're supported. > > > Note that the packet given to lagg0 is four bytes bigger than the packet > > given to lagg0.10, and this is always true. If you make the MTU of > > lagg0.10 equal to the MTU of lagg0, then lagg0.10 will end up generating > > packets that are oversize for lagg0, and you don't want that. > > Yes, I get that - but as I said I thought 'native VLAN' tagging was handled > differently - as shown by the example above with em3. > > afaik - Lagging interfaces has no effect on MTU, but something behind the > scenes is treating lagg0.10 differently from, say em0.10 as far as MTU > configuration goes? > > Ultimately the question is - why are other people running the same ifconfig > (admittedly on different FreeBSD versions / cards) and getting what I'd > expect [a working system], but I don't? Have you read the HARDWARE section of vlan(4)? Regards, Gary From owner-freebsd-net@freebsd.org Mon Jul 13 12:52:33 2015 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 3F48D999EC5 for ; Mon, 13 Jul 2015 12:52:33 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0D78B1A4A; Mon, 13 Jul 2015 12:52:32 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t6DCqTLs032113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jul 2015 13:52:30 +0100 (BST) Date: Mon, 13 Jul 2015 13:52:30 +0100 From: Karl Pielorz To: Gary Palmer cc: freebsd-net@freebsd.org, Steve Read Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: <558FF7CA779176D3F35B6D99@[10.12.30.106]> In-Reply-To: <20150713120651.GA68542@in-addr.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <55A37C1E.90804@stormshield.eu> <20150713120651.GA68542@in-addr.com> 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.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 12:52:33 -0000 --On 13 July 2015 13:06 +0100 Gary Palmer wrote: > Have you read the HARDWARE section of vlan(4)? Kind of cryptic answer ;) - But I just read vlan(4). So it looks like my understanding of vlans (i.e. 'long frames' as it calls them) was right? On supported kit - creating a sub interface on a VLAN on will not reduce the MTU of that sub interface, e.g. to 1496. em is listed as Hardware Tagging supported, but is not listed under the 'natively support long frames for vlan' in that man page. But I can set the MTU on em to anything I want, e.g. 1504, 1600, anything up to 9k on these cards - that's a little confusing. This still doesn't really solve the question of why the MTU remains at 1500 (as I think it should) when adding a VLAN to a standalone em interface, but it 'shrinks' to 1496 when the parent interface is a LAGG of em's. Even if the actual LAGG (and it's members) are forced to an MTU 1504 first before the VLAN interface is created (which is useless in this environment anyway), the created VLAN interface comes up with an MTU of only 1496 (i.e. not '1504 -4' if it were doing that maths). End of the man page says, "The vlan driver automatically recognizes devices that natively support long frames for vlan use and calculates the appropriate frame MTU based on the capabilities of the parent interface." I would ask - does that include if the parent interface (lagg) has another parent (i.e. em0/em1)? - It would seem to in at least some cases (i.e. the other people who seem to have this working). -Karl From owner-freebsd-net@freebsd.org Mon Jul 13 16:56:32 2015 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 2047E99C963 for ; Mon, 13 Jul 2015 16:56:32 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EAE071CB8 for ; Mon, 13 Jul 2015 16:56:31 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t6DGuVN0007062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jul 2015 09:56:31 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t6DGuVxJ007061; Mon, 13 Jul 2015 09:56:31 -0700 (PDT) (envelope-from jmg) Date: Mon, 13 Jul 2015 09:56:31 -0700 From: John-Mark Gurney To: Karl Pielorz Cc: freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: <20150713165631.GN8523@funkthat.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <20150710180627.GA8523@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Mon, 13 Jul 2015 09:56:31 -0700 (PDT) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 16:56:32 -0000 Karl Pielorz wrote this message on Mon, Jul 13, 2015 at 09:33 +0100: > --On 10 July 2015 11:06 -0700 John-Mark Gurney wrote: > > > Try bumping the MTU on the root em's by 4 (1504) before creating the > > lagg... > > I had thought of that - but didn't want to try it (on the basis that out of > all the other example config's I've seen - no one else has to, and it will > break the lagg MTU). > > Anyway I tried it, by: > > - Bump the MTU on the em interfaces before creating the lagg to 1504 > > - The lagg created, inherits this 1504 MTU > > That breaks the untagged IP on lagg0 - i.e. I end up with: > > " > lagg0: flags=8843 metric 0 mtu 1504 > > options=4019b > ether 68:05:ca:08:1d:3b > inet x.x.x.x netmask 0xffffff00 broadcast y.y.y.y > " > > That MTU of 1504 is going to break lagg0 for untagged traffic :( > > > - However, the VLAN's setup on the lagg still default to 1496 MTU (despite > the underlying interface lagg0 being MTU 1504) > > If I 'manually' bump the MTU on the individual lagg0.x VLAN interfaces - > they will go to 1500, but traffic is still 'broken'. > > I can't 'reduce' the bad MTU on lagg0 either - i.e. 'ifconfig lagg0 mtu > 1500' (to try to put it back to 1500) fails with an ioctl error. > > So sadly, I'm still stuck :( You can fix the untagged traffic on lagg0 with something like the following: route change -mtu 1500 You can see which routes need to be changed w/ the netstat -rWnfinet command... > Something is lopping 4 bytes off the MTU when it shouldn't need to. None of > the example configs I could find were from 10.1-R (or with exactly the same > cards) - but obviously this is just bread & butter lagg/VLAN stuff, so it > should work? You should be able to make it work, but it definately needs more work to make it work automaticly... There was a recent change that went in that makes changing lagg mtu easier, but I think that's only in HEAD right now... Hope this helps... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@freebsd.org Mon Jul 13 20:05:14 2015 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 DE0BE99C283 for ; Mon, 13 Jul 2015 20:05:14 +0000 (UTC) (envelope-from hiren@FreeBSD.org) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEC621D79; Mon, 13 Jul 2015 20:05:14 +0000 (UTC) (envelope-from hiren@FreeBSD.org) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPSA id 5486AD27AE; Mon, 13 Jul 2015 13:05:13 -0700 (PDT) Date: Mon, 13 Jul 2015 13:05:13 -0700 From: hiren panchasara To: freebsd-net@FreeBSD.org Cc: erj@FreeBSD.org, scottl@FreeBSD.org Subject: Exposing full 32bit RSS hash from card for ixgbe(4) Message-ID: <20150713200513.GD22795@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yudcn1FV7Hsu/q59" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 20:05:15 -0000 --yudcn1FV7Hsu/q59 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Here is the patch I'd like to push which exposes 32bit RSS has that we get from ixgbe cards irrespective of whether RSS is defined or not. https://people.freebsd.org/~hiren/patches/ix_expose_rss_hash.patch This is similar to what we've done for igb(4): r281838 In this patch I am also proposing to remove FreeBSD version check (and therefore the check for M_FLOWID) as I don't see such a check in other Intel drivers like igb(4). But I am on adamant wrt that and can restore if someone feels strongly about it. (I need to update my arc client (again) to generate the phabric review and that can take some time so I'd appreciate any reviews/comments here.) Cheers, Hiren --yudcn1FV7Hsu/q59 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJVpBn4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lsEoH/ijD2SX8Rh3t42QXz9BFjTg5 /ixOutSVunLpFM3Kmp9wbU6cFC4qvtNUN4XFvYWlA0B1AUHQEt+RHmsqERJAQo60 zWHk8ZG7Iz7pvGdDWJcB34+65OgX71yOV8DhBye+W/AVfcXhAvj0MH4eBY5jou/1 SsblrNeBddxy8HLUL0OVYkKOTWSeRo+UjZaLltX/90jXIc0ygJdz/C2Oa9bWXl+k 0MdKWANprSw0p9XNXcpaKHeHMGmZ1FpejQWzs5RcVz/f5KVDAj1BsSnwlh+ZKhG9 FekeuPcJqLa0Utx3bRYKwj95bRxOn6LsFJZRNywbVlfITAcouzGj+nFo553Fvf8= =sQ1H -----END PGP SIGNATURE----- --yudcn1FV7Hsu/q59-- From owner-freebsd-net@freebsd.org Mon Jul 13 22:16:00 2015 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 8877299CE3E for ; Mon, 13 Jul 2015 22:16:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 55E0BFA8; Mon, 13 Jul 2015 22:16:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iggp10 with SMTP id p10so86168896igg.0; Mon, 13 Jul 2015 15:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4HZS4dXNoPi7ThfQUmPMIfO541pUjyM1o6I+sBbOBMY=; b=q3zIgG1B+3f0sdLUWvaXUgeL67eCgxdcLugoTjvV6ldykPmXUp2zWbTb7cN2wZVuFD 7K8Fz2U5JVxiBvVnZLy0Tw7SMgCY6YN4MTKfzsT4R6/+1zTgWRYr0mV/yy1fpF5vJT+H IIgniFtvyoL24LUz100Qpb5wiWxoOWePowZDVeCT/g2V6kICoKSS03u3pTtACdfqM6HN J675Slqk/gHJyXw7z1weU5gedh6ea8j35V6eV7nWIMi+pD8LJ6Ui5XVRfgbUp2NAvZb0 LJy4oKRqzUlvXZ2ub9maIdeXSFLxo3u/tKd81vZacoceJY4bvtTwtU1FT9Q7C8NgaYoz pWCQ== MIME-Version: 1.0 X-Received: by 10.107.27.195 with SMTP id b186mr19122825iob.140.1436825759765; Mon, 13 Jul 2015 15:15:59 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Mon, 13 Jul 2015 15:15:59 -0700 (PDT) In-Reply-To: <20150713200513.GD22795@strugglingcoder.info> References: <20150713200513.GD22795@strugglingcoder.info> Date: Mon, 13 Jul 2015 15:15:59 -0700 Message-ID: Subject: Re: Exposing full 32bit RSS hash from card for ixgbe(4) From: Adrian Chadd To: hiren panchasara Cc: FreeBSD Net , Eric Joyner , "scottl@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 22:16:00 -0000 Hi, It's fine by me. Please do it! -a On 13 July 2015 at 13:05, hiren panchasara wrote: > Here is the patch I'd like to push which exposes 32bit RSS has that we > get from ixgbe cards irrespective of whether RSS is defined or not. > > https://people.freebsd.org/~hiren/patches/ix_expose_rss_hash.patch > > This is similar to what we've done for igb(4): r281838 > > In this patch I am also proposing to remove FreeBSD version check (and > therefore the check for M_FLOWID) as I don't see such a check in other > Intel drivers like igb(4). But I am on adamant wrt that and can restore > if someone feels strongly about it. > > (I need to update my arc client (again) to generate the phabric review > and that can take some time so I'd appreciate any reviews/comments > here.) > > Cheers, > Hiren From owner-freebsd-net@freebsd.org Tue Jul 14 00:39:13 2015 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 A812C999B40 for ; Tue, 14 Jul 2015 00:39:13 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (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 6DCB51EAD; Tue, 14 Jul 2015 00:39:12 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by iebmu5 with SMTP id mu5so1111630ieb.1; Mon, 13 Jul 2015 17:39:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=VzwQyVkS1sPWMwRhymnhtiFwV6j49iZgEM/y6YOrOPw=; b=CTlzpGku2PYOPjYVkj8c03fuhcTKpLVmeq8SR4yVPsl7sGs7jDSlBKvmvzeuBeAi5l dxe0X0aRPeUjtltq0Vy8Ql8NmjsRh4QlFZT7Ck15yMWrOvmufyzlvhgoSY0LXsTHjDDd NeH4HV6jGJnytJXxAly6VbNslre2NlLDUT3V/olF0kzDgKl9sPTe4QsjG6Qj9iOLYbVr vVkjJij9yT84LwRBpUdszngi6FFaytt98vLLV4iZp2Gr09KcEegpln2VdrW3mEqgfP79 U0qhjbMVB+SZToq0X6DEelXb32sRiLJiDAE7ODVU8GczJx4cmRlcOuavE8KrFr3oEVN4 PN0w== X-Received: by 10.50.40.42 with SMTP id u10mr11758001igk.71.1436834346005; Mon, 13 Jul 2015 17:39:06 -0700 (PDT) Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com. [209.85.213.169]) by smtp.gmail.com with ESMTPSA id e69sm2547344ioe.31.2015.07.13.17.39.05 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jul 2015 17:39:05 -0700 (PDT) Received: by igbpg9 with SMTP id pg9so1249208igb.0; Mon, 13 Jul 2015 17:39:05 -0700 (PDT) X-Received: by 10.50.79.169 with SMTP id k9mr14411093igx.63.1436834345591; Mon, 13 Jul 2015 17:39:05 -0700 (PDT) MIME-Version: 1.0 References: <20150713200513.GD22795@strugglingcoder.info> In-Reply-To: From: Eric Joyner Date: Tue, 14 Jul 2015 00:38:56 +0000 Message-ID: Subject: Re: Exposing full 32bit RSS hash from card for ixgbe(4) To: Adrian Chadd , hiren panchasara Cc: FreeBSD Net , "scottl@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 00:39:13 -0000 Sorry for the delay; it looked fine to me, but I never got back to you. - Eric On Mon, Jul 13, 2015 at 3:16 PM Adrian Chadd wrote: > Hi, > > It's fine by me. Please do it! > > > -a > > > On 13 July 2015 at 13:05, hiren panchasara wrote: > > Here is the patch I'd like to push which exposes 32bit RSS has that we > > get from ixgbe cards irrespective of whether RSS is defined or not. > > > > https://people.freebsd.org/~hiren/patches/ix_expose_rss_hash.patch > > > > This is similar to what we've done for igb(4): r281838 > > > > In this patch I am also proposing to remove FreeBSD version check (and > > therefore the check for M_FLOWID) as I don't see such a check in other > > Intel drivers like igb(4). But I am on adamant wrt that and can restore > > if someone feels strongly about it. > > > > (I need to update my arc client (again) to generate the phabric review > > and that can take some time so I'd appreciate any reviews/comments > > here.) > > > > Cheers, > > Hiren > From owner-freebsd-net@freebsd.org Tue Jul 14 09:18:54 2015 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 0DD9999CB9B for ; Tue, 14 Jul 2015 09:18:54 +0000 (UTC) (envelope-from hiren@freebsd.org) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE6E5329; Tue, 14 Jul 2015 09:18:53 +0000 (UTC) (envelope-from hiren@freebsd.org) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPSA id A4A36D1555; Tue, 14 Jul 2015 02:18:47 -0700 (PDT) Date: Tue, 14 Jul 2015 02:18:47 -0700 From: hiren panchasara To: Eric Joyner Cc: Adrian Chadd , FreeBSD Net , "scottl@freebsd.org" Subject: Re: Exposing full 32bit RSS hash from card for ixgbe(4) Message-ID: <20150714091847.GI22795@strugglingcoder.info> References: <20150713200513.GD22795@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RwxaKO075aXzzOz0" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 09:18:54 -0000 --RwxaKO075aXzzOz0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 07/14/15 at 12:38P, Eric Joyner wrote: > Sorry for the delay; it looked fine to me, but I never got back to you. >=20 > - Eric >=20 > On Mon, Jul 13, 2015 at 3:16 PM Adrian Chadd wro= te: >=20 > > Hi, > > > > It's fine by me. Please do it! Thanks Adrian and Eric. Committed as r285528. Cheers, Hiren --RwxaKO075aXzzOz0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJVpNP3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lOe8H/RhG5mi2pf2a5Khy5zbVSEOT bsESMfdJCyU/0/ukceYKeUq+GQGVst9yNoKLO0egGbFjSAG9C1bS7rnK+ThTeHy0 G0Oodl531fKneSZvbdpJwUvkUpbDlXbOnIBJYV0F45H/pi/os2tdHK0/5zhCejnO G10JDvK9pq10yqzeOUVrHno4lNjEa/29tivZbJpHWuUDEqMUQ4whmVLQAhpBUbl3 ADR19fnn3uopKwfGQ7rPwGDOFQxpQCUuxY+1ZcQz3jWO79gisgSSId/rZLMoDWqF MBZStw0+UQZeBywa4R1KK6iwyVmNmu2fTijYFqrimQGzCzzGJEebA6mplsHqDOY= =mSAC -----END PGP SIGNATURE----- --RwxaKO075aXzzOz0-- From owner-freebsd-net@freebsd.org Tue Jul 14 10:28:25 2015 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 0837E99C1E5 for ; Tue, 14 Jul 2015 10:28:25 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.wp.pl", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8679FB52 for ; Tue, 14 Jul 2015 10:28:24 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: (wp-smtpd smtp.wp.pl 20254 invoked from network); 14 Jul 2015 12:28:14 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a; t=1436869694; bh=CfQS6jgVsCtpGNAOfgSq1401uy+1tKQSlzUWjs/NHTU=; h=Subject:To:From; b=QzCdIAptWbuNVzxs+AzkvrvwhgBiReC5hLaf/ZdHLPTTK3i+fzRHp4bnsb5yYLQWe 2yJ+wfMeKwfQWtJE//llrnpMwq9rdIyatUtZEF8rO0AYoKR0iPyxqjOn2Y4+omjoCy ZvcKszGqobcbdrVIMsbN0H6lzt7SQWucaBBKIy6E= Received: from pb-d-128-141-2-235.cern.ch (HELO [128.141.2.235]) (marek_sal@[128.141.2.235]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with ECDHE-RSA-AES256-SHA encrypted SMTP for ; 14 Jul 2015 12:28:14 +0200 Subject: Re: lagg of em0/em1 + VLAN = lower MTU? To: Karl Pielorz , freebsd-net@freebsd.org References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> From: Marek Salwerowicz Message-ID: <55A4E429.10605@wp.pl> Date: Tue, 14 Jul 2015 12:27:53 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-WP-MailID: 830a4b82da7f2ca24da6e2a291434342 X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [cfOU] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 10:28:25 -0000 W dniu 2015-07-10 o 15:04, Karl Pielorz pisze: > > > The MTU on lagg0.10 has shrunk by 4 (size of VLAN tag). Is there a way > of avoiding that? That's my working setup (hardware is based on http://www.supermicro.com/products/system/4U/6047/SSG-6047R-E1R36L.cfm) #/etc/rc.conf: ifconfig_igb0="mtu 9000 up" ifconfig_igb1="mtu 9000 up" ifconfig_igb2="mtu 9000 up" ifconfig_igb3="mtu 9000 up" cloned_interfaces="lagg0 vlan14 vlan100 vlan900" ifconfig_lagg0="laggproto lacp laggport igb0 laggport igb1 laggport igb2 laggport igb3" #VLAN ifconfig_vlan14="inet 192.168.1.72/24 vlan 14 vlandev lagg0" ifconfig_vlan100="inet 192.168.21.253/24 vlan 100 vlandev lagg0" ifconfig_vlan900="inet 172.25.25.72/24 vlan 900 vlandev lagg0" % ifconfig -a | grep mtu igb0: flags=8843 metric 0 mtu 9000 igb1: flags=8843 metric 0 mtu 9000 igb2: flags=8843 metric 0 mtu 9000 igb3: flags=8843 metric 0 mtu 9000 lo0: flags=8049 metric 0 mtu 16384 lagg0: flags=8843 metric 0 mtu 9000 vlan14: flags=8843 metric 0 mtu 9000 vlan100: flags=8843 metric 0 mtu 9000 vlan900: flags=8843 metric 0 mtu 9000 Reboot is needed after MTU change. Cheers -- Marek From owner-freebsd-net@freebsd.org Wed Jul 15 12:21:50 2015 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 E35559A2711 for ; Wed, 15 Jul 2015 12:21:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B58D31214 for ; Wed, 15 Jul 2015 12:21:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6FCLogP070772 for ; Wed, 15 Jul 2015 12:21:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200221] em0 watchdog timeout under load Date: Wed, 15 Jul 2015 12:21:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: anthony@ury.org.uk X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 12:21:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200221 --- Comment #10 from anthony@ury.org.uk --- Now using sys/dev/e1000@283959 from 10-STABLE (rest of the kernel 10.1-RELEASE as before), I'm seeing watchdog timeouts again, with tso4 enabled. Again, this only seems to happen at a point of high network load (nightly backup over NFS). I'll try disabling tso4 on this revision but failing that, will go back to e1000@269196. There is slightly more detail in messages now, though: Jul 8 07:31:58 urybsod kernel: em0: Watchdog timeout Queue[0]-- resetting Jul 8 07:31:58 urybsod kernel: Interface is RUNNING and ACTIVE Jul 8 07:31:58 urybsod kernel: em0: TX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw tdh = 909, hw tdt = 1015 Jul 8 07:31:58 urybsod kernel: em0: Tx Queue Status = -2147483648 Jul 8 07:31:58 urybsod kernel: em0: TX descriptors avail = 914 Jul 8 07:31:58 urybsod kernel: em0: Tx Descriptors avail failure = 114 Jul 8 07:31:58 urybsod kernel: em0: RX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw rdh = 959, hw rdt = 958 Jul 8 07:31:58 urybsod kernel: em0: RX discarded packets = 0 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Check = 959 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Refresh = 958 Jul 8 07:31:58 urybsod kernel: em0: Link is Down Jul 8 07:31:58 urybsod kernel: em0: link state changed to DOWN Jul 8 07:32:01 urybsod kernel: em0: Link is up 1000 Mbps Full Duplex Jul 8 07:32:01 urybsod kernel: em0: link state changed to UP Jul 8 07:32:01 urybsod devd: Executing '/etc/rc.d/dhclient quietstart em0' -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@freebsd.org Wed Jul 15 16:19:23 2015 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 624BF9A1A22 for ; Wed, 15 Jul 2015 16:19:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4EFC01628 for ; Wed, 15 Jul 2015 16:19:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6FGJNP6094283 for ; Wed, 15 Jul 2015 16:19:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200221] em0 watchdog timeout under load Date: Wed, 15 Jul 2015 16:19:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 16:19:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200221 --- Comment #11 from Sean Bruno --- Can you try the following patch to if_em.c and see if it helps? I'm trying to diagnose this here. Index: dev/e1000/if_em.c =================================================================== --- dev/e1000/if_em.c (revision 285481) +++ dev/e1000/if_em.c (working copy) @@ -3034,6 +3034,9 @@ if_setflags(ifp, IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST); if_setioctlfn(ifp, em_ioctl); if_setgetcounterfn(ifp, em_get_counter); + ifp->if_hw_tsomax = 65518; /* 32*MCLBYTES - max_mac_hdr_len*/ + ifp->if_hw_tsomaxsegcount = EM_MAX_SCATTER; + ifp->if_hw_tsomaxsegsize = 65536; #ifdef EM_MULTIQUEUE /* Multiqueue stack interface */ if_settransmitfn(ifp, em_mq_start); -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@freebsd.org Wed Jul 15 16:19:48 2015 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 772789A1A39 for ; Wed, 15 Jul 2015 16:19:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63B9316B5 for ; Wed, 15 Jul 2015 16:19:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6FGJmde094431 for ; Wed, 15 Jul 2015 16:19:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 199174] em tx and rx hang Date: Wed, 15 Jul 2015 16:19:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sbruno@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: mfc-stable9? mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 16:19:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199174 --- Comment #29 from Sean Bruno --- (In reply to david.keller from comment #28) Rick has suggested this. It seems to work, but I'm unsure of the impact. Can you try the following patch to if_em.c and see if it helps? I'm trying to diagnose this here. Index: dev/e1000/if_em.c =================================================================== --- dev/e1000/if_em.c (revision 285481) +++ dev/e1000/if_em.c (working copy) @@ -3034,6 +3034,9 @@ if_setflags(ifp, IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST); if_setioctlfn(ifp, em_ioctl); if_setgetcounterfn(ifp, em_get_counter); + ifp->if_hw_tsomax = 65518; /* 32*MCLBYTES - max_mac_hdr_len*/ + ifp->if_hw_tsomaxsegcount = EM_MAX_SCATTER; + ifp->if_hw_tsomaxsegsize = 65536; #ifdef EM_MULTIQUEUE /* Multiqueue stack interface */ if_settransmitfn(ifp, em_mq_start); -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-net@freebsd.org Wed Jul 15 18:01:41 2015 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 8F2979A20CC for ; Wed, 15 Jul 2015 18:01:41 +0000 (UTC) (envelope-from hiren@freebsd.org) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A1A111C2; Wed, 15 Jul 2015 18:01:40 +0000 (UTC) (envelope-from hiren@freebsd.org) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPSA id E07CDD2A07; Wed, 15 Jul 2015 11:01:38 -0700 (PDT) Date: Wed, 15 Jul 2015 11:01:38 -0700 From: hiren panchasara To: Eric Joyner Cc: Adrian Chadd , FreeBSD Net , "scottl@freebsd.org" Subject: Re: Exposing full 32bit RSS hash from card for ixgbe(4) Message-ID: <20150715180138.GK8260@strugglingcoder.info> References: <20150713200513.GD22795@strugglingcoder.info> <20150714091847.GI22795@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fLj60tP2PZ34xyqD" Content-Disposition: inline In-Reply-To: <20150714091847.GI22795@strugglingcoder.info> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 18:01:41 -0000 --fLj60tP2PZ34xyqD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 07/14/15 at 02:18P, hiren panchasara wrote: > On 07/14/15 at 12:38P, Eric Joyner wrote: > > Sorry for the delay; it looked fine to me, but I never got back to you. > >=20 > > - Eric > >=20 > > On Mon, Jul 13, 2015 at 3:16 PM Adrian Chadd w= rote: > >=20 > > > Hi, > > > > > > It's fine by me. Please do it! >=20 > Thanks Adrian and Eric. Committed as r285528. FYI: I am planning to do a partial mfc of this to stable10. Here is the patch: https://people.freebsd.org/~hiren/patches/ix_expose_rss_hash_stable10.patch (I did the same for igb(4), r282831) Cheers, Hiren --fLj60tP2PZ34xyqD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQF8BAEBCgBmBQJVpqABXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/l5Z0H/RRamX6w8lXrnMDbldi9eCwb UuDcwYPbKwOge9rmTaUMycF3oxT1XmXZJcc+1D1/ToITTCZZ1bG9MKzNCxXQZu50 YYuuA7HEi6gWnEp4EnxiX1Jq1GNQiP2DtsIHkGqHKrOOCMAzhIcE/pk/F7KACnDq UlOGVjX1JLqq+gDv8CCyQVqbfCVdO9kzrO7VxCaHKETeCs0UKM5IhNmtOIILXdAW +H7SeLwUXedJtGwg8wpr2Pp2E7v4CefIMJjrAnGz9iued5vf9WfIYwAFrIDRCCM1 y7o/zWyrvpD9di3j/BWwtObcOZ0GrIsOHUl3jVXKV1eJUEi2RQta5XYCp97MCb0= =kyzy -----END PGP SIGNATURE----- --fLj60tP2PZ34xyqD-- From owner-freebsd-net@freebsd.org Wed Jul 15 22:25:53 2015 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 C5C279A385D for ; Wed, 15 Jul 2015 22:25:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 905B41225; Wed, 15 Jul 2015 22:25:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by oihq81 with SMTP id q81so38651163oih.2; Wed, 15 Jul 2015 15:25:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=/km6WZboF0P6hgB3cBHmFYCuzwxl2JXeeLc/cvpLNIg=; b=g+nmIoXOmY6FzxfBrluI84CYSmWDDADiUWt1sETxNhlirCkuyduSi6a0P9T1P6quvs 5/w5Bk2SxD+OgKO5uMSytaUNMZnd7dlkBc+doRcY/BOibQjBIEbe+Z5rIaPXCICYKkyA +dITf0/5COfwDv34WGrVl61XOfbgYQ+aOBvjXP/DNLIxoxs0fik0upbyY7fzCU5iD1qe DSxg3kn5NJEgEcvdNC3KxMc9uLRQz09kqS3kwn93JFi0xcjK2zX67B0AN/Ix/p8K3S3R QbgL5Wu1YxCv79zIDh5rMppf8lUuiCgoIjZXntjVx6eJU28vNxAwVciTn9kVJoRIVxX7 R9tw== MIME-Version: 1.0 X-Received: by 10.182.65.164 with SMTP id y4mr5701769obs.65.1436999152860; Wed, 15 Jul 2015 15:25:52 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.71.135 with HTTP; Wed, 15 Jul 2015 15:25:52 -0700 (PDT) Date: Wed, 15 Jul 2015 16:25:52 -0600 X-Google-Sender-Auth: PWvrsZoxLCOn4Ug7T3DBuDUKaRY Message-ID: Subject: Displaying the supported module types of a network adapter From: Alan Somers To: FreeBSD Net , Navdeep Parhar , "Alexander V. Chernikov" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 22:25:53 -0000 SIOCGIFMEDIA will return the list of supported media types and the current media type of a network interface. But for NICs with pluggable modules (SFP+, QSFP, etc), it would also be useful to know the allowed module type. I can't find any way to determine that using the standard tools. cxgbe(4) is aware of the module type allowed by the card, but doesn't expose that information to userspace. I can add a simple sysctl to do so, but it would be better to add a standard ioctl that can be used by all network drivers. Besides cxgbe(4), can any other network drivers support this? If so, would anybody else be interested? If so, should I add it to the "ifconfig -v" output? -Alan From owner-freebsd-net@freebsd.org Thu Jul 16 07:18:37 2015 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 B30539A39F7 for ; Thu, 16 Jul 2015 07:18:37 +0000 (UTC) (envelope-from admin@WHW0050.whservidor.com) Received: from a2-salada2.whservidor.com (a2-salada2-webwindows.whservidor.com [200.147.34.186]) by mx1.freebsd.org (Postfix) with ESMTP id 3CF991FE6 for ; Thu, 16 Jul 2015 07:18:35 +0000 (UTC) (envelope-from admin@WHW0050.whservidor.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by a2-salada2.whservidor.com (Postfix) with ESMTP id 566DE1C01A9C for ; Thu, 16 Jul 2015 04:09:27 -0300 (BRT) Received: from a2-salada2.whservidor.com ([127.0.0.1]) by localhost (a2-salada2.host.intranet [127.0.0.1]) (UOL-patch-amavisd-new, port 30024) with ESMTP id OvUKJ2lz8Cij for ; Thu, 16 Jul 2015 04:09:27 -0300 (BRT) Received: from whw0050.uolhost.org (whw0050.whservidor.com [200.98.255.130]) by a2-salada2.whservidor.com (Postfix) with ESMTP id 0A2231C01ADD for ; Thu, 16 Jul 2015 04:09:22 -0300 (BRT) Received: from a1-whw-b50 ([200.98.255.130]) by whw0050.uolhost.org with Microsoft SMTPSVC(7.0.6002.18222); Thu, 16 Jul 2015 03:45:40 -0300 Subject: Indebted for driving on toll road #000518415 To: freebsd-net@freebsd.org Date: Thu, 16 Jul 2015 03:45:40 -0300 From: "E-ZPass Agent" Reply-To: "E-ZPass Agent" Message-ID: X-Priority: 3 MIME-Version: 1.0 X-PHP-Script: E:\home\universalc\Web\post.php(13) : eval()'d code X-OriginalArrivalTime: 16 Jul 2015 06:45:40.0279 (UTC) FILETIME=[07A05470:01D0BF93] X-SIG5: 6e7dcb12c80aa5d6a9d63eed5e744265 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 16 Jul 2015 07:18:37 -0000 Notice to Appear, You have a unpaid bill for using toll road. You are kindly asked to service your debt in the shortest time possible. You can find the invoice is in the attachment. Kind regards, Ian Schaefer, E-ZPass Agent. From owner-freebsd-net@freebsd.org Thu Jul 16 13:01:52 2015 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 2811199C51C for ; Thu, 16 Jul 2015 13:01:52 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward17p.cmail.yandex.net (forward17p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::b3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE2AB1AF5; Thu, 16 Jul 2015 13:01:51 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web4g.yandex.ru (web4g.yandex.ru [95.108.252.104]) by forward17p.cmail.yandex.net (Yandex) with ESMTP id 8AAE322439; Thu, 16 Jul 2015 16:01:46 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web4g.yandex.ru (Yandex) with ESMTP id DBCD23800CAF; Thu, 16 Jul 2015 16:01:45 +0300 (MSK) Received: by web4g.yandex.ru with HTTP; Thu, 16 Jul 2015 16:01:45 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Alan Somers , FreeBSD Net , Navdeep Parhar In-Reply-To: References: Subject: Re: Displaying the supported module types of a network adapter MIME-Version: 1.0 Message-Id: <1127061437051705@web4g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 16 Jul 2015 16:01:45 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 16 Jul 2015 13:01:52 -0000 16.07.2015, 01:25, "Alan Somers" : > SIOCGIFMEDIA will return the list of supported media types and the > current media type of a network interface. But for NICs with > pluggable modules (SFP+, QSFP, etc), it would also be useful to know > the allowed module type. I can't find any way to determine that using Well, it might be a bit tricky. There are basically 2 parts: physical constraints and logical ones. E.g. first we have to specify what we could physically insert (gbic, rj45?, sfp/sfp+, qsfp+). Here we can consider adopting values from ftp://ftp.seagate.com/sff/SFF-8024.PDF Table 4.1 Next step would be specifying what exact modules could be used. Examples could be: * 1G sfp on 10G card (chip constraint) * qsfp<>sfp hydra cables (chip constraint) * QSFP-2-SFP+ (chip constraint) * using SR/LR transceiver on card, sold as "Direct attached one" (Vendor SW constraint) It looks like that bit masks from TABLE 6-17 SPECIFICATION COMPLIANCE CODES from ftp://ftp.seagate.com/sff/SFF-8636.PDF can be adopted for the logical part. so we could have something like { u16 version; u16 cage_type; u32 spare; u64 module_type; u64 spare; } for the new ioctl. > the standard tools. cxgbe(4) is aware of the module type allowed by > the card, but doesn't expose that information to userspace. I can add > a simple sysctl to do so, but it would be better to add a standard > ioctl that can be used by all network drivers. > > Besides cxgbe(4), can any other network drivers support this? If so, > would anybody else be interested? If so, should I add it to the > "ifconfig -v" output? > > -Alan From owner-freebsd-net@freebsd.org Thu Jul 16 14:53:16 2015 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 EFBA59A1CAD for ; Thu, 16 Jul 2015 14:53:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id BEB661C3D for ; Thu, 16 Jul 2015 14:53:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t6GEr8Nr042377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jul 2015 15:53:09 +0100 (BST) Date: Thu, 16 Jul 2015 15:53:08 +0100 From: Karl Pielorz To: John-Mark Gurney cc: freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: <162CD3DC2BDDC847DF7987D0@[10.12.30.106]> In-Reply-To: <20150713165631.GN8523@funkthat.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <20150710180627.GA8523@funkthat.com> <20150713165631.GN8523@funkthat.com> 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.20 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, 16 Jul 2015 14:53:17 -0000 --On 13 July 2015 09:56 -0700 John-Mark Gurney wrote: > You can fix the untagged traffic on lagg0 with something like the > following: > route change -mtu 1500 > > You can see which routes need to be changed w/ the netstat -rWnfinet > command... Ok, that works. It's clunky - but it works... > You should be able to make it work, but it definately needs more work > to make it work automaticly... There was a recent change that went > in that makes changing lagg mtu easier, but I think that's only in > HEAD right now... Presumably, other people configuring it don't run into the issue (lagg+VLAN) because of different FreeBSD version / NIC's? Is the issue just that the VLAN code thinks the LAGG is the parent, and doesn't "see" the underlying card is long-frame capable? Or is it as simple as the em cards not being listed as 'long-frame capable' (i.e. from the man page). > Hope this helps... Certainly appears to have, thanks! -Karl From owner-freebsd-net@freebsd.org Thu Jul 16 16:30:51 2015 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 74D1B9A333B for ; Thu, 16 Jul 2015 16:30:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A4B11C62 for ; Thu, 16 Jul 2015 16:30:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6GGUpDc080465 for ; Thu, 16 Jul 2015 16:30:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 168246] [em] Multiple legacy em(4) not working with qemu Date: Thu, 16 Jul 2015 16:30:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.0-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 16 Jul 2015 16:30:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168246 Sean Bruno changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[em] Multiple em(4) not |[em] Multiple legacy em(4) |working with qemu |not working with qemu --- Comment #2 from Sean Bruno --- If you get a chance to retest this, can you try this with 10 or head? The driver being used in freebsd is lem(4) and not em(4) for this adapter and I'm curious if its still broken for you. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@freebsd.org Thu Jul 16 18:35:13 2015 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 541F49A3F54 for ; Thu, 16 Jul 2015 18:35:13 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3661E84 for ; Thu, 16 Jul 2015 18:35:13 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.isc.freebsd.org (Postfix, from userid 1346) id 39A45E70C; Thu, 16 Jul 2015 18:35:13 +0000 (UTC) Date: Thu, 16 Jul 2015 18:35:13 +0000 To: freebsd-net@freebsd.org From: "robak (Bartek Rutkowski)" Reply-to: D1944+325+8925873bdc96dfc2@FreeBSD.org Subject: [Differential] [Commented On] D1944: PF and VIMAGE fixes Message-ID: X-Priority: 3 Thread-Topic: D1944: PF and VIMAGE fixes X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: NDc2NzM0MzY4OTdiYThiNTU1MjY2ZDZmMTJiIFWn+WE= Precedence: bulk X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2015 18:35:13 -0000 robak added a comment. Is there any update on those fixes? REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, zec, trociny, kristof, gnn, glebius, rodrigc Cc: julian, robak, freebsd-virtualization-list, freebsd-pf-list, freebsd-net-list From owner-freebsd-net@freebsd.org Thu Jul 16 18:36:19 2015 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 3294F9A30F0 for ; Thu, 16 Jul 2015 18:36:19 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) by mx1.freebsd.org (Postfix) with ESMTP id 184E616E1 for ; Thu, 16 Jul 2015 18:36:19 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.isc.freebsd.org (Postfix, from userid 1346) id 13A06E7E1; Thu, 16 Jul 2015 18:36:19 +0000 (UTC) Date: Thu, 16 Jul 2015 18:36:19 +0000 To: freebsd-net@freebsd.org From: "robak (Bartek Rutkowski)" Reply-to: D1309+325+0d824220adb279e7@FreeBSD.org Subject: [Differential] [Commented On] D1309: VIMAGE PF fixes #1 Message-ID: X-Priority: 3 Thread-Topic: D1309: VIMAGE PF fixes #1 X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: NzA2ZjJlODRkOGZmNmYwM2M1MmQ1N2YzYTJkIFWn+aM= Precedence: bulk X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2015 18:36:19 -0000 robak added a subscriber: robak. robak added a comment. Is there update to these fixes? REVISION DETAIL https://reviews.freebsd.org/D1309 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: rodrigc, glebius, trociny, zec, network, gnn, bz Cc: robak, emaste, freebsd-virtualization-list, freebsd-pf-list, freebsd-net-list From owner-freebsd-net@freebsd.org Fri Jul 17 15:40:57 2015 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 1D3B59A48A2 for ; Fri, 17 Jul 2015 15:40:57 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (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 E32651FAF; Fri, 17 Jul 2015 15:40:56 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by ietj16 with SMTP id j16so79689862iet.0; Fri, 17 Jul 2015 08:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=48znXJr+cQpaKejSINw2ha2VWEC8xWMLjqnim6C5/o0=; b=lzknyh+lP2BWxlr/0lWGLear0mjsLFimSrcSaQx0nhMFRRRnj5g5/LxwdJ0uQ663lk k63fUvnRRjVK42biC6P23A5lF2eUCEkp01ng1hjQS2luX9RQgGxUa2u+Ix4+kSQo3JfF TWWMnUGfQhnJyYn2pdgKuACIgnBWSQmCQ1GzwihxuaahGht7hICHBQCbs/S24qlkWt/S 6Y8H+Hj7DMWl08Et2GEIBzp54nWDMpNYtQoiqfSJWnLAyHbAXgQ9toeeAIGvTMgfrWz5 HtBo1K9/ubETBxVXxCJQwOsJIbyQdHIId/oWRVkEvpIOiAlhPdV6H8oMsCBjuuc+zslt Jfyw== X-Received: by 10.107.7.21 with SMTP id 21mr19637347ioh.81.1437147656237; Fri, 17 Jul 2015 08:40:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eric Joyner Date: Fri, 17 Jul 2015 15:40:46 +0000 Message-ID: Subject: Re: Displaying the supported module types of a network adapter To: Alan Somers , FreeBSD Net , Navdeep Parhar , "Alexander V. Chernikov" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 17 Jul 2015 15:40:57 -0000 ixl(4) will list all of the supported module types for the device if you use ifconfig -m, but I know that isn't the intended purpose of the -m flag. I wouldn't mind moving all of that to another function whose purpose is to just list all supported module types. - Eric On Wed, Jul 15, 2015 at 3:26 PM Alan Somers wrote: > SIOCGIFMEDIA will return the list of supported media types and the > current media type of a network interface. But for NICs with > pluggable modules (SFP+, QSFP, etc), it would also be useful to know > the allowed module type. I can't find any way to determine that using > the standard tools. cxgbe(4) is aware of the module type allowed by > the card, but doesn't expose that information to userspace. I can add > a simple sysctl to do so, but it would be better to add a standard > ioctl that can be used by all network drivers. > > Besides cxgbe(4), can any other network drivers support this? If so, > would anybody else be interested? If so, should I add it to the > "ifconfig -v" output? > > -Alan > _______________________________________________ > 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" >