From owner-freebsd-net@freebsd.org Sun May 8 09:33:13 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 0240DB30487 for ; Sun, 8 May 2016 09:33:13 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 D082B17D0 for ; Sun, 8 May 2016 09:33:12 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pa0-x22c.google.com with SMTP id bt5so61762104pac.3 for ; Sun, 08 May 2016 02:33:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ELX8ovyGI6VHWi0eVtFImuMy1D4DtOam+YSEBh92dfc=; b=y8y1whdshim/stv1tF8io2/l7vsFZj+wvt3GEfKsW6b+kE+9vmApkwuKAafmC/INFD rDpU5FsLIf2idhFTc79SXfAZPGZDQe9I/uR/mHXnyVx4RYpHQIxMVhpBEKGtlxPheqfd ik45a5lPokWlD6609k2w3sWSICT2R+5iZzF5CLyge8wuj9QElY7MLi7KUmB4wOdpAN7u 6nVffJ0nJ8KeJRBMxa+10B2c7QTmnbkdA/5A+z0sqWcd+OalucTQz/yGMFWHyjCQH0e4 j9mD0GjIFSKROjKAJJwQFnQbXfrLpLYeKpxdX+859YHOvm5xonmd7OKDNMtPR8X5g4RO apSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=ELX8ovyGI6VHWi0eVtFImuMy1D4DtOam+YSEBh92dfc=; b=gOmvGcv2R3wPjGguPhnDHZByuhkoPA0R85X/AKAEyIpGDgqKGP7arb8d0BRQm2NDFX ili+j95r51A1pNFMf7uwGWQ7VY78tXnBrrcfjuYSkhGY3cM7S3F56uLROs3YYiTr+k3c o4iqIgBLtUuhUSDp4QzXX3esSlmZapdE1YMLEvG/yolvg0bbigo7C1pIPsrTTkLIdUR0 VXZUp+YX9/z+CYWlM8dFc/CIAa5f8PYKMHpnoVDO4sceCRE5RCxkUS2OUopvRDfu3sOQ 97Ly/Z9IzLGaM2xTykIVzCUIZ0KtfWMqFPJguFKYHZbQaLcMKNt6jv2laWRYvKsui1z7 rlsQ== X-Gm-Message-State: AOPr4FXDZIohnoExBpPYLQMaiwGyjnEnF0MM0gKMolI0hoioXW+lDLTp8VRxP4d3HBYBmw== X-Received: by 10.67.1.233 with SMTP id bj9mr41742746pad.46.1462699992310; Sun, 08 May 2016 02:33:12 -0700 (PDT) Received: from localhost ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id 63sm32663500pff.43.2016.05.08.02.33.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 May 2016 02:33:11 -0700 (PDT) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Sun, 08 May 2016 18:33:06 +0900 Date: Sun, 8 May 2016 18:33:05 +0900 To: Yuri Cc: Eugene Grosbein , freebsd-net@freebsd.org Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time Message-ID: <20160508093305.GA1558@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <572E18E3.30300@rawbw.com> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 09:33:13 -0000 On Sat, May 07, 2016 at 09:33:39AM -0700, Yuri wrote: > On 05/07/2016 08:34, Eugene Grosbein wrote: > > > >Verify if your mouse (USB one?) is using IRQ 18 too. > >"vmstat -ai" command would be helpful. > Yes, I have a USB mouse, and my USB uses IRQ 18: > > irq18: ehci0 uhci5 503154 9 > stray irq18 0 0 > msk(4) will try to use MSI unless not configured to do so the IRQ wouldn't be shared with other devices. If msk(4) is using MSI you should see a high irq number greater than or equal to 256 in vmstat output. Given that you're seeing issues with MSI, try disabling MSI for msk(4). Add the following tunable to /boot/loader.conf and reboot. hw.msk.msi_disable="1" Let me know whether that makes any difference for you. From owner-freebsd-net@freebsd.org Sun May 8 21:00:12 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 0AA8EB33D18 for ; Sun, 8 May 2016 21:00:12 +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 01E5F1753 for ; Sun, 8 May 2016 21:00:12 +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 u48L0136058769 for ; Sun, 8 May 2016 21:00:11 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201605082100.u48L0136058769@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 Date: Sun, 08 May 2016 21:00:11 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 21:00:12 -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 ------------+-----------+--------------------------------------------------- In Progress | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic Open | 148807 | [panic] 8.1-RELEASE/10.1-STABLE "panic: sbdrop" a Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 201694 | 10.2-BETA2 crashing when killing VIMAGE/VNET jail Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; 12 problems total for which you should take action. From owner-freebsd-net@freebsd.org Sun May 8 21:35:37 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 823E2B327CD for ; Sun, 8 May 2016 21:35:37 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 06F071BEA; Sun, 8 May 2016 21:35:37 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id u64so182182391lff.3; Sun, 08 May 2016 14:35:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iS0n2721rJiZZ43C07GFZaYOze6f5H01tpXIKR4ec+g=; b=ycgULtDcoU5zTIe4psETjTY9d8O1vmBtYGXUArUfywX4y2rT9awhJutP1ap/MRJE4d /dut7jox3Z8LZ7yGZ+Bh23eIpfNOMmmAQ+2J7ed9NnCwcyp9HK1hgqpbpjO02a56lvsU TnZrQjZzejWQgvHU0k/Z3oyb2tzhWlhLk77Ipjsotkdy35piD2fEXSpy2mPtmUo69RuT KixePVLi/sP3QVxK398Njso/xBB7psCmSGtKEBZCwDoV915fsosUAgzqlrRWNsIHhlLC gVd2/UQrKd6YRNGfeIznMe2HxxmewrU77sa2kl8nsF3lQY82tMIhTrQGNPoxq2zGZBbp E84w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iS0n2721rJiZZ43C07GFZaYOze6f5H01tpXIKR4ec+g=; b=dO+hwA1NjfV6o87ETFHCLVkiUGuM+WfNALsfXDsQgseNcf/1Am4rF8X5/Lp+yd2ZIQ 7b3/d8UXNgXoRm/qMksXAMMA1n+HLEHx6p64xOI65s4lO1Jf2YEte2IqyAYOK40aOs95 xS3kaB78FPrFbbQdvo2x7B9BX2UT6EcftqngEPhWGhFDZVPhQ3zmCgaW2BfdA2Yn+Vco HDpCmg1oWURnBkVhzkGPhSpS14NW2yCmy6O5iUfw+B8U0CTn210ICoTbtebr46s2eg/7 WWqZbKpiU6CnY7uRIXRAUSyqCt6zb99xVdKXok//5tT0oWmDTYDwSZQh+abltp291wzg 00YQ== X-Gm-Message-State: AOPr4FXnEovsj9KsZyggNlKP+UBa8/h2WOYBCmiwvr6ptPZysFktaI94Lon4dEQ9WW857Ojl+fyk7mgu2hWtpg== X-Received: by 10.25.149.84 with SMTP id x81mr4576571lfd.166.1462743333965; Sun, 08 May 2016 14:35:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.20.194 with HTTP; Sun, 8 May 2016 14:35:04 -0700 (PDT) In-Reply-To: References: From: Victor Toni Date: Sun, 8 May 2016 23:35:04 +0200 Message-ID: Subject: Re: setsourcefilter/getsourcefilter missing const qualifier? To: Eric van Gyzen Cc: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 21:35:37 -0000 Thank for the explanation. Changed the code respectively. 2016-05-05 2:23 GMT+02:00 Eric van Gyzen : > On 05/ 3/16 03:50 PM, Victor Toni wrote: > >> When trying to compile some linux-originated code on FreeBSD I get the >> following errors: >> >> /usr/include/netinet/in.h:585:5: note: candidate function not viable: 3rd >> argument ('const sockaddr *') would lose const qualifier >> int setsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, >> ^ >> /usr/include/netinet/in.h:587:5: note: candidate function not viable: 3rd >> argument ('const sockaddr *') would lose const qualifier >> int getsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, >> ^ >> >> the main difference is that the linux version makes guarantees about >> the parameters. >> >> >> Wouldn't it be safe for the FreeBSD version to make the same assumption? >> > > Yes, it would be safe in practice, since the implementation does not > modify those parameters. However, RFC 3678 does not specify them as const, > and neither do illumos (Solaris) and Mac OS X, so code that tries to pass > const parameters is not portable. I would suggest changing the code to > pass non-const parameters. > > Eric > From owner-freebsd-net@freebsd.org Sun May 8 21:47:23 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 36BB3B32AC6 for ; Sun, 8 May 2016 21:47:23 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 9E9FF1FA0 for ; Sun, 8 May 2016 21:47:22 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id u64so182314053lff.3 for ; Sun, 08 May 2016 14:47:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=dKqIbRU0yfqhym4+FLRBzBFc89q5tZnj/qLXnreKVTg=; b=BnpKsmhBm4/WJh6vRDgXvxcx5cquN6Bd3t9UEdaiP7zPpefvP0P7ehJM+O1lAuNs1n csjsVzqLbQuZKAAEyiUuDICZNoRgMzc1s7igJZUxnxw8wx/TDM1bzfme1o8ZyTdHn9cH 7/VcolSuTLSnX8NufP1JH1/rLWldXIu6+a3jiGm+OLGK4tx9zvO2BZ1D5ppdmqcr4PO7 qJr4n5MC/+PHxOE99aMvrmCXM5A15iUZq2irk9NFiNkf++zy9BZw+vEuQPxNRh5Am41b GwaXvlySajQoIFFIn0EwRpHtdF2lS683DEKdwFVZ9Z2pssRw4wx+r6yhvnXE7ORnL+4s i52g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dKqIbRU0yfqhym4+FLRBzBFc89q5tZnj/qLXnreKVTg=; b=OC+7f2quQJ1uM5thcfGRrCDTLU+oB7YmTziwFMDPHabZJnWfIwDS6Vz9zXeL+iEedn b0AWRvGnyTG9BwpkPY5FWzk/hBjIlgN0+kpY7L3UhTmvZseJA2miKNkxeoLoFiZ11+w+ uqpE+qc0emEWBu66hVoGP8scPHHH7N0N4wndDoM+SkocJlz9e8jpZ4eaZpPWZLR8lt0+ vl4hSmvLIhDpPd0j1ioIX2pDmjngCbW/tw8l9hCifKqgKq7BYZqGezAgQu2Qfxu6zEEU gmDY87ACo+Jek/JwlNcNTP1SX/iRF5v8lk5qBinA2lf9b01w40kg9Thb8wOEs2AOuGJW r0fg== X-Gm-Message-State: AOPr4FWcWbwbkT/HGJZ26q+q1GYh1aFN92bbrMgLsiiGxOBw9/iR7lbSNskEUgeF6kRV0BBtyywGXuf9AdoPxg== X-Received: by 10.25.143.16 with SMTP id r16mr14175085lfd.59.1462744040735; Sun, 08 May 2016 14:47:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.20.194 with HTTP; Sun, 8 May 2016 14:46:51 -0700 (PDT) From: Victor Toni Date: Sun, 8 May 2016 23:46:51 +0200 Message-ID: Subject: [FreeBSD 10-3] undefined reference to getsourcefilter /setsourcefilter To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 21:47:23 -0000 Trying to port mcproxy to FreeBSD I encountered a quite strange problem. Compiling everything works but linking fails with the following error: $ c++ -v -Wl,-rpath,/usr/local/lib -pthread -o mcproxy main.o hamcast_logging.o mc_socket.o addr_storage.o mroute_socket.o if_prop.o reverse_path_filter.o proxy.o sender.o receiver.o mld_receiver.o igmp_receiver.o mld_sender.o igmp_sender.o proxy_instance.o routing.o worker.o timing.o check_if.o check_kernel.o membership_db.o querier.o timers_values.o interfaces.o def.o simple_mc_proxy_routing.o simple_routing_data.o scanner.o token.o configuration.o parser.o interface.o -L/usr/local/lib -L/usr/lib -lpthread FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: i386-unknown-freebsd10.3 Thread model: posix Selected GCC installation: "/usr/bin/ld" --eh-frame-hdr -dynamic-linker /libexec/ld-elf.so.1 --hash-style=both --enable-new-dtags -m elf_i386_fbsd -o mcproxy /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/local/lib -L/usr/lib -L/usr/lib -rpath /usr/local/lib main.o hamcast_logging.o mc_socket.o addr_storage.o mroute_socket.o if_prop.o reverse_path_filter.o proxy.o sender.o receiver.o mld_receiver.o igmp_receiver.o mld_sender.o igmp_sender.o proxy_instance.o routing.o worker.o timing.o check_if.o check_kernel.o membership_db.o querier.o timers_values.o interfaces.o def.o simple_mc_proxy_routing.o simple_routing_data.o scanner.o token.o configuration.o parser.o interface.o -lpthread -lc++ -lm -lgcc --as-needed -lgcc_s --no-as-needed -lpthread -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/crtend.o /usr/lib/crtn.o mc_socket.o: In function `mc_socket::set_source_filter(unsigned int, addr_storage const&, unsigned int, std::__1::list > const&) const': src/utils/mc_socket.cpp:(.text+0x29cc): undefined reference to `setsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int, unsigned int, sockaddr_storage*)' mc_socket.o: In function `mc_socket::get_source_filter(unsigned int, addr_storage const&, unsigned int&, std::__1::list >&) const': src/utils/mc_socket.cpp:(.text+0x2c29): undefined reference to `getsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int*, unsigned int*, sockaddr_storage*)' src/utils/mc_socket.cpp:(.text+0x2cae): undefined reference to `getsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int*, unsigned int*, sockaddr_storage*)' c++: error: linker command failed with exit code 1 (use -v to see invocation) The methods should be found: $ readelf -s /usr/lib/libc.a | grep etsourcefilter 10: 00000600 392 FUNC GLOBAL DEFAULT 1 getsourcefilter 12: 00000290 305 FUNC GLOBAL DEFAULT 1 setsourcefilter What am I missing? From owner-freebsd-net@freebsd.org Sun May 8 21:50:39 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10C6DB32BE8 for ; Sun, 8 May 2016 21:50:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::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 D16061093 for ; Sun, 8 May 2016 21:50:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x236.google.com with SMTP id s8so78840454ign.0 for ; Sun, 08 May 2016 14:50:38 -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; bh=UZwVphRZVn9XyK9lV6EAn+GpawgNhX6tGxfNnH7bCv8=; b=pVYeslsUXHVLRcvFL1j/1TNOfamYkX2vUM+7pohXHQg6mwbf33cJupC7TCeMYaM04Q pYsV9kMCKzWIlp5/xC96CmUdPW9i6zibcZZU6d2lcIcQAMu13cjmpUmRFe6AL7HhuSPI obBz3S9Ic1BUODjMOX+eNw8z/WT7ApOEnYQxfG//pgVwClZxH9yl3mSIZtCpdj/Abu4A yC3UuNkI4Cdr8KBkNOLsmUm3Y1jvPTpE5WkAr2HDMaV/DIaL6YjBvzyZt2vIXBliAXvB 5GlxNj4g2U6lTwEfj5iAOtRWb0VddS+aPCB+nBfo3co6X4sRfU3PgS0FLhXqGP+4CEbv RNTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=UZwVphRZVn9XyK9lV6EAn+GpawgNhX6tGxfNnH7bCv8=; b=GOxlhRugyIfV204Qp+PYXiJ1KDZmd2s0V6CvpWOVTKyq5SDGvFrMYThOdsncsCtRVP +m5NcCQnurWIfiinLmpcGm3UALXHl/3Q4Cs1WlHvCAz1+1TBN0TOe2HqWbaM280RbF4d E7V4EGsvsYeHVblpF9SecllN9xYMS5+zSf9hblt0BQt3cQM0nmZtvdKqbNAnYzCGUcy0 aCaHZ6es4GiCRqYLF0e9Z+1acXLyJsYwiLNYQIzFcyLE7ILJ0GkiAf2Pbn2QzDb5MOby ROLILm14Ssb6CiamN2SFZuYVNwKG88cjctsLCW+G7N8+sADbl2LoDIgVjPo6Oc7i7KPP pgxA== X-Gm-Message-State: AOPr4FU8QF72e/wUpuATOrOwRFk+Eq0uczV6fdEXjWtCvZUzsVd2i0t8Uvit1dl3Cu7FmQR4M2Msx5+3JzAM6w== MIME-Version: 1.0 X-Received: by 10.50.3.73 with SMTP id a9mr7447493iga.22.1462744238290; Sun, 08 May 2016 14:50:38 -0700 (PDT) Received: by 10.36.113.3 with HTTP; Sun, 8 May 2016 14:50:38 -0700 (PDT) In-Reply-To: References: Date: Sun, 8 May 2016 14:50:38 -0700 Message-ID: Subject: Re: [FreeBSD 10-3] undefined reference to getsourcefilter /setsourcefilter From: Adrian Chadd To: Victor Toni Cc: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 21:50:39 -0000 Some extern "C" { } around some includes? :) -a On 8 May 2016 at 14:46, Victor Toni wrote: > Trying to port mcproxy to FreeBSD I encountered a quite strange problem. > Compiling everything works but linking fails with the following error: > > $ c++ -v -Wl,-rpath,/usr/local/lib -pthread -o mcproxy main.o > hamcast_logging.o mc_socket.o addr_storage.o mroute_socket.o if_prop.o > reverse_path_filter.o proxy.o sender.o receiver.o mld_receiver.o > igmp_receiver.o mld_sender.o igmp_sender.o proxy_instance.o routing.o > worker.o timing.o check_if.o check_kernel.o membership_db.o querier.o > timers_values.o interfaces.o def.o simple_mc_proxy_routing.o > simple_routing_data.o scanner.o token.o configuration.o parser.o > interface.o -L/usr/local/lib -L/usr/lib -lpthread > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > Target: i386-unknown-freebsd10.3 > Thread model: posix > Selected GCC installation: > "/usr/bin/ld" --eh-frame-hdr -dynamic-linker /libexec/ld-elf.so.1 > --hash-style=both --enable-new-dtags -m elf_i386_fbsd -o mcproxy > /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/local/lib > -L/usr/lib -L/usr/lib -rpath /usr/local/lib main.o hamcast_logging.o > mc_socket.o addr_storage.o mroute_socket.o if_prop.o reverse_path_filter.o > proxy.o sender.o receiver.o mld_receiver.o igmp_receiver.o mld_sender.o > igmp_sender.o proxy_instance.o routing.o worker.o timing.o check_if.o > check_kernel.o membership_db.o querier.o timers_values.o interfaces.o def.o > simple_mc_proxy_routing.o simple_routing_data.o scanner.o token.o > configuration.o parser.o interface.o -lpthread -lc++ -lm -lgcc --as-needed > -lgcc_s --no-as-needed -lpthread -lc -lgcc --as-needed -lgcc_s > --no-as-needed /usr/lib/crtend.o /usr/lib/crtn.o > mc_socket.o: In function `mc_socket::set_source_filter(unsigned int, > addr_storage const&, unsigned int, std::__1::list std::__1::allocator > const&) const': > src/utils/mc_socket.cpp:(.text+0x29cc): undefined reference to > `setsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int, > unsigned int, sockaddr_storage*)' > mc_socket.o: In function `mc_socket::get_source_filter(unsigned int, > addr_storage const&, unsigned int&, std::__1::list std::__1::allocator >&) const': > src/utils/mc_socket.cpp:(.text+0x2c29): undefined reference to > `getsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int*, > unsigned int*, sockaddr_storage*)' > src/utils/mc_socket.cpp:(.text+0x2cae): undefined reference to > `getsourcefilter(int, unsigned int, sockaddr*, unsigned int, unsigned int*, > unsigned int*, sockaddr_storage*)' > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > > The methods should be found: > > $ readelf -s /usr/lib/libc.a | grep etsourcefilter > 10: 00000600 392 FUNC GLOBAL DEFAULT 1 getsourcefilter > 12: 00000290 305 FUNC GLOBAL DEFAULT 1 setsourcefilter > > > What am I missing? > _______________________________________________ > 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" From owner-freebsd-net@freebsd.org Mon May 9 08:50:02 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 2F83CB31EEF for ; Mon, 9 May 2016 08:50:02 +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 1FEE21FDC for ; Mon, 9 May 2016 08:50:02 +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 u498o1eq024671 for ; Mon, 9 May 2016 08:50:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 08:50:02 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nick@van-laarhoven.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 08:50:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 Nick Hibma changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@van-laarhoven.org --- Comment #3 from Nick Hibma --- What about security implications? I guess that this warning is a security related one, to show that the system is being used to sniff network traffic? Note: I would like to see this happen too, but perhaps this needs to be tie= d in with an ACL. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 08:56:52 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 B6EE9B33273 for ; Mon, 9 May 2016 08:56:52 +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 A775413C0 for ; Mon, 9 May 2016 08:56:52 +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 u498uqhW041267 for ; Mon, 9 May 2016 08:56:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 08:56:52 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@grosbein.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 08:56:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #4 from eugen@grosbein.net --- (In reply to Nick Hibma from comment #3) How an ACL would be better than single root-modified sysctl from the securi= ty point of view? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 09:02:52 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 4D52AB33621 for ; Mon, 9 May 2016 09:02:52 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from valery.hibma.org (valery.hibma.org [IPv6:2a02:2308::216:3eff:fe79:3a6c]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB1A186B for ; Mon, 9 May 2016 09:02:51 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from [IPv6:2001:980:530a:1:7012:3883:b88:d228] (unknown [IPv6:2001:980:530a:1:7012:3883:b88:d228]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by valery.hibma.org (Postfix) with ESMTPSA id E21086E0A0E; Mon, 9 May 2016 11:02:42 +0200 (CEST) From: Nick Hibma Date: Mon, 9 May 2016 11:02:42 +0200 Subject: PR 166255 - disable promiscuous mode warning via sysctl To: freebsd-net@freebsd.org Message-Id: <52FB7430-BC4D-4157-94FB-4245BA1C3066@van-laarhoven.org> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 09:02:52 -0000 Folks, In PR 166255 [1] it is suggested to allow disabling =E2=80=98promiscuous = mode enabled=E2=80=99 warnings. It adds a sysctl to allow toggling this = behaviour. I have a number of questions before I commit the patch: - are there any security related considerations wrt disabling = this warning? - any other warnings that could be useful to disable/enable - is the sysctl name net.link.log_promisc_mode_change , to be = set to 0 to disable, suitable (compare: = net.link.ether.inet.log_arp_warnings)? - perhaps a different value for that sysctl to warn only the = first time? Not warn again within the next 10 minutes? etc. I=E2=80=99d appreciate your suggestions. Nick Hibma nick@van-laarhoven.org [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 = From owner-freebsd-net@freebsd.org Mon May 9 09:07:26 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 62BEFB337B6 for ; Mon, 9 May 2016 09:07:26 +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 533B21A8F for ; Mon, 9 May 2016 09:07:26 +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 u4997QpK011384 for ; Mon, 9 May 2016 09:07:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 09:07:26 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nick@van-laarhoven.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 09:07:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #5 from Nick Hibma --- That's not the point. The point is that an ACL might have to be applied when the value is being changed, depending on security level that the kernel is = in, and I am not knowledgable about that. I've sent a message to freebsd-net@ about this and will proceed to commit t= his if there is no response or there is consensus. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 09:08:44 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 29704B33834 for ; Mon, 9 May 2016 09:08:44 +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 1A0EB1B5D for ; Mon, 9 May 2016 09:08:44 +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 u4998hrw020745 for ; Mon, 9 May 2016 09:08:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 09:08:43 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: borjam@sarenet.es X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 09:08:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #6 from borjam@sarenet.es --- Some admins would certainly feel uncomfortable with this, as an unexpected promisc mode can be a signal of something fishy going on. As a lesser evil I would make the variable a loader only tunable. At least changing it would require a reboot. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 13:36:31 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 A4F37B33A9D for ; Mon, 9 May 2016 13:36:31 +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 958231F1E for ; Mon, 9 May 2016 13:36:31 +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 u49DaV6J015742 for ; Mon, 9 May 2016 13:36:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 13:36:31 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@grosbein.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 13:36:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #7 from eugen@grosbein.net --- (In reply to borjam from comment #6) Better than nothing. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 13:56:59 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 E43FDB341BB for ; Mon, 9 May 2016 13:56:59 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 94B5813B4 for ; Mon, 9 May 2016 13:56:59 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x233.google.com with SMTP id v200so21452754wmv.1 for ; Mon, 09 May 2016 06:56:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=2TRhHoUEQW0iDMqOzwaLmOb98Osg1sOWYD6AqvForNw=; b=j7JTosyV9dSRXE6meGsM0NMwIUY5gMdpBF9Z1U6WoJC3BjwiGXfZZ4aL2HmtsCK8FU eHLrH/35pstuW1ApzFXybHYsFuMFCzdFvjLsgj3XbVMhDTGW4YsfDDLQYFm92X/yiUGF hRhQd+NLNf97uxAbEwFIr55KbZ35PPBAP6oYc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=2TRhHoUEQW0iDMqOzwaLmOb98Osg1sOWYD6AqvForNw=; b=SsWbRynnD7fleDWRR4HX4q7ux5e9uwujOo5e1bzXvsqObhpJQb76RM5/K7A8b0s1Tw Xgtge5+vkfFvjn/AOb/zPe40LFTiGWqvKV9ecZ0/Jk7CKPR4a3bldUaBUT0NifSESmri 37+uMCToxYVt8NefgHaBZyIy1srYPmCC6STSNcvqT7sGw5BwN0KnDOYVEwX/0/PVXsLJ uGB0298iLy5yo1FrX3LalvzcICmpDPeGNgxxANhkDj1Iir6ZiJWNSHNQiHULABpTjwQ0 /O6XHg3pdjb/IeuFPy8rayp6e7daeJaQmrr9TOWua3hZNlOfBKFKKgmwiC5/LWdB9j3k s09A== X-Gm-Message-State: AOPr4FW4dPlzgrNK/4nNLMm5Q0KfTBY0byzag7SCAfST69LEpeVlazWUovAIiIgHtWq6F272GtDI+CSwIvckCg== X-Received: by 10.194.143.51 with SMTP id sb19mr34244688wjb.98.1462802217912; Mon, 09 May 2016 06:56:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.31.137 with HTTP; Mon, 9 May 2016 06:56:28 -0700 (PDT) In-Reply-To: <52FB7430-BC4D-4157-94FB-4245BA1C3066@van-laarhoven.org> References: <52FB7430-BC4D-4157-94FB-4245BA1C3066@van-laarhoven.org> From: Eitan Adler Date: Mon, 9 May 2016 06:56:28 -0700 Message-ID: Subject: Re: PR 166255 - disable promiscuous mode warning via sysctl To: Nick Hibma Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 13:57:00 -0000 On 9 May 2016 at 02:02, Nick Hibma wrote: > Folks, > > In PR 166255 [1] it is suggested to allow disabling =E2=80=98promiscuous= mode enabled=E2=80=99 warnings. It adds a sysctl to allow toggling this be= haviour. I have a number of questions before I commit the patch: I don't any concern with a sysctl, but I wonder if some better ore more generic mechanism could be built (like syslog.conf). --=20 Eitan Adler From owner-freebsd-net@freebsd.org Mon May 9 14:07:40 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 E0224B3445F for ; Mon, 9 May 2016 14:07:40 +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 D0BC81B7A for ; Mon, 9 May 2016 14:07:40 +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 u49E7e2n018431 for ; Mon, 9 May 2016 14:07:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Mon, 09 May 2016 14:07:41 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: borjam@sarenet.es X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 14:07:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 borjam@sarenet.es changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |borjam@sarenet.es --- Comment #8 from borjam@sarenet.es --- Note that I'not comfortable at all with a mechanism to disable such an important error message. If I were in this situation I would either log to a remote location or inst= all a syslog version with more filtering capabilities (syslog-ng, for instance) rather than pushing a potentially risky change to the base system. My suggestion to at least make it a tunable is a last resort one ;) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 9 15:16:36 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 1B782B3463C for ; Mon, 9 May 2016 15:16:36 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 9EFA5104F for ; Mon, 9 May 2016 15:16:34 +0000 (UTC) (envelope-from ml@my.gd) Received: by mail-lf0-x234.google.com with SMTP id m64so203470044lfd.1 for ; Mon, 09 May 2016 08:16:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=my-gd.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Tyfzjm+80b06b+CczWuA5UJ8KKoxWvaKqHjxd7V5ITw=; b=LICWYnfSS8JEgyK/IyZGXgVe6HlyvlD8RhNe0/6sYpCCnRdO+Klno1LTS2IgITyJaK 2J3atS2rVOupcVxMfJr0KgDRr6zNPVIMjxcUjmNSBQ5UEqUexu/FItlTKDVmei3p7uWM BCB+ZkfP+bCApPJgAQpp/qDyduHbah/PRKEASvQMyvotGF1uGYfb/YFBV8y7w4NecyUf 5TYr2wi+moUHRE08e5ZVJqG2APDnZEyelMyet5fQgtoRDMAUOeSZNbvBcdy4ajkM06iX e0YG2vIjkQ8h/E0VYbdig7Sj1rotG9IL+s6iWZ1STSmdUeaUk7wcohHxTg6ZT4XZykTx 3wwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Tyfzjm+80b06b+CczWuA5UJ8KKoxWvaKqHjxd7V5ITw=; b=QXSd+JiCWBp42olQ55nlwSHxv2p9c2l1EyAvYZl1ifRZRdK54CU57uWSj3tQYM8roT RRmJ+LhU09V/52VcsCrxOLEQI03KH0X88IZPnMbGQjA830KmSi11oCxYghht+t0i5T+f YlZOek40I7EcaBACS/KLceqTcqXXZNuKDSFycrgimH7WJU8QflEZCG55GiZKkBG8Fi6A mgp5+RuFaCH879d9VaDUDD2mLWEaF3iy8oklljk4pYLMJdWXCUIrOUF2ys5Tk//rMyBx vz1ZLT8cJdYQ6KgW6wpRsKdGU8stPC93Xpaagl5+eBbzXWiPVuQ9f9DKRn1AEOyDk4Jz wpCA== X-Gm-Message-State: AOPr4FXXVra3TrXp0AftKHfF1mM6pDPg3d9VDjI14t5YSu54lKsnoWqdEFrZV9J+kO7ryfE6o1PBUsTTgOTXZQ== MIME-Version: 1.0 X-Received: by 10.112.43.168 with SMTP id x8mr14988660lbl.132.1462806992378; Mon, 09 May 2016 08:16:32 -0700 (PDT) Received: by 10.112.54.226 with HTTP; Mon, 9 May 2016 08:16:32 -0700 (PDT) In-Reply-To: References: <52FB7430-BC4D-4157-94FB-4245BA1C3066@van-laarhoven.org> Date: Mon, 9 May 2016 17:16:32 +0200 Message-ID: Subject: Re: PR 166255 - disable promiscuous mode warning via sysctl From: Damien Fleuriot To: Nick Hibma Cc: "freebsd-net@freebsd.org" , Eitan Adler Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 15:16:36 -0000 On 9 May 2016 at 15:56, Eitan Adler wrote: > On 9 May 2016 at 02:02, Nick Hibma wrote: > > Folks, > > > > In PR 166255 [1] it is suggested to allow disabling =E2=80=98promiscuo= us mode > enabled=E2=80=99 warnings. It adds a sysctl to allow toggling this behavi= our. I > have a number of questions before I commit the patch: > > I don't any concern with a sysctl, but I wonder if some better ore > more generic mechanism could be built (like syslog.conf). > > > Hello Nick, Eitan, @Nick WRT security, I have to agree with borjam's comment [1] about making this a loader-time tunable. WRT different values, I would think it a shore to implement "warn again after X minutes". Certainly for the needs referenced by PR 166255, this would be overkill. @Eitan The problem with adjusting this at syslog (or rsyslog)'s level is that you effectively generate the message, then have to expand even more work to actually suppress it, making your machine work twice for no reason. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255#c6 From owner-freebsd-net@freebsd.org Mon May 9 19:52:38 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 7EC11B34D73 for ; Mon, 9 May 2016 19:52:38 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 722C21B0B for ; Mon, 9 May 2016 19:52:38 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 00AB61751D; Mon, 9 May 2016 12:44:19 -0700 (PDT) Date: Mon, 9 May 2016 12:44:19 -0700 From: hiren panchasara To: Sonny Son Cc: freebsd-net , njwilliams@swin.edu.au Subject: Re: multipath tcp Message-ID: <20160509194419.GH79033@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6lCXDTVICvIQMz0h" 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 19:52:38 -0000 --6lCXDTVICvIQMz0h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable + Nigel On 05/06/16 at 03:00P, Sonny Son wrote: > Dear, >=20 > I would like to try multipath TCP. Can somebody tell me what is the most > recommended one? v0.51 seems to be the latest one. Is it the one that I > should try? >=20 > Thank you! >=20 >=20 > _______________________________________________ > 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" --6lCXDTVICvIQMz0h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJXMOiNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lg0EH/3bTQLBCeQVEjLImedh2/Oh5 gIK7wWT48cirhH8ZsLo/aML+kikwIbzZqXTq3t7XK/VY16Lxxd9JBK+xy+M8Shch M8Hvk8C73YDmJnrwLQ5JJK1iae2FoxGv3G1g8i1ZpPWBtQg8eZnzbueYO3UL8gor eMnAakbw3pLqjk3GUnIhSjXhxeUvun8tVILJKU/Fvl1QhPC59C0ixtaEPr5Xizdi bAQbzNmK1ST0zC/zpESkTs8QjsCz8MiDNTDHL3j2YQwyzXF3D0SZV0a+YwoCMRJp dDGcdyQRPq+/iGxAJaDcpAfI0SrMSIOGCaMB8cEOVsnIxYlLcaXqCXzoDiednnI= =PYcb -----END PGP SIGNATURE----- --6lCXDTVICvIQMz0h-- From owner-freebsd-net@freebsd.org Tue May 10 04:59:15 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 7932AB35D15 for ; Tue, 10 May 2016 04:59:15 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB1011C1 for ; Tue, 10 May 2016 04:59:15 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id CDCB21543D; Tue, 10 May 2016 04:59:14 +0000 (UTC) Date: Tue, 10 May 2016 04:59:14 +0000 To: freebsd-net@freebsd.org From: Phabricator Reply-to: D6148+325+ea9e78ec8d498ebd@reviews.freebsd.org Subject: [Differential] D6148: tcp/syncache: Add comment for syncache_respond Message-ID: <7d8afe816999479ba7e90cb36f734853@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D6148: tcp/syncache: Add comment for syncache_respond X-Herald-Rules: <64> 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-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: Y2FkNGI5OTYzNDYzYzgyNmZmMTk0MGY3OGYwIFcxaqI= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_7d8afe816999479ba7e90cb36f734853" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 04:59:15 -0000 --b1_7d8afe816999479ba7e90cb36f734853 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit This revision was automatically updated to reflect the committed changes. Closed by commit rS299315: tcp/syncache: Add comment for syncache_respond (authored by sephe). CHANGED PRIOR TO COMMIT https://reviews.freebsd.org/D6148?vs=15728&id=16100#toc REPOSITORY rS FreeBSD src repository CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D6148?vs=15728&id=16100 REVISION DETAIL https://reviews.freebsd.org/D6148 AFFECTED FILES head/sys/netinet/tcp_syncache.c CHANGE DETAILS diff --git a/head/sys/netinet/tcp_syncache.c b/head/sys/netinet/tcp_syncache.c --- a/head/sys/netinet/tcp_syncache.c +++ b/head/sys/netinet/tcp_syncache.c @@ -1505,6 +1505,10 @@ return (rv); } +/* + * Send SYN|ACK to the peer. Either in response to the peer's SYN, + * i.e. m0 != NULL, or upon 3WHS ACK timeout, i.e. m0 == NULL. + */ static int syncache_respond(struct syncache *sc, struct syncache_head *sch, int locked, const struct mbuf *m0) @@ -1688,6 +1692,11 @@ M_SETFIB(m, sc->sc_inc.inc_fibnum); m->m_pkthdr.csum_data = offsetof(struct tcphdr, th_sum); + /* + * If we have peer's SYN and it has a flowid, then let's assign it to + * our SYN|ACK. ip6_output() and ip_output() will not assign flowid + * to SYN|ACK due to lack of inp here. + */ if (m0 != NULL && M_HASHTYPE_GET(m0) != M_HASHTYPE_NONE) { m->m_pkthdr.flowid = m0->m_pkthdr.flowid; M_HASHTYPE_SET(m, M_HASHTYPE_GET(m0)); EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, transport, adrian, rwatson, gnn, lstewart, glebius, delphij, mike-karels.net, jtl, hiren, hselasky, sbruno Cc: freebsd-net-list --b1_7d8afe816999479ba7e90cb36f734853 Content-Type: text/x-patch; charset=utf-8; name="D6148.16100.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D6148.16100.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL25ldGluZXQvdGNwX3N5bmNhY2hlLmMgYi9oZWFkL3N5cy9u ZXRpbmV0L3RjcF9zeW5jYWNoZS5jCi0tLSBhL2hlYWQvc3lzL25ldGluZXQvdGNwX3N5bmNhY2hl LmMKKysrIGIvaGVhZC9zeXMvbmV0aW5ldC90Y3Bfc3luY2FjaGUuYwpAQCAtMTUwNSw2ICsxNTA1 LDEwIEBACiAJcmV0dXJuIChydik7CiB9CiAKKy8qCisgKiBTZW5kIFNZTnxBQ0sgdG8gdGhlIHBl ZXIuICBFaXRoZXIgaW4gcmVzcG9uc2UgdG8gdGhlIHBlZXIncyBTWU4sCisgKiBpLmUuIG0wICE9 IE5VTEwsIG9yIHVwb24gM1dIUyBBQ0sgdGltZW91dCwgaS5lLiBtMCA9PSBOVUxMLgorICovCiBz dGF0aWMgaW50CiBzeW5jYWNoZV9yZXNwb25kKHN0cnVjdCBzeW5jYWNoZSAqc2MsIHN0cnVjdCBz eW5jYWNoZV9oZWFkICpzY2gsIGludCBsb2NrZWQsCiAgICAgY29uc3Qgc3RydWN0IG1idWYgKm0w KQpAQCAtMTY4OCw2ICsxNjkyLDExIEBACiAKIAlNX1NFVEZJQihtLCBzYy0+c2NfaW5jLmluY19m aWJudW0pOwogCW0tPm1fcGt0aGRyLmNzdW1fZGF0YSA9IG9mZnNldG9mKHN0cnVjdCB0Y3BoZHIs IHRoX3N1bSk7CisJLyoKKwkgKiBJZiB3ZSBoYXZlIHBlZXIncyBTWU4gYW5kIGl0IGhhcyBhIGZs b3dpZCwgdGhlbiBsZXQncyBhc3NpZ24gaXQgdG8KKwkgKiBvdXIgU1lOfEFDSy4gIGlwNl9vdXRw dXQoKSBhbmQgaXBfb3V0cHV0KCkgd2lsbCBub3QgYXNzaWduIGZsb3dpZAorCSAqIHRvIFNZTnxB Q0sgZHVlIHRvIGxhY2sgb2YgaW5wIGhlcmUuCisJICovCiAJaWYgKG0wICE9IE5VTEwgJiYgTV9I QVNIVFlQRV9HRVQobTApICE9IE1fSEFTSFRZUEVfTk9ORSkgewogCQltLT5tX3BrdGhkci5mbG93 aWQgPSBtMC0+bV9wa3RoZHIuZmxvd2lkOwogCQlNX0hBU0hUWVBFX1NFVChtLCBNX0hBU0hUWVBF X0dFVChtMCkpOwoK --b1_7d8afe816999479ba7e90cb36f734853-- From owner-freebsd-net@freebsd.org Tue May 10 06:11:57 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 095F1B35F2F for ; Tue, 10 May 2016 06:11:57 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 A172010A9 for ; Tue, 10 May 2016 06:11:56 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x229.google.com with SMTP id g17so7656235wme.1 for ; Mon, 09 May 2016 23:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=D5gBXWaujb6q78Id+KfhtgdtuYECKIwl2dsMooPtNMg=; b=d1g68lL7FVSo4y97tusQ3ZSRZ8r1roAZFyIpGZaYtym7ylTlOokOWQfX5tJKWDq+mp wo5C4ntJbEJKFMLTlNyQmqOENFdVz6i4HJoJ0iBQ+DBD7iINLFdcua3bawKSPSYT1bKL tZosLJCUorwj/N4Q5gOIThGdbK4M4i3E31Nh8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=D5gBXWaujb6q78Id+KfhtgdtuYECKIwl2dsMooPtNMg=; b=aDnZZJgcLkCG4kL+WIssYa7t/n+k0t9T1ZpADBvL57b/Qf2dqCC8mY3t1RFN/YWmRA vnyjU2HxRJtjXqVvLmpuD4tToksB0DkBGzu07zcmKd+6XhuqduDv/U3+TlzuKRf/rCNl 6Ko1t4pRDomcHVPykjAPqgGfJrtsDjwVahfC3F78NlkW1s7JaaTsqCS0Kz6t4O0DFuvp LPHdRAHmYzrA5ACQoQYY7a3Bl78UOQQVVCn4LZXConyYJOIwmCgFOihTxj4eiT2O0qIs A57BMbZ6DodYD7Tdb+kJYV0o7mKPaeM91otzcXbLwxZDRS5BNG2s9x55s5DNhdGkiJ59 43wg== X-Gm-Message-State: AOPr4FWrB+7GpfIzoewI+fcf+e9cd76cqPOIgG6WZoaIHz00gWNxwVSZKcJDmxsZ5sZpA5rATuIT+3I1gcJNYw== X-Received: by 10.194.143.51 with SMTP id sb19mr37668145wjb.98.1462860715256; Mon, 09 May 2016 23:11:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.31.137 with HTTP; Mon, 9 May 2016 23:11:25 -0700 (PDT) In-Reply-To: References: <52FB7430-BC4D-4157-94FB-4245BA1C3066@van-laarhoven.org> From: Eitan Adler Date: Mon, 9 May 2016 23:11:25 -0700 Message-ID: Subject: Re: PR 166255 - disable promiscuous mode warning via sysctl To: Damien Fleuriot Cc: Nick Hibma , "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 06:11:57 -0000 On 9 May 2016 at 08:16, Damien Fleuriot wrote: > @Eitan > The problem with adjusting this at syslog (or rsyslog)'s level is that you > effectively generate the message, then have to expand even more work to > actually suppress it, making your machine work twice for no reason. To be clear: I wasn't suggesting using syslog.conf. I was suggesting something more generic than a sysctl-per-warning though. -- Eitan Adler From owner-freebsd-net@freebsd.org Tue May 10 07:27:03 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 BF519B35C6F for ; Tue, 10 May 2016 07:27:03 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 475D81106 for ; Tue, 10 May 2016 07:27:03 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id u64so4748191lff.3 for ; Tue, 10 May 2016 00:27:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=SkO7pccfHfn0ykBH1HYDFGu9EoKUNEnI67v0rFuBRd0=; b=DbCpD68Jbf83OVVB/B78YmuyryoDvD6cYnf0B6bur6tSAMHVzDbFBB5BzoIAm/tzsX hDflZvyUwbm0PDmf38ctbd6L9d1i1JE/AmQkib1XdGXNaFjD1FYYi6psxUl13ycVdiKL V5UaB1pZSloDPRi5ePXWznqfX5Tb+bVpjsYYS8z5gL7OHz24JRqsB3dOHJ2Guldtk5gD eDSGaXQz8sOORRVpQy/sj57OAhHYe1oFrk+cEvfGjBB0Fo5w13qxv/rJ6o/niYdWYS76 NKArU+IyIouFlkKh21WqEgYXIt1DnY2AFBEC0y7x6A1d+NqNbgm8GY2L12V+A8mYaDpx lw+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=SkO7pccfHfn0ykBH1HYDFGu9EoKUNEnI67v0rFuBRd0=; b=huwBO3XFoSi6/sr4oF0wyXuILZP9F7LfcPsay9U+p7suWKSx4xjTPyvYrQc+/p/IMb TJt8AglX1RLCypV70VhOmc3L0dXfO5E1XscGbMG7qHazc/TtrpSPzM0Qpp6vuPen7dcl O0miPdzElax5G/yeJU/buoPbe+LE34PbAg0uvaDRbvhDI0g03GpIXsgPW8D7Cn6OoEzH 6wRLxeE9e2kahsaA4rvMk04nSabKWogs+m7vsJN5r2s1z5XACGdX4InYau9Ucpv3O1kU Ciq8xHAQAIM7KnantumUT5+U9S3YyuB7mc44i8rTk0PIN8IZFZ6g0BnV4tgclMPdBL1R /rsg== X-Gm-Message-State: AOPr4FW4e/vLHXRGDJipER8KVPNlZlOkEuYFmbCQZqvVnRqYBCH5+AfEFwxFxp2XoUhH5w== X-Received: by 10.112.140.3 with SMTP id rc3mr16216059lbb.85.1462865221164; Tue, 10 May 2016 00:27:01 -0700 (PDT) Received: from 95.108.172.115-red.dhcp.yndx.net (95.108.172.115-red.dhcp.yndx.net. [95.108.172.115]) by smtp.gmail.com with ESMTPSA id cv11sm132418lbb.49.2016.05.10.00.27.00 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 May 2016 00:27:00 -0700 (PDT) From: Dmitry Sivachenko Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: ping6: failed to get receiving hop limit Message-Id: Date: Tue, 10 May 2016 10:26:59 +0300 To: FreeBSD Net Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 07:27:03 -0000 Hello, Sometimes ping6 command writes the following warning to stderr: ping6: failed to get receiving hop limit I can easily reproduce this with for n in `jot - 1 1000` ; do /sbin/ping6 -n -c 5 $HOST > /dev/null ; done It is very likely that even 100 repetitions is enough to catch this. Other than this warning IPv6 network seems to work properly. What does it mean? Thanks. From owner-freebsd-net@freebsd.org Tue May 10 07:51:23 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 A7C1DB35573 for ; Tue, 10 May 2016 07:51: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 98E1C1B3A for ; Tue, 10 May 2016 07:51: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 u4A7pNNp036080 for ; Tue, 10 May 2016 07:51:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208977] bxe driver causes packet corruption with RLO activated Date: Tue, 10 May 2016 07:51: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.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: fbsd@qty.se X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 07:51:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208977 --- Comment #1 from slindgren --- Correction, it's about LRO (large receive offload), not RLO. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue May 10 10:58:19 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 45BF4B35D52 for ; Tue, 10 May 2016 10:58:19 +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 363971208 for ; Tue, 10 May 2016 10:58:19 +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 u4AAwF72020697 for ; Tue, 10 May 2016 10:58:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Tue, 10 May 2016 10:58:15 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: elofu17@hotmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 10:58:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 elofu17@hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |elofu17@hotmail.com --- Comment #9 from elofu17@hotmail.com --- Eugen, Instead of messing with the log message, can't you simply put all vlan interfaces in promiscuous mode permanently? ifconfig vlan1 promisc ifconfig vlan2 promisc ifconfig vlan3 promisc ... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue May 10 11:34:19 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 D603BB35C0F for ; Tue, 10 May 2016 11:34:19 +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 C67FA1236 for ; Tue, 10 May 2016 11:34:19 +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 u4ABYI1V036493 for ; Tue, 10 May 2016 11:34:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Tue, 10 May 2016 11:34:18 +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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@grosbein.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 11:34:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #10 from eugen@grosbein.net --- (In reply to elofu17 from comment #9) AFAIK, there is no such thing as "vlan promiscuous mode" in FreeBSD and only parent interface can be placed to such mode. Not all vlans should get traff= ic promiscuously. In fact, none should as I need to send/receive DHCP traffic = only for selected vlans and promiscuous mode should not be needed for that, is i= t? OTOH, I have another applications utilizing BPF to send/receive traffic. It should be possible to filter unneeded kernel logs. I can rewrite my patch to make configuration loader tunnable and read-only at run time. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue May 10 16:30:34 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 16A0BB364F0 for ; Tue, 10 May 2016 16:30:34 +0000 (UTC) (envelope-from jinmei.tatuya@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::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 D6D6E1B5D for ; Tue, 10 May 2016 16:30:33 +0000 (UTC) (envelope-from jinmei.tatuya@gmail.com) Received: by mail-ig0-x22c.google.com with SMTP id lr7so14550518igb.1 for ; Tue, 10 May 2016 09:30:33 -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=uBxGK5cpJlS5wvubGRmeFlxUWmsWH7eZkpoz6lxLBLs=; b=Gvs77e6ge3ea96yBGdb2Yph2+kx5961FFKQkabEeTvjPAiWpnKOf2HbERxI6bJNUbk RfE0XlGwNq26thM2HAQScGxuauMiBpgLyB9c0XZ5Zxug/dUhL5kIgkwyqWa/kVI1wc65 ZzAkm+l4ikM7Im6VoNuH2IL30f7Rv8geZrtipuSqy2W2S4JclvFzDcoUaTaUCTqSTEPX Yop9OVNLPRMFFb9eqCqLAMMhsYVp9F0tc0K5Y5YZ3yj/8NoueMvfqV7RP+n3NqVye3oi mwIA81HjPXV61T40FWFOD6/2GGGWgvWtSdLStDA0u8SwlT3X1asL+lrr7Ugla2/m9wuX N5Ww== 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=uBxGK5cpJlS5wvubGRmeFlxUWmsWH7eZkpoz6lxLBLs=; b=ZnFsZ4BkXr4mfMwJmczDhMIs4MSqy8eTjoLScu9HWKeI/7egpRMdvq2mcdt+dwMaJ8 enRqHLHPr3I3YkZqippQ3M6CpyzAFL/A8ulHr9AQyWhO1Q4H8aLE14WBzX7J1KxJsNOj cczRfvRqwk9Thm0vDzzeIq4UdQWeF4QiGeNi2V4m2c09c56jwRsb3XO+HlG72KqewLLY RAqQKJAqZDhq5MyjwOc8nyxxVZAtIr2zFARyqsXKE5b6S+JSzQAsyJyFpl4fgfVz925y 0uxXubvlWPry+Iw+esVMAE71xVRxCt/BLqQ9hGUmFFA0yGHuf6AjihaY1iDXCW9Hy9jb dxfg== X-Gm-Message-State: AOPr4FWNe8kii3uUgOBaM0baNs2umgWyUFd7Dwb6qmbw+AYWKy49bVslZc9mNvz23+l76H7khw+uDhN3lAe9JA== MIME-Version: 1.0 X-Received: by 10.50.100.135 with SMTP id ey7mr16824219igb.41.1462897833157; Tue, 10 May 2016 09:30:33 -0700 (PDT) Sender: jinmei.tatuya@gmail.com Received: by 10.107.19.218 with HTTP; Tue, 10 May 2016 09:30:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 May 2016 09:30:33 -0700 X-Google-Sender-Auth: uWQ-VqQD01W-n1VX2jkl0ZqGIeM Message-ID: Subject: Re: ping6: failed to get receiving hop limit From: =?UTF-8?B?56We5piO6YGU5ZOJ?= To: Dmitry Sivachenko Cc: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 16:30:34 -0000 At Tue, 10 May 2016 10:26:59 +0300, Dmitry Sivachenko wrote: > Sometimes ping6 command writes the following warning to stderr: > > ping6: failed to get receiving hop limit > > I can easily reproduce this with > for n in `jot - 1 1000` ; do /sbin/ping6 -n -c 5 $HOST > /dev/null ; done > > It is very likely that even 100 repetitions is enough to catch this. > > Other than this warning IPv6 network seems to work properly. > > What does it mean? That should mean the IPV6_RECVHOPLIMIT socket option somehow didn't work as expected: the kernel didn't provide the information in the ancillary data chain. I have no idea about how this could happen - it's quite likely to be some kind of kernel bug, but I have no specific idea. -- JINMEI, Tatuya From owner-freebsd-net@freebsd.org Tue May 10 16:46:31 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 EDA98B36C17; Tue, 10 May 2016 16:46:31 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0108.outbound.protection.outlook.com [65.55.169.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 665DC1D77; Tue, 10 May 2016 16:46:30 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qlgc.onmicrosoft.com; s=selector1-qlogic-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YEgyNHtmY8BZGyz0lE+ZgNXQN6V5iHlZciru38J6ujs=; b=TtJj+Bt3YLirxn2YK2ybz4n0a+RvxpA7zs8nIqvnt6PDmD7eZlVCnPfZpHS/qWVpI3VSh7JEYV45F9Ja2iSLuwuH6PZQw64b+efjQJfp5OHMkI6u1yAGZbGvTFBxgDSXWDiCjtcZBobjUxvVSxtIJNKwoM1AAA73+NWhCwmv/nM= Received: from DM2PR11MB0222.namprd11.prod.outlook.com (10.160.132.25) by DM2PR11MB0221.namprd11.prod.outlook.com (10.160.132.24) with Microsoft SMTP Server (TLS) id 15.1.485.9; Tue, 10 May 2016 16:46:23 +0000 Received: from DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) by DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) with mapi id 15.01.0485.011; Tue, 10 May 2016 16:46:23 +0000 From: David Somayajulu To: "freebsd-net@freebsd.org" , "freebsd-drivers@freebsd.org" Subject: Questions on iflib Thread-Topic: Questions on iflib Thread-Index: AdGq2vkrJDN9k431RNmE5gasApboFA== Date: Tue, 10 May 2016 16:46:23 +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;freebsd.org; dmarc=none action=none header.from=qlogic.com; x-originating-ip: [2602:306:3449:6010:1978:e303:410e:8a17] x-ms-office365-filtering-correlation-id: 8b7b65df-3ebf-46bc-0038-08d378f29f2a x-microsoft-exchange-diagnostics: 1; DM2PR11MB0221; 5:e479xh8lj38NW+sdFQu//qcKJxcufIRUN7LmLYbnQ4qgMU7YO4NPPSEcsn7KIov0GYdeHWha2/+S1FVMMQ2sGkS8ZUCsayaubw++z2kNd5YXKnVWwgf7AbcUluz9svKa1z0pLMdnaVjqTaooKcR0Ug==; 24:I2naVcumUd5dxfsT3gCRxGZNj6LP5t8LIiM/KhTT6oplYl4ayr6v+93MMrDqWZKT8JIb8YpRtOKhwBtyYIiqjnMomJ4DOOL1ozmCPv9xMy8=; 7:i7opir5oSz8+Qn+zTCJxef5Ww7D7oREu8CCu6u4g35RyztX9ar07wbNnZL7AXCk3dd4bHOAmLEYFtt9l6zOoV9p6iRqpUCD8+cUKgJCLgHA/YsxcIlVAH3PkzGQLMSL58tHT4WATwo8gQ5mD0shE/PCl/LznCfzFBAHYQXd4saRVEp9m2kfkiFOBt+0Po+Gg; 20:SgVekqDB3ySgJRpXAGaAmkdzTm/FqTCuCYuJybQJdXvX9xTCklDjm7lE46l3HtQXEgNz/3+fjZo3MKmcOUUqarusr9qSrnpM026fI/lNVDiGr2hB/ZvItLUOETrHy0bBs5CwOuyO/wbn3dtoA8uGZXGDwiLF42ek4SQGrCLRn/s= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0221; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DM2PR11MB0221; BCL:0; PCL:0; RULEID:; SRVR:DM2PR11MB0221; x-forefront-prvs: 0938781D02 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(53754006)(5003600100002)(2501003)(2900100001)(3280700002)(2906002)(5002640100001)(92566002)(9326002)(86362001)(8936002)(5008740100001)(19580405001)(19580395003)(3660700001)(9686002)(99286002)(15975445007)(77096005)(50986999)(450100001)(189998001)(6116002)(790700001)(16236675004)(586003)(54356999)(107886002)(122556002)(102836003)(33656002)(1220700001)(81166005)(5004730100002)(10400500002)(19625215002)(229853001)(76576001)(11100500001)(5001770100001)(19300405004)(558084003)(3480700004)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR11MB0221; H:DM2PR11MB0222.namprd11.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2016 16:46:23.5558 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR11MB0221 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 16:46:32 -0000 Hi All, I have a couple of questions on iflib : 1. Are there plans to incorporate iflib into CURRENT. If yes, will it= make it into FreeBSD11 release ? 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ? Thanks David S (davidcs@freebsd.org) From owner-freebsd-net@freebsd.org Tue May 10 17:25:25 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 E6B84B35A20; Tue, 10 May 2016 17:25:25 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id D57361D85; Tue, 10 May 2016 17:25:25 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 075E217BF2; Tue, 10 May 2016 10:25:25 -0700 (PDT) Date: Tue, 10 May 2016 10:25:24 -0700 From: hiren panchasara To: David Somayajulu Cc: "freebsd-net@freebsd.org" , "freebsd-drivers@freebsd.org" , scottl@FreeBSD.org, kmacy@freebsd.org Subject: Re: Questions on iflib Message-ID: <20160510172524.GK79033@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QWRRbczYj8mXuejp" 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 17:25:26 -0000 --QWRRbczYj8mXuejp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable + Kip, Scott. On 05/10/16 at 04:46P, David Somayajulu wrote: > Hi All, > I have a couple of questions on iflib : >=20 > 1. Are there plans to incorporate iflib into CURRENT. If yes, will = it make it into FreeBSD11 release ? Yes. The library itself (without any drivers) is being prepared for committing to CURRENT. >=20 > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ? Kip or Scott may provide more info. Cheers, Hiren --QWRRbczYj8mXuejp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJXMhmBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/ldwMH/3HsAEKyB8ZqtGtOgwFgqWtJ oyqA7o2Qh8sPZZJMnF0aOp63RBJeRS8UGkv0Oqm0cAiIJtbadRKkX9yAl0O6FevQ KAtnNdk7oQRckE5Xeqs7MNxms4usSkflA4kLRGZ8q2QcP4PV3QSskd5lPg/PvogB odAuRZPTAMi5Z7KNwOOzRJOkSHjVHVLoszJXvS+0z0DMWMWp91d7jyLieyY1lsfg R6jV3srF70AC6pP1McQc5WubmNIYzf67wdNRg39A+LeWKrWZNV0h2UEVbQ8pZC3X czJ4bhw77hjRIAjmNuD+lfx/bFyP0ubO1gpf6uWJxiksY16wLNxfcxWrG7bnQEI= =GHxC -----END PGP SIGNATURE----- --QWRRbczYj8mXuejp-- From owner-freebsd-net@freebsd.org Tue May 10 19:30:55 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 950F5B36236; Tue, 10 May 2016 19:30:55 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::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 5EA0318CC; Tue, 10 May 2016 19:30:55 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ig0-x22c.google.com with SMTP id lr7so18605830igb.1; Tue, 10 May 2016 12:30:55 -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=Imhj+YGYwBIG8elmzNxoCLtrkBcF1HROiEQhExvS17Q=; b=Rp1tWXJxUAfSkkxrj8MgnBjhpY8nIJdhz+NolET2yikq7BHOjZs+7thkaJDuLp/AmO Vz4w4T807fR8xaai+A339HJSaMHR1pZwknuDH+8LEFAOwDirKdYFWXUJlMDhUqwsGMY2 KCZBDxRFSGxu3dKu/RQf7d2LESyeq1HIeoRMoUfytUuA+5w98sRxR3RYpl8XXFCK6M7V p1VqqZyKsKUbxupsu/XXiLdOyoVDduIGW7r1cYRCWkAZJPZ6ZYyKhk1ZadAdR0M7tmQ/ KW8NB4Eu4I2nI/UD/a2TuPdC9j089ZWaXgI1dqJviJOrtCSZhSzXMH4JhOGPM3A9Xs2f AJsg== 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=Imhj+YGYwBIG8elmzNxoCLtrkBcF1HROiEQhExvS17Q=; b=I8nEDpn6rnUpN7UGXSbUhApqVodoyTTVBeqykCMCdBPcQ1Cb/HxPhQbF4HCKx0w2iQ HMfdBKlnuNQkBg9zX19CetnYolCT8RpSI+kXFxOiY1bGcCEJvTSpf8Pz7uKF3NslarxA TQmD6NOrufZDqEcsi4XfyrxtKyJ1HDLMbdL8jdvD8CoADrRbTZW7aK9uOJ8aM+1v9MH4 rcfI+Z8vqjI6xr1+8mlVkhgYCA14UBmQg17hMOgSOMEgWBEovt19B+smEEdu92svwfA1 X/pUVpIIn4Kxtv1HSKXiXR/MxREiTFosbFwgiyq7TOVUEhIU6dK/XaL8ENsfk/i93DCF XLrA== X-Gm-Message-State: AOPr4FVWfnv64enVjnoAtqRwu7jmK1o72vSH6odDX6eZ/k70dt1ETP0jefUsNmeReWpdfVh9i0n3USEKLDCaYg== MIME-Version: 1.0 X-Received: by 10.50.147.7 with SMTP id tg7mr17926341igb.63.1462908653392; Tue, 10 May 2016 12:30:53 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.140.8 with HTTP; Tue, 10 May 2016 12:30:53 -0700 (PDT) In-Reply-To: <20160510172524.GK79033@strugglingcoder.info> References: <20160510172524.GK79033@strugglingcoder.info> Date: Tue, 10 May 2016 12:30:53 -0700 X-Google-Sender-Auth: xvCNj6j7b497iTvBvoonFZN7AlQ Message-ID: Subject: Re: Questions on iflib From: "K. Macy" To: hiren panchasara Cc: David Somayajulu , "freebsd-net@freebsd.org" , "freebsd-drivers@freebsd.org" , "scottl@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 19:30:55 -0000 I'm waiting on erj to commit his ixl update. It will go in immediately following that with an ixgbe and ixl driver. It would have also included a bxe driver, but the original bxe driver is too flaky to even test that cabling is OK and my 10GbaseT version frequently had unrecoverable dmae errors. It may just be the "ET game" of ethernet cards, meriting a similar fate. Cheers. -M On Tuesday, May 10, 2016, hiren panchasara wrote: > + Kip, Scott. > > On 05/10/16 at 04:46P, David Somayajulu wrote: > > Hi All, > > I have a couple of questions on iflib : > > > > 1. Are there plans to incorporate iflib into CURRENT. If yes, will > it make it into FreeBSD11 release ? > > Yes. The library itself (without any drivers) is being prepared for > committing to CURRENT. > > > > > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ? > > Kip or Scott may provide more info. > > Cheers, > Hiren > From owner-freebsd-net@freebsd.org Wed May 11 01:37:35 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 8F232B369B1 for ; Wed, 11 May 2016 01:37:35 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 51C901DCF for ; Wed, 11 May 2016 01:37:35 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 86F6F15222; Wed, 11 May 2016 01:37:34 +0000 (UTC) Date: Wed, 11 May 2016 01:37:34 +0000 To: freebsd-net@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5872+325+9dea0574509cdbb3@reviews.freebsd.org Subject: [Differential] D5872: tcp: Don't prematurely drop receiving-only connections Message-ID: <56eb15d1f3565ca04fbef7c3c9c286e8@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , Thread-Topic: D5872: tcp: Don't prematurely drop receiving-only connections X-Herald-Rules: <64> 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-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: MmVmNzYzNzljOGQxMmM4MWI4MmNjYzcxMzczIFcyjN4= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_56eb15d1f3565ca04fbef7c3c9c286e8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 01:37:35 -0000 --b1_56eb15d1f3565ca04fbef7c3c9c286e8 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit sepherosa_gmail.com updated this revision to Diff 16171. sepherosa_gmail.com added a comment. Change if(..) {panic} into assertion and wrap the assertion using macro. CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D5872?vs=15642&id=16171 REVISION DETAIL https://reviews.freebsd.org/D5872 AFFECTED FILES sys/netinet/tcp_output.c EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, glebius, adrian, delphij, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, freebsd-net-list, lstewart, hiren, transport, jtl Cc: gnn, mike-karels.net, jtl --b1_56eb15d1f3565ca04fbef7c3c9c286e8 Content-Type: text/x-patch; charset=utf-8; name="D5872.16171.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D5872.16171.patch" ZGlmZiAtLWdpdCBhL3N5cy9uZXRpbmV0L3RjcF9vdXRwdXQuYyBiL3N5cy9uZXRpbmV0L3RjcF9v dXRwdXQuYwotLS0gYS9zeXMvbmV0aW5ldC90Y3Bfb3V0cHV0LmMKKysrIGIvc3lzL25ldGluZXQv dGNwX291dHB1dC5jCkBAIC0xMzAsNiArMTMwLDE2IEBACiAJJlZORVRfTkFNRSh0Y3BfYXV0b3Nu ZGJ1Zl9tYXgpLCAwLAogCSJNYXggc2l6ZSBvZiBhdXRvbWF0aWMgc2VuZCBidWZmZXIiKTsKIAor LyoKKyAqIE1ha2Ugc3VyZSB0aGF0IGVpdGhlciByZXRyYW5zbWl0IG9yIHBlcnNpc3QgdGltZXIg aXMgc2V0IGZvciBTWU4sIEZJTiBhbmQKKyAqIG5vbi1BQ0suCisgKi8KKyNkZWZpbmUgVENQX1hN SVRfVElNRVJfQVNTRVJUKHRwLCBsZW4sIHRoX2ZsYWdzKQkJCVwKKwlLQVNTRVJUKCgobGVuKSA9 PSAwICYmICgodGhfZmxhZ3MpICYgKFRIX1NZTiB8IFRIX0ZJTikpID09IDApIHx8XAorCSAgICB0 Y3BfdGltZXJfYWN0aXZlKCh0cCksIFRUX1JFWE1UKSB8fAkJCQlcCisJICAgIHRjcF90aW1lcl9h Y3RpdmUoKHRwKSwgVFRfUEVSU0lTVCksCQkJCVwKKwkgICAgKCJuZWl0aGVyIHJleG10IG5vciBw ZXJzaXN0IHRpbWVyIGlzIHNldCIpKQorCiBzdGF0aWMgdm9pZCBpbmxpbmUJaGhvb2tfcnVuX3Rj cF9lc3Rfb3V0KHN0cnVjdCB0Y3BjYiAqdHAsCiAJCQkgICAgc3RydWN0IHRjcGhkciAqdGgsIHN0 cnVjdCB0Y3BvcHQgKnRvLAogCQkJICAgIGxvbmcgbGVuLCBpbnQgdHNvKTsKQEAgLTE1NDUsOSAr MTU1NSw3IEBACiAJCQl0cC0+dF9zb2Z0ZXJyb3IgPSBlcnJvcjsKIAkJCXJldHVybiAoZXJyb3Ip OwogCQljYXNlIEVOT0JVRlM6Ci0JICAgICAgICAgICAgICAgIGlmICghdGNwX3RpbWVyX2FjdGl2 ZSh0cCwgVFRfUkVYTVQpICYmCi0JCQkgICAgIXRjcF90aW1lcl9hY3RpdmUodHAsIFRUX1BFUlNJ U1QpKQotCSAgICAgICAgICAgICAgICAgICAgICAgIHRjcF90aW1lcl9hY3RpdmF0ZSh0cCwgVFRf UkVYTVQsIHRwLT50X3J4dGN1cik7CisJCQlUQ1BfWE1JVF9USU1FUl9BU1NFUlQodHAsIGxlbiwg ZmxhZ3MpOwogCQkJdHAtPnNuZF9jd25kID0gdHAtPnRfbWF4c2VnOwogCQkJcmV0dXJuICgwKTsK IAkJY2FzZSBFTVNHU0laRToKCg== --b1_56eb15d1f3565ca04fbef7c3c9c286e8-- From owner-freebsd-net@freebsd.org Wed May 11 01:38:34 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 591B3B36A21 for ; Wed, 11 May 2016 01:38:34 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 1881C1EC3 for ; Wed, 11 May 2016 01:38:34 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 95DED152C0; Wed, 11 May 2016 01:38:33 +0000 (UTC) Date: Wed, 11 May 2016 01:38:33 +0000 To: freebsd-net@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5872+325+9dea0574509cdbb3@reviews.freebsd.org Subject: [Differential] D5872: tcp: Don't prematurely drop receiving-only connections Message-ID: <382a6675e8933770ccec10088ce00ef8@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5872: tcp: Don't prematurely drop receiving-only connections X-Herald-Rules: <64> 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-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: MmVmNzYzNzljOGQxMmM4MWI4MmNjYzcxMzczIFcyjRk= 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.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 01:38:34 -0000 sepherosa_gmail.com added a comment. In https://reviews.freebsd.org/D5872#130813, @lstewart wrote: > In https://reviews.freebsd.org/D5872#130806, @sepherosa_gmail.com wrote: > > > In https://reviews.freebsd.org/D5872#130805, @lstewart wrote: > > > > > In https://reviews.freebsd.org/D5872#130179, @sepherosa_gmail.com wrote: > > > > > > > We probably can leave the cwnd resetting to later rexmt timeout or possible later fast retransmit (I think fast retransmit could kick in under some cases, if ENOBUFS happened); instead of resetting the cwnd immediately upon ENOBUFS. > > > > > > > > > Please leave the manipulation of cwnd as is so as to avoid conflating two different changes. The manipulation of cwnd on local drop has nothing to do with the subject of this particular change. > > > > > > Yep, I am not going to delete the cwnd reset in this patch. > > > errr, not sure if we're on the same page or not, but I am in strong agreement with Mike. Please leave the line "tp->snd_cwnd = tp->t_maxseg;" where it is and untouched i.e. don't delete or change it. > > >> Also, the patch we're reviewing here should be the commit candidate i.e. what will actually land in the tree. I understand that you need to test with something different than the commit candidate, but that should just be noted in the review description. We all need to see the final code as there are many subtleties here that require close attention from as many sets of eyes as possible. > > > > This is what I am testing now. Since this path is not on a hot code path and we obviously don't want to have timers unset for data/FIN/SYN, can we just use the "if() panic" here? > > No. This isn't a condition we should bring the whole machine down for. A rate limited log message would be appropriate so the admin knows there's a potential for hung connections, but I don't insist on this. > > > And another thing is abstract it as a macro. Maybe we just leave the macro abstraction to the next step? > > I don't see any good reason not to define and use the macro as part of this patch. It can then be used in follow up commits to check the other return points from the input and output processing paths. Done. REVISION DETAIL https://reviews.freebsd.org/D5872 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, glebius, adrian, delphij, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, freebsd-net-list, lstewart, hiren, transport, jtl Cc: gnn, mike-karels.net, jtl From owner-freebsd-net@freebsd.org Wed May 11 05:58:33 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 92506B36937; Wed, 11 May 2016 05:58:33 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0119.outbound.protection.outlook.com [65.55.169.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D96311BEC; Wed, 11 May 2016 05:58:31 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qlgc.onmicrosoft.com; s=selector1-qlogic-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=e5un63/8tqC9bu/zio8zUuVBPYNDC7SWUiUBXnbGjGo=; b=UfvP2lZWAyWpK/QR0BsPvk8mV4uCYLN6mlZB57/r5nxc1GcNNPhOmiu9Lo+7mnzalCG65Dr8lFcxXugRZcPKCnbiNrDm7/t4/98SdpCbezN28Yj9K1/bMj7xojVdMjVsITBr3/zfhcY1aO+iY1M7kMV2THphbBWnQOdLZf/6sAw= Received: from DM2PR11MB0222.namprd11.prod.outlook.com (10.160.132.25) by DM2PR11MB0222.namprd11.prod.outlook.com (10.160.132.25) with Microsoft SMTP Server (TLS) id 15.1.485.9; Wed, 11 May 2016 05:58:23 +0000 Received: from DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) by DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) with mapi id 15.01.0485.011; Wed, 11 May 2016 05:58:23 +0000 From: David Somayajulu To: "K. Macy" , hiren panchasara CC: "freebsd-net@freebsd.org" , "scottl@freebsd.org" , "freebsd-drivers@freebsd.org" Subject: RE: Questions on iflib Thread-Topic: Questions on iflib Thread-Index: AdGq2vkrJDN9k431RNmE5gasApboFAABfZwAAARh6YAAFcjqsA== Date: Wed, 11 May 2016 05:58:23 +0000 Message-ID: References: <20160510172524.GK79033@strugglingcoder.info> In-Reply-To: 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;freebsd.org; dmarc=none action=none header.from=qlogic.com; x-originating-ip: [198.186.0.2] x-ms-office365-filtering-correlation-id: 0fa3ef7f-733f-43ae-1f18-08d3796142fe x-microsoft-exchange-diagnostics: 1; DM2PR11MB0222; 5:AL373hucwP8Qajs5PCTpdV6hqNGUCFA3ZUpL3I1DYWw+Yke5MKIXZ+4qZITAVHfrqqA/LGVr7FepMp0a4qDN5CSOIA/VlWSGe/jyMLjVX7Sd1PuQ0OvZ6M6+bAtKrfT+WeZVlVcJXuxUd6mPBmQ0mw==; 24:8g4aQsPV3UzRNYnknEbsU6AAa3DZ5lAJQaxZFfxz6xLZOS+Q2gd+iEdewhZ5+hVkhNuHfoKTlESMjrFGlo8yWSdeONkIsvpdWjkDeBiN2iE=; 7:0TrnO4mh2KEs6LXUtgTcyfXSPMPjtp2TAdlza+xfxtWRCPlUH24+RkJZ57zUaAS7SDTDc13AuOt+EM5qksOiLi9Ch2smnRnwSWhsapWuYXByxRAsf0VPJLoWYmZ1zBddYSsUcmgcCsgGlOquh8P8pPP5aYb+hDydbSX+1k8VShMxiu2yLNUABOUjDpLbMAt0; 20:Shs/TsrTyguhwFWUdmnJrimEt/4dUdxG2cpb8u+f1i4lbGnIZ4R8Zf2OSyVqH5u5vLXtwPiHxOLOzgD+rxIPsQDAI1Q6jyWhOI0JkoPlq5gVppxeWxLyRkWv/RiRJM9GtjrsdZcsEjElFxwZm+PuQKIZ02zU08hqHUYrk9jRbkg= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0222; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DM2PR11MB0222; BCL:0; PCL:0; RULEID:; SRVR:DM2PR11MB0222; x-forefront-prvs: 0939529DE2 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377454003)(53754006)(55674003)(13464003)(66066001)(3280700002)(50986999)(3660700001)(77096005)(87936001)(86362001)(2906002)(15975445007)(19580395003)(189998001)(74316001)(4326007)(3480700004)(5004730100002)(9686002)(76576001)(54356999)(76176999)(33656002)(19580405001)(10400500002)(5008740100001)(11100500001)(8936002)(99286002)(6116002)(92566002)(122556002)(2950100001)(5002640100001)(81166006)(2900100001)(5003600100002)(102836003)(3846002)(586003)(1220700001)(5001770100001)(6606295002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR11MB0222; H:DM2PR11MB0222.namprd11.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2016 05:58:23.0860 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR11MB0222 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 05:58:33 -0000 Thanks for info. Is there a link to the latest patch which I can apply to CURRENT in the mea= ntime ? Thanks David S. -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of K. Macy Sent: Tuesday, May 10, 2016 12:31 PM To: hiren panchasara Cc: freebsd-net@freebsd.org; scottl@freebsd.org; freebsd-drivers@freebsd.or= g; David Somayajulu Subject: Re: Questions on iflib I'm waiting on erj to commit his ixl update. It will go in immediately foll= owing that with an ixgbe and ixl driver. It would have also included a bxe = driver, but the original bxe driver is too flaky to even test that cabling = is OK and my 10GbaseT version frequently had unrecoverable dmae errors. It = may just be the "ET game" of ethernet cards, meriting a similar fate. Cheers. -M On Tuesday, May 10, 2016, hiren panchasara wrote: > + Kip, Scott. > > On 05/10/16 at 04:46P, David Somayajulu wrote: > > Hi All, > > I have a couple of questions on iflib : > > > > 1. Are there plans to incorporate iflib into CURRENT. If yes, wil= l > it make it into FreeBSD11 release ? > > Yes. The library itself (without any drivers) is being prepared for=20 > committing to CURRENT. > > > > > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT = ? > > Kip or Scott may provide more info. > > Cheers, > Hiren > _______________________________________________ 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" From owner-freebsd-net@freebsd.org Wed May 11 06:11:25 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 E7A41B36B4C; Wed, 11 May 2016 06:11:25 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 AF6AF118E; Wed, 11 May 2016 06:11:25 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-io0-x244.google.com with SMTP id d62so4471088iof.1; Tue, 10 May 2016 23:11:25 -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:content-transfer-encoding; bh=53G1iF7xkIVux2Dx+bauRDsW3ZKE5HrlN8XK7XElwAo=; b=W34bTdY+n5nYogFQow2pZN1Tt3MhnU2UHMc0Uhd2ctBzR3uizTUQRNySJ+4fYkuA9C NX9D8qdaskhy4Hj+J6ru7pVCM0duK7ZmchUKmVgmi7GEGsXPH3a0rbHc636R7rSr6hlD tV6X9nM0YcV+KsCqsgrjC0t7PSxkrdOuuhoGxQ4KE15y5X8iWkZhUCse3lsegQdRhVlV NFPCuQE+jJ0PmM831e7Ny6ugmlQhYRoZYfHLa8W7HNijNAzHMVnqAPTd7Z/Fw64r1j5w TgfOFUixWG+j/PpW7tSuVMxCmzoQolMTXCwFMmJu0A1Sksk0hzE7mRJQTB7U0lJIuwaZ 9RZg== 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:content-transfer-encoding; bh=53G1iF7xkIVux2Dx+bauRDsW3ZKE5HrlN8XK7XElwAo=; b=LSfMzw5ULWCHqkk8qNJ2pXJfSRmyrXp4iY/WaLbzqKiNHGFJKaz/D057mWSUVGoJt4 aHEpxNjymmkf59npGaByyD3CqxE0sKpkYAF8LfswtRSt6U1La+9J03VpNY+Qp07gj1gR Odyncqi0815HF6Y3wqgjXWJswirdhRAQg5GU/NnhDDSmNHw4gGbTPjxDOyQxFn84FoHZ sVPr6j1NOpe0JYXZ4UYSSm377wxNcxcVyf1qGIkEcY7UTJxjwPntEZ0iKuzdxF1g3PXA P7dP14wjZY/6hbUvL+SR0nqjtuPUNg3A9+4pfXuLINS9uhoxenmp7iNIsaDaPQQoLYc+ yg+A== X-Gm-Message-State: AOPr4FWL/z8kFLvRPUWNOamkKyNAz0a+wU9Nbephp24EHEwrhz29WA25jLebAfre9NKoPFh+qiQDvw6gfO0lhQ== MIME-Version: 1.0 X-Received: by 10.107.7.170 with SMTP id g42mr1755837ioi.81.1462947085202; Tue, 10 May 2016 23:11:25 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.140.8 with HTTP; Tue, 10 May 2016 23:11:25 -0700 (PDT) In-Reply-To: References: <20160510172524.GK79033@strugglingcoder.info> Date: Tue, 10 May 2016 23:11:25 -0700 X-Google-Sender-Auth: trrLD8Lji7hGUFc-9438TOih_A0 Message-ID: Subject: Re: Questions on iflib From: "K. Macy" To: David Somayajulu Cc: hiren panchasara , "freebsd-net@freebsd.org" , "scottl@freebsd.org" , "freebsd-drivers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 06:11:26 -0000 It's a bit cumbersome to manage as a patch: https://github.com/NextBSD/NextBSD/tree/HEAD_MERGE/iflib git clone https://github.com/NextBSD/NextBSD.git -b HEAD_MERGE/iflib make sure to use the HEAD_MERGE/iflib branch not the default one. -M On Tue, May 10, 2016 at 10:58 PM, David Somayajulu wrote: > Thanks for info. > Is there a link to the latest patch which I can apply to CURRENT in the m= eantime ? > Thanks > David S. > > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org= ] On Behalf Of K. Macy > Sent: Tuesday, May 10, 2016 12:31 PM > To: hiren panchasara > Cc: freebsd-net@freebsd.org; scottl@freebsd.org; freebsd-drivers@freebsd.= org; David Somayajulu > Subject: Re: Questions on iflib > > I'm waiting on erj to commit his ixl update. It will go in immediately fo= llowing that with an ixgbe and ixl driver. It would have also included a bx= e driver, but the original bxe driver is too flaky to even test that cablin= g is OK and my 10GbaseT version frequently had unrecoverable dmae errors. I= t may just be the "ET game" of ethernet cards, meriting a similar fate. > > Cheers. > -M > > > On Tuesday, May 10, 2016, hiren panchasara > wrote: > >> + Kip, Scott. >> >> On 05/10/16 at 04:46P, David Somayajulu wrote: >> > Hi All, >> > I have a couple of questions on iflib : >> > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, wi= ll >> it make it into FreeBSD11 release ? >> >> Yes. The library itself (without any drivers) is being prepared for >> committing to CURRENT. >> >> > >> > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT= ? >> >> Kip or Scott may provide more info. >> >> Cheers, >> Hiren >> > _______________________________________________ > 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" From owner-freebsd-net@freebsd.org Wed May 11 14:55:47 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 91B21B37C18 for ; Wed, 11 May 2016 14:55:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 7536F1337 for ; Wed, 11 May 2016 14:55:46 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u4BEumdX007617 for ; Wed, 11 May 2016 07:56:55 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20160510172524.GK79033@strugglingcoder.info> References: , <20160510172524.GK79033@strugglingcoder.info> From: "Chris H" Subject: Re: Questions on iflib Date: Wed, 11 May 2016 07:56:55 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 14:55:47 -0000 On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara wrote > + Kip, Scott. > > On 05/10/16 at 04:46P, David Somayajulu wrote: > > Hi All, > > I have a couple of questions on iflib : > > > > 1. Are there plans to incorporate iflib into CURRENT. If yes, will it > > make it into FreeBSD11 release ? > > Yes. The library itself (without any drivers) is being prepared for > committing to CURRENT. This is intended to be optional. Right? > > > > > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ? > > Kip or Scott may provide more info. > > Cheers, > Hiren --Chris From owner-freebsd-net@freebsd.org Wed May 11 18:27:20 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 D79C9B37CE0 for ; Wed, 11 May 2016 18:27:20 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 AE7EF1F58 for ; Wed, 11 May 2016 18:27:20 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-io0-x235.google.com with SMTP id f89so65322457ioi.0 for ; Wed, 11 May 2016 11:27:20 -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=Zv/pNNbpl7prQ4u8uaU2uCZeiDgQAR68FkjNWEW5DNs=; b=dPzgd0m3xA+DImT6hpNOngsTtOuK87zAjR3kOh0NAcM8roA0v5URJASQvYWrY3jMuq ABE+lQgXReSi3hRof9502LpiTdwf+++DWpN4xAP2CmZGra94sguQMNQsAP5u47/SYyuV ZEck8OPAjA/klfIPolf2c9jeX0ORAH3vji8mlZOH/60TIvVwD+5g8rbj+GkdBs2Cd7xD K6udzHCeqoc6XuzgzCMaTPvoqywZ5q0pGpQ+v08fTSH19T48d2BzmROMPrHWp+vpjW2s PZruG4oNVFTSm4dLH7LPniZ/Sc+paGB06vD/9n56h44yC+jbGMExsydJSz9kKN3KO5Xf POkw== 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=Zv/pNNbpl7prQ4u8uaU2uCZeiDgQAR68FkjNWEW5DNs=; b=bzST0sVn3X7B6V0rkAUeKOOzJAMDZPqa14zVCdK1MTrS1H5Zp4mYgSvtPFZX4+m+tq CuQuW45YdkG7HmPjfvPwkJjTC1w2DGeCGlIIqFuxt1AoW04c9Le+X96ztRxPPQL3Emsk rpTsELiSI80DUrzyvUcEc6hfPImhADWTEc0h5zPKRVMZ+hqaNa1de86wKvqvybmfVsup fqdHkW4agp9/uzPQ/MxZviyUi6b4M/u1mPjmPUmoXrOO0V5tqFFOXkmbFIcMdjbqqjuO VTYQ9iR9GZacuFaQ6X5Vn9+I7X6x/KjgNzdeg9lN9Sz7XJdoXXP5H+eeUoDkJw+ftxif RL9A== X-Gm-Message-State: AOPr4FWJepRpzFkT8eX8+hD8L5IOR51/VXfvu8rubSpzCgykC7H/0mzpyZKpJUdszK5cychlQuJxrfpsl8I+eQ== MIME-Version: 1.0 X-Received: by 10.36.44.200 with SMTP id i191mr3298707iti.99.1462991240066; Wed, 11 May 2016 11:27:20 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.140.8 with HTTP; Wed, 11 May 2016 11:27:20 -0700 (PDT) In-Reply-To: <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net> References: <20160510172524.GK79033@strugglingcoder.info> <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net> Date: Wed, 11 May 2016 11:27:20 -0700 X-Google-Sender-Auth: WOfKvdf3jdGhVi33CZPhc11W2Y0 Message-ID: Subject: Re: Questions on iflib From: "K. Macy" To: Chris H Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 18:27:20 -0000 On Wed, May 11, 2016 at 7:56 AM, Chris H wrote: > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara > wrote > >> + Kip, Scott. >> >> On 05/10/16 at 04:46P, David Somayajulu wrote: >> > Hi All, >> > I have a couple of questions on iflib : >> > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, will it >> > make it into FreeBSD11 release ? >> >> Yes. The library itself (without any drivers) is being prepared for >> committing to CURRENT. > This is intended to be optional. Right? The name Iflib is short for iflnet library. A driver has to be programmed to it. It will always be possible to program directly to ifnet, but henceforth it will be frowned upon when not absolutely necessary. As iflib will ultimately make the driver more performant and more maintainable. As a counterexample, the Chelsio driver has to manage multiple ports on a single device and handle synchronization with upper level protocols. It's also extremely well optimized already. I don't know of any other network driver that can justify opting out for one of those reasons, much less both. -M From owner-freebsd-net@freebsd.org Wed May 11 19:46:37 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 B72D4B3731A for ; Wed, 11 May 2016 19:46:37 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 990D11F00 for ; Wed, 11 May 2016 19:46:36 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u4BJljGt052899 for ; Wed, 11 May 2016 12:47:51 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: "freebsd-net@freebsd.org" In-Reply-To: References: <20160510172524.GK79033@strugglingcoder.info> <8cf1894ea5271efab3f544e378679cb2@ultimatedns.net>, From: "Chris H" Subject: Re: Questions on iflib Date: Wed, 11 May 2016 12:47:51 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <936d7920c3d2b29a9d2e9bd7447c9515@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 19:46:37 -0000 On Wed, 11 May 2016 11:27:20 -0700 "K. Macy" wrote > On Wed, May 11, 2016 at 7:56 AM, Chris H wrote: > > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara > > wrote > > > >> + Kip, Scott. > >> > >> On 05/10/16 at 04:46P, David Somayajulu wrote: > >> > Hi All, > >> > I have a couple of questions on iflib : > >> > > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, will > >> > it make it into FreeBSD11 release ? > >> > >> Yes. The library itself (without any drivers) is being prepared for > >> committing to CURRENT. > > This is intended to be optional. Right? > > The name Iflib is short for iflnet library. A driver has to be > programmed to it. It will always be possible to program directly to > ifnet, but henceforth it will be frowned upon when not absolutely > necessary. As iflib will ultimately make the driver more performant > and more maintainable. As a counterexample, the Chelsio driver has to > manage multiple ports on a single device and handle synchronization > with upper level protocols. It's also extremely well optimized > already. I don't know of any other network driver that can justify > opting out for one of those reasons, much less both. > > -M No. Makes perfect sense. I'm afraid I mis-guessed it's intent. Sorry for the noise, and thanks for taking the time to reply. :) --Chris -- From owner-freebsd-net@freebsd.org Wed May 11 19:51:13 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 54873B3757F for ; Wed, 11 May 2016 19:51:13 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::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 23689134F for ; Wed, 11 May 2016 19:51:13 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: by mail-io0-x229.google.com with SMTP id 190so68434936iow.1 for ; Wed, 11 May 2016 12:51:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:date:message-id:subject:from:to; bh=4OYPJGiwusX1/A/fW6jYqe8CRmGZt6erOeIzJDM0Ugo=; b=X9kSb9pZibRzYsUjhH6QmITQvqyzim/yrNcnp3uiiemJC/BDBA48djvTJ1gOUYuLWn Gjf4OrquxzrHY9JXyTudteaBsTuHDPftBa82RAwJiCyPosJZm7GTTzZLr1W6nhtRCsb7 +Uup3PPf0HeKtHeK3CwoiiDEEkfJu4KNKpyN4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=4OYPJGiwusX1/A/fW6jYqe8CRmGZt6erOeIzJDM0Ugo=; b=SLrhHuJdVam0+22eB580bYnMoaJ+/5KI5Wn125UXLhJD0C0dZsmiPTHfVCr6xzIw9y Q7Li0tVZ1hFs4NUu6r+ALmiiHJ212GjKruuG4NomJDRp7iDbI/CJWqCHefZ1PnmEpSxg lsvPwzt+Fda+rnjSCFkTJ8mFNCCY1Ic181+gduGAvmT/ObLMOp/OXzZhoGzoJzZHjve4 r2DFj31CvAIjO0+cM9oG7xJX5LTBA9avRimf3ZDIKe2MnpYr0altO3uFlS0HhoypcX8o cXrSTlNjtG0yW+MejAB0SwYt6M4Df0lOgB6tB9uMgnzCrbW+hcjQxVwR6OgMXZ3ynXqv fmBA== X-Gm-Message-State: AOPr4FWjOWBLw91raFnEVVe9zRLGb9xQ8EyNOSj469WfzalzQkVU4twAXAWoyxIAGGBq9PrA5PTI4zmLuf+KNA== MIME-Version: 1.0 X-Received: by 10.36.83.20 with SMTP id n20mr3921338itb.61.1462996272521; Wed, 11 May 2016 12:51:12 -0700 (PDT) Received: by 10.107.29.16 with HTTP; Wed, 11 May 2016 12:51:12 -0700 (PDT) Date: Wed, 11 May 2016 16:51:12 -0300 Message-ID: Subject: ipfw tcpack won't match a given ack # From: Ze Claudio Pastore To: freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 19:51:13 -0000 Hello, This rule: 1 0 0 deny log logamount 1000 tcp from any to 100.100.224.66 tcpack 2 Won't match this attack pattern below. Is tcpack supposed to match it? FreeBSD 10.2-STABLE #0 r292035M Can I try to match it with some other tool? I tried pf but looks like it won't filter (look into) this kind of information. Thank you. 16:20:47.583871 IP 200.200.67.221.51352 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584022 IP 200.200.67.221.51354 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584324 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584475 IP 200.200.67.221.51364 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584718 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584868 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585169 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585557 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585623 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585801 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586081 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586226 IP 200.200.67.221.51354 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586649 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586652 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.587124 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.587129 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 From owner-freebsd-net@freebsd.org Thu May 12 05:46:09 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 E8892B38841 for ; Thu, 12 May 2016 05:46:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id D94FB129C for ; Thu, 12 May 2016 05:46:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u4C5k2Ft009237 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 11 May 2016 22:46:03 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time To: pyunyh@gmail.com References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> <20160508093305.GA1558@michelle.fasterthan.co.kr> Cc: freebsd-net@freebsd.org From: Yuri Message-ID: <57341899.2040600@rawbw.com> Date: Wed, 11 May 2016 22:46:01 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20160508093305.GA1558@michelle.fasterthan.co.kr> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 05:46:10 -0000 On 05/08/2016 02:33, YongHyeon PYUN wrote: > msk(4) will try to use MSI unless not configured to do so the IRQ > wouldn't be shared with other devices. If msk(4) is using MSI you > should see a high irq number greater than or equal to 256 in vmstat > output. Given that you're seeing issues with MSI, try disabling > MSI for msk(4). Add the following tunable to /boot/loader.conf and > reboot. > > hw.msk.msi_disable="1" For some reason hw.msk.msi_disable isn't found: # sysctl hw.msk.msi_disable=1 sysctl: unknown oid 'hw.msk.msi_disable' even though it is defined in sys/dev/msk/if_msk.c and if_msk module is loaded. Yuri From owner-freebsd-net@freebsd.org Thu May 12 05:58:44 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 4E22AB38AC8 for ; Thu, 12 May 2016 05:58:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x241.google.com (mail-pa0-x241.google.com [IPv6:2607:f8b0:400e:c03::241]) (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 17D5D186D for ; Thu, 12 May 2016 05:58:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pa0-x241.google.com with SMTP id i5so5232079pag.3 for ; Wed, 11 May 2016 22:58:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=tOhHEVnriwrHQEmvKnc1vZYSiz3MOoXltydNtf+h+lE=; b=y4aQbsivwH+xt7RlxYLZXxrV+ofQ2mmGnD0vjupk9kosXhrao1Gt4i5/W0EnAeeD61 KKp+V90awu/FUc/zM9Zr1lcpV9VJpspsK1DHbH3Bj7eMwIlqPLyd7+vPUPDeSnM/eTOO FdurFMLp3QAngYzLpIvEq/d6SHBO/W7u3ZuJRSZaYgmsOKXVl/CPYS7HyCyuNu9vBl+6 yAkcdUsxhkRAT4NditBgTQk4ijAWv/OPj7w3ibNVoOXaakPXYqdhQ1jRt+FcIBgs0tib f0/AoJ1ZeLjhMseSMMi6BFca/ndewKApUL/ZGNzCB8MaR9o/wZhvY+Bom8aMjfoTONaI fe9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=tOhHEVnriwrHQEmvKnc1vZYSiz3MOoXltydNtf+h+lE=; b=WLwkl7Q7OMBg8TSwRG89zAbdW5R7dhzE+ds12p5O1IoDWoiGpZPWDfTl0/ndc1QScS WOQ9z+jvG8YR6AZAKQie1rQn1Q4J57VyFn6ZYdxBLsv1MeDuso/4+2NwRhSdhPa13kaA VwgYV9K8zuL0uIKwvU8nzi6ecWZ/aOa0irEVAPj5Y0xXs1dsP2axq/zkzCp0MBJLM/uV 2TRvwjVHt3B2zcUyiZwS8YLDZuwbtw5zUsdEXcr8FDefxskyCWss8alsB0RPSPso9vqN dlol8SFsPPji2BdG/0i6V86t55db8BkybXu3RDcilchU4WgJsnWCJ+gNr3iclC/Q7q2V aE+w== X-Gm-Message-State: AOPr4FWKsk7CAV/7SEMqLSTizQyeQAq+8lu/jFfXZ8cpPdWLjtKcKcXEh9xYQ27fnzOX0A== X-Received: by 10.66.162.39 with SMTP id xx7mr10871358pab.97.1463032723778; Wed, 11 May 2016 22:58:43 -0700 (PDT) Received: from localhost ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id u65sm16534361pfa.9.2016.05.11.22.58.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 May 2016 22:58:42 -0700 (PDT) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Thu, 12 May 2016 14:58:34 +0900 Date: Thu, 12 May 2016 14:58:34 +0900 To: Yuri Cc: freebsd-net@freebsd.org Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time Message-ID: <20160512055834.GA1198@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> <20160508093305.GA1558@michelle.fasterthan.co.kr> <57341899.2040600@rawbw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57341899.2040600@rawbw.com> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 05:58:44 -0000 On Wed, May 11, 2016 at 10:46:01PM -0700, Yuri wrote: > On 05/08/2016 02:33, YongHyeon PYUN wrote: > >msk(4) will try to use MSI unless not configured to do so the IRQ > >wouldn't be shared with other devices. If msk(4) is using MSI you > >should see a high irq number greater than or equal to 256 in vmstat > >output. Given that you're seeing issues with MSI, try disabling > >MSI for msk(4). Add the following tunable to /boot/loader.conf and > >reboot. > > > >hw.msk.msi_disable="1" > > For some reason hw.msk.msi_disable isn't found: > # sysctl hw.msk.msi_disable=1 > sysctl: unknown oid 'hw.msk.msi_disable' > even though it is defined in sys/dev/msk/if_msk.c and if_msk module is > loaded. hw.msk.msi_disable is a loader tunable so you can't check it with sysctl(8). Add the tunable to boot/loader.conf to take it effect. See loader.conf(5) for more information. From owner-freebsd-net@freebsd.org Thu May 12 17:27:03 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 B0773B38726 for ; Thu, 12 May 2016 17:27:03 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0131.outbound.protection.outlook.com [65.55.169.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4765E17A5; Thu, 12 May 2016 17:27:02 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qlgc.onmicrosoft.com; s=selector1-qlogic-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xoPXCFEHnUxXAfEAb7gA7n7EcVduNCHmEhEFUKDy65U=; b=FUw/tOmnfefia9RiHEbmfoPBLM1N1k3HcWIcoL6CwLVCvONJqUd80nRe6PyKyQuEVLyiYjl5k9PKJHzEoOurhvud0pN7d2d2epEfbyo8Y2X+I1q3Wn+IP+E18Wb6f7UrCQp5UcgKiaQVZ9pJD1wABLw4uFIKVh+/EBo1Waz/gPE= Received: from DM2PR11MB0222.namprd11.prod.outlook.com (10.160.132.25) by DM2PR11MB0221.namprd11.prod.outlook.com (10.160.132.24) with Microsoft SMTP Server (TLS) id 15.1.485.9; Thu, 12 May 2016 17:26:54 +0000 Received: from DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) by DM2PR11MB0222.namprd11.prod.outlook.com ([10.160.132.25]) with mapi id 15.01.0485.018; Thu, 12 May 2016 17:26:54 +0000 From: David Somayajulu To: "bugzilla-noreply@freebsd.org" , "freebsd-net@FreeBSD.org" Subject: RE: [Bug 208977] bxe driver causes packet corruption with RLO activated Thread-Topic: [Bug 208977] bxe driver causes packet corruption with RLO activated Thread-Index: AQHRqpDJd4bgSCC7DUOj0rOFqzY8e5+1j2ug Date: Thu, 12 May 2016 17:26:54 +0000 Message-ID: References: In-Reply-To: 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;freebsd.org; dmarc=none action=none header.from=qlogic.com; x-originating-ip: [198.186.0.2] x-ms-office365-filtering-correlation-id: af87e88d-58b3-4b60-9f3d-08d37a8a9cfe x-microsoft-exchange-diagnostics: 1; DM2PR11MB0221; 5:35NDGjhM+YdkmXnUREJPAByuIwcg4k8dGEGw25M00DsS84MJ8sV+FaRUxVBEx9wcYS5nZ6xlc8+ZyBKFqM4X257k1cKCqMrWdgZUskFHSvLHiMv7CA8TjHJmPOcqNz+1WJK7BJANLyfspmB5rteF4Q==; 24:RX2aGrFcXQ3rcvfhP4kUOV954gp1OVinNj9kaoKmki1JTjXRrAkxJZtSFxHbgqe+a+jQmjAk/1DVruXPArrX1CQO9Z2PUI7q/N3etzG7G/I=; 7:2ehsJIwWbO4o/Gdt+OutzbYiQ4WsT51dYwBkhqRzdfM+hx5QAxrE0XxsqMI62mO6cY6rkrGAERTJeCHxC5ugTzHyUk195dcuNm/KPVZk8t0i+w2CJHguxSzdQ1I4uCJQurF6AhMK8AD4xqcX/GNiVzeecXU62kjyW8j6xybfHWncOyen9WS33I98eTgH2wRW; 20:2WdR5MYJjI0js07oJsU6ECu8k9oIirPd32N+SwrSWineHmMP557ONv/Vdll+c0rmBuNp+3KZzePC7FUDwN4SsMUCUxvKZpyFvXd7Yet3PFW35Y2tT6LDaVdeID0KWGxOvifDKh1FIjNA+REhpbOeEHG48s1EOfOqDNpDfoxcP10= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0221; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DM2PR11MB0221; BCL:0; PCL:0; RULEID:; SRVR:DM2PR11MB0221; x-forefront-prvs: 0940A19703 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(377454003)(50986999)(87936001)(66066001)(76576001)(77096005)(10400500002)(107886002)(9686002)(122556002)(450100001)(1220700001)(189998001)(15975445007)(19580395003)(19580405001)(8936002)(6116002)(586003)(76176999)(102836003)(3846002)(54356999)(81166006)(2900100001)(92566002)(2950100001)(5001770100001)(33656002)(106116001)(74316001)(3660700001)(3280700002)(5003600100002)(2906002)(5002640100001)(86362001)(2501003)(5004730100002)(99286002)(11100500001)(5008740100001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR11MB0221; H:DM2PR11MB0222.namprd11.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 12 May 2016 17:26:54.6130 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR11MB0221 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 17:27:03 -0000 Please sync up with the latest code from stable_10 ( https://svnweb.freebs= d.org/base/stable/10/sys/dev/bxe ). =20 The following might be the cause. https://svnweb.freebsd.org/base?view=3Drevision&revision=3D293787 If the issue still persists please let me know. Thanks David S. -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of bugzilla-noreply@freebsd.org Sent: Tuesday, May 10, 2016 12:51 AM To: freebsd-net@FreeBSD.org Subject: [Bug 208977] bxe driver causes packet corruption with RLO activate= d https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208977 --- Comment #1 from slindgren --- Correction, it's about LRO = (large receive offload), not RLO. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ 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" From owner-freebsd-net@freebsd.org Thu May 12 19:07:57 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 97AE0B388E1 for ; Thu, 12 May 2016 19:07:57 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3220A16E0 for ; Thu, 12 May 2016 19:07:56 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u4CJ7kdl097452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 12 May 2016 21:07:46 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u4CJ7fJb065711 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 13 May 2016 02:07:41 +0700 (KRAT) (envelope-from eugen@grosbein.net) To: "freebsd-net@freebsd.org" From: Eugene Grosbein Subject: NAT SIP ALG Message-ID: <5734D478.2010809@grosbein.net> Date: Fri, 13 May 2016 02:07:36 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.8 required=5.0 tests=BAYES_00,LOCAL_FROM, SUBJ_ALL_CAPS autolearn=no version=3.3.2 X-Spam-Report: * 1.5 SUBJ_ALL_CAPS Subject is all capitals * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 19:07:57 -0000 Hi! Does FreeBSD have any kind of NAT capable of parsing SIP signalling traffic to properly translate IP addresses inside protocol? Eugene Grosbein From owner-freebsd-net@freebsd.org Thu May 12 19:42:52 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 C0BCFB388CA for ; Thu, 12 May 2016 19:42:52 +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 B12E81142 for ; Thu, 12 May 2016 19:42:52 +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 u4CJgoKc096520 for ; Thu, 12 May 2016 19:42:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Thu, 12 May 2016 19:42: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: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 19:42:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #11 from commit-hook@freebsd.org --- A commit references this bug: Author: n_hibma Date: Thu May 12 19:42:13 UTC 2016 New revision: 299559 URL: https://svnweb.freebsd.org/changeset/base/299559 Log: Allow silencing of 'promiscuous mode enabled/disabled' messages. PR: 166255 Submitted by: eugen.grosbein.net Obtained from: eugen.grosbein.net MFC after: 1 week Changes: head/sys/net/if.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri May 13 00:43:48 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 7878DB34E47 for ; Fri, 13 May 2016 00:43:48 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.184.240]) (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 3952A1ED7 for ; Fri, 13 May 2016 00:43:47 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 33B85301BB for ; Fri, 13 May 2016 02:37:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1463099878; bh=8BOTOSioDvIhi1oS6wDPaC8WvNwHjAXAD8pzhLfOf14=; h=To:References:Subject:From:Date:In-Reply-To; b=Sfc3yATKTXzLtHJV6vJCqKRvfM0ckjq1MqWZkTap8W0TkRSm5+z1INeXeuehXwvzR tLYHGnBrDTThGHDXJQd96R+t4B1efWO/s8BnhGuxP5kNjCf2UDs0G+YlQTtWpl4sja btW/oSbm30taZ4Zq4g/z8ztNJlvOcAHrJkkUzSSz23hzHgjX3pOJSVI3t5XZCjtOGq YLCbeWOb9I/51sXRgAp1UTf29WI70FhKTUlpOlM69xHqeIAjPlnM5vb664QjbtFQ7q I2fxMgbutLTkeauB2fW1REAhgd4qFhYJ2JrxZf9pkKl7m7LZltH9kaDaXjAXoEwfJF vx6Xo0wr1KwuwHiSSY3c4g3Apa0ZOAuUJk8Mrks4RPnZN6ZWqJIApRsD6DC9ZY+x1S HPhgCFCrssfZZC/0rrCZs3H409vcnvS4sMEvxrWmih67PesmZJT6bzeeFEOF2+/lCR ylxgMzFEsdXoTpELcdjobm+JiNlkFUFF+BEt3Dkmu06Ltqd5Yd7ue+qaNJ08YRfyug plGkPs5PuxgmYuV1TLvQ5M7ir6NfuPyJKU5rWDmR35WRN3RpXellg2sbiAaHQUMfg9 jtaNnJeIj/QidK+5x+9ZrlJ9eBUSWL7oLBfInxNkA5536Vs7z4EPShPiZQSz2WVQp7 wxkSf/RmD9GbbVEh3dt14BAc= Received: from rubens-MacBook-Air.local (ip4da7bddc.direct-adsl.nl [77.167.189.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA id C234B301AE for ; Fri, 13 May 2016 02:37:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1463099877; bh=8BOTOSioDvIhi1oS6wDPaC8WvNwHjAXAD8pzhLfOf14=; h=To:References:Subject:From:Date:In-Reply-To; b=HRX1Tx8clJsiwIExSfkXePqCHENc5y09aNmcMXRtay1VShfko/Ek1hXAmXM5dnAbC 2fCqx6JA5NkcbVHLKpTt3gtiB5baqk97kIIyHgzWGd3idlXc1qhPfwpJlIHD3XE4yn YXHk8CwSFh8Sv3JtNjbDYMMCJBlYPb2xgYpSXT5aTR8eSsc87m8tBEkbsLtEYUkxiZ CNSu441DFvFtGSJHMvUpTRAXFclbgAmqAJsRKR+894Yyqk1qrRuLVRgiv2wHHwL4nA f7a0x7GhJXXlyby8+cAYt1wTguGh8lemNRlv++uVkw6zvxDvfhDgiEmtQqctfG9Iah T0EXGeUBNwR7+zUuuDwVPhXI002gcMSqMdysKSBWY0+CsX9x52/Fbyx/BUDNHSfJWf j6XCSAsb6podtyZkxlZh99l0/sg3pqV+BRGFqNHeNElXG9LzNDHHjCQd95r5L7r6YI xJP22Mn96c+1vT3M9l8Pr17XiT2vdN0Z56Xj5UhXxHTUDH1tDbaybqmLaH4pVGaZNx gcNAlkYnT1gyoqKwps7pnfwd6+cdrTZrHkemeRGhBc0vIw9JsP/rjoe5/y5hTvhurM d6R7DtbF3mhr0jKcj3CxDXetmCECV9gyf0lpehi5iALUA8H8Kiy/8/L/RNijkuQI01 lrTrCcrcsAmPoU0ZtIJJMgRI= To: freebsd-net@freebsd.org References: <553A8DF0.2060901@sds.com> Subject: Re: bhyve with vlans - host and vm can't pass traffic From: Ruben Message-ID: <9c759cf4-01f0-6f21-c18a-27b3d491dcbf@osfux.nl> Date: Fri, 13 May 2016 02:37:56 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <553A8DF0.2060901@sds.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 00:43:48 -0000 Hi Scott, Since I'm currently facing a somewhat similar problem (to the best of my understanding): where you ever able to solve this? I'd be more than happy to hear of any solution for the predicament you were in :P Kind regards, Ruben From owner-freebsd-net@freebsd.org Fri May 13 08:10:53 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 B7C1CB391E2 for ; Fri, 13 May 2016 08:10:53 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (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 7C6601E31 for ; Fri, 13 May 2016 08:10:52 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3r5jGX0VYzzZqp; Fri, 13 May 2016 10:10:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject:received:received; s=mail; t= 1463127042; x=1464941443; bh=RN1zxR3XdLSZPvcU+efOktCKHh4sIZbfFeO W8FCPyo0=; b=FIU1JfPgkq5aWKPB6Te5YdLor7E4/3l1TinwzQu/p9HpmpiOy5c u/DZUTqbg46lGfe5LSNUUXa4WRra0OUeq91SbEs2kp2+Oj0S4rNEGozSR8RjfQY5 w9Qg9rj9IN0tdPA++fHb4sFSGElhNgaA9rri8nruBYj607xJXrJdDm8k= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id bO2z5Au-7Duw; Fri, 13 May 2016 10:10:42 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Fri, 13 May 2016 10:10:42 +0200 (CEST) Subject: Re: NAT SIP ALG To: Eugene Grosbein , "freebsd-net@freebsd.org" References: <5734D478.2010809@grosbein.net> From: Guido Falsi Message-ID: <70337093-6977-54d2-63cb-15b931c8c726@madpilot.net> Date: Fri, 13 May 2016 10:10:41 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <5734D478.2010809@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 08:10:53 -0000 On 05/12/16 21:07, Eugene Grosbein wrote: > Hi! > > Does FreeBSD have any kind of NAT capable of parsing SIP signalling traffic > to properly translate IP addresses inside protocol? Not that I know of. You could use the net/kamailio port to proxy SIP traffic though. It should be able to do what you are asking for. -- Guido Falsi From owner-freebsd-net@freebsd.org Fri May 13 09:17:17 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 A5E82B39D70 for ; Fri, 13 May 2016 09:17:17 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 95CE110AB for ; Fri, 13 May 2016 09:17:17 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u4D9HAdk047701 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 13 May 2016 02:17:10 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time To: pyunyh@gmail.com References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> <20160508093305.GA1558@michelle.fasterthan.co.kr> <57341899.2040600@rawbw.com> <20160512055834.GA1198@michelle.fasterthan.co.kr> Cc: freebsd-net@freebsd.org From: Yuri Message-ID: <5ecf1c0e-af92-982e-528f-1160b5bc761d@rawbw.com> Date: Fri, 13 May 2016 02:17:09 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160512055834.GA1198@michelle.fasterthan.co.kr> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 09:17:17 -0000 On 05/11/2016 22:58, YongHyeon PYUN wrote: > hw.msk.msi_disable is a loader tunable so you can't check it with > sysctl(8). Add the tunable to boot/loader.conf to take it effect. > See loader.conf(5) for more information. Adding hw.msk.msi_disable="1" reduced the mouse problem, but Marvell Yukon card still didn't function properly. Speed test showed much slower result. And mouse still doesn't move as freely as usual. Something isn't right with it. Yuri From owner-freebsd-net@freebsd.org Fri May 13 12:31:13 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 D7740B39C7B for ; Fri, 13 May 2016 12:31:13 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 70A141808 for ; Fri, 13 May 2016 12:31:12 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u4DCV5EU001695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 13 May 2016 14:31:06 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: James@Lodge.me.uk Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u4DCUvfh072400 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 13 May 2016 19:30:57 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: NAT SIP ALG To: James Lodge References: <5734D478.2010809@grosbein.net> <9F55FBCB-4B1A-4134-8912-9A5B25F37703@Lodge.me.uk> Cc: "freebsd-net@freebsd.org" From: Eugene Grosbein Message-ID: <5735C8FB.908@grosbein.net> Date: Fri, 13 May 2016 19:30:51 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <9F55FBCB-4B1A-4134-8912-9A5B25F37703@Lodge.me.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 12:31:13 -0000 13.05.2016 5:26, James Lodge wrote: > I use siproxd on pfsense and it works really well. How do you use them? I have SIP PBX inside private network that has old slow Cisco router as NAT box. The PBX registers with several distinct external SIP providers and accepts external calls for local call center. I need to replace Cisco router with something having much more horsepower and consider FreeBSD/amd64 but need to make sure SIP won't break. Will siproxd help me in such case? I still need the PBX to be able to register directly to external SIP providers as it is administrated by outsourced company. From owner-freebsd-net@freebsd.org Fri May 13 13:32:31 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 494F4B39F71; Fri, 13 May 2016 13:32:31 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F5A712C6; Fri, 13 May 2016 13:32:31 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=X1cx9I4zwMd/xSt105woNYGstXzH/1rwO9NvdolTPCI=; b=oybQFP2uOCq0UpJIczxHogE4/7 N5Qgal5l/QrDp/xMlZF+SDdr75xD9v+AOTh9hkz1QrjqdW4A91UVQKgJgdLihPwpw769XJi0aQmbI VtJrJkyIZ7F1+i6Np7Ltf8woSzF75uUqnkXikHSPm7sfjlMwPKwirDU5OYgkQuMnPHts=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:37685 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b1DCb-0009TD-9O; Fri, 13 May 2016 08:32:25 -0500 Received: from proxy.na.alcatel-lucent.com ([135.245.48.84]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Fri, 13 May 2016 08:32:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 13 May 2016 08:32:25 -0500 From: Larry Rosenman To: Eugene Grosbein Cc: James Lodge , freebsd-net@freebsd.org, owner-freebsd-net@freebsd.org Subject: Re: NAT SIP ALG In-Reply-To: <5735C8FB.908@grosbein.net> References: <5734D478.2010809@grosbein.net> <9F55FBCB-4B1A-4134-8912-9A5B25F37703@Lodge.me.uk> <5735C8FB.908@grosbein.net> Message-ID: <027cf5fb5beaf0ab01045f49a4a2adb1@thebighonker.lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.1.4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 13:32:31 -0000 On 2016-05-13 07:30, Eugene Grosbein wrote: > 13.05.2016 5:26, James Lodge wrote: > >> I use siproxd on pfsense and it works really well. > > How do you use them? > > I have SIP PBX inside private network that has old slow Cisco router as > NAT box. > > The PBX registers with several distinct external SIP providers and > accepts external > calls for local call center. I need to replace Cisco router with > something having much > more horsepower and consider FreeBSD/amd64 but need to make sure SIP > won't break. > > Will siproxd help me in such case? I still need the PBX to be able to > register > directly to external SIP providers as it is administrated by outsourced > company. > My asterisk server (pbx) registers through my NAT without ANY rules or what have you. I do have the NAT option turned on for the 4 providers I connect to. That said, sipoxd/pfSense may work as well. I do go through pfSense, but again do NOT have any SUP proxying. The asterisk server just keeps a registration open. I can get and receive calls. FWIW -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-net@freebsd.org Fri May 13 13:59:25 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 E21CCB3A46F for ; Fri, 13 May 2016 13:59:25 +0000 (UTC) (envelope-from James@Lodge.me.uk) Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0127.outbound.protection.outlook.com [157.55.234.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78CD01E67 for ; Fri, 13 May 2016 13:59:24 +0000 (UTC) (envelope-from James@Lodge.me.uk) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gavinlodge.onmicrosoft.com; s=selector1-Lodge-me-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3gRrB+vwKSE8QV6lwsWwlIhIA7d4w7LyJjrznzLD/OA=; b=kGZ7f3kw0wbM4+jQe+EOSynh+HAEZBYDJYVADHgL1CM7pjSzaM9T7cVSMzcZaPfSfOur8YQpP4pp9bUW89Ky6FriizPrOvKL/DnpHLC5PPNKFj0uW+oxSveKQXORY2vgSeq0cZAvWIs52UG7D/Z4jJx33Oz6flG4cPS4ieRFBiY= Received: from DB5PR06MB1718.eurprd06.prod.outlook.com (10.165.213.16) by DB5PR06MB1720.eurprd06.prod.outlook.com (10.165.213.18) with Microsoft SMTP Server (TLS) id 15.1.497.3; Thu, 12 May 2016 22:26:33 +0000 Received: from DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) by DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) with mapi id 15.01.0497.014; Thu, 12 May 2016 22:26:33 +0000 From: James Lodge To: Eugene Grosbein CC: "freebsd-net@freebsd.org" Subject: Re: NAT SIP ALG Thread-Topic: NAT SIP ALG Thread-Index: AQHRrIGkuSfwQn+AdkSKYLIyrKYgY5+14al7 Date: Thu, 12 May 2016 22:26:33 +0000 Message-ID: <9F55FBCB-4B1A-4134-8912-9A5B25F37703@Lodge.me.uk> References: <5734D478.2010809@grosbein.net> In-Reply-To: <5734D478.2010809@grosbein.net> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: grosbein.net; dkim=none (message not signed) header.d=none;grosbein.net; dmarc=none action=none header.from=Lodge.me.uk; x-originating-ip: [81.174.132.199] x-ms-office365-filtering-correlation-id: 4b31c20a-3f7f-4315-b398-08d37ab4795a x-microsoft-exchange-diagnostics: 1; DB5PR06MB1720; 5:Q8BMrGnr7Zxr1DKsi3himwdhd+R4zd27a2/3+IwBaUAIrLGG2jKszsSnsKXwkCc7odO0F3/vSC2BHbFEIHgNhQuJc0HzucvUmHP8eIkEi0p3rBebnPyqGj+ZHk8nFKFK5PpIOWLfEVVAImv5Lkhs3g==; 24:qkJ+UeBm0aVaiucLOGa5hoU3bsyRlDhJi9cQGJ17hCR1bgKwbnknyqBJrkUHNUphE9HHLJcKbCw8u7J9Ai+RXPmYcV3Oofnt9ovm1zzhX3E=; 7:EbsQZHbh2/TSpQwy8NN2DT8t5sLkheVPwQ7sGgKXZ3EfrW8/nZRZ3wJqUKk7GBkdK5Q5gRxl7jf75u7ya2+YSdUFm0ARiniD/CVW83F19gkE94A6/SvFrxhIfJCBds8caj4qMJHsNe+GNIFI9GGIlw6d9m5Dhs6padS5kZ2TFHXyeTyIMKEUL47WQPV0YhPk x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB1720; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040130)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041072)(6043046); SRVR:DB5PR06MB1720; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB1720; x-forefront-prvs: 0940A19703 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(3660700001)(4326007)(50986999)(74482002)(76176999)(6116002)(102836003)(3846002)(54356999)(586003)(3280700002)(77096005)(81166006)(19580405001)(19580395003)(8936002)(15975445007)(92566002)(2906002)(10400500002)(2950100001)(2900100001)(36756003)(5008740100001)(86362001)(122556002)(1220700001)(5002640100001)(33656002)(87936001)(3480700004)(11100500001)(5004730100002)(189998001)(80792005)(106116001)(110136002)(66066001)(217873001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR06MB1720; H:DB5PR06MB1718.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Lodge.me.uk X-MS-Exchange-CrossTenant-originalarrivaltime: 12 May 2016 22:26:33.4623 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ded56ae9-7c77-4cf6-bbfd-39e6a505742d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR06MB1720 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 13:59:26 -0000 > On 12 May 2016, at 20:08, Eugene Grosbein wrote: >=20 > Hi! >=20 > Does FreeBSD have any kind of NAT capable of parsing SIP signalling traff= ic > to properly translate IP addresses inside protocol? >=20 > Eugene Grosbein >=20 > _______________________________________________ > 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" I use siproxd on pfsense and it works really well.=20 https://www.freshports.org/net/siproxd/