From owner-freebsd-net@freebsd.org Sun Mar 18 00:28:20 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B82B7F523FF for ; Sun, 18 Mar 2018 00:28:20 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 31F52754DB for ; Sun, 18 Mar 2018 00:28:19 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2I0SACa004590; Sat, 17 Mar 2018 17:28:10 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2I0S96f004589; Sat, 17 Mar 2018 17:28:09 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803180028.w2I0S96f004589@pdx.rh.CN85.dnsmgr.net> Subject: Re: Does FreeBSD do proactive ARP refresh? In-Reply-To: <7275711521311778@web56g.yandex.ru> To: "Alexander V. Chernikov" Date: Sat, 17 Mar 2018 17:28:09 -0700 (PDT) CC: "freebsd-net@freebsd.org" , "sthaug@nethelp.no" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Mar 2018 00:28:20 -0000 [ Charset UTF-8 unsupported, converting... ] > 17.03.2018, 21:23, "Rodney W. Grimes" : > >> ?16.03.2018, 14:50, "sthaug@nethelp.no" : > >> ?.. > >> ?>> ?And thank you for that suggestion! The packet loss during ARP refresh > >> ?>> ?(of the destination address connected to the output interface) does > >> ?>> ?*not* happen when the box is forwarding! It only happens with locally > >> ?>> ?generated traffic. > >> ?Should be fixed by r331098. > > > > Thanks for the quick fix, do we know about when this breakage started? > I guess it's something like r297225. SO 2 years ago, meaning it effects stable/11, and may of been merged to stable/10? Do you plan to MFC your fix? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Sun Mar 18 09:39:02 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA930F68B94 for ; Sun, 18 Mar 2018 09:39:02 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 5405187FFF for ; Sun, 18 Mar 2018 09:39:02 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2I9cv3f006184; Sun, 18 Mar 2018 02:38:57 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2I9cvJs006183; Sun, 18 Mar 2018 02:38:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803180938.w2I9cvJs006183@pdx.rh.CN85.dnsmgr.net> Subject: Re: Does FreeBSD do proactive ARP refresh? In-Reply-To: <3023141521364867@web33j.yandex.ru> To: "Alexander V. Chernikov" Date: Sun, 18 Mar 2018 02:38:57 -0700 (PDT) CC: "freebsd-net@freebsd.org" , "sthaug@nethelp.no" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Mar 2018 09:39:03 -0000 > 18.03.2018, 03:31, "Rodney W. Grimes" : > >> ?17.03.2018, 21:23, "Rodney W. Grimes" : > >> ?>> ?16.03.2018, 14:50, "sthaug@nethelp.no" : > >> ?>> ?.. > >> ?>> ?>> ?And thank you for that suggestion! The packet loss during ARP refresh > >> ?>> ?>> ?(of the destination address connected to the output interface) does > >> ?>> ?>> ?*not* happen when the box is forwarding! It only happens with locally > >> ?>> ?>> ?generated traffic. > >> ?>> ?Should be fixed by r331098. > >> ?> > >> ?> Thanks for the quick fix, do we know about when this breakage started? > >> ?I guess it's something like r297225. > > > > SO 2 years ago, meaning it effects stable/11, > > and may of been merged to stable/10? > Side note: if one has monitoring which does ICMP checks, it will mask the issue because icmp replies don't use route caching. > Typical story when the observer changes the state of an observed object :-). Also perhaps why it has not been reported before, as other side effects have caused it to be a pretty invisible issue. > IIRC it was not merged to stable/10. > > > > Do you plan to MFC your fix? > Yes, I do :-) For some reason the MFC: 2 weeks did not register when I read the commit. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Sun Mar 18 09:53:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43EBD270 for ; Sun, 18 Mar 2018 09:53:16 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with ESMTP id C6FA86865A for ; Sun, 18 Mar 2018 09:53:15 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id C6354E6047; Sun, 18 Mar 2018 10:53:07 +0100 (CET) Date: Sun, 18 Mar 2018 10:53:07 +0100 (CET) Message-Id: <20180318.105307.74674158.sthaug@nethelp.no> To: "Rodney W. Grimes" Cc: "Alexander V. Chernikov" , freebsd-net@freebsd.org Subject: Re: Does FreeBSD do proactive ARP refresh? From: sthaug@nethelp.no In-Reply-To: <201803180938.w2I9cvJs006183@pdx.rh.CN85.dnsmgr.net> References: <3023141521364867@web33j.yandex.ru> <201803180938.w2I9cvJs006183@pdx.rh.CN85.dnsmgr.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Mar 2018 09:53:16 -0000 > > Side note: if one has monitoring which does ICMP checks, it will mask the issue because icmp replies don't use route caching. > > Typical story when the observer changes the state of an observed object :-). > > Also perhaps why it has not been reported before, as other side effects > have caused it to be a pretty invisible issue. The reason I discovered this is because I was running longer (1 hour or more) iperf3 sessions, and I got some small but regular packet loss that I couldn't remember having seen before. Which may be because my previous longer iperf3 sessions had been with FreeBSD 9.3-STABLE. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@freebsd.org Sun Mar 18 09:21:12 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69BCAF67E8C for ; Sun, 18 Mar 2018 09:21:12 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7566874C7 for ; Sun, 18 Mar 2018 09:21:11 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mxback5g.mail.yandex.net (mxback5g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:166]) by forward105j.mail.yandex.net (Yandex) with ESMTP id 1EA211816AA; Sun, 18 Mar 2018 12:21:09 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback5g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id qpp1Z1cnUS-L7f8WiPE; Sun, 18 Mar 2018 12:21:07 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1521364867; bh=/iH+Q6Kn6saW9qtOLegSQh54vxb7fNZuHebeSxNpEQc=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=ZQDNjacs827yDEjkEi8G+vgaTTJm8z4WJu+vRhS9pPVQ2+smbToWHnxof52GsjG0t U0iVxh/wjvDRjpGfhLuEGhXlgkeNsJv+kEID8y15gdPxLhWzFSc9hXV8iGvbcnRpEt GKXt/mE/OkU1s51Gd6dRDmefZlNuDNa2x006l1Q0= Authentication-Results: mxback5g.mail.yandex.net; dkim=pass header.i=@ipfw.ru Received: by web33j.yandex.ru with HTTP; Sun, 18 Mar 2018 12:21:07 +0300 From: Alexander V. Chernikov To: Rodney W. Grimes Cc: "freebsd-net@freebsd.org" , "sthaug@nethelp.no" In-Reply-To: <201803180028.w2I0S96f004589@pdx.rh.CN85.dnsmgr.net> References: <7275711521311778@web56g.yandex.ru> <201803180028.w2I0S96f004589@pdx.rh.CN85.dnsmgr.net> Subject: Re: Does FreeBSD do proactive ARP refresh? MIME-Version: 1.0 Message-Id: <3023141521364867@web33j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 18 Mar 2018 12:21:07 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Mar 2018 09:21:12 -0000 18.03.2018, 03:31, "Rodney W. Grimes" : > [ Charset UTF-8 unsupported, converting... ] >>  17.03.2018, 21:23, "Rodney W. Grimes" : >>  >> ?16.03.2018, 14:50, "sthaug@nethelp.no" : >>  >> ?.. >>  >> ?>> ?And thank you for that suggestion! The packet loss during ARP refresh >>  >> ?>> ?(of the destination address connected to the output interface) does >>  >> ?>> ?*not* happen when the box is forwarding! It only happens with locally >>  >> ?>> ?generated traffic. >>  >> ?Should be fixed by r331098. >>  > >>  > Thanks for the quick fix, do we know about when this breakage started? >>  I guess it's something like r297225. > > SO 2 years ago, meaning it effects stable/11, > and may of been merged to stable/10? Side note: if one has monitoring which does ICMP checks, it will mask the issue because icmp replies don't use route caching. Typical story when the observer changes the state of an observed object :-). IIRC it was not merged to stable/10. > > Do you plan to MFC your fix? Yes, I do :-) > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > 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 Sun Mar 18 21:01:07 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88450F5375A for ; Sun, 18 Mar 2018 21:01:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2839686A07 for ; Sun, 18 Mar 2018 21:01:07 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 680F81C531 for ; Sun, 18 Mar 2018 21:01:06 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IL16oK048973 for ; Sun, 18 Mar 2018 21:01:06 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IL16uA048972 for freebsd-net@FreeBSD.org; Sun, 18 Mar 2018 21:01:06 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201803182101.w2IL16uA048972@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 18 Mar 2018 21:01:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Mar 2018 21:01:07 -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 | 165622 | [ndis][panic][patch] Unregistered use of FPU in k In Progress | 206581 | bxe_ioctl_nvram handler is faulty In Progress | 221146 | [ixgbe] Problem with second laggport 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 New | 209682 | [panic] [netinet] arptimer race New | 213410 | [carp] service netif restart causes hang only whe New | 217748 | sys/dev/ixgbe/if_ix.c: PVS-Studio: Assignment to Open | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc 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 | 202510 | [CARP] advertisements sourced from CARP IP cause Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ Open | 213814 | AWS/EC2: no egress traffic stats on ixv(4) Open | 222273 | igb(4): Kernel panic (fatal trap 12) due to netwo 18 problems total for which you should take action. From owner-freebsd-net@freebsd.org Mon Mar 19 04:16:53 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E844F4C911 for ; Mon, 19 Mar 2018 04:16:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B35D478F6E for ; Mon, 19 Mar 2018 04:16: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 053F220186 for ; Mon, 19 Mar 2018 04:16:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2J4GpsE000433 for ; Mon, 19 Mar 2018 04:16:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2J4Gpo6000430 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 04:16:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26). Date: Mon, 19 Mar 2018 04:16:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED 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.25 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, 19 Mar 2018 04:16:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206721 --- Comment #7 from commit-hook@freebsd.org --- A commit references this bug: Author: eadler Date: Mon Mar 19 04:16:38 UTC 2018 New revision: 331179 URL: https://svnweb.freebsd.org/changeset/base/331179 Log: MFC r305306: dhclient: add support for interface-mtu (26) Make dhclient set interface MTU if it was provided. This version implements MTU setting in dhclient itself before it runs dhclient-script. PR: 206721 Changes: _U stable/11/ stable/11/sbin/dhclient/clparse.c stable/11/sbin/dhclient/dhclient.c stable/11/sbin/dhclient/dhcpd.h stable/11/sbin/dhclient/dispatch.c stable/11/sbin/dhclient/privsep.c stable/11/sbin/dhclient/privsep.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 04:56:59 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A47D4F4F5D2 for ; Mon, 19 Mar 2018 04:56:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 435F37A419 for ; Mon, 19 Mar 2018 04:56:59 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8E51F206FB for ; Mon, 19 Mar 2018 04:56:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2J4uwQA004449 for ; Mon, 19 Mar 2018 04:56:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2J4uwOX004446 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 04:56:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4) Date: Mon, 19 Mar 2018 04:56:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: resolution bug_status 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.25 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, 19 Mar 2018 04:56:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199136 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|Open |Closed --- Comment #11 from Eugene Grosbein --- Just use ifconfig_tap0=3D"inet 192.168.0.1/29 link0" *** This bug has been marked as a duplicate of bug 165174 *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 04:57:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0558F4F5D7 for ; Mon, 19 Mar 2018 04:57:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89DA27A424 for ; Mon, 19 Mar 2018 04:57:00 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E00B520702 for ; Mon, 19 Mar 2018 04:56:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2J4uxPh004501 for ; Mon, 19 Mar 2018 04:56:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2J4ux3Y004500 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 04:56:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 165174] [patch] [tap] allow tap(4) to keep its address on close Date: Mon, 19 Mar 2018 04:56:56 +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.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED 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.25 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, 19 Mar 2018 04:57:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D165174 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yuri@freebsd.org --- Comment #4 from Eugene Grosbein --- *** Bug 199136 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 11:31:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8819F67A65 for ; Mon, 19 Mar 2018 11:31:01 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by mx1.freebsd.org (Postfix) with ESMTP id 62DB46AEEF for ; Mon, 19 Mar 2018 11:31:01 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id D1596E6047; Mon, 19 Mar 2018 12:30:58 +0100 (CET) Date: Mon, 19 Mar 2018 12:30:58 +0100 (CET) Message-Id: <20180319.123058.74660594.sthaug@nethelp.no> To: Alexander V. Chernikov Cc: freebsd-net@freebsd.org Subject: Re: Does FreeBSD do proactive ARP refresh? From: sthaug@nethelp.no In-Reply-To: <14964521521306770@web10o.yandex.ru> References: <20180316.122720.71152047.sthaug@nethelp.no> <20180316.124748.104098359.sthaug@nethelp.no> <14964521521306770@web10o.yandex.ru> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 11:31:02 -0000 > >> =A0And thank you for that suggestion! The packet loss during ARP r= efresh > >> =A0(of the destination address connected to the output interface) = does > >> =A0*not* happen when the box is forwarding! It only happens with l= ocally > >> =A0generated traffic. > Should be fixed by r331098. I can confirm that 12.0-CURRENT with the r331098 updates fixes this problem for me for locally generated traffic. The ARP entry seems to be refreshed around 4 seconds before expiry, and there is no packet loss. Transit traffic (non locally generated) also works as before, the ARP entry is refreshed before expiry and there is no packet loss. Thanks for the quick fix! Now waiting for the MFC :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@freebsd.org Mon Mar 19 11:40:40 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E722CF68438 for ; Mon, 19 Mar 2018 11:40:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C3876B4C4 for ; Mon, 19 Mar 2018 11:40:39 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AEB2B23E47 for ; Mon, 19 Mar 2018 11:40:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2JBecga023796 for ; Mon, 19 Mar 2018 11:40:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2JBecDc023793 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 11:40:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26). Date: Mon, 19 Mar 2018 11:40:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cem@freebsd.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11+ X-Bugzilla-Changed-Fields: keywords assigned_to flagtypes.name see_also 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.25 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, 19 Mar 2018 11:40:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206721 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |feature Assignee|freebsd-net@FreeBSD.org |cem@freebsd.org Flags| |mfc-stable10?, | |mfc-stable11+ See Also| |https://reviews.freebsd.org | |/D4788 --- Comment #8 from Kubilay Kocak --- Assign to committer that resolved. Thanks Conrad! Also track MFC's correctly, currently only to stable/11 Can stable/10 not receive it? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 13:56:39 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ED97F4EB5E for ; Mon, 19 Mar 2018 13:56:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0ED7A7085B for ; Mon, 19 Mar 2018 13:56:39 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 33BE1251B0 for ; Mon, 19 Mar 2018 13:56:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2JDucnV069936 for ; Mon, 19 Mar 2018 13:56:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2JDucJ9069935 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 13:56:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26). Date: Mon, 19 Mar 2018 13:56:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cem@freebsd.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11+ 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.25 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, 19 Mar 2018 13:56:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206721 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-net@FreeBSD.org --- Comment #9 from Rodney W. Grimes --- Put back on freebsd-net@ notification list --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 19:31:31 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEDAAF66438 for ; Mon, 19 Mar 2018 19:31:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B7B0809B2 for ; Mon, 19 Mar 2018 19:31: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 72B18E5 for ; Mon, 19 Mar 2018 19:31:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2JJVUrt056494 for ; Mon, 19 Mar 2018 19:31:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2JJVUc3056493 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 19:31:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218579] Wake on Lan doesn't work for bge NIC driver Date: Mon, 19 Mar 2018 19:31:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gmc@metro.cx X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.25 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, 19 Mar 2018 19:31:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 Koen Martens changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gmc@metro.cx --- Comment #5 from Koen Martens --- Not sure what the fix is, and how 171744 is relevant (it's about the wake command, if I understand correctly). Just wanted to chime in. I have a machine with a bge-driven card for which = WOL worked perfectly with 10.3-RELEASE. I activated it with 'ifconfig bge0 wol_magic' and then used the wakeonlan utility on a linux (ubuntu 16.04) machine to wake up the freebsd machine. Yesterday I upgraded to 11.1-RELEASE (something I have put off for ages bec= ause I was afraid something would break, but with the EOL coming up I decided to take the risk), and WOL just stopped working. It isn't even advertised anymore as a capability in ifconfig: # ifconfig -m bge0 bge0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3D8009b =20=20=20=20=20=20=20 capabilities=3D8009b ether 00:1e:c9:5b:75:11 hwaddr 00:1e:c9:5b:75:11 inet 10.1.3.8 netmask 0xffffff00 broadcast 10.1.3.255=20 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active supported media: media autoselect mediaopt flowcontrol media autoselect media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP Needless to say, 'ifconfig bge0 wol_magic' doesn't enable it anymore either. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 19:43:24 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C04EF672FE for ; Mon, 19 Mar 2018 19:43:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE6818140E for ; Mon, 19 Mar 2018 19:43: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1FC3F29F for ; Mon, 19 Mar 2018 19:43:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2JJhN8Z091450 for ; Mon, 19 Mar 2018 19:43:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2JJhMm4091449 for freebsd-net@FreeBSD.org; Mon, 19 Mar 2018 19:43:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218579] Wake on Lan doesn't work for bge NIC driver Date: Mon, 19 Mar 2018 19:43:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cy@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.25 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, 19 Mar 2018 19:43:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 --- Comment #6 from Cy Schubert --- I don't understand why it worked on 10.3. The WOL code was not in bge at the time. The patch is for 12-CURRENT. I'll rework it for 11-STABLE. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 19 19:49:21 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8651F67959 for ; Mon, 19 Mar 2018 19:49:21 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net [68.230.241.217]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0B88189B for ; Mon, 19 Mar 2018 19:49:21 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo110.cox.net ([68.230.241.223]) by eastrmfepo202.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20180319194915.TEIW7322.eastrmfepo202.cox.net@eastrmimpo110.cox.net> for ; Mon, 19 Mar 2018 15:49:15 -0400 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo110.cox.net with cox id PvpE1x00j1LxgH801vpEna; Mon, 19 Mar 2018 15:49:15 -0400 X-Authority-Analysis: v=2.2 cv=VfuHBBh9 c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=v2DPQv5-lfwA:10 a=e9ASbk4n0QUA:10 a=GaCiEt_Ov1hTDkfTx3YA:9 a=QEXdDO2ut3YA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (LOGIN) smtp.auth=jbuehler@cox.net Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id 43CBD1152A; Mon, 19 Mar 2018 15:49:14 -0400 (EDT) Message-ID: <5AB01439.3090003@cox.net> Date: Mon, 19 Mar 2018 15:49:13 -0400 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" Subject: Re: netmap ixgbevf mtu References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 19:49:22 -0000 Vincenzo Maffione wrote: > To receive a frame larger than the RX buffer size you need multiple > netmap slots (as multiple descriptors are > used by the hardware), looking at the NS_MOREFRAG flag. > See the example code in utils/functional.c::rx_one(). This works fine -- thanks. > Also TX may have per-slot limitations (e.g. due to the size of the NIC > TX fifo), but this is usually > 9K, so using a single descriptor per > packet should always > be ok. However, you can also use multiple slots on the TX side (see > utils/functional.c::tx_one()). Trying to split TX frames into multiple buffers does not work, the NIC is sending 2048 byte frames (the buf_size I am using). I will re-check my code. Do I need a particular version of ixgbevf perhaps? Joe Buehler From owner-freebsd-net@freebsd.org Mon Mar 19 21:29:15 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C16C2F4AD29 for ; Mon, 19 Mar 2018 21:29:15 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 3CD9186923 for ; Mon, 19 Mar 2018 21:29:15 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id t7so4971515wmh.5 for ; Mon, 19 Mar 2018 14:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=lDfzasxWt04NsgTrQhH5tDvl7hk+jamv9ZqSoOfgRXo=; b=fs4qkld3mfELb7ms0aiRTmKU39FQ9LdRzzSyBVo06YNDGGXCXJtDyUDIDlb+LBmel2 pa9jcLbZnL8rYCl9LSv6yPX1JlDdSTJszMrsTOZycdEVDafeuPFIIHQFFeqVfOpE4C2D Cao2FjPIi43irFm72qfTn0XFY/Wl/Zm8RWkNZCI2QP+hTke4JbQJuYtKL0vpWS8Vmzqf 8hLzljWdfVFSzWha1QKYBJkkAsP46/PtRlRZnZblYEkhg4wtLMbrbYgWVJRhwXpl2pQ7 iWQPC1462WDHK2ClzsBmKAdn7dxWeIfYZxgw2p/qamuqyu7305KRM4mYO8UA1GzVrqf4 aY2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=lDfzasxWt04NsgTrQhH5tDvl7hk+jamv9ZqSoOfgRXo=; b=azsRrc55dqu9STADCJhe8EqeJ/c+plrRD84tUAkPeqmzbicZ7k5qQZTRlKFeq5N1l6 KAhvrKXDTvDjQmtbTCt1HUIE0dMUUGC/MARGzrbgEJvudCfBpU+rG8Z6rBdKOXNBZFpQ XZLa7uc06UBTCBVV4kA4ZbvlZnI0U/KPtacuEwnlnmn6GqQ8L+T3rCsBs8kVAyMM0v8X hmjlMlI4/XeAJCL45TJKBRARG+aEqA/PQGD0UHSjS26u3r21kExuG83WY9+G3lUQJ0sE JQ722LCm5nO89PEEG66xv6kYCca0MMSmqSH+wEegiABaxy1HqnJFPSswVUHsou0qpKlf XArw== X-Gm-Message-State: AElRT7H/yR9vtKG+gSJtEKHInjnXFVsln6DCHT2kI3LFplQszB9fmRAX 52qUuX4CbYT/2cqa38TYTTdiCDp3 X-Google-Smtp-Source: AG47ELscSocuNVOO2UDeUyp/DwcT2yDdUcW2JrhR6IGeQMoXsqul4yTUsgueNLJsOE+2eb00BQtoWQ== X-Received: by 10.80.189.131 with SMTP id y3mr15238929edh.122.1521494953990; Mon, 19 Mar 2018 14:29:13 -0700 (PDT) Received: from juntos.woohoo.ch ([2a02:168:681c:460:e533:d878:a326:9600]) by smtp.gmail.com with ESMTPSA id t19sm113727edd.56.2018.03.19.14.29.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 14:29:13 -0700 (PDT) To: freebsd-net@freebsd.org From: Andreas Scherrer Subject: Multicast/SSDP not working (on VLAN interface) Message-ID: Date: Mon, 19 Mar 2018 22:29:12 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 21:29:16 -0000 Dear List I was unfortunately unable to find a way to search this mailing list's archive; so please bear with me if the question was answered before. My goal is to have DLNA clients (VLC, Heos music system, ...) in multiple networks discover a MiniDLNA server. The server shows up in VLC when it starts (or is restarted) after VLC is running. If the server is already running when VLC is started, VLC does not detect/find the server. Very much like this source states: https://sourceforge.net/p/minidlna/bugs/94/#8c8f I suspect a problem with the M-SEARCH messages the client is sending. Using tcpdump on the interface where M-SEARCH from VLC are coming in, I can indeed see the packets/messages arrive (they are sent from the client to 239.255.255.250). So it is is not a router or switch or whatever blocking the packets. Now, if I (manually) add a static route for 224.0.0.0/4 via the interface the M-SEARCH messages are coming in, everything starts to work! route add -net 224.0.0.0/4 -iface re1.32 The (main) problem here is that I have multiple networks with clients in them. So a static route does not REALLY solve my problem. Also I do not (yet?) understand why the route should be required. What I see is that ifmcstat -f inet -i re1.32 does not list a membership for 239.255.255.250 when it is not working, but does list the membership when it is working... So I suspect that "something" is dropping the M-SEARCH packets for some reason after they are received. And I cannot get rid of the feeling that it has something to do with the fact that the incoming interface is a VLAN interface... My first guess, anti spoofing, seems not to be the problem (I am using ipfw and "not antispoof in" but that does not seem to drop any traffic). Do I miss something obvious or can someone point me in the right direction? VLC v2.2.8 is running on Mac OSX 10.12. MiniDLNA v1.2.1,1 is running on FreeBSD RELEASE-11.1. More information can be found in the FreeBSD forum [1]. Thanks heaps andreas [1] https://forums.freebsd.org/threads/minidlna-not-discovered-multicast-issue.64947/ From owner-freebsd-net@freebsd.org Mon Mar 19 22:37:36 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02CBEF4FD94 for ; Mon, 19 Mar 2018 22:37:36 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 605FF69AE8 for ; Mon, 19 Mar 2018 22:37:35 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id p142-v6so5163205lfd.6 for ; Mon, 19 Mar 2018 15:37:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Bs6N3e1UIIJOxXbc9r+ktBS7gS/FO9ox+09YxAfSZ1c=; b=dQfhfBzfTUb67GW2bjVWOIMPjXMW+yIsoX0/7hnFdtjNx60zYjdSs/JjKOjpFWXmkw jwvABTGTtC+jCLO4Cn4zNlxSlnnrvREaN07ucx1GjuYF8Ayiu2nSYsX7rsRndog+dLkm Ave1XzgO02CeWjks0O9zmPGCq7mrZ8iCNHPPEro1hmfIRH2QHiOwY8zLaZmFfxxhCRBJ jHkqyyt4VqZTvMSnyEvM0V4TV6ys5/9kikv5u+mUnsfO3zVLkGMcs3ce3F7yUT+/Ewt5 82I+6p7yHyNBNXO5g4WL2O3UkJOHZhw2/yKGGYEtXqy4H3IU62H8bIGqK0vFXpWEUWly I+SQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Bs6N3e1UIIJOxXbc9r+ktBS7gS/FO9ox+09YxAfSZ1c=; b=MxVltXkWGxwmrp0jTORYyA++CfZWowPfv7bzsiyd12LP6EoFt3/PDx3mWI2sncucSU WJjY8ywz/O/316DELWYIbX6npx7KRZtkwvZKqh+Hbgr7X2pMe78PbhrnXel+gN57nZxI AdYTD9HzSlobs094jTmB9q2l+9GlIxDe/eqvLWq9tpd8VyppkRZLpQ69t0ons5RNIuvP G5A8IKOM+Mi2o7bQMp0Rj8sW0u3SpOfCGlsL1TJlyVH1GSLzq42r87vzQPQ2tCU9nNbH Cwmbw36OEJPXNhIAKUWUZMgsFICo4a6BP2mWCxO6M2t9aqxFVQUEqc2GgNLuistcKR/q 4oeQ== X-Gm-Message-State: AElRT7GIauUmgUFpl4gdpB95numExejsTCZ7AvgeeKXlhzfRFiLOdGfd DTmdL1a/dcGwaqcVFaOGAWg= X-Google-Smtp-Source: AG47ELuTJ6ti0E4ojUSexf6GITOLRMnclgCujQg/Pgjmh9/XE8L5widogW/R2rpZ3EuIvFPSjAvSJQ== X-Received: by 2002:a19:2744:: with SMTP id n65-v6mr9733457lfn.67.1521499054095; Mon, 19 Mar 2018 15:37:34 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id l8-v6sm64356lfb.19.2018.03.19.15.37.32 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Mar 2018 15:37:32 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Tue, 20 Mar 2018 01:34:40 +0300 To: Andreas Scherrer Cc: freebsd-net@freebsd.org Subject: Re: Multicast/SSDP not working (on VLAN interface) Message-ID: <20180320013440.009b6d6f@gmail.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 22:37:36 -0000 On Mon, 19 Mar 2018 22:29:12 +0100 Andreas Scherrer wrote: > Now, if I (manually) add a static route for 224.0.0.0/4 via the > interface the M-SEARCH messages are coming in, everything starts to > work! > > route add -net 224.0.0.0/4 -iface re1.32 > > The (main) problem here is that I have multiple networks with clients > in them. So a static route does not REALLY solve my problem. > > Also I do not (yet?) understand why the route should be required. > > What I see is that ifmcstat -f inet -i re1.32 does not list a > membership for 239.255.255.250 when it is not working, but does list > the membership when it is working... That is because many software use old dumb multicast socket api. It requres that use add route to mc net via one net iface. If no mc route present then OS will send all mc packets to default gw, using unicast gw mac addr instead of specific mc mac addr. On linux all same. Mine https://github.com/rozhuk-im/ssdpd can send and receive mc packet via many net ifaces. From owner-freebsd-net@freebsd.org Mon Mar 19 23:10:34 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9A7EF5248D for ; Mon, 19 Mar 2018 23:10:34 +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 200766B300 for ; Mon, 19 Mar 2018 23:10:33 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w2JMxokE050071 for ; Mon, 19 Mar 2018 15:59:57 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD NET" Subject: WiGig feature / support? Date: Mon, 19 Mar 2018 15:59:56 -0700 Message-Id: <334d5f2a176da62f7a0137399077b4ad@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 23:10:34 -0000 Apologies in advance, should this have gone to @wireless, or =2E=2E=2E That said; I'm performing some R&D on an efficient alternative to gigabit networking w/o cables=2E To that end; my Atheros (QCA9005) WiGig (7Gbps tri-b= and)=20 half mini-pcie card just arrived, and my target test rig (laptop) will arri= ve next week=2E So I suppose I've sort of put the cart before the horse here=2E Bu= t, any chance I can pull up this card on FreeBSD? If work still needs to be do= ne, anything you'd like to point me at? In fact, if need be, I'd be willing to = send one of these cards to someone working on this (@adrian ?)=2E :-) Anyway, if anyone can further enlighten me on WiGig on FreeBSD=2E I'd *greatl= y* appreciate it=2E :-) Thanks! --Chris From owner-freebsd-net@freebsd.org Mon Mar 19 23:11:09 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FABAF52582 for ; Mon, 19 Mar 2018 23:11:09 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 06FB96B4AE for ; Mon, 19 Mar 2018 23:11:08 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2JNB56m014040; Mon, 19 Mar 2018 16:11:05 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2JNB5lU014039; Mon, 19 Mar 2018 16:11:05 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803192311.w2JNB5lU014039@pdx.rh.CN85.dnsmgr.net> Subject: Re: Multicast/SSDP not working (on VLAN interface) In-Reply-To: To: Andreas Scherrer Date: Mon, 19 Mar 2018 16:11:05 -0700 (PDT) CC: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 23:11:09 -0000 > Dear List > > I was unfortunately unable to find a way to search this mailing list's > archive; so please bear with me if the question was answered before. google: site:freebsd.org Then what you are searching for is one way to search all of freebsd.org for what you are seeking. > > My goal is to have DLNA clients (VLC, Heos music system, ...) in > multiple networks discover a MiniDLNA server. > > The server shows up in VLC when it starts (or is restarted) after VLC is > running. If the server is already running when VLC is started, VLC does > not detect/find the server. > > Very much like this source states: > https://sourceforge.net/p/minidlna/bugs/94/#8c8f > I suspect a problem with the M-SEARCH messages the client is sending. > > Using tcpdump on the interface where M-SEARCH from VLC are coming in, I > can indeed see the packets/messages arrive (they are sent from the > client to 239.255.255.250). So it is is not a router or switch or > whatever blocking the packets. > > Now, if I (manually) add a static route for 224.0.0.0/4 via the > interface the M-SEARCH messages are coming in, everything starts to work! > > route add -net 224.0.0.0/4 -iface re1.32 > > The (main) problem here is that I have multiple networks with clients in > them. So a static route does not REALLY solve my problem. > > Also I do not (yet?) understand why the route should be required. > > What I see is that ifmcstat -f inet -i re1.32 does not list a membership > for 239.255.255.250 when it is not working, but does list the membership > when it is working... > > So I suspect that "something" is dropping the M-SEARCH packets for some > reason after they are received. And I cannot get rid of the feeling that > it has something to do with the fact that the incoming interface is a > VLAN interface... > My first guess, anti spoofing, seems not to be the problem (I am using > ipfw and "not antispoof in" but that does not seem to drop any traffic). Are you running with "firewall_type="simple""? If so it is set to block all 224/4 packets, see this part of /etc/rc.firewall: # And stop draft-manning-dsua-03.txt (1 May 2000) nets (includes RESERVED-1, # DHCP auto-configuration, NET-TEST, MULTICAST (class D), and class E) # on the outside interface ${fwcmd} table ${BAD_ADDR_TBL} add 0.0.0.0/8 ${fwcmd} table ${BAD_ADDR_TBL} add 169.254.0.0/16 ${fwcmd} table ${BAD_ADDR_TBL} add 192.0.2.0/24 ${fwcmd} table ${BAD_ADDR_TBL} add 224.0.0.0/4 ${fwcmd} table ${BAD_ADDR_TBL} add 240.0.0.0/4 ${fwcmd} add deny all from any to "table($BAD_ADDR_TBL)" via ${oif} Your route effected this as your packets are no longer trying to use an all interfaces path, but a specific interface, and that is probably not ${oif} of your firewall. > > Do I miss something obvious or can someone point me in the right direction? Probably just remove the 224.0.0.0/4 from the above table and things may start to work. > > VLC v2.2.8 is running on Mac OSX 10.12. MiniDLNA v1.2.1,1 is running on > FreeBSD RELEASE-11.1. > > More information can be found in the FreeBSD forum [1]. > > > Thanks heaps > andreas > > [1] > https://forums.freebsd.org/threads/minidlna-not-discovered-multicast-issue.64947/ > _______________________________________________ > 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" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Mon Mar 19 23:30:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EEF1F53A06 for ; Mon, 19 Mar 2018 23:30:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::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 B26596BFF2 for ; Mon, 19 Mar 2018 23:30:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x22c.google.com with SMTP id s18so20270679wrg.9 for ; Mon, 19 Mar 2018 16:30:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SHIPAwoU9BE6c4i2cIDLc5KkAnyw2Vzs5DAPabG26f0=; b=Bu9sGRDVjkCuESF+xUW7JEF4PFN2C2cpN+Jmw5DJIKroJ4I3Qw26mjs1W4rh2vsPUE 2gzG6iYQYQRCz0j+foYc/VtFyVECjCEOxdLTAmH3pKDEYHJLNjNs0t4XaDLjt9Pydsf0 0VIUHRi5rznO2k3S03PD5GQGkilCyKtohY47YWsMi0NVnjrLpxu278Mq0sw0bugZIzEb YFlICXVyXT+3rRn1bMINUX3b0rYfGD3KfavvPit6eiAkmbHzcPRbi70Y+iFuBgoaCBpQ VQ6Z5RbpG58nK5eIzAQq3S9dSeXYRvhAoe4bDzEy4wDF5pPf1JMEGCt1c6HeCMmN5zAM hHNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SHIPAwoU9BE6c4i2cIDLc5KkAnyw2Vzs5DAPabG26f0=; b=X/dCNoeFTGlVbHwssCaPTUPTQySJWw09r0esim8u0weIncOfTCodE2wwrq/X7mD0Fj KjjS3Y0eeRjEZ2tl3aw681HxPpMt9Tjak6oZYPspBTkR0wHWtnNcUlgOCiTFnxjfeMZh uVe9JkFRNOhklDXbZ0yaiGbZ78aVcltSVl1bZ4jBO13hbWjbq8bLkuVq9UN+cSkB+bir G0YIVv5JWqpUiGpbHM/HFPp/7of7ekpyxZKYHhAmy3PbgU8y9awMDXba7CLCiqHf73+M VdGgRQ+KP6vhPCFqOZwWJZU+44HLpFFhhY+YhYwg5L9WrDQdVwD6un7dRY8+iV5DhZ/k zH0g== X-Gm-Message-State: AElRT7E/XzEQAsF4f/VAMvn8egvnKMteU5dkeP1C3UrpngBURnCwF6Lr T3D2+2I58Ni3UE0oTpV9TEdVUE+IpEo/jUVzexA9aQ== X-Google-Smtp-Source: AG47ELsnqQSLnwTWQcZOi3jAgWqwY0+uK8diXoqd2lcF6lQnBSnGMFRqIDr38++SMADgmzYl8bWi4uba+i44bHA3e2A= X-Received: by 10.223.192.3 with SMTP id z3mr3457776wre.177.1521502201573; Mon, 19 Mar 2018 16:30:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.4.12 with HTTP; Mon, 19 Mar 2018 16:30:00 -0700 (PDT) In-Reply-To: <334d5f2a176da62f7a0137399077b4ad@udns.ultimatedns.net> References: <334d5f2a176da62f7a0137399077b4ad@udns.ultimatedns.net> From: Adrian Chadd Date: Mon, 19 Mar 2018 16:30:00 -0700 Message-ID: Subject: Re: WiGig feature / support? To: Chris H Cc: FreeBSD NET Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Mar 2018 23:30:03 -0000 hi! There's a lot of work to do for this card. The challenge is it's a completely different thing that our stack needs to understand /and/ it also kinda pretends to be a PCIe end point too. I'd start by looking at what the linux stack/driver does for 11ad. We'd at least have to add 60GHz channel support. I don't know what else is required for 11ad as I haven't really looked in a few years. -adrian From owner-freebsd-net@freebsd.org Tue Mar 20 00:18:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A00CAF56FE6 for ; Tue, 20 Mar 2018 00:18:01 +0000 (UTC) (envelope-from rozhuk.im@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 0BA846DD85 for ; Tue, 20 Mar 2018 00:18:01 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id a22-v6so28101492lfg.9 for ; Mon, 19 Mar 2018 17:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=KyEK3INFNUKU8qEL8XxVbXnL5MG0YxR9PPYns4+LMFc=; b=L+sIS0NCUuZzhRmr7doduA84NKxeVGSpsUsYUVcn/2K22EJbZG7kDo6myqdGQEJQIC nDB/w2DLDX2447oddXsbqvj9iQrGqQRnuhueYwQi5KVjlNI7MtkKDmV1R0dke1uCmXYV R/MKw9rZADE/92lFaB/LHbQsghIty1Cd9JRD9mW4rKQedZhYjX4PDo1KPnO9KdPmiopr dBKYCZNmun+sFHKXOPnYYh5lZ686XgsOs6+rN3AOmJ6rFxSKWBedbAtM38d7CZXhiOK1 eal0cP+hydOCyesxXIbpXGHbi0PLctCgLhXdPeuIQhWRi+ZwLgQk9wGy+iWutCF/ro1H veAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=KyEK3INFNUKU8qEL8XxVbXnL5MG0YxR9PPYns4+LMFc=; b=DHqvZu338LfCkMzard54ceNhfTgUPEIbBTmV2MNlmsXTtehBJsvtevTXtwQ7TCZ7BZ 8+Bo+8y7I4uu4TpCJEnt+HJYkcEAZAFEC98JLaWR72V9jDBu8k7zsjt+VU6GnhO1sEUw +IbwdPwi5EqsdzEGxqZfBCq2rwxTbYF3Wd0OTZVCq7NJJVxW90E2N7yvb2Y17crg5PZi thAqSwhYXzr3wlkoh9GQ59RGtVolCm3gBX/FHO3ZiNv1MCPTN7aOTXJxObr3P1bXDnAl WH0X45e6DEH2e9zFtPT/Yj8aWrVZ6gDyf7ipeW0fwUxlLBFndQkk+gBhMkCZOlIOBgA3 Sk1w== X-Gm-Message-State: AElRT7F+plEFNIVf7R8hEK8HtR0ANAGC64MuaInbWF5Vv3IojWIAtsCp lupu72N6h3eEcyZGaRnj9CRRiA== X-Google-Smtp-Source: AG47ELs85IeIW8di+ESvBaOx28prQM4RHqgXBTohlkdtl2rUguXSXL23L3hz3e2tJv1o84P2vVe9uA== X-Received: by 10.46.134.146 with SMTP id l18mr546285lji.4.1521505079428; Mon, 19 Mar 2018 17:17:59 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:2475:413f:d27b:c44c]) by smtp.gmail.com with ESMTPSA id q29sm78691ljc.78.2018.03.19.17.17.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Mar 2018 17:17:58 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Tue, 20 Mar 2018 03:15:06 +0300 To: "Rodney W. Grimes" Cc: Andreas Scherrer , freebsd-net@freebsd.org Subject: Re: Multicast/SSDP not working (on VLAN interface) Message-ID: <20180320031506.10b5cd89@gmail.com> In-Reply-To: <201803192311.w2JNB5lU014039@pdx.rh.CN85.dnsmgr.net> References: <201803192311.w2JNB5lU014039@pdx.rh.CN85.dnsmgr.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 00:18:01 -0000 On Mon, 19 Mar 2018 16:11:05 -0700 (PDT) "Rodney W. Grimes" wrote: > Are you running with "firewall_type="simple""? > If so it is set to block all 224/4 packets, see this part > of /etc/rc.firewall: > # And stop draft-manning-dsua-03.txt (1 May 2000) nets > (includes RESERVED-1, # DHCP auto-configuration, NET-TEST, MULTICAST > (class D), and class E) # on the outside interface > ${fwcmd} table ${BAD_ADDR_TBL} add 0.0.0.0/8 > ${fwcmd} table ${BAD_ADDR_TBL} add 169.254.0.0/16 > ${fwcmd} table ${BAD_ADDR_TBL} add 192.0.2.0/24 > ${fwcmd} table ${BAD_ADDR_TBL} add 224.0.0.0/4 > ${fwcmd} table ${BAD_ADDR_TBL} add 240.0.0.0/4 > > ${fwcmd} add deny all from any to "table($BAD_ADDR_TBL)" via > ${oif} > > Your route effected this as your packets are no longer trying to > use an all interfaces path, but a specific interface, and that is > probably not ${oif} of your firewall. > One more fw tip: pf by default drops all IP packets with options, so IGMP does not work. From owner-freebsd-net@freebsd.org Tue Mar 20 00:23:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4DABF576A3 for ; Tue, 20 Mar 2018 00:23:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 428C56E21A for ; Tue, 20 Mar 2018 00:23: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 81C092A21 for ; Tue, 20 Mar 2018 00:23:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2K0NPBP088129 for ; Tue, 20 Mar 2018 00:23:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2K0NPRr088128 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 00:23:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218579] Wake on Lan doesn't work for bge NIC driver Date: Tue, 20 Mar 2018 00:23:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cy@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: bug_status 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.25 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, 20 Mar 2018 00:23:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 Cy Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --- Comment #7 from Cy Schubert --- The patch attached to this PR also works with stable/11 and releng/11.1. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 00:56:24 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F411F59B99 for ; Tue, 20 Mar 2018 00:56:24 +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 0B2E66FA70 for ; Tue, 20 Mar 2018 00:56:23 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w2K0ud1X067749; Mon, 19 Mar 2018 17:56:46 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD NET" In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Adrian Chadd" Subject: Re: WiGig feature / support? Date: Mon, 19 Mar 2018 17:56:45 -0700 Message-Id: <52b95c9fa1e9ebe028e98c5999cf7df8@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 00:56:24 -0000 On Mon, 19 Mar 2018 16:30:00 -0700 "Adrian Chadd" = said > hi! Hi! Thanks for the quick reply, Adrian! >=20 > There's a lot of work to do for this card=2E The challenge is it's a > completely different thing that our stack needs to understand /and/ it > also kinda pretends to be a PCIe end point too=2E Ah, OK=2E I was afraid I might find it wasn't supported=2E >=20 > I'd start by looking at what the linux stack/driver does for 11ad=2E > We'd at least have to add 60GHz channel support=2E I don't know what > else is required for 11ad as I haven't really looked in a few years=2E OK=2E I'll have a look and see what I can come up with=2E I'll poke you when I can come up with anything worth while=2E BTW I meant what I said about sending you one of these cards=2E Lemme know if you're interested=2E Thanks again! --Chris >=20 >=20 >=20 > -adrian From owner-freebsd-net@freebsd.org Tue Mar 20 03:23:42 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 655ABF6A548 for ; Tue, 20 Mar 2018 03:23:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E78579B04 for ; Tue, 20 Mar 2018 03:23:41 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D003447DC for ; Tue, 20 Mar 2018 03:23:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2K3Netw054390 for ; Tue, 20 Mar 2018 03:23:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2K3Nelh054389 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 03:23:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218579] Wake on Lan doesn't work for bge NIC driver Date: Tue, 20 Mar 2018 03:23:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: see_also 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.25 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, 20 Mar 2018 03:23:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D1= 717 | |44 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 03:23:43 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F9E6F6A55B for ; Tue, 20 Mar 2018 03:23:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 38A9579B15 for ; Tue, 20 Mar 2018 03:23:43 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 508F747E3 for ; Tue, 20 Mar 2018 03:23:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2K3NgF8054424 for ; Tue, 20 Mar 2018 03:23:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2K3NgoG054423 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 03:23:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 171744] [PATCH] Fix wake(8) command not sending proper WOL packet Date: Tue, 20 Mar 2018 03:23:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also 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.25 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, 20 Mar 2018 03:23:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D171744 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 185 | |79 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 05:06:14 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED555F51CC6 for ; Tue, 20 Mar 2018 05:06:13 +0000 (UTC) (envelope-from iec05@edusenda.top) Received: from out29-143.mail.aliyun.com (out29-143.mail.aliyun.com [115.124.29.143]) (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 2C4B97F0BA for ; Tue, 20 Mar 2018 05:06:12 +0000 (UTC) (envelope-from iec05@edusenda.top) X-Alimail-AntiSpam: AC=CONTINUE; BC=0.3945327|-1; CH=blue; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03308; MF=iec05@edusenda.top; NM=1; PH=DS; RN=1; RT=1; SR=0; TI=SMTPD_---.BNDzEl3_1521522364; Received: from Redins-PC(mailfrom:iec05@edusenda.top fp:123.146.50.244) by smtp.aliyun-inc.com(10.147.41.231); Tue, 20 Mar 2018 13:06:04 +0800 Message-ID: <20180320130604626.iec05@edusenda.top> MIME-Version: 1.0 From: "Reed" To: "Freebsd-net" Reply-To: iec05@globalsenda.com Date: 20 Mar 2018 13:06:05 +0800 Subject: Newest design digital signage Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 05:06:14 -0000 Dear ,=0D=0AWe are so glad to hear that you are also in the field= of presentation equipment.=0D=0AThis is Redins from Hongbao whic= h is focused on Interactive Displaying Equipment. We have differe= nt Interactive Touch Screen, Digital Signage, etc.=0D=0AIf you ha= ve more question, we would like to give you more information abou= t our products.=0D=0AThank you for your time.--------------------= --------Best regards, Mr. ReedSales Manager Chongqing Hongbao Tec= hnology Co., Ltd.Address: Building 9, Area C, Jinglong Industrial= Park, Jiulongpo District, Chongqing, China=0D=0ASKYPE: iec05_1Of= fice: 0086 23 8867 0519Whatsapp: +86 17784283905=0D=0AContact of = General Manager,Mr.Alan TanSKYPE: sendaindustryWhatsapp/Cellphone= : +86 18008300007=0A=0A91Q6zf9ZNgNixxFRU0uLkcWYyWQs4cr11ytFqAGyff= qxjFCbOiyBW0xW5RxDoGUAOLhY4ZqjkVw5MoETkFEMEQ501xAz23aykPJxoD7PSfh= 0tsaGcEjJ28WYGgXxoQggLXKXF6uHxPTpy5xzmTmoKqwcSKR8FAq1Y0fvHd16aBcd= expBIoavuSwlry4Vem1XoSqyP1R9Sge8djXlkgphpVx6uU4886ROAfOm6RLHw1CdE= n78BJAYWKxtkk4VXJ0MpqyYuBetvHKoijs6NWxpvTRPHl1MNQKN1QOeP8D0u7se09= a0SX80bAgvyIh9zsFEXWmsvegFjxVoqCPya0UPIJCqziF7Qtq1rNh3MHvDHsHEES5= VTIYyyQWdkWScy9OP6UWClLMtug8f2XMHcJe8vRsBR3IPPj5xESxKVtz7Wv3iHHbm= 9aZOVGkfrlLi3WDbbAAaq1MJa6bZNaT9RlGEjgCYxijzIh4ZRR7771W8ogEOukrgs= BqHgYSUXCC8Hd1S2c7V3L2Qpxg2BOudQ276QmJSZc9uoNqbfMLhcvdGzzhIIPj98p= hF5U1FteWQBxrC65NP3c0lPqxh50a9S0mZvL5kK5OXym417ECC1u5VoWPFnKAt4NY= Aas7l0t4Xn2Mslv9roy7oUqAzVqXZvlTLotRFxgCyp8yl9njSB94vFzFJRypAw5r1= 913REtT7WyYMSfpy64nmgn5OO7OZQ12jGwc8jre8fXz6ATRC8RtrI5KLVe3wFTgUw= E5l2heFQf6jOYdUgbQZyBBBMrc4nHslGEAWOvARCNAsYrWW08ft2gmV3tzA4ai9ML= C9oh6LBZnK09Dkvg3esYiqiFSkWZMsvrFdONyI2uS3TBUUQe5O63GOscQIpMPBcUe= ztqvIHkcX6fwHLYuHUYmsKRLCWPjgFgQZmkqpIm6LQJHcF9Xqh7GeyMPBFTLS1WhP= pxkrx4YxRBB09yWMRTYxABrzvPKPBdKUrSN8OwSd88mWbOr6WZ17YJfN6KWIk9WDR= GzhKNXl1KprfuoGnDSBcCWHD023A9TZcI5ufam91F6dkNxCmfkGgkreKREKKUKRRp= fwoUrdhJAwwJmPsqHkPcIRhRKnvBo7VelVy1drO7pxKUI1vOhkcp2FGoexa3HFltB= hnrhqcfwINb6n8ISGk3VvcGeaNGhKpJchiqD3xQ7WTkSvhQorb0lhy55Hc7DwYMi3= YP4I4O9tWYCSOISWiQzonVIdlWQqdBY61OxsMGmmRSlztdTueGe7cUF36Rm8YIfl0= vQZbq9BtdwvA9J83mbwmQU68tlVjeo8CZzXmTiOwCEZoatX7e5BxIYaBKRH4eifOn= TAAML94n0KbUIX0oO49MBT1pmC1AKijpa0hTnlsVx9IdYG1THGqd51LZyap97tCHq= MJIG71sCdfraOqFA8T4R5j9ehkcViN3x1McXjcAFXBRLkOKKKzZAyQlsAuoMOxjqc= U91eHhVipTurnUtAsaJOtYbrJnOOOQqirzpFIv2i4i9WQ0cAVcmnACJWYAvks7uyt= c0NuORX7qJbOeAJaeSCt3HOQtG80IPWNAsEZp57kpf9Sy7JZLadeS4qubX17JWpAN= neMWJL9Lh4NyWimW9eyCIVv1aOs4ZBsQy5aSX32o4tA0CWfEFbzIRY4rIKLVj5MFC= XZR7tZ5c9xekvpdzNoO1KYA0Jach65ZHUnEXnwcbuwHqP6clymvGXESYoQoiMO53y= xp8KgbgcCxeg9aCXRJKzjJgvFyx7ToGqERiH4Ahbetl7EHfGMkV4kufO9C4ID9idQ= NCiSUTgszkPo9QXjQkytB69Ctxrwyx5a7gR5WNRrECK9qq0L6pMOJJfHsFonsKT2f= EgSZSm2t7PYl0c3xFq9Khqn19ChpuZUJITL97Md3JlCUglstlPMkKiXdTRPg4DY8V= fD6qUqTc50WOtKO9N3FcAYqWxffWWY6mtY0Il2rpS7Eh1pq717gzjVlgcaTEaXg6U= zkuJ5OLCfjsk8V8P8UPHw3xDKva9MeVRxnr4WnVivX3CSW3fKP23qpowNQZzDCP1o= BMLt4SKYwcyZVKNsVoXbSq8ZVh5omET72dhaiMGWi4UdPwR5b7IdRPvbDMyNNlCRi= qXItC99I1TNwVaop0ceWFfcH6wwdS9Ws2Uoy9CyXzuQWIEIC9nN9nVDbK0n6DVPSW= lu0LQgnDgmapgZrOT4vmN46hdN8esjEFY0maIQj6pw7ysLu0VhJQkw9hnJy289aWI= vqfCg63LpWgXxPrj7iazNksQ5NYhhXflaQWkeoFbG5VzSkPU6J0QZnVbYpxt7LurH= VMHS64JDZTIpTYLX4axXplNVLlPQb4UAtRXx81ZEhd0tcL5rMv2BWuizZM7LeSrUZ= 7V10dP3aTFbljIZgo4G1jEZznylTeqoL5u5P4qyGZq3O6eF48uPNLTFsWrDFu9Vsh= qfPD9bYwZ2TBbt9ShLKABZcOCTDMScPuAwFYQrYiRgLRMRKXtNcobRGq300gybENc= o0ENa2QMrJkek2K9Fj5ZqiJQfUPqIJFCXEnR59iKmBK7mcJYf6TSyOM5gOygdp4H3= HgGES3w0kDOyBu2bQaBQN49ShAhA2xWx24EW2km3nSdaXxFjv4mftQgC6NmiMVXNH= hwxP68vNytVQZVKVX4YaG3bN1PfY4grUqtF08tpVQrVnlM7SBmOQZC0dkJOgTxIh1= 0qwfJNtF2ke8OrfImmIsBVNssGoF82jJDllmBDRzkaXiL4whyywb0Pq5C3M3pOxZ1= vut6T7Ju97qYvGn966zv8IOUgKxQO9wDXhgA2bFrMGQH076npTiHXuTMFyQ9zSGZA= N0eqN7Vr8IrS6U8D9rURPFsntUukwRTZR7c6RXBMnfPLrUzEHvprL8K7xQXTCAUgO= s0ZH2LcP8tzQHWylPD1rsdIm5y1ZI9NkyWZUzWEJdBDFbgQTpyNXTPmeiCBuKd7YF= ehLXELTYheQA3bOI7A9mQrJzKBXkaZZtFZWY4WLMUYCAvEerNMDCXCPNybc2OyOie= nV4fPDaPmsRO846nwxolnv298qTJIYmajl8JabX8sMBaXZp76Ei0pWRRSU7pKr6o6= HuNVndkAfTAUSb90LD4GlKmuhQf4xo1Gc4guCbIrXpa3gW0JYoYN2HKW8iEwYf3RR= UHOVEozUCJWAjekQw69pdDvjkmkxbtHmjblebNj0pSqYNmO3jGs9TrEhcuBi32J91= Ag7S6EIN80kdxwXxgev0ysRx42Gc0Wm9gXd5Hbc1JmLrj3EYDLNOd8s7pAN4YvMcD= aWAiSQ41thbHpd1nIze8yW7u5G7o83ezyO864GLVIMJRhqZmMHfWx34eP6ccIGTq3= C8B4Ui2OjqLcgcEGKBqNh1vKUhYtyc1TjOEiohRpd7eCi2yTyvY4sCLACRaCjzf7o= STsxlitK1AaNSrSI5U3eXrG34Gw7e5ES6eq96lccukq2BMKpiUeEbTrrcotFLmvWW= hGE1JCKIRJC0EsiW7PkRZGdNYWHRwq8Pu6j55nzhuVk9OryWbJEwa5WAtQ2MUSbqA= Mvx8cQKg3m4m3YxoKGNMBFp9ICfkMnBJUz1V0OZTTg7ISepSvo9boDY75npzBptFL= kruWBnWHTTlyHhucmPndplgAUQCppiuNrWyMVWT1duvKDzo6UneA5slZaT2LKxiBo= y6KJIhqWm0VPwXkswu13THZBzB1U7gGcTl5sDmc5OEIrq9EWHje2gxuQ79a6gwO6k= JWbRRO9hVffYxapX4cN2DVlQeluc6PiPC7Hct5Pu4LkieSAYK9bj13GNAkDwkXb6X= qlptdtZniXSA3BmKvrWEYOyrTC9sia6zekOwauxFcVI5OcwIgLPwesYCMYzAkx48R= imINPA0Uhr35sCH5qbwlAlMmbJcVWkFQzevPOUrbOBW0VwjlSvUlyNgXAmC5n5XXM= cwd7RhwJkxZoLqFpQ2rqjiMYxfsimOIEZdJ06d0eoCdghzOVXFw2wwtTJfzCOdnwO= loyHEjC2c2G5wHYrxlGhF7sKPgQEopafGrWagdilT0juMOdxBahSGf8dWNSotYDNR= rp4LOaj2lnFNXX13i3d7hyqj From owner-freebsd-net@freebsd.org Tue Mar 20 06:44:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B125AF56FA3 for ; Tue, 20 Mar 2018 06:44:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C49C828EC for ; Tue, 20 Mar 2018 06:44:03 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 976916378 for ; Tue, 20 Mar 2018 06:44:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2K6i2UR082060 for ; Tue, 20 Mar 2018 06:44:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2K6i27Z082058 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 06:44:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 226763] Wake on lan (WOL_MAGIC) stopped working with re nic Date: Tue, 20 Mar 2018 06:44: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: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org 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: keywords assigned_to 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.25 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, 20 Mar 2018 06:44:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226763 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 08:21:28 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFFB2F5D16B for ; Tue, 20 Mar 2018 08:21:27 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 75A90868F5 for ; Tue, 20 Mar 2018 08:21:27 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-qk0-x234.google.com with SMTP id s9so705455qke.12 for ; Tue, 20 Mar 2018 01:21:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RPppaJkBVdVALYPw6cnnRszWdZG9mt4Zs/p/IFanXDo=; b=GQ3Y8SjcrY0AdCWnJ0vjKEt9XOxbdOHqaxNQ7cCZgpda1LXIq02h/jZ4N1w1pNQktj nCunx6CXEKv/MYlUVn2ORTtrFIRKQYxcy4ZJUdBsjwPxolDiMW+UhJJ4HgcmRyl8TJl5 m405I8aYQg3ZwfkkTVBOGfWb+2xC5BqtzlsxwnMUJXGvTGXgEFtVLbIkeaXFcy2x2NlI lzCTFfwSV0zDNFNAntf7cbWtysx+s7juCmMaEfLLCbo9X9BBjIgrnCmq8ZXo7ZZmp9yG PFfx1QSONf62aoEvWgPkK1OgSIuzHd4WmqCAsaX2z0pkWx7TY9YA1x9gANbUkM0nD/E0 nYFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RPppaJkBVdVALYPw6cnnRszWdZG9mt4Zs/p/IFanXDo=; b=BKoU8S/P7OzDXsREu1mrjejXkhJ74oU0sK6MbbPbUFTusYH22n1X8NbPvj+hKqbM2f y5B2iUnQ9QRvUa59KvBxZneKmvKzfSVOvYHxZ7+pWiZ2ioiIuCPavBgafMbsQUTNpYz1 lyU+P4NkPo6YfGfD8oUI4E+B+dFd647WtvarKQUmdnl9gEDbePOkElHDlHaPuvoFg6yS k/LrzNMhxkFTATjwI5zKubhjBeRFj3J30cMe7lQUrEyymXtrlCRu/8lbLGjhGYew4w7A fYYHyvhPm2y49no1Kf+kjfx0n7PpGwP6ZZi5pAF+mxhOV7A3doQcK/cSVfLYICEzxmqU cGeQ== X-Gm-Message-State: AElRT7GKUsCzXxNMP+rDhLzq8YhBjrb282Lv5sOLDwKe+/5kzwMklF4z 5Q36hFh30KWHHL6nzKB3bI3rNAMLOp29m9pax6g= X-Google-Smtp-Source: AG47ELv9gn6XCtSyMxfZU+8kU1pl4EcTrAdihT0YwOzwVXqRbPeZrvu+abqM/2rfbRKvKwUaFx8aR3UdJxv+B2G76xo= X-Received: by 10.233.235.2 with SMTP id b2mr22662205qkg.27.1521534086843; Tue, 20 Mar 2018 01:21:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.195.204 with HTTP; Tue, 20 Mar 2018 01:21:26 -0700 (PDT) In-Reply-To: <5AB01439.3090003@cox.net> References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> From: Vincenzo Maffione Date: Tue, 20 Mar 2018 09:21:26 +0100 Message-ID: Subject: Re: netmap ixgbevf mtu To: Joe Buehler Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 08:21:28 -0000 2018-03-19 20:49 GMT+01:00 Joe Buehler : > Vincenzo Maffione wrote: > > > To receive a frame larger than the RX buffer size you need multiple > > netmap slots (as multiple descriptors are > > used by the hardware), looking at the NS_MOREFRAG flag. > > See the example code in utils/functional.c::rx_one(). > > This works fine -- thanks. > > > Also TX may have per-slot limitations (e.g. due to the size of the NIC > > TX fifo), but this is usually > 9K, so using a single descriptor per > > packet should always > > be ok. However, you can also use multiple slots on the TX side (see > > utils/functional.c::tx_one()). > > Trying to split TX frames into multiple buffers does not work, the NIC is > sending 2048 byte frames (the buf_size I am using). > > I will re-check my code. Do I need a particular version of ixgbevf > perhaps? > > I don't think so, but you need to use the latest netmap from github. The NS_MOREFRAG support for ixgbe/ixgbevf is here https://github.com/luigirizzo/netmap/blob/master/LINUX/ixgbe_netmap_linux.h#L344-L345 The problem is that nobody really tried to use NS_MOREFRAG on ixgbevf transmission so far. So there may be a bug on how we set the flags in the hardware descriptor. We should look at what the driver does. Here https://elixir.bootlin.com/linux/v3.8/source/drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c#L2903 I see that the olinfo_status field is set with the total frame length (and not just the fragment length). In the netmap code we set to the fragment length, so that's probably why you see that behaviour. Here https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf in sec. 7.2.3.2.4 I read that we need to properly set the olinfo_status field on the firsts TX descriptor, while the others are irrelevant. Cheers, Vincenzo > Joe Buehler > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Tue Mar 20 11:19:11 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F2DEF6910D for ; Tue, 20 Mar 2018 11:19:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E48E6DD23 for ; Tue, 20 Mar 2018 11:19:11 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 28B39108D5 for ; Tue, 20 Mar 2018 11:19:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2KBJA3k094882 for ; Tue, 20 Mar 2018 11:19:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2KBJAVJ094881 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 11:19:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218579] Wake on Lan doesn't work for bge NIC driver Date: Tue, 20 Mar 2018 11:19:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: see_also 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.25 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, 20 Mar 2018 11:19:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 267 | |63 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 11:19:10 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D37E8F69101 for ; Tue, 20 Mar 2018 11:19:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A03C6DD1E for ; Tue, 20 Mar 2018 11:19:10 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5C673108D2 for ; Tue, 20 Mar 2018 11:19:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2KBJ9M6094869 for ; Tue, 20 Mar 2018 11:19:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2KBJ9PV094868 for freebsd-net@FreeBSD.org; Tue, 20 Mar 2018 11:19:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 226763] Wake on lan (WOL_MAGIC) stopped working with re nic Date: Tue, 20 Mar 2018 11:19:09 +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: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org 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: see_also 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.25 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, 20 Mar 2018 11:19:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226763 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 185 | |79 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 20 18:42:46 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14EF6F64B63 for ; Tue, 20 Mar 2018 18:42:46 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmfepo201.cox.net (eastrmfepo201.cox.net [68.230.241.216]) by mx1.freebsd.org (Postfix) with ESMTP id AC99E81840 for ; Tue, 20 Mar 2018 18:42:45 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo210.cox.net ([68.230.241.225]) by eastrmfepo201.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20180320184239.VBTG1466.eastrmfepo201.cox.net@eastrmimpo210.cox.net> for ; Tue, 20 Mar 2018 14:42:39 -0400 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo210.cox.net with cox id QJif1x0081LxgH801JifpX; Tue, 20 Mar 2018 14:42:39 -0400 X-Authority-Analysis: v=2.2 cv=fefd8wYF c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=v2DPQv5-lfwA:10 a=e9ASbk4n0QUA:10 a=NEAV23lmAAAA:8 a=P-IC7800AAAA:8 a=QyXUC8HyAAAA:8 a=iFnR9IgGT0Xcdpwh32IA:9 a=BXztF5QcbhpWnWO5:21 a=ZFuU1ysdDbrGSKE0:21 a=QEXdDO2ut3YA:10 a=d3PnA9EDa4IxuAV0gXij:22 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (LOGIN) smtp.auth=jbuehler@cox.net Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id E5CCD1152A; Tue, 20 Mar 2018 14:42:38 -0400 (EDT) Message-ID: <5AB1561D.7010608@cox.net> Date: Tue, 20 Mar 2018 14:42:37 -0400 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" Subject: Re: netmap ixgbevf mtu References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 18:42:46 -0000 If you could fix this I would appreciate it. My L1 TX performance for 64 byte L2 frames drops significantly, from about 9 gigbits to 7 gigabits, when I use buffers large enough to hold jumbo frames. I will play with it a bit locally. One thing that occurs to me is to pass the full frame length when NS_MOREFRAG is set and have the driver assume that the buffer is full if that length is more than the buffer length. That way netmap knows both the total length and the fragment length. Very ugly but... Joe Buehler > I don't think so, but you need to use the latest netmap from github. > The NS_MOREFRAG support for ixgbe/ixgbevf is here > https://github.com/luigirizzo/netmap/blob/master/LINUX/ixgbe_netmap_linux.h#L344-L345 > > The problem is that nobody really tried to use NS_MOREFRAG on ixgbevf > transmission so far. > So there may be a bug on how we set the flags in the hardware descriptor. > We should look at what the driver does. Here > https://elixir.bootlin.com/linux/v3.8/source/drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c#L2903 > I see that the olinfo_status field is set with the total frame length > (and not just the fragment length). > In the netmap code we set to the fragment length, so that's probably why > you see that behaviour. > Here > https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf > in sec. 7.2.3.2.4 I read that we need to properly set the olinfo_status > field on the firsts TX descriptor, while the others are irrelevant. > > Cheers, > Vincenzo > > > > > > Joe Buehler > > > > > -- > Vincenzo Maffione From owner-freebsd-net@freebsd.org Tue Mar 20 19:54:14 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E48CF69390 for ; Tue, 20 Mar 2018 19:54:14 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id 96E5B841BC for ; Tue, 20 Mar 2018 19:54:13 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo209.cox.net ([68.230.241.224]) by eastrmfepo102.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20180320195407.YLVZ24661.eastrmfepo102.cox.net@eastrmimpo209.cox.net> for ; Tue, 20 Mar 2018 15:54:07 -0400 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo209.cox.net with cox id QKu61x00W1LxgH801Ku7PR; Tue, 20 Mar 2018 15:54:07 -0400 X-Authority-Analysis: v=2.2 cv=JbLMlQCV c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=x7bEGLp0ZPQA:10 a=v2DPQv5-lfwA:10 a=e9ASbk4n0QUA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=a2fyScrFYJEhPD73AkgA:9 a=74FAferboko-xCEp:21 a=8UeKvEBbmdWUWlPf:21 a=QEXdDO2ut3YA:10 a=zE9a5rZaH-iPzQhwlkkA:9 a=CdiWusdWvyIA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (LOGIN) smtp.auth=jbuehler@cox.net Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id 78F701152A; Tue, 20 Mar 2018 15:54:06 -0400 (EDT) Message-ID: <5AB166DC.8060708@cox.net> Date: Tue, 20 Mar 2018 15:54:04 -0400 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" Subject: Re: netmap ixgbevf mtu References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> In-Reply-To: Content-Type: multipart/mixed; boundary="------------070501060205030509030002" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 19:54:14 -0000 This is a multi-part message in MIME format. --------------070501060205030509030002 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Attached is a patch that allows fragmented TX with the ixgbevf driver. For the first TX buffer set the slot length to the full length of the frame and make sure that the slot buffer is fully filled. For succeeding slots just set the length to the amount of the buffer filled. Not intended as the perfect solution but it works fine for my situation. Joe Buehler --------------070501060205030509030002 Content-Type: text/x-patch; name="fragmented-tx.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="fragmented-tx.patch" --- LINUX/ixgbe_netmap_linux.h.~1~ 2018-03-19 12:36:09.000000001 -0400 +++ LINUX/ixgbe_netmap_linux.h 2018-03-20 14:54:47.000000001 -0400 @@ -329,7 +329,8 @@ nic_i = netmap_idx_k2n(kring, nm_i); for (n = 0; nm_i != head; n++) { struct netmap_slot *slot = &ring->slot[nm_i]; - u_int len = slot->len; + u_int full_len = slot->len; + u_int len = full_len > ring->nr_buf_size ? ring->nr_buf_size : full_len; uint64_t paddr; void *addr = PNMB(na, slot, &paddr); @@ -347,8 +348,8 @@ /* Fill the slot in the NIC ring. */ curr->read.buffer_addr = htole64(paddr); - curr->read.olinfo_status = htole32(len << IXGBE_ADVTXD_PAYLEN_SHIFT); - curr->read.cmd_type_len = htole32(len | hw_flags | + curr->read.olinfo_status = htole32(full_len << IXGBE_ADVTXD_PAYLEN_SHIFT); + curr->read.cmd_type_len = htole32(len | hw_flags | IXGBE_ADVTXD_DTYP_DATA | IXGBE_ADVTXD_DCMD_DEXT | IXGBE_ADVTXD_DCMD_IFCS); netmap_sync_map(na, (bus_dma_tag_t) na->pdev, &paddr, len, NR_TX); --------------070501060205030509030002-- From owner-freebsd-net@freebsd.org Tue Mar 20 20:09:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7E75F6A2B2 for ; Tue, 20 Mar 2018 20:09:01 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 67EAE84A7A for ; Tue, 20 Mar 2018 20:09:01 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 98F933AEF2 for ; Tue, 20 Mar 2018 13:09:00 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org Subject: Raw Sockets: Two Questions Date: Tue, 20 Mar 2018 13:09:00 -0700 Message-ID: <98551.1521576540@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 20:09:02 -0000 I'm going to be doing some stuff with raw sockets pretty soon, and while scrounging around, looking for some nice coding examples, I found the following very curious comment on one particular message board: https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems "Using raw sockets isn't hard but it's not entirely portable. For instance, both in BSD and in Linux you can send whatever you want, but in BSD you can't receive anything that has a handler (like TCP and UDP)." So, first question: Is the above comment actually true & accurate? Second question: If the above assertion is actually true, then how can nmap manage to work so well on FreeBSD, despite what would appear to be this insurmountable stumbling block (of not being able to receive replies)? From owner-freebsd-net@freebsd.org Tue Mar 20 22:08:17 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9E0DF4F055 for ; Tue, 20 Mar 2018 22:08:17 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 368F76ADA9 for ; Tue, 20 Mar 2018 22:08:17 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id h76so6320546wme.4 for ; Tue, 20 Mar 2018 15:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=1DtpjNJRis2lobKtCFuDtWGti4HPKQoDrfyoJjZVhMc=; b=msFzv4RpVe6sNxxukYPjxAd7QiApnPArRde/6tFqvKpniAiXfj/jtwsa5gwG/WwuCO +9qQ4Nnye2VXYqbH13NuRQYQO75XZmdRvOSgjmGdrwvk7DEJaACJVJeItdiSnkpS5irU 83zshg2cvzQe49GN/dmuuQidlLxD/opGEPJtyF4r8Tbbk84pps/xe0eIn38DYKK+LUPc UFV2SvNXRPu83SlUxZx36DkH6yz7cY+Zu+hCkRyMRiF0h9SMC1021cIPQR2f4xmtX7us d127T76sBRgY1suMms7aBzaaCZv54MJEmCDUKhVUYAiDK0xfoR6ajkzPqlj1A+jp5xAV PBAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1DtpjNJRis2lobKtCFuDtWGti4HPKQoDrfyoJjZVhMc=; b=avxNTOxGa95XKORP1pOGk6m7g3V8ZKWuU8QheipzAVXpbnUwnKrtFniXwTsUzljlum FbFSG++wY2W3UEOnvcggUTPr6owhw8BwaZheWHWbSK2xx+oH9Ov7HFj8jVHChDXDNQCv ct2E4hxpkxo59c73EYxEszTt7TQ4yFL0V2d1ReQa2eKz3T4rr3/bOc/twY37rWFXEU4H l2GttywJGpgR3fr2W4olk0BXvKBKThtSk7dznElV2uPO0Q/62Wzjg8QMsTHBz/YDIR08 ILqYLWMpsweHU8w3+yldaNELAGwOJKgvlq0O3CTcRSewYtjCX3yM2/hqFECkIMMrOcQf 6akw== X-Gm-Message-State: AElRT7FVBF40MzTHdMhznmuvAupvQrZyMgiqYlh07M+daRgsGDtkEIbL 1meUpAGist2Aeg87yTvL84uskqx6 X-Google-Smtp-Source: AG47ELuf7nTo2jn8P825HThA4qxHKTXPxU+i1jrdp66UQr8lSOoGgthum8vIBoQ2kuSwXUcQqWI8jw== X-Received: by 10.80.224.205 with SMTP id j13mr19471184edl.304.1521583695559; Tue, 20 Mar 2018 15:08:15 -0700 (PDT) Received: from juntos.woohoo.ch ([2a02:168:681c:460:dcd1:14c1:6604:1e9b]) by smtp.gmail.com with ESMTPSA id o52sm2596268edc.93.2018.03.20.15.08.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 15:08:14 -0700 (PDT) Subject: Re: Multicast/SSDP not working (on VLAN interface) To: freebsd-net@freebsd.org References: <201803192311.w2JNB5lU014039@pdx.rh.CN85.dnsmgr.net> From: Andreas Scherrer Message-ID: Date: Tue, 20 Mar 2018 23:08:14 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803192311.w2JNB5lU014039@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Mar 2018 22:08:18 -0000 Hi Thank you, Rodney and Ivan, for coming back to me (and so quickly). On 20.03.18 00:11, Rodney W. Grimes wrote: ... >> So I suspect that "something" is dropping the M-SEARCH packets for some >> reason after they are received. And I cannot get rid of the feeling that >> it has something to do with the fact that the incoming interface is a >> VLAN interface... >> My first guess, anti spoofing, seems not to be the problem (I am using >> ipfw and "not antispoof in" but that does not seem to drop any traffic). > > Are you running with "firewall_type="simple""? > If so it is set to block all 224/4 packets, see this part > of /etc/rc.firewall: ... No, my firewall is made from "hand curated" ipfw rules. And I am pretty sure (never 100%, but 99% this time), that this is not a firewall issue. Why? I have the following rule that should accept traffic from my client(s) to 239.255.255.250:1900 in place: allow ip from any to not me in recv re1\* And, when I place a rule like this just before and after that rule: count log ip from any to any via re1\* I see hits before but not after the "allow" rule. Hence, the policy accepts the packet(s). No? Also, just adding the route for 224.0.0.0/4, without touching the ipfw rules, makes things work... And I am *not* using "verrevpath" in my ifpw rules (I do use "antispoof", but as the packets hit the rule(s) mentioned above, that does not seem to be the problem). I might give Ivan's code a try, but I am not very good at compiling and installing software :( If anybody is able to provide an additional hint in the mean time, I am more than happy to follow up. Best andreas From owner-freebsd-net@freebsd.org Wed Mar 21 00:40:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4377FF5A514 for ; Wed, 21 Mar 2018 00:40:03 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB6BE724CE for ; Wed, 21 Mar 2018 00:40:02 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2L0dnd7082983 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 01:39:50 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rfg@tristatelogic.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2L0dcuT027057 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 21 Mar 2018 07:39:38 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: "Ronald F. Guilmette" , freebsd-net@freebsd.org References: <98551.1521576540@segfault.tristatelogic.com> From: Eugene Grosbein Message-ID: <5AB1A9C5.9050707@grosbein.net> Date: Wed, 21 Mar 2018 07:39:33 +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: <98551.1521576540@segfault.tristatelogic.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 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 * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 00:40:03 -0000 21.03.2018 3:09, Ronald F. Guilmette wrote: > I'm going to be doing some stuff with raw sockets pretty soon, and > while scrounging around, looking for some nice coding examples, I > found the following very curious comment on one particular message > board: > > https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems > > "Using raw sockets isn't hard but it's not entirely portable. For > instance, both in BSD and in Linux you can send whatever you want, > but in BSD you can't receive anything that has a handler (like TCP > and UDP)." > > So, first question: Is the above comment actually true & accurate? Not for FreeBSD. > Second question: If the above assertion is actually true, then how can > nmap manage to work so well on FreeBSD, despite what would appear to be > this insurmountable stumbling block (of not being able to receive replies)? nmap uses libdnet that provides some portability layer, including RAW socket operations. It uses bundled stripped-down version but we have "normal" one as net/libdnet port/package. You should consider using it too as convenience layer. From owner-freebsd-net@freebsd.org Wed Mar 21 00:44:38 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8B5DF5AB4E for ; Wed, 21 Mar 2018 00:44:37 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 3AA2172928 for ; Wed, 21 Mar 2018 00:44:36 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2L0iQ3N018954; Tue, 20 Mar 2018 17:44:26 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2L0iQww018953; Tue, 20 Mar 2018 17:44:26 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803210044.w2L0iQww018953@pdx.rh.CN85.dnsmgr.net> Subject: Re: Multicast/SSDP not working (on VLAN interface) In-Reply-To: To: Andreas Scherrer Date: Tue, 20 Mar 2018 17:44:26 -0700 (PDT) CC: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 00:44:38 -0000 > Hi > > Thank you, Rodney and Ivan, for coming back to me (and so quickly). > > On 20.03.18 00:11, Rodney W. Grimes wrote: > > ... > > >> So I suspect that "something" is dropping the M-SEARCH packets for some > >> reason after they are received. And I cannot get rid of the feeling that > >> it has something to do with the fact that the incoming interface is a > >> VLAN interface... > >> My first guess, anti spoofing, seems not to be the problem (I am using > >> ipfw and "not antispoof in" but that does not seem to drop any traffic). > > > > Are you running with "firewall_type="simple""? > > If so it is set to block all 224/4 packets, see this part > > of /etc/rc.firewall: > > ... > > No, my firewall is made from "hand curated" ipfw rules. > > And I am pretty sure (never 100%, but 99% this time), that this is not a > firewall issue. Why? > > I have the following rule that should accept traffic from my client(s) > to 239.255.255.250:1900 in place: > > allow ip from any to not me in recv re1\* > > And, when I place a rule like this just before and after that rule: > > count log ip from any to any via re1\* > > I see hits before but not after the "allow" rule. Hence, the policy > accepts the packet(s). No? > > Also, just adding the route for 224.0.0.0/4, without touching the ipfw > rules, makes things work... And I am *not* using "verrevpath" in my ifpw > rules (I do use "antispoof", but as the packets hit the rule(s) > mentioned above, that does not seem to be the problem). Your missing that WITHOUT that route the packets from your application TOWARDS your client are going to try and use the default route and go out the default interface. Your IN RULE has 0 effect on that, however your route add probably changes the interface these OUTWARD packets have. > > I might give Ivan's code a try, but I am not very good at compiling and > installing software :( > > If anybody is able to provide an additional hint in the mean time, I am > more than happy to follow up. Show me your full firewall rule set, without that I can only speculate as to where it is getting blocked, but given your symptoms I highly suspect the firewall is blocking the packets OUT of your SERVER back towards the client as they try to go out what ever interface your default route is on. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Wed Mar 21 01:03:08 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6994F5C29C for ; Wed, 21 Mar 2018 01:03:08 +0000 (UTC) (envelope-from michael.tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F094736D1 for ; Wed, 21 Mar 2018 01:03:08 +0000 (UTC) (envelope-from michael.tuexen@lurchi.franken.de) Received: from dhcp-9621.meeting.ietf.org (dhcp-9621.meeting.ietf.org [31.133.150.33]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 913EB721E281A; Wed, 21 Mar 2018 02:03:04 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Raw Sockets: Two Questions From: Michael Tuexen In-Reply-To: <5AB1A9C5.9050707@grosbein.net> Date: Wed, 21 Mar 2018 01:03:02 +0000 Cc: "Ronald F. Guilmette" , freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <98551.1521576540@segfault.tristatelogic.com> <5AB1A9C5.9050707@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 01:03:09 -0000 > On 21. Mar 2018, at 00:39, Eugene Grosbein wrote: >=20 > 21.03.2018 3:09, Ronald F. Guilmette wrote: >=20 >> I'm going to be doing some stuff with raw sockets pretty soon, and >> while scrounging around, looking for some nice coding examples, I >> found the following very curious comment on one particular message >> board: >>=20 >> = https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-s= ystems >>=20 >> "Using raw sockets isn't hard but it's not entirely portable. = For >> instance, both in BSD and in Linux you can send whatever you = want, >> but in BSD you can't receive anything that has a handler (like = TCP >> and UDP)." >>=20 >> So, first question: Is the above comment actually true & accurate? >=20 > Not for FreeBSD. Are you saying that I can receive on a raw socket SCTP, TCP and UDP = packets? Best regards Michael >=20 >> Second question: If the above assertion is actually true, then how = can >> nmap manage to work so well on FreeBSD, despite what would appear to = be >> this insurmountable stumbling block (of not being able to receive = replies)? >=20 > nmap uses libdnet that provides some portability layer, including RAW = socket operations. > It uses bundled stripped-down version but we have "normal" one as = net/libdnet port/package. > You should consider using it too as convenience layer. >=20 >=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" From owner-freebsd-net@freebsd.org Wed Mar 21 03:43:37 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F87F66989 for ; Wed, 21 Mar 2018 03:43:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3844379588 for ; Wed, 21 Mar 2018 03:43:36 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2L3hPSP084703 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 04:43:26 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: michael.tuexen@lurchi.franken.de Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id w2L3hEZv036778; Wed, 21 Mar 2018 10:43:14 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: Michael Tuexen References: <98551.1521576540@segfault.tristatelogic.com> <5AB1A9C5.9050707@grosbein.net> Cc: "Ronald F. Guilmette" , freebsd-net@freebsd.org From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <5AB1D4D2.8000001@grosbein.net> Date: Wed, 21 Mar 2018 10:43:14 +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: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 03:43:37 -0000 On 21.03.2018 08:03, Michael Tuexen wrote: >> On 21. Mar 2018, at 00:39, Eugene Grosbein wrote: >> >> 21.03.2018 3:09, Ronald F. Guilmette wrote: >> >>> I'm going to be doing some stuff with raw sockets pretty soon, and >>> while scrounging around, looking for some nice coding examples, I >>> found the following very curious comment on one particular message >>> board: >>> >>> https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems >>> >>> "Using raw sockets isn't hard but it's not entirely portable. For >>> instance, both in BSD and in Linux you can send whatever you want, >>> but in BSD you can't receive anything that has a handler (like TCP >>> and UDP)." >>> >>> So, first question: Is the above comment actually true & accurate? >> >> Not for FreeBSD. > Are you saying that I can receive on a raw socket SCTP, TCP and UDP packets? No. I'm saying one can send/receive RAW IP packets no matter are they SCTP, TCP or UDP or something else by means of libdnet. It uses raw sockets and BPF internally but hides this complexity. nmap uses it just fine. From owner-freebsd-net@freebsd.org Wed Mar 21 03:55:35 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43C09F67703 for ; Wed, 21 Mar 2018 03:55:35 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) (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 B34F179E4F for ; Wed, 21 Mar 2018 03:55:34 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: by mail-wm0-f51.google.com with SMTP id f19so7211456wmc.0 for ; Tue, 20 Mar 2018 20:55:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QPYfsvZmxAfR9oQAJzNkmBDiD5KrBfYfRH8HJF4AYkk=; b=HFPF+WRDMZl3+Jsrrb5DlN5qY2tS+iK75SghE0YNKFWJDUq22YVJkCHOgfLUY2lepO fnUcJbNd7PEbQ/LdInorkRjG2UCJNy31LszepCaf3ZT1pBApK/XMOPJ+iYWqoNhkMoK5 +qTJJbfvIWJyXb+873Awje51QisBtwtZwnhbca/jJKIF+vZIEahccAOIZEOrO0o7Awbd orCTeDXdzDzG78Z7s8qtK9yFkfaUgySNa/FVAq0vHaAJuvjmZOk7aTrGPGQP1afM3nZ0 7Li79M5bqYL0rqn3M/P04fO9yRwq1OKr4Jjt00ffkMzEfxTn+WMNNgY1Z//XMGrnJyzh EejQ== X-Gm-Message-State: AElRT7FP4jjsNfzOPhapuA+nKpQXDalwc+lWV5mn+d/qXkkYkZmv/zOO 8zmQkEtaKF6gKOtWZQsLZi3QESRg X-Google-Smtp-Source: AG47ELsJfZuyi/2/CY0aBHe0tN/vSeabVkg/ARBZOusIiZgDFaKQAg5/Xq+R4ikfPoSRG08iP3JVgA== X-Received: by 10.80.182.52 with SMTP id b49mr20129428ede.279.1521604526625; Tue, 20 Mar 2018 20:55:26 -0700 (PDT) Received: from mail-wr0-f181.google.com (mail-wr0-f181.google.com. [209.85.128.181]) by smtp.gmail.com with ESMTPSA id m23sm2744820edc.69.2018.03.20.20.55.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 20:55:26 -0700 (PDT) Received: by mail-wr0-f181.google.com with SMTP id z8so3780253wrh.7 for ; Tue, 20 Mar 2018 20:55:26 -0700 (PDT) X-Received: by 10.223.186.140 with SMTP id p12mr14849625wrg.162.1521604526115; Tue, 20 Mar 2018 20:55:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.167.12 with HTTP; Tue, 20 Mar 2018 20:55:25 -0700 (PDT) In-Reply-To: <5AB1D4D2.8000001@grosbein.net> References: <98551.1521576540@segfault.tristatelogic.com> <5AB1A9C5.9050707@grosbein.net> <5AB1D4D2.8000001@grosbein.net> From: Matt Joras Date: Tue, 20 Mar 2018 20:55:25 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Raw Sockets: Two Questions To: Eugene Grosbein Cc: Michael Tuexen , FreeBSD Net , "Ronald F. Guilmette" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 03:55:35 -0000 On Tue, Mar 20, 2018 at 8:43 PM, Eugene Grosbein wrote: > On 21.03.2018 08:03, Michael Tuexen wrote: > >>> On 21. Mar 2018, at 00:39, Eugene Grosbein wrote: >>> >>> 21.03.2018 3:09, Ronald F. Guilmette wrote: >>> >>>> I'm going to be doing some stuff with raw sockets pretty soon, and >>>> while scrounging around, looking for some nice coding examples, I >>>> found the following very curious comment on one particular message >>>> board: >>>> >>>> https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems >>>> >>>> "Using raw sockets isn't hard but it's not entirely portable. For >>>> instance, both in BSD and in Linux you can send whatever you want, >>>> but in BSD you can't receive anything that has a handler (like TCP >>>> and UDP)." >>>> >>>> So, first question: Is the above comment actually true & accurate? >>> >>> Not for FreeBSD. >> Are you saying that I can receive on a raw socket SCTP, TCP and UDP packets? > > No. I'm saying one can send/receive RAW IP packets no matter are they SCTP, TCP or UDP > or something else by means of libdnet. It uses raw sockets and BPF internally > but hides this complexity. nmap uses it just fine. > Saying "Not for FreeBSD" is needlessly confusing and not accurate. In the common parlance "raw sockets" does not refer to libdnet, which is not a part of the FreeBSD base system. You cannot use traditional raw sockets on FreeBSD to receive traditional protocol packets. The only way to do that in the base system is to use a BPF handle directly. Matt From owner-freebsd-net@freebsd.org Wed Mar 21 11:19:48 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31986F5EB8D for ; Wed, 21 Mar 2018 11:19:48 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B9ED069FD3; Wed, 21 Mar 2018 11:19:47 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2LBJYJo087491 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 12:19:35 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: mjoras@freebsd.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id w2LBJLKv055000; Wed, 21 Mar 2018 18:19:21 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: Matt Joras References: <98551.1521576540@segfault.tristatelogic.com> <5AB1A9C5.9050707@grosbein.net> <5AB1D4D2.8000001@grosbein.net> Cc: Michael Tuexen , "Ronald F. Guilmette" , FreeBSD Net From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <5AB23FB9.7050407@grosbein.net> Date: Wed, 21 Mar 2018 18:19:21 +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: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 11:19:48 -0000 On 21.03.2018 10:55, Matt Joras wrote: >>>>> I'm going to be doing some stuff with raw sockets pretty soon, and >>>>> while scrounging around, looking for some nice coding examples, I >>>>> found the following very curious comment on one particular message >>>>> board: >>>>> >>>>> https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems >>>>> >>>>> "Using raw sockets isn't hard but it's not entirely portable. For >>>>> instance, both in BSD and in Linux you can send whatever you want, >>>>> but in BSD you can't receive anything that has a handler (like TCP >>>>> and UDP)." >>>>> >>>>> So, first question: Is the above comment actually true & accurate? >>>> >>>> Not for FreeBSD. >>> Are you saying that I can receive on a raw socket SCTP, TCP and UDP packets? >> >> No. I'm saying one can send/receive RAW IP packets no matter are they SCTP, TCP or UDP >> or something else by means of libdnet. It uses raw sockets and BPF internally >> but hides this complexity. nmap uses it just fine. >> > Saying "Not for FreeBSD" is needlessly confusing and not accurate. In > the common parlance "raw sockets" does not refer to libdnet, which is > not a part of the FreeBSD base system. You cannot use traditional raw > sockets on FreeBSD to receive traditional protocol packets. The goal is to send/receive RAW IP packets, not to use raw sockets, isn't it? > The only way to do that in the base system is to use a BPF handle directly. Not exactly. For example: if_ethersubr.c/ether_input_internal() performs some sanity checks then passes incoming frame to BPF and to NETGRAPH (ng_ether) before passing it to upper stack layers. One can do almost anything with the frame by means of NETGRAPH subsystem and pass it to userland too. One have to setup some NETGRAPH nodes before, though - just like ppp(8) does to process control PPPoE frames. From owner-freebsd-net@freebsd.org Wed Mar 21 11:37:39 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E73FF60092 for ; Wed, 21 Mar 2018 11:37:39 +0000 (UTC) (envelope-from michael.tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B74A66AB9B for ; Wed, 21 Mar 2018 11:37:38 +0000 (UTC) (envelope-from michael.tuexen@lurchi.franken.de) Received: from dhcp-9621.meeting.ietf.org (dhcp-9621.meeting.ietf.org [31.133.150.33]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 45FFB721E2822; Wed, 21 Mar 2018 12:37:25 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Raw Sockets: Two Questions From: Michael Tuexen In-Reply-To: <5AB1D4D2.8000001@grosbein.net> Date: Wed, 21 Mar 2018 11:35:46 +0000 Cc: "Ronald F. Guilmette" , freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <98551.1521576540@segfault.tristatelogic.com> <5AB1A9C5.9050707@grosbein.net> <5AB1D4D2.8000001@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 11:37:39 -0000 > On 21. Mar 2018, at 03:43, Eugene Grosbein wrote: >=20 > On 21.03.2018 08:03, Michael Tuexen wrote: >=20 >>> On 21. Mar 2018, at 00:39, Eugene Grosbein = wrote: >>>=20 >>> 21.03.2018 3:09, Ronald F. Guilmette wrote: >>>=20 >>>> I'm going to be doing some stuff with raw sockets pretty soon, and >>>> while scrounging around, looking for some nice coding examples, I >>>> found the following very curious comment on one particular message >>>> board: >>>>=20 >>>> = https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-s= ystems >>>>=20 >>>> "Using raw sockets isn't hard but it's not entirely portable. = For >>>> instance, both in BSD and in Linux you can send whatever you = want, >>>> but in BSD you can't receive anything that has a handler (like = TCP >>>> and UDP)." >>>>=20 >>>> So, first question: Is the above comment actually true & accurate? >>>=20 >>> Not for FreeBSD. >> Are you saying that I can receive on a raw socket SCTP, TCP and UDP = packets? >=20 > No. I'm saying one can send/receive RAW IP packets no matter are they = SCTP, TCP or UDP > or something else by means of libdnet. It uses raw sockets and BPF = internally > but hides this complexity. nmap uses it just fine. OK. Thanks for the clarification. Best regards Michael >=20 >=20 From owner-freebsd-net@freebsd.org Wed Mar 21 12:51:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A386AF65653 for ; Wed, 21 Mar 2018 12:51:01 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmfepo201.cox.net (eastrmfepo201.cox.net [68.230.241.216]) by mx1.freebsd.org (Postfix) with ESMTP id 481626DABF for ; Wed, 21 Mar 2018 12:51:01 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo109.cox.net ([68.230.241.222]) by eastrmfepo201.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20180321125100.PYZR1466.eastrmfepo201.cox.net@eastrmimpo109.cox.net> for ; Wed, 21 Mar 2018 08:51:00 -0400 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo109.cox.net with cox id Qcr01x00L1LxgH801cr0RY; Wed, 21 Mar 2018 08:51:00 -0400 X-Authority-Analysis: v=2.2 cv=CZV43Pjl c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=v2DPQv5-lfwA:10 a=e9ASbk4n0QUA:10 a=S_tuheKzbOEv_BRnm3wA:9 a=QEXdDO2ut3YA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (LOGIN) smtp.auth=jbuehler@cox.net Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id 11FDD1152A for ; Wed, 21 Mar 2018 08:51:00 -0400 (EDT) Message-ID: <5AB25533.3020003@cox.net> Date: Wed, 21 Mar 2018 08:50:59 -0400 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: netmap ixgbevf max frame size References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 12:51:01 -0000 I am unable to send frames larger than 9216 bytes (destination MAC through trailing CRC inclusive) using ixgbevf hardware with latest netmap code (LINUX). What is the source of this limitation? From the chip datasheet it appears that much larger frames are supported. There is mention of 9216 in some of the driver source files but as an MTU, the max frame size is larger. Joe Buehler From owner-freebsd-net@freebsd.org Wed Mar 21 13:32:50 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C661F686C5 for ; Wed, 21 Mar 2018 13:32:50 +0000 (UTC) (envelope-from jhpb@cox.net) Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by mx1.freebsd.org (Postfix) with ESMTP id A80F46FA33 for ; Wed, 21 Mar 2018 13:32:49 +0000 (UTC) (envelope-from jhpb@cox.net) Received: from eastrmimpo109.cox.net ([68.230.241.222]) by eastrmfepo203.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20180321133242.UZSW31819.eastrmfepo203.cox.net@eastrmimpo109.cox.net> for ; Wed, 21 Mar 2018 09:32:42 -0400 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo109.cox.net with cox id QdYi1x00T1LxgH801dYiAX; Wed, 21 Mar 2018 09:32:42 -0400 X-Authority-Analysis: v=2.2 cv=CZV43Pjl c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=9cW_t1CCXrUA:10 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=v2DPQv5-lfwA:10 a=e9ASbk4n0QUA:10 a=GjeyiUamVxH073NwtRcA:9 a=QEXdDO2ut3YA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (LOGIN) smtp.auth=jbuehler@cox.net Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id 323AB1152A for ; Wed, 21 Mar 2018 09:32:41 -0400 (EDT) Message-ID: <5AB25EF9.4080100@cox.net> Date: Wed, 21 Mar 2018 09:32:41 -0400 From: "Joseph H. Buehler" User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 CC: "freebsd-net@freebsd.org" Subject: Re: netmap ixgbevf max frame size References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> <5AB25533.3020003@cox.net> In-Reply-To: <5AB25533.3020003@cox.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 13:32:50 -0000 This turned out to be a limitation of the box we are using, there is apparently hardware between the ixgbevf chip and the fiber. Joe Buehler > I am unable to send frames larger than 9216 bytes (destination MAC through trailing CRC inclusive) using ixgbevf hardware with latest netmap code (LINUX). > > What is the source of this limitation? From the chip datasheet it appears that much larger frames are supported. > > There is mention of 9216 in some of the driver source files but as an MTU, the max frame size is larger. > > Joe Buehler > > From owner-freebsd-net@freebsd.org Wed Mar 21 17:38:47 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D321BF572F4 for ; Wed, 21 Mar 2018 17:38:47 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD2E7CAD3 for ; Wed, 21 Mar 2018 17:38:46 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id DC7C53AEF2 for ; Wed, 21 Mar 2018 10:38:45 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org Subject: Re: Raw Sockets: Two Questions In-Reply-To: <5AB1A9C5.9050707@grosbein.net> Date: Wed, 21 Mar 2018 10:38:45 -0700 Message-ID: <3394.1521653925@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 17:38:48 -0000 In message <5AB1A9C5.9050707@grosbein.net>, Eugene Grosbein wrote: >21.03.2018 3:09, Ronald F. Guilmette wrote: >> https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems >> "Using raw sockets isn't hard but it's not entirely portable. For >> instance, both in BSD and in Linux you can send whatever you want, >> but in BSD you can't receive anything that has a handler (like TCP >> and UDP)." >> >> So, first question: Is the above comment actually true & accurate? > >Not for FreeBSD. Is it true for other *BSDs? >> Second question: If the above assertion is actually true, then how can >> nmap manage to work so well on FreeBSD, despite what would appear to be >> this insurmountable stumbling block (of not being able to receive replies)? > >nmap uses libdnet that provides some portability layer, including RAW socket operations. >It uses bundled stripped-down version but we have "normal" one as net/libdnet port/package. >You should consider using it too as convenience layer. Thank you. I will certainly look into this, however my needs are quite small and modest... probably so modest that a "convenience layer" wouldn't be a substantial help. From owner-freebsd-net@freebsd.org Wed Mar 21 18:08:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEA20F595B2 for ; Wed, 21 Mar 2018 18:08:26 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 674EE7E18E for ; Wed, 21 Mar 2018 18:08:25 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 20FDA3AEF2 for ; Wed, 21 Mar 2018 11:08:25 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Raw Sockets: Two Questions In-Reply-To: <5AB23FB9.7050407@grosbein.net> Date: Wed, 21 Mar 2018 11:08:24 -0700 Message-ID: <3559.1521655704@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 18:08:27 -0000 In message <5AB23FB9.7050407@grosbein.net>, Eugene Grosbein wrote: >On 21.03.2018 10:55, Matt Joras wrote: >> Saying "Not for FreeBSD" is needlessly confusing and not accurate. In >> the common parlance "raw sockets" does not refer to libdnet, which is >> not a part of the FreeBSD base system. You cannot use traditional raw >> sockets on FreeBSD to receive traditional protocol packets. > >The goal is to send/receive RAW IP packets, not to use raw sockets, isn't it? > >> The only way to do that in the base system is to use a BPF handle directly. > >Not exactly. For example: if_ethersubr.c/ether_input_internal() performs some sanity checks >then passes incoming frame to BPF and to NETGRAPH (ng_ether) before passing it to upper stack l >ayers. > >One can do almost anything with the frame by means of NETGRAPH subsystem >and pass it to userland too. One have to setup some NETGRAPH nodes before, though - >just like ppp(8) does to process control PPPoE frames. OK, so, if I have understood all that has been said in this thread so far, then I would assert that, from the perspective of a simple-minded and naive end user (e.g. me), the assertion that I originally quoted -is- in fact correct, i.e. one -cannot- just simply do sendto/recvfrom (and expect to get back responses) if the raw packets that one sends out happen to be, for example, well formed TCP or UDP packets. If I have correctly understood Matt Joras, there -are- ways to get hold of such reply packets, under FreeBSD, but those require getting a bit more "under the hood" in order to actually get hold of them... more than just a simple recvfrom on the RAW socket. Have I understood correctly? From owner-freebsd-net@freebsd.org Wed Mar 21 18:48:44 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38831F5C643 for ; Wed, 21 Mar 2018 18:48:44 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B83F7800BD for ; Wed, 21 Mar 2018 18:48:43 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2LImPEQ090680 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 19:48:25 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rfg@tristatelogic.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2LImEOk058203 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Mar 2018 01:48:14 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: "Ronald F. Guilmette" , freebsd-net@freebsd.org References: <3394.1521653925@segfault.tristatelogic.com> From: Eugene Grosbein Message-ID: <5AB2A8E9.5020002@grosbein.net> Date: Thu, 22 Mar 2018 01:48:09 +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: <3394.1521653925@segfault.tristatelogic.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 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 * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 18:48:44 -0000 22.03.2018 0:38, Ronald F. Guilmette пишет: > > In message <5AB1A9C5.9050707@grosbein.net>, > Eugene Grosbein wrote: > >> 21.03.2018 3:09, Ronald F. Guilmette wrote: >>> https://stackoverflow.com/questions/7048448/raw-sockets-on-bsd-operating-systems >>> "Using raw sockets isn't hard but it's not entirely portable. For >>> instance, both in BSD and in Linux you can send whatever you want, >>> but in BSD you can't receive anything that has a handler (like TCP >>> and UDP)." >>> >>> So, first question: Is the above comment actually true & accurate? >> >> Not for FreeBSD. > > Is it true for other *BSDs? Don't know about raw sockets. But I know that NETGRAPH that allows to send/receive RAW frames is FreeBSD specific. From owner-freebsd-net@freebsd.org Wed Mar 21 19:08:31 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 520D8F5E302 for ; Wed, 21 Mar 2018 19:08:31 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DEF5D824A3 for ; Wed, 21 Mar 2018 19:08:30 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2LJ8NX1090988 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 20:08:24 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rfg@tristatelogic.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2LJ8KfW058508 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Mar 2018 02:08:20 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: "Ronald F. Guilmette" , FreeBSD Net References: <3559.1521655704@segfault.tristatelogic.com> From: Eugene Grosbein Message-ID: <5AB2AD9F.6040600@grosbein.net> Date: Thu, 22 Mar 2018 02:08:15 +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: <3559.1521655704@segfault.tristatelogic.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 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 * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 19:08:31 -0000 22.03.2018 1:08, Ronald F. Guilmette wrote: > OK, so, if I have understood all that has been said in this thread so > far, then I would assert that, from the perspective of a simple-minded > and naive end user (e.g. me), the assertion that I originally quoted > -is- in fact correct, i.e. one -cannot- just simply do sendto/recvfrom > (and expect to get back responses) if the raw packets that one sends out > happen to be, for example, well formed TCP or UDP packets. Not exactly. You can't use raw sockets to receive but that does not mean you cannot use sendto/recvfrom (or similar calls) at all: there are libpcap, libdnet and NETGRAPH allowing to send requests and receive answers. > If I have correctly understood Matt Joras, there -are- ways to get hold > of such reply packets, under FreeBSD, but those require getting a bit more > "under the hood" in order to actually get hold of them... more than just > a simple recvfrom on the RAW socket. Why should you concentrate on RAW sockets? I have small perl script that sends manually crafted PPPoE frames and receives replies using simple libpcap interface: use Net::Pcap qw(:DEFAULT :functions); use constant V8021Q => 0x8100; use constant ETHERTYPE_PPPOEDISC => 0x8863; use constant PPPOE_VER => 1; use constant PPPOE_TYPE => 1; use constant PADO_CODE => 7; use constant PADI_CODE => 9; use constant TAG_END_OF_LIST => 0x0000; use constant TAG_SERVICE_NAME => 0x0101; use constant TAG_AC_NAME => 0x0102; use constant TAG_HOST_UNIQ => 0x0103; $packet = # Ethernet header: dst MAC, src MAC, TYPE ether_aton('ff:ff:ff:ff:ff:ff') . $bmac . pack('n', ETHERTYPE_PPPOEDISC) . # PPPoE PADI: VER, TYPE, CODE, SESSION_ID=0 pack('C', (PPPOE_VER<<4) + PPPOE_TYPE) . pack('C', PADI_CODE) . pack('n', 0) # LENGTH, tags pack('n', $tlen) . $tags; # zero padding upto 60 bytes ethernet frame length (without checksum) $packet .= pack('a' . (40-$tlen) , '') if $tlen < 40; err("cannot open interface $interface: $err") unless $pcap = pcap_open_live($interface, $snaplen, 0, 0, \$err); err("could not send PADI") if pcap_sendpacket($pcap, $packet) != 0; $filter = "ether proto " . ETHERTYPE_PPPOEDISC . " and ether dst $mac"; err("cannot compile filter: $filter") if pcap_compile($pcap, \$bpf, $filter, 1, 0) < 0; pcap_setfilter($pcap, $bpf); $ec = 0; while($ec == 0) { $ec = pcap_loop($pcap, -1, \&callback, undef); } pcap_close($pcap); exit(0); sub callback($$$) { return if $_[1]->{'len'} < 20; # sanity check: short frame my ($dst, $src, $ftype, $ftag, $fp) = unpack('a6a6na4a*' , $_[2]); ... } From owner-freebsd-net@freebsd.org Wed Mar 21 20:03:50 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34CD6F625D0 for ; Wed, 21 Mar 2018 20:03:50 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id C1B1984CAE for ; Wed, 21 Mar 2018 20:03:49 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 784DA3AEF2 for ; Wed, 21 Mar 2018 13:03:48 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Raw Sockets: Two Questions In-Reply-To: <5AB2AD9F.6040600@grosbein.net> Date: Wed, 21 Mar 2018 13:03:48 -0700 Message-ID: <4584.1521662628@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 20:03:50 -0000 In message <5AB2AD9F.6040600@grosbein.net>, Eugene Grosbein wrote: >Why should you concentrate on RAW sockets? Well, for reasons that are completely legitimate, and that I'll explain in detail, if anyone is seriously interested, I'd like to check each IPv4 address within a set of about 90 or so modest sized CIDRs and find out which ones of those have a certain TCP port accepting connections. It would be (and is) trivial, of course, to just simply write a little program to perform an ordinary TCP connect, complete with all three parts of the TCP handshake, and then have the program do that, individually, for each IP in the specified CIDRs, but my opinion/impression is that this could be quite slow. Obviously, it would be rather faster to just send out the SYNs, full throttle, one per IP, and then see what SYN-ACKs come back. And actually, now that I've just reviewed the online man page for zmap, I see that (contrary to my earlier belief/suspicion) this has enough control options to me useful to me, so I'll probably just use that instead of rolling my own. (I first learned about zmap some long time ago, but only just today decided to actually take it out for a test drive.) Still, there may be some other reasons for me to educate myself about proper programming techniques utilizing raw sockets, but I'll talk about that in a separate post to follow this one. From owner-freebsd-net@freebsd.org Wed Mar 21 20:29:53 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0617F64813 for ; Wed, 21 Mar 2018 20:29:53 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 38CDC86557 for ; Wed, 21 Mar 2018 20:29:52 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2LKTjfh091598 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 21:29:46 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rfg@tristatelogic.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2LKTfiG059480 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Mar 2018 03:29:41 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Raw Sockets: Two Questions To: "Ronald F. Guilmette" , FreeBSD Net References: <4584.1521662628@segfault.tristatelogic.com> From: Eugene Grosbein Message-ID: <5AB2C0B1.3020709@grosbein.net> Date: Thu, 22 Mar 2018 03:29:37 +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: <4584.1521662628@segfault.tristatelogic.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 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 * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 20:29:53 -0000 22.03.2018 3:03, Ronald F. Guilmette wrote: >> Why should you concentrate on RAW sockets? > > Well, for reasons that are completely legitimate, and that I'll > explain in detail, if anyone is seriously interested, I'd like > to check each IPv4 address within a set of about 90 or so > modest sized CIDRs and find out which ones of those have a > certain TCP port accepting connections. > > It would be (and is) trivial, of course, to just simply write a > little program to perform an ordinary TCP connect, complete > with all three parts of the TCP handshake, and then have the > program do that, individually, for each IP in the specified > CIDRs, but my opinion/impression is that this could be quite > slow. > > Obviously, it would be rather faster to just send out the SYNs, > full throttle, one per IP, and then see what SYN-ACKs come back. It does not mean you need to stick with raw sockets API. libpcap can be used too, as I've shown in previous letter. In fact, I use that code for very similar task: I send out several thousands of PPPoE service discovery frames (PADI) at full throttle (one per vlan) and then wait for responses (PADO) to come back. No raw socket (ab)used in progress :-) From owner-freebsd-net@freebsd.org Wed Mar 21 20:40:27 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 495FAF65431 for ; Wed, 21 Mar 2018 20:40:27 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 DAF3986CAA for ; Wed, 21 Mar 2018 20:40:26 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-qk0-x236.google.com with SMTP id s188so6948483qkb.2 for ; Wed, 21 Mar 2018 13:40:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0mrWqNKoB4Mv6nYtAdPI44d7XFuoWs+Ss03BecObgeI=; b=tz4KaSdKfb/Ap5swWFbnJiPkTe1Iz+JrwyBBN46bupIGd0472Ymp+hQ7DZxveqpofP YUNCWhT4uzg8GCSDcN1FxVN7r8wd95G+FTlKHQpkuhTDhlScXhNBfEJsOeR0n4RVwb02 cayLbik5tOiLNDVjF5a+9CVhcsLPZERgV6Y/zhFucZkHWqsG2jw8gfrYHfeS3B1sFffm UwB13c+3s/+gFOlWDscQ5q1gDnuB/P1ZYcKTe6clXTJ8WVb6yphi4zuwsLF1H+Mr/SZf CeBU9YrWo52pO+YiCfhdDLShCtEGBUfic5rAja5QBfHKFmi7Y6hPwhT7AymmGip3K0F3 etlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0mrWqNKoB4Mv6nYtAdPI44d7XFuoWs+Ss03BecObgeI=; b=Viq3vguuZfJpkIVJeTgbQwbGT5hxbJ8HxnZaPytkPbkNjDxOrlQhGk1Ux6r6ge9i1g v+qF/XaTZKaDQOR3AHc1PEaSpQk0ujaXsn8Hf/bbuMj97EW8KGOzzFtly8Os8ijkLN5D zwGnLSsIqkwabVIoQBCavzLW5ae7VP2agTq/6j9lKkzpGh3/xKY2UVq7cTq+ym/Z+npG uOcgsPVWbT8E1ElsxWeJpTzZkLrW2U73+3uHOJbRLpw5vv+emuvX99zQxZ3yDA2kdvUs nKs7imFP4UqcKfrQ+mVawGzL18x6S2uvV3SV3760DZCc2lYkFxjQLcFjAeM132QDK4hf rTfA== X-Gm-Message-State: AElRT7FgmKTYS2z620/ZoIAThSYpyqEw9jYAUJ+Istf7Xq9hIGXArkEq YQUGMpmUvgcuXqWr84CipfsuJa4aFVDV4Ou0WV0= X-Google-Smtp-Source: AG47ELtU5pBFIRO6hcc0wifnlPZzBb+0lUFo2w8QZEAYYNkfiRAIynQ/fKs9TUo03FmRC5n5RUlEYcUD8CrPtIQuRZg= X-Received: by 10.55.192.5 with SMTP id o5mr31634825qki.87.1521664826259; Wed, 21 Mar 2018 13:40:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.195.204 with HTTP; Wed, 21 Mar 2018 13:40:25 -0700 (PDT) In-Reply-To: <5AB166DC.8060708@cox.net> References: <5AAC49BE.3030508@cox.net> <5AAC4A96.1040107@cox.net> <5AB01439.3090003@cox.net> <5AB166DC.8060708@cox.net> From: Vincenzo Maffione Date: Wed, 21 Mar 2018 21:40:25 +0100 Message-ID: Subject: Re: netmap ixgbevf mtu To: Joe Buehler Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 20:40:27 -0000 I see. Unfortunately this breaks the API, so I don't think we can accept it. We should probably sum up the fragment lengths, remember which one was the first descriptor and write the olinfo field when we process the last descriptor ... I hope this does not slow down the simpler case where NS_MOREFRAG is not used. In any, case we should move this discussion to the github, if possible (so that the issue gets tracked). Cheers, Vincenzo 2018-03-20 20:54 GMT+01:00 Joe Buehler : > Attached is a patch that allows fragmented TX with the ixgbevf driver. > > For the first TX buffer set the slot length to the full length of the > frame and make sure that the slot buffer is fully filled. For succeeding > slots just set the length to the amount of the buffer filled. > > Not intended as the perfect solution but it works fine for my situation. > > Joe Buehler > > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Wed Mar 21 20:50:28 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A7FBF65E76 for ; Wed, 21 Mar 2018 20:50:28 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 08ACA87359 for ; Wed, 21 Mar 2018 20:50:27 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id AAEB53AEF8 for ; Wed, 21 Mar 2018 13:50:26 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Raw Sockets: Two Questions In-Reply-To: <5AB2C0B1.3020709@grosbein.net> Date: Wed, 21 Mar 2018 13:50:26 -0700 Message-ID: <4802.1521665426@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 20:50:28 -0000 In message <5AB2C0B1.3020709@grosbein.net>, Eugene Grosbein wrote: >It does not mean you need to stick with raw sockets API. >libpcap can be used too, as I've shown in previous letter. Thank you. If zmap ends up not suiting my needs, I will definitely look into libpcap. From owner-freebsd-net@freebsd.org Wed Mar 21 21:19:45 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EF26F6828B for ; Wed, 21 Mar 2018 21:19:45 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 1C09968DA6 for ; Wed, 21 Mar 2018 21:19:44 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 940983AEF2 for ; Wed, 21 Mar 2018 14:19:43 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Same host or different? How can you tell "over the wire"? Date: Wed, 21 Mar 2018 14:19:43 -0700 Message-ID: <4903.1521667183@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 21:19:45 -0000 This problem has been preplexing me for ages and ages. I looked at it again, just briefly, and re-read parts of some potentially relevant RFCs, just the other day, but frankly, I'm just too ignorant and/or too stupid to be able to think up a solution, so I'll just drop the problem description here and see if any of you more knowledgable people can devise or suggest a solution. The Problem: Suppose that there exist two IPv4 addresses, A and A'. Both addresses have the exact same set of ports open, and both respond in identical ways, at least at the application level, when sent identical inputs. In short, at the application layer level, at least, there appears to be no way to reliably differentiate between the case where the two IP addresses are being routed to a single common physical machine (or to a single common virtual OS instance) or to two separate physical machines (or two separate virtual OS instances). Is there any method which can be applied to A and A' over the Internet and which could reliably differentiate these two possible cases from one another (i.e. a single common host versus two separate hosts)? If any such method or mechanism exists, I would very much like to know all of the details thereof. Such a method, if one exists, would certainly have value in various types of forensic investigations. Regards, rfg P.S. It is my assumption that the kind of thing I'm looking for, if it exists at all, will be found somewhere below the application layer. I do not rule out however that there may be some way of differentiating the two cases described above by looking at application layer responses for some certain common applications. As far as I know however, it is not possible to make the desired differentiation on the basis of application layer responses for most typical network applications, e.g. various makes and model numbers of servers for HTTP, HTTPS, SMTP, SSH, DNS, etc. Of course, if I have simply missed something, and if there is in fact a way to differentiate the two cases on the basis of responses sent for any of these application protocols, then I sure would like to know about that too. From owner-freebsd-net@freebsd.org Wed Mar 21 21:39:56 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD4F5F69AB9 for ; Wed, 21 Mar 2018 21:39:56 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C73E69E93 for ; Wed, 21 Mar 2018 21:39:55 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2LLdm84092149 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 22:39:48 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rfg@tristatelogic.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2LLdhhn060394 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Mar 2018 04:39:44 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Same host or different? How can you tell "over the wire"? To: "Ronald F. Guilmette" , FreeBSD Net References: <4903.1521667183@segfault.tristatelogic.com> From: Eugene Grosbein Message-ID: <5AB2D11A.6060605@grosbein.net> Date: Thu, 22 Mar 2018 04:39:38 +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: <4903.1521667183@segfault.tristatelogic.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 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 * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 21:39:57 -0000 22.03.2018 4:19, Ronald F. Guilmette wrote: > This problem has been preplexing me for ages and ages. I looked at it > again, just briefly, and re-read parts of some potentially relevant > RFCs, just the other day, but frankly, I'm just too ignorant and/or > too stupid to be able to think up a solution, so I'll just drop the > problem description here and see if any of you more knowledgable > people can devise or suggest a solution. > > The Problem: > > Suppose that there exist two IPv4 addresses, A and A'. Both addresses > have the exact same set of ports open, and both respond in identical > ways, at least at the application level, when sent identical inputs. > In short, at the application layer level, at least, there appears to > be no way to reliably differentiate between the case where the two > IP addresses are being routed to a single common physical machine > (or to a single common virtual OS instance) or to two separate physical > machines (or two separate virtual OS instances). > > Is there any method which can be applied to A and A' over the > Internet and which could reliably differentiate these two possible > cases from one another (i.e. a single common host versus two separate > hosts)? > > If any such method or mechanism exists, I would very much like to know > all of the details thereof. Such a method, if one exists, would > certainly have value in various types of forensic investigations. > > > Regards, > rfg > > > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of differentiating > the two cases described above by looking at application layer responses > for some certain common applications. As far as I know however, it is > not possible to make the desired differentiation on the basis of > application layer responses for most typical network applications, > e.g. various makes and model numbers of servers for HTTP, HTTPS, > SMTP, SSH, DNS, etc. Of course, if I have simply missed something, > and if there is in fact a way to differentiate the two cases on the > basis of responses sent for any of these application protocols, then > I sure would like to know about that too. If they respond truly identically, there are no reasons to treat them like distinct hosts despite of different IP addresses. And if you have such reason despite they respond truly identically, then such a reason steams from matters other than their response on requests to open ports. In this case you should differentiate them by other means too, not by open port's responses. From owner-freebsd-net@freebsd.org Wed Mar 21 21:53:37 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52C95F6A994 for ; Wed, 21 Mar 2018 21:53:37 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (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 C85886A8F2 for ; Wed, 21 Mar 2018 21:53:36 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by mail-pl0-x22b.google.com with SMTP id b7-v6so3975587plr.8 for ; Wed, 21 Mar 2018 14:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=dApe6qVOnvKDBJojzTiiyzcPXeHgsdY8kB2iKCJJRW0=; b=SFtqQQETFxZoyOys+JSbk6aNdf2NYmRmfxdddtIf+2BYbqdscQ6AUu0m/F8qhBppb6 yDqSDFnov2qg0OqVecH5NTyhrGdJrT4r4v3K+xX0eqLmmFmkk2Xln9iRNUPX+jgRKkfi GgftaiG0lzPpYsPI0vcFLCVcQh/EYmCUaCHXoQITbGrN+ri49bZdzuRhOSogTteFLpzA Xn6RvHyz8z2tjg5QO0SSl/TYfjVeCcIeOUuTel21VPL3E2bOY0TDjnmgbG/mpjdExuGh +ngecMgJGRRkvrQ1FuFbqIv/6yqzk7866SK4Hkzvp2Qsoojr12vGIQrNGKvZKzEIpmEv 0aXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=dApe6qVOnvKDBJojzTiiyzcPXeHgsdY8kB2iKCJJRW0=; b=PNRfbHf3NZO4GnQ2uAGiW2pCstjfvkPkQGlAHpKKN25DqQMf5A0OI2q1aAx86MnWBK qSvWo2CqRriYg2YBRDDcfxQXL+Z3k95byfVeANev4q00uyva+Qf8NJzNCOP9pfpdACHY itBWAruqvJFEOJdLDOPOMbkndRyWIeYQN+kfgRKVms0k03dAzIeZFkMsyD4t+b1TgvOT vp2+cqTobNNNTYqTChVJv0PsqgYUpsJ75/9IK4enFsdO+0N6umquxrBU6B2363t3WfW5 DwCPnqBMSCvWGO9+b5yijVnimSzSlSLPY0cgTUPmhHQZlyT54rLGr6M42Q7ffr5Csfbl LQfA== X-Gm-Message-State: AElRT7GSXoe6566bTdEjk7F06+5V3VDWQc1iYpL4VCHNuulaMlRMCMqB YyUvWiUp+ScgbueovDj067CGqxOqxZLDzVZRcbQ= X-Google-Smtp-Source: AG47ELtFtO5K71tUwsNcyJ6dqjeEVHb43a+zJpAqCQxTkeZw2uTxIX/xOB8/80HuHDIDL+hnocRMAf3PwWiYYFRd4Z8= X-Received: by 2002:a17:902:2e43:: with SMTP id q61-v6mr21985206plb.404.1521669215512; Wed, 21 Mar 2018 14:53:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.174.20 with HTTP; Wed, 21 Mar 2018 14:53:35 -0700 (PDT) In-Reply-To: <4903.1521667183@segfault.tristatelogic.com> References: <4903.1521667183@segfault.tristatelogic.com> From: Kurt Buff Date: Wed, 21 Mar 2018 14:53:35 -0700 Message-ID: Subject: Re: Same host or different? How can you tell "over the wire"? To: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 21:53:37 -0000 Do you mean that the application banners for all applications are the same? A comprehensive scan with nmap shows no differences? I know you specified SSH as outside of the application layer, but I would think if it's even to the point that the same SSH key (or credentials) work for both machines, and upon login provide the same hostname in the prompt, you'd have to dig and see if the NIC configs show a difference, or perhaps that there are multiple NICs, or a single NIC aliased with the IP addresses you're reviewing. Kurt On Wed, Mar 21, 2018 at 2:19 PM, Ronald F. Guilmette wrote: > > This problem has been preplexing me for ages and ages. I looked at it > again, just briefly, and re-read parts of some potentially relevant > RFCs, just the other day, but frankly, I'm just too ignorant and/or > too stupid to be able to think up a solution, so I'll just drop the > problem description here and see if any of you more knowledgable > people can devise or suggest a solution. > > The Problem: > > Suppose that there exist two IPv4 addresses, A and A'. Both addresses > have the exact same set of ports open, and both respond in identical > ways, at least at the application level, when sent identical inputs. > In short, at the application layer level, at least, there appears to > be no way to reliably differentiate between the case where the two > IP addresses are being routed to a single common physical machine > (or to a single common virtual OS instance) or to two separate physical > machines (or two separate virtual OS instances). > > Is there any method which can be applied to A and A' over the > Internet and which could reliably differentiate these two possible > cases from one another (i.e. a single common host versus two separate > hosts)? > > If any such method or mechanism exists, I would very much like to know > all of the details thereof. Such a method, if one exists, would > certainly have value in various types of forensic investigations. > > > Regards, > rfg > > > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of differentiating > the two cases described above by looking at application layer responses > for some certain common applications. As far as I know however, it is > not possible to make the desired differentiation on the basis of > application layer responses for most typical network applications, > e.g. various makes and model numbers of servers for HTTP, HTTPS, > SMTP, SSH, DNS, etc. Of course, if I have simply missed something, > and if there is in fact a way to differentiate the two cases on the > basis of responses sent for any of these application protocols, then > I sure would like to know about that too. > _______________________________________________ > 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 Mar 21 22:04:21 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 420ECF6B630 for ; Wed, 21 Mar 2018 22:04:21 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 98EDF6B401 for ; Wed, 21 Mar 2018 22:04:20 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2LM4Gf9023321; Wed, 21 Mar 2018 15:04:16 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2LM4G8h023320; Wed, 21 Mar 2018 15:04:16 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803212204.w2LM4G8h023320@pdx.rh.CN85.dnsmgr.net> Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <4903.1521667183@segfault.tristatelogic.com> To: "Ronald F. Guilmette" Date: Wed, 21 Mar 2018 15:04:16 -0700 (PDT) CC: FreeBSD Net X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 22:04:21 -0000 > > This problem has been preplexing me for ages and ages. I looked at it > again, just briefly, and re-read parts of some potentially relevant > RFCs, just the other day, but frankly, I'm just too ignorant and/or > too stupid to be able to think up a solution, so I'll just drop the > problem description here and see if any of you more knowledgable > people can devise or suggest a solution. > > The Problem: > > Suppose that there exist two IPv4 addresses, A and A'. Both addresses > have the exact same set of ports open, and both respond in identical > ways, at least at the application level, when sent identical inputs. > In short, at the application layer level, at least, there appears to > be no way to reliably differentiate between the case where the two > IP addresses are being routed to a single common physical machine > (or to a single common virtual OS instance) or to two separate physical > machines (or two separate virtual OS instances). > > Is there any method which can be applied to A and A' over the > Internet and which could reliably differentiate these two possible > cases from one another (i.e. a single common host versus two separate > hosts)? > > If any such method or mechanism exists, I would very much like to know > all of the details thereof. Such a method, if one exists, would > certainly have value in various types of forensic investigations. > > > Regards, > rfg > > > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of differentiating > the two cases described above by looking at application layer responses > for some certain common applications. As far as I know however, it is > not possible to make the desired differentiation on the basis of > application layer responses for most typical network applications, > e.g. various makes and model numbers of servers for HTTP, HTTPS, > SMTP, SSH, DNS, etc. Of course, if I have simply missed something, > and if there is in fact a way to differentiate the two cases on the > basis of responses sent for any of these application protocols, then > I sure would like to know about that too. One thing you could look at is the OS finger printing of nmap, that could look for possible things to diffentiate the hosts. Depending on just what the host is there could be other tale tale signs picked up from "forensic" type of data captured with tcpdump while playing known packet sequences against each host at identical time. What you ask I believe could be done, but it non trivial and would require a very good understanding of both forensics and the differing ways that TCP/IP is implemented. One simple thing is a record route of a packet, it might show that the hosts are clearly at differing paths. If the hosts are very different a ssh connect could lead to an answer as it may give a differing answer string: telnet freefall.freebsd.org 22 Trying 2610:1c1:1:6074::16:84... Trying 96.47.72.132... Connected to freefall.freebsd.org. Escape character is '^]'. SSH-2.0-OpenSSH_7.5 FreeBSD-20170804 telnet localhost 22 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_7.2 FreeBSD-20161230 Clearly these are 2 different machines.... It would also be possible to implemented controlled DOS techniques to cause "measureable" load on one IP, and then see if the other IP has a similiar measureable load factor. This does not work well if the DOS technique causes a commond mode issue, but that just fails in the "can not tell" mode. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Wed Mar 21 22:50:13 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FB10F4692E for ; Wed, 21 Mar 2018 22:50:12 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 4AF616CF0C for ; Wed, 21 Mar 2018 22:50:12 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id v21so1370874wmc.1 for ; Wed, 21 Mar 2018 15:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=CH5pWzh0HRFthPJTcKQmp/hbyItl3cFtdX451n+DmS0=; b=b5Gm04tENkcurlGxlSQ49kJX6fwpKDgnA9r7ySo2RgncECL8IfQKc2CIH/TIDbkZRE 4/eQIzl7V5/h2O3GY1xoLcMVyaNc4CAJ6mCgT/o2AxQiYte8TiqgAddualqHu7ovcVuU phhVe1jbETKn5/oeWDJzkZCM7hukG6V8fQtr1ToJJ8vbrsoh0Q9j8ntP3lMIVY4yjhkS KXQUV/7LqQI5Uy1aAspMkyZL14U07OmW67DVU0QaV5/fFRnvbT5V6snAnc2UWU7DZJTl cmTLHUWaHqw/n1f2N4/Jz8YtmY5tmd25pYSvUSJ6Sx14ixxbTmONez5EejyuXWfNn2yw QSIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CH5pWzh0HRFthPJTcKQmp/hbyItl3cFtdX451n+DmS0=; b=EO7ZMhUNLl/6vyGHzoHxFx6p7qNJOrkMeuGHDqcqyfZzrmONnWVddxB3cHWadABvdH 701VBdON45ct/ls8IXf1cR1ShEXso0C1bSXlFBgQE6d7jwSTY6/IKSti27UeTjSv7zJQ xRmRIcfltdXMGWUWPwdS3UJSoOkYVw7gUuP5waBM5cRxPpJvt65MfF7SY3AD6gqGbtsi yfdtfkkSI+VUrboqIxnkVph1hhU280WiIO8P4cLggRpg/J2zIqq139V4Xge8oQGUHEUd LdZpSBykJdvbhXjLrdHrEuE38l+x3MVyrdIc6N8oRnXX8YX/6vtb4eni2hlF8oNYSwNf xwew== X-Gm-Message-State: AElRT7H40zUIWmsFXNkWFbwIkHv4X4/QvLUdGRs0A4yl2gtEO9znswcY zXGxd/msxGzFTFvL0pFd2nqo8APF X-Google-Smtp-Source: AG47ELsz6pW6XOwI8Ky9tf/WrrnsNVMNvkCQKE3V4F0MpK7Hg7+ble5P41N3lDO5z630SMVZLk4lBg== X-Received: by 10.80.201.196 with SMTP id c4mr22717086edi.32.1521672610914; Wed, 21 Mar 2018 15:50:10 -0700 (PDT) Received: from juntos.woohoo.ch ([2a02:168:681c:460:2c94:a00:34cb:9fa1]) by smtp.gmail.com with ESMTPSA id w10sm383221eda.66.2018.03.21.15.50.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 15:50:09 -0700 (PDT) Subject: Re: Multicast/SSDP not working (on VLAN interface) To: freebsd-net@freebsd.org References: <201803210044.w2L0iQww018953@pdx.rh.CN85.dnsmgr.net> From: Andreas Scherrer Message-ID: <0b920e07-8ad3-deb9-a876-9523b18678f7@gmail.com> Date: Wed, 21 Mar 2018 23:50:09 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803210044.w2L0iQww018953@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 22:50:13 -0000 Thank you for bearing with me. On 21.03.18 01:44, Rodney W. Grimes wrote: ... > Show me your full firewall rule set, without that I can only speculate > as to where it is getting blocked, but given your symptoms I highly > suspect the firewall is blocking the packets OUT of your SERVER back > towards the client as they try to go out what ever interface your > default route is on. OK, I see your point. But I obviously forgot to mention some important things. I am sorry for that. First of all, my rules file is 800+ lines, I am not sure how much it helps to throw that at anybody. I agree that this makes it somewhat more likely that the firewall IS the problem, but I do have reason to believe that it is not. I did check on the interface the default route is pointing through: there is no incorrect outgoing traffic. Obviously, if the firewall blocks the traffic, then I expect not to see any. But there are the following rules as well: allow ip4 from me to "table($internal)" out xmit re1\* keep-state allow ip4 from me to "table($broadcast)" out xmit re1\* table($internal) is basically RFC1918 and table($broadcast) contains 224.0.0.0/4 and ff00::/8. To test, I have also added the following rule allow ip4 from me to "table($broadcast)" out xmit but did not see any outgoing multicast traffic from MiniDLNA. Also, when MiniDLNA is running before I add the interface route for 244.0.0.0/4, the VLC test client does NOT discover the MiniDLNA server (despite the route). If, however, the MiniDLNA service is (re)started after the route is in place (but before the test client is running), it does detect the server immediately. I therefore suspect that the "MiniDLNA startup code" does something different when the route is there as compared to when it is not. But I don't know what... I assume it is not related to mrouted (which is NOT running)? Also, again, if setting the interface route for 224.0.0.0/4 absolutely IS required, I will not be able to make my intended setup work. I have multiple interfaces connected to potential clients for MiniDLNA. Best regards andreas From owner-freebsd-net@freebsd.org Wed Mar 21 23:14:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2F33F4C843 for ; Wed, 21 Mar 2018 23:14:01 +0000 (UTC) (envelope-from emorrasg@yahoo.es) Received: from sonic302-21.consmr.mail.ir2.yahoo.com (sonic302-21.consmr.mail.ir2.yahoo.com [87.248.110.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D5936DF6C for ; Wed, 21 Mar 2018 23:14:00 +0000 (UTC) (envelope-from emorrasg@yahoo.es) X-YMail-OSG: PT3kqlUVM1l2ok6Q0isyQjGorAoLTkF5FwioGoD0MC8C1We3SR3oSVqmXy6vFJ7 aKrRx03D3TLoqEjLRaq5_CepPpJde9ku5fuaQEMYOiOdtaXdUIrq89YkAt.8HAnY8sKX856RkC8. M20mmkK2BXx7jiM3XFhyehmQVgJ.BT8nCfYXGTW6jTK_klBoG4Rvu2erkwfIJMGdcCHyWAfE9ooZ T4tV3QCS5ePzH1DkQGZjwlYK6EcNCQRolTJ2j00gMBnOqnegoKNyr52BWH5Q3HQnr09XgTFovXY4 5gnodIUSkntFaCu8lqA.wqMB9EN_71.NsLeqLS3optXfcqXamRoJUp.6qx_TPhk3rNVeirTkwKY4 g9y5kkGUgy6WuQlqFyBZ9hRSZB45R6K0l9s83.AXHQHXqoVz0Asv6qmKss_Y_K_0nUSiQ01cgFfH MwktUZ4p0x3ZwAHBpNdWR3Jx2xafNrRkZS644bViPKVFxEedf0FMkeQ5YxJDFqzC6y7Mj1kSl3Vt IabkVt4kSqXtqrglBwwcIVSpINql.NnSXMmU7f_BGras1Wg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ir2.yahoo.com with HTTP; Wed, 21 Mar 2018 23:13:59 +0000 Received: from 3.red-83-41-214.dynamicip.rima-tde.net (EHLO emorras.eu) ([83.41.214.3]) by smtp420.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 5129413be0673c2307c3b29c6a9aec13 for ; Wed, 21 Mar 2018 22:43:37 +0000 (UTC) Date: Wed, 21 Mar 2018 23:51:39 +0100 From: Eduardo Morras To: freebsd-net@freebsd.org Subject: Re: Same host or different? How can you tell "over the wire"? Message-Id: <20180321235139.1d96e600e76b455703f43f48@yahoo.es> In-Reply-To: <4903.1521667183@segfault.tristatelogic.com> References: <4903.1521667183@segfault.tristatelogic.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 23:14:01 -0000 On Wed, 21 Mar 2018 14:19:43 -0700 "Ronald F. Guilmette" wrote: > > This problem has been preplexing me for ages and ages. I looked at it > again, just briefly, and re-read parts of some potentially relevant > RFCs, just the other day, but frankly, I'm just too ignorant and/or > too stupid to be able to think up a solution, so I'll just drop the > problem description here and see if any of you more knowledgable > people can devise or suggest a solution. > > The Problem: > > Suppose that there exist two IPv4 addresses, A and A'. Both addresses > have the exact same set of ports open, and both respond in identical > ways, at least at the application level, when sent identical inputs. > In short, at the application layer level, at least, there appears to > be no way to reliably differentiate between the case where the two > IP addresses are being routed to a single common physical machine > (or to a single common virtual OS instance) or to two separate > physical machines (or two separate virtual OS instances). > > Is there any method which can be applied to A and A' over the > Internet and which could reliably differentiate these two possible > cases from one another (i.e. a single common host versus two separate > hosts)? > > If any such method or mechanism exists, I would very much like to know > all of the details thereof. Such a method, if one exists, would > certainly have value in various types of forensic investigations. > Perhaps I don't understand the question but: A ping should measure the "distance" to A and A', traceroute works too. If you disable protections (firewalls, ids, etc) you could inject tcp packets with fake ips. Or make a dDoS to one, the other should stay alive. If you go to layer 2 there are mac differences. Take the whois info from both, it will be the same, but you can ask the owner to switch off one of them. If SNMP is enabled and accesible it must show some differences (ethernet mac) > Regards, > rfg > > > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of > differentiating the two cases described above by looking at > application layer responses for some certain common applications. As > far as I know however, it is not possible to make the desired > differentiation on the basis of application layer responses for most > typical network applications, e.g. various makes and model numbers of > servers for HTTP, HTTPS, SMTP, SSH, DNS, etc. Of course, if I have > simply missed something, and if there is in fact a way to > differentiate the two cases on the basis of responses sent for any of > these application protocols, then I sure would like to know about > that too. _______________________________________________ > 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" --- --- Eduardo Morras From owner-freebsd-net@freebsd.org Wed Mar 21 23:30:53 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6149F4DE9C for ; Wed, 21 Mar 2018 23:30:53 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 5BD3F6ED3C for ; Wed, 21 Mar 2018 23:30:52 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id EB4563AEF2 for ; Wed, 21 Mar 2018 16:30:51 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <5AB2D11A.6060605@grosbein.net> Date: Wed, 21 Mar 2018 16:30:51 -0700 Message-ID: <5700.1521675051@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 23:30:53 -0000 In message <5AB2D11A.6060605@grosbein.net>, Eugene Grosbein wrote: >If they respond truly identically, there are no reasons to treat them like >distinct hosts >despite of different IP addresses. Well, for my purposes, it would be inapporpriate to make any such leap of faith. If address A is somehow established to be under the control of a given Bad Actor, then even if address A' is seen to yield essentially identical results at the level of the application layer, this is most certainly -not- an adequate justification for anyone (e.g. me, or anyone else for that matter) to affirmatively assert that A' is under the control of the exact same Bad Actor. Individual IPv4 addresses may often exhibit an identical set of open ports. And the responses provided when sending data to those ports may be "generic" and thus may be actually or virtually identical. This alone is not nearly enough to assert that A' is under the control of the exact same Bad Actor who is in control of A. >And if you have such reason despite they respond truly identically, >then such a reason steams from matters other than their response on requests >to open ports. >In this case you should differentiate them by other means too, not by open >port's responses. Yes... by other means -also-, e.g. DNS. Assume that this has already been done. Assume that two different (and somehow related) FQDNs point to two different IPv4 addreses, A and A'. As we all know, any fool on the Internet can point any FQDN for which he controls the DNS to any bloody address he wants. But any such "pointing", standing alone and by itself, does not -prove- a damn thing about the pointed-at addresses, or about who is -currently- controlling them. (I wish that I had a dollar for every FQDN I had ever come across that resolved to either 127/8 or 10/8, or that pointed to an address that is not currently routed, and which perhaps never has been.) If other data persuasively indicates that address A is under the control of a Bad Actor, and if there appears to be some connection between A and A' (such as some sort of association indicated by the DNS) then if there were a way to also establish that A and A' are both being routed to a single machine, then it could be reliably and persuasively asserted, without fear of contradiction, that A' is also under the control of the same Bad Actor. I would like to be able to make such logical inferences and assertions, which is what prompted my question. From owner-freebsd-net@freebsd.org Wed Mar 21 23:47:30 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25606F4F16E for ; Wed, 21 Mar 2018 23:47:30 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id B59F76F845 for ; Wed, 21 Mar 2018 23:47:28 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 1096A3AEF2 for ; Wed, 21 Mar 2018 16:47:28 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org Subject: Same host or different? How can you tell "over the wire"? Date: Wed, 21 Mar 2018 16:47:27 -0700 Message-ID: <5755.1521676047@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 23:47:30 -0000 "Kurt Buff" wrote: >Do you mean that the application banners for all applications are the >same? A comprehensive scan with nmap shows no differences? Correct. This is the case I was/am asking about. >I know you specified SSH as outside of the application layer, but I >would think if it's even to the point that the same SSH key (or >credentials) work for both machines, and upon login provide the same >hostname in the prompt In case it was not clear, none of the IPv4 addresses that are of interest, or that are relevant to my question, are ones for which *I* posses any type of SSH login credentials. But your question certainly raises an interesting possibility, and an interesting question... one that I myself am not at all equiped or qualified to answer (because I am almost totally ignorant about even the bare mechanics of the SSH protocol): How could one tickle an open SSH port and obtain from it not just its greeting banner (which may be, and often is, rather generic and non-specific) but also so as to get the host's host-specific public key? (Yes, I am indeed displaying an unforgivable level of laziness here. I can and most probably should, and most probably eventually -will- just go off now and read the relevant RFCs, but if anyone wants to save me the trouble, just for this one question, that would be appreciated.) >you'd have to dig and see if the NIC configs >show a difference, or perhaps that there are multiple NICs, or a >single NIC aliased with the IP addresses you're reviewing. Yes. This is yet a different way that the problem might be attacked. I am most interested in that last possibility you mentioned, and specifically I am interested in differentiating that case from all other possible cases. But I am far too ignorant of the relevant protocols to be able to work out a way to solve the problem this way, so if anyone might be willing to explain it to me, in detail, that also would be most appreciated. From owner-freebsd-net@freebsd.org Thu Mar 22 00:11:59 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED6F0F5124D for ; Thu, 22 Mar 2018 00:11:58 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4CC2670D37 for ; Thu, 22 Mar 2018 00:11:57 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 23DFD3AEF2 for ; Wed, 21 Mar 2018 17:11:57 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <201803212204.w2LM4G8h023320@pdx.rh.CN85.dnsmgr.net> Date: Wed, 21 Mar 2018 17:11:56 -0700 Message-ID: <5843.1521677516@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 00:11:59 -0000 In message <201803212204.w2LM4G8h023320@pdx.rh.CN85.dnsmgr.net>, "Rodney W. Grimes" wrote: >One thing you could look at is the OS finger printing of nmap, >that could look for possible things to diffentiate the hosts. Yea, that idea occurred to me. But this solution has the same problem that I just mentioned in another one of my replies in this thread: Even if nmap says that two IP addresses have the exact same OS signature, that is far from enough to assert that they are both under the control of the exact same Bad Actor. You certainly wouldn't want to send someone to prison, or even to after-school detention, based on such limited circumstantial evidence. >Depending on just what the host is there could be other tale >tale signs picked up from "forensic" type of data captured >with tcpdump while playing known packet sequences against >each host at identical time. Such as? I'm all ears. >What you ask I believe could be done, but it non trivial and >would require a very good understanding of both forensics >and the differing ways that TCP/IP is implemented. I like to think that I am a quick learner. Please proceed with the lesson. >One simple thing is a record route of a packet, it might show >that the hosts are clearly at differing paths. Again, not adequate, I think. Not for my purposes. The addresses A and A' might very well be within the same /24, and the routing might thus be identical. Does that prove that both are under the control of the same single guy? I would say not. >If the hosts are very different a ssh connect could >lead to an answer as it may give a differing answer string: >... >SSH-2.0-OpenSSH_7.5 FreeBSD-20170804 >... >SSH-2.0-OpenSSH_7.2 FreeBSD-20161230 Believe me, if the problem were as easy to solve as in this example, I wouldn't even be here asking the questions I'm asking. The question is: What can be reliably deduced when we see this? Address A: SSH-2.0-OpenSSH_7.5 Address A': SSH-2.0-OpenSSH_7.5 i.e. the kind of identical outputs that I posited in my original statement of the problem. >It would also be possible to implemented controlled DOS techniques >to cause "measureable" load on one IP, and then see if the other >IP has a similiar measureable load factor. This also occured to me. Ignoring for the moment the various... and I hope obvious... ethical and legal questions, it isn't even clear to me how this might be made to work, in practice. I did make it a point to look over some online simple-minded tutorials relating to SYN cookies just the other day... not long before starting this thread. I am guessing that the use of those is now quite widespread, and it seemed to me that these (SYN cookies) would render any attempt at (for lack of a better term) "limit probing" non-useful, at least with respect to TCP. But maybe I'm wrong about that. In any case, the ideal solution to my original problem statement would quite certainly -not- involve anything as obtrusive (or as potentially illegal and/or unethical) as pushing any host hard enough to find its capacity limits. Rather, I am still vaguely hoping that there may be something burried deep down in the IP protocol or perhaps even lower (MAC addresses?) that will provide an elegant and minimally impactful solution. Alternatively, if it turns out that there is something.... anmything... that is host-specific and that can be teased out from some commonly used application layer protocol (e.g. an SSH server's public key) then that will probably do quite nicely also. From owner-freebsd-net@freebsd.org Thu Mar 22 00:15:20 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF52CF51818 for ; Thu, 22 Mar 2018 00:15:19 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 613AA70FDB for ; Thu, 22 Mar 2018 00:15:18 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2M0FFpu023792; Wed, 21 Mar 2018 17:15:15 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2M0FFbg023791; Wed, 21 Mar 2018 17:15:15 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803220015.w2M0FFbg023791@pdx.rh.CN85.dnsmgr.net> Subject: Re: Multicast/SSDP not working (on VLAN interface) In-Reply-To: <0b920e07-8ad3-deb9-a876-9523b18678f7@gmail.com> To: Andreas Scherrer Date: Wed, 21 Mar 2018 17:15:15 -0700 (PDT) CC: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 00:15:20 -0000 > Thank you for bearing with me. > > On 21.03.18 01:44, Rodney W. Grimes wrote: > > ... > > > Show me your full firewall rule set, without that I can only speculate > > as to where it is getting blocked, but given your symptoms I highly > > suspect the firewall is blocking the packets OUT of your SERVER back > > towards the client as they try to go out what ever interface your > > default route is on. > > OK, I see your point. But I obviously forgot to mention some important > things. I am sorry for that. > > First of all, my rules file is 800+ lines, I am not sure how much it > helps to throw that at anybody. I agree that this makes it somewhat more > likely that the firewall IS the problem, but I do have reason to believe > that it is not. If your rule set is 800+ lines I highly suspect your doing something in a very non-optimal way. It also leads to be VERY suspeciious that it is infact in your firewall. Try as a very first rules: ipfw add 1 log allow ip from any to 224.0.0.0/4 ipfw add 2 log allow ip from 224.0.0.0/4 to any DO NOT put any restricting clauses on these.. if this makes things work simply move them down a few rules until you find the point at which things stop working. You may want to examine the log, as it would tell you what ipfw thinks the packet path is, and may shed some light on why other things are not happening the way you expect. Also do you have any nat, divert, or other things going on, they can all have an effect on mutlicast packets. > I did check on the interface the default route is pointing through: > there is no incorrect outgoing traffic. > > Obviously, if the firewall blocks the traffic, then I expect not to see any. > > But there are the following rules as well: > > allow ip4 from me to "table($internal)" out xmit re1\* keep-state > allow ip4 from me to "table($broadcast)" out xmit re1\* > > table($internal) is basically RFC1918 and table($broadcast) contains > 224.0.0.0/4 and ff00::/8. > > To test, I have also added the following rule You using an out xmit re1, and that is probably what is NOT happening. What does: route get default show? > > allow ip4 from me to "table($broadcast)" out xmit > > but did not see any outgoing multicast traffic from MiniDLNA. The packet may NOT match the specific out xmit $dgw clause. > Also, when MiniDLNA is running before I add the interface route for > 244.0.0.0/4, the VLC test client does NOT discover the MiniDLNA server > (despite the route). If, however, the MiniDLNA service is (re)started > after the route is in place (but before the test client is running), it > does detect the server immediately. > > I therefore suspect that the "MiniDLNA startup code" does something > different when the route is there as compared to when it is not. That could be, it could also be shutting down its response cause it gets an error from the firewall code saying "permission denied". > But I don't know what... I assume it is not related to mrouted (which is > NOT running)? You should not need mrouted, it does not sound as if your running as a multicast router. > Also, again, if setting the interface route for 224.0.0.0/4 absolutely > IS required, I will not be able to make my intended setup work. I have > multiple interfaces connected to potential clients for MiniDLNA. It should not be required. I run large amounts of OSPF which is a multicast protocol without any mrouted, and given the descriptiong of your topology your only trying to do mutlicast to directly attached machines, not routed multicast. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Thu Mar 22 02:06:13 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72B54F5ADF7 for ; Thu, 22 Mar 2018 02:06:13 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-pl0-x22c.google.com (mail-pl0-x22c.google.com [IPv6:2607:f8b0:400e:c01::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 F335A76308 for ; Thu, 22 Mar 2018 02:06:12 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by mail-pl0-x22c.google.com with SMTP id m22-v6so4354530pls.5 for ; Wed, 21 Mar 2018 19:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ilNzd39eAQIr/htNk2NwgHkyF8yOnr5sGBzrtlKfedI=; b=OY9OXj49wFyjCd1sDJKYZ7IuFmiDneyQ1+gfMA4NfaZZaZDBxk5FCLayPQOeSTpI6f A+U+Ny/tWGwyl+YaYTetgWTgoWVBDumDAgxg1irStzzYdkF8SffNPwvyE3DYs3ogyM7V Qg+v44g0AHfFvUP4SIE/UTH1y9Zp9pjNx2JkjXyVeg9Yod2fC8BD2vG2AiNQoZpvFubF UENpOS66hiFCp2zJWAOmPOEgjY1WjtgAwyZYgeireT4Mi5C+WO+VaBBJKU8tTow2fesW RJJegpr26Wo4+XET+31DvMBTavTc/ZRNS41MY3U6VmZ/cwkvi4u8jncVpdcnFv9HmMsB CAhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ilNzd39eAQIr/htNk2NwgHkyF8yOnr5sGBzrtlKfedI=; b=j5I7tGXrXxWhW5C8YUeDzbToPhCNowDcl488GWtQfHVNlT5joS6ox9X8hLybUQfDu9 veQUKhIuuT2RWvFRDWc3uMMPuH0bAapewZlyfj4qunbR9HwwxeTxviWUukUFO4FWQPii 4Fa2rWojZ4QQ0R8dEmM3GU7bPyH3qOPcdfddIfOLRCPS3rIJVafWTU/dqyRrG4HakNgt a8qc8idRRwubChgQdwlY79UHb1HWAOaaFpYAA2tsylg9IF1bGPunOG91duh2O15yvwIm ROFKb+GcWU+6mRVk7KXRNVRB0+VYIXA7J6GXCu4il9yqmRJpgQCJIP/T2dzr+zDE++iK SIqA== X-Gm-Message-State: AElRT7G60Fz00PXHzRIhEvf1VSs1j5Hbigq6Dwm3U9mxi7hWwKB2RRVf hpr6QRX9gRo+epiB71Uk7rn4+ZwM8HrJZ9MloHFYDQ== X-Google-Smtp-Source: AG47ELtKWVdVLsMxFNvPkCN9dfr+Lvgey3gfiT0tQPDneh0wh0FfiUPaDMgQrvrkCpzeqnmfcpeI12XdM/NukRefFOs= X-Received: by 2002:a17:902:7008:: with SMTP id y8-v6mr23669985plk.395.1521684371617; Wed, 21 Mar 2018 19:06:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.174.20 with HTTP; Wed, 21 Mar 2018 19:06:11 -0700 (PDT) In-Reply-To: <5755.1521676047@segfault.tristatelogic.com> References: <5755.1521676047@segfault.tristatelogic.com> From: Kurt Buff Date: Wed, 21 Mar 2018 19:06:11 -0700 Message-ID: Subject: Re: Same host or different? How can you tell "over the wire"? To: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 02:06:13 -0000 On Wed, Mar 21, 2018 at 4:47 PM, Ronald F. Guilmette wrote: > > "Kurt Buff" wrote: > In case it was not clear, none of the IPv4 addresses that are of interest, > or that are relevant to my question, are ones for which *I* posses any type > of SSH login credentials. > > But your question certainly raises an interesting possibility, and an > interesting question... one that I myself am not at all equiped or > qualified to answer (because I am almost totally ignorant about even > the bare mechanics of the SSH protocol): How could one tickle an open > SSH port and obtain from it not just its greeting banner (which may be, > and often is, rather generic and non-specific) but also so as to get > the host's host-specific public key? > > (Yes, I am indeed displaying an unforgivable level of laziness here. > I can and most probably should, and most probably eventually -will- > just go off now and read the relevant RFCs, but if anyone wants to save > me the trouble, just for this one question, that would be appreciated.) Well, I'm not expert myself, but when I use putty from my Windows machine to talk with an ssh server that it's not seen before, I get a popup talking about the host ssh key which is new to putty., and that happens any time, e.g., the IP address of the machine changes. This query: https://www.google.com/search?q=scan+host+collect+ssh+key&ie=utf-8&oe=utf-8 reveals this tool: http://rc.quest.com/man.php?id=ssh-keyscan%281%29 which might be useful to you, and I do indeed see the man page for it on my box. Kurt From owner-freebsd-net@freebsd.org Thu Mar 22 02:37:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC60BF5E2BA for ; Thu, 22 Mar 2018 02:37:15 +0000 (UTC) (envelope-from kevin@your.org) Received: from mail.your.org (mail.your.org [IPv6:2001:4978:1:2::cc09:3717]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E93C77BF7 for ; Thu, 22 Mar 2018 02:37:15 +0000 (UTC) (envelope-from kevin@your.org) Received: by mail.your.org (Postfix, from userid 1000) id 166AD3C7E7D; Thu, 22 Mar 2018 02:37:14 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on mail.your.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=ham version=3.3.0 Received: from mail.your.org (chi02.mail.your.org [204.9.55.23]) by mail.your.org (Postfix) with ESMTP id 1C5863C7E78; Thu, 22 Mar 2018 02:37:13 +0000 (UTC) X-Virus-Scanned: amavisd-new at example.com Received: from mail.your.org ([204.9.55.23]) by mail.your.org (mail.your.org [204.9.55.23]) (amavisd-new, port 10024) with LMTP id 5L44tL7cXiMQ; Thu, 22 Mar 2018 02:37:11 +0000 (UTC) Received: from [10.10.38.97] (unknown [12.144.188.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTPSA id A326A3C7E73; Thu, 22 Mar 2018 02:37:11 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Same host or different? How can you tell "over the wire"? From: Kevin Day In-Reply-To: <5755.1521676047@segfault.tristatelogic.com> Date: Wed, 21 Mar 2018 19:37:08 -0700 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4DB72389-D167-4152-A15F-4710C54B2E1A@your.org> References: <5755.1521676047@segfault.tristatelogic.com> To: "Ronald F. Guilmette" X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 02:37:16 -0000 > On Mar 21, 2018, at 4:47 PM, Ronald F. Guilmette = wrote: >=20 > But your question certainly raises an interesting possibility, and an > interesting question... one that I myself am not at all equiped or > qualified to answer (because I am almost totally ignorant about even > the bare mechanics of the SSH protocol): How could one tickle an open > SSH port and obtain from it not just its greeting banner (which may = be, > and often is, rather generic and non-specific) but also so as to get > the host's host-specific public key? Does the ssh-keyscan tool do what you want? # ssh-keyscan github.com # github.com:22 SSH-2.0-libssh_0.7.0 github.com ssh-rsa = AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7= PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQq= ZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG= 6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3J= EAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ= =3D=3D Unless you've copied the host ssh keys manually, this will be unique to = the system. From owner-freebsd-net@freebsd.org Thu Mar 22 02:51:07 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D532F5F658 for ; Thu, 22 Mar 2018 02:51:07 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 E8A5D7859A for ; Thu, 22 Mar 2018 02:51:06 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2M2owxl024293; Wed, 21 Mar 2018 19:50:58 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2M2owMf024292; Wed, 21 Mar 2018 19:50:58 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803220250.w2M2owMf024292@pdx.rh.CN85.dnsmgr.net> Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <5843.1521677516@segfault.tristatelogic.com> To: "Ronald F. Guilmette" Date: Wed, 21 Mar 2018 19:50:58 -0700 (PDT) CC: FreeBSD Net X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 02:51:07 -0000 > > In message <201803212204.w2LM4G8h023320@pdx.rh.CN85.dnsmgr.net>, > "Rodney W. Grimes" wrote: > > >One thing you could look at is the OS finger printing of nmap, > >that could look for possible things to diffentiate the hosts. > > Yea, that idea occurred to me. But this solution has the same problem > that I just mentioned in another one of my replies in this thread: > Even if nmap says that two IP addresses have the exact same OS > signature, that is far from enough to assert that they are both > under the control of the exact same Bad Actor. You are not going to prove the "control of the exact same Bad Actor" without a warrant to search and seize. You might prove they are 2 different boxes if the nmap finger print shows a difference, but if they show identical you have proved nothing. > You certainly wouldn't want to send someone to prison, or even to > after-school detention, based on such limited circumstantial evidence. > > >Depending on just what the host is there could be other tale > >tale signs picked up from "forensic" type of data captured > >with tcpdump while playing known packet sequences against > >each host at identical time. > > Such as? > > I'm all ears. At this point I have to state I am not going to do your research work for free. I have given you plenty of free leads to persue. > >What you ask I believe could be done, but it non trivial and > >would require a very good understanding of both forensics > >and the differing ways that TCP/IP is implemented. > > I like to think that I am a quick learner. Please proceed with the > lesson. The rates for lessons in Forensics start at reasonable enough amounts, you can contact me off list if you wish to persue that. ... rest deleted ... -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Thu Mar 22 06:23:59 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7645F6E264 for ; Thu, 22 Mar 2018 06:23:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 3D15782928 for ; Thu, 22 Mar 2018 06:23:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id f19so13774389wmc.0 for ; Wed, 21 Mar 2018 23:23:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=DydWTnHwRE8LHNe24ugE7Mft4ipjr9F0NrlWj3/jyVc=; b=hXHneC1z6dtSAh2da2NcnV2VSRYOm1J0sWe3dc+jfqevFI8Rb7pSlof4QwDWij20fW 6AYcMR2rNv7iPOChm+mOI8kOPaWjND0Eze7ZsXqsH3rv4ems5lbxRcLV4Q1Y4l1KHCfV mXAjqsQEUowOyAe1A1R6pSPOWJtbWhNLqK8t8/IwO/549SqA7JMfl5lPIgexuY6eEi54 lC6zyzQ2AZBEOJzMIHMviTXPvPM0LVfq5YRCV4xJ2J4HIVvm2awvdlddDxOxubX+i+nO BvMAxhNlz0Jn5Uo0KIXYV83UZNoKq1NvTbgIuCC6JK4uL8rKV2ObnR+4O0FI+TH5Qi8F C5qA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=DydWTnHwRE8LHNe24ugE7Mft4ipjr9F0NrlWj3/jyVc=; b=YlyPKmTrC1lbO92oklcptKyRl/OZoP5vO+36emy3IKVWHInHhmGC2Xt0mwvYT6c7SJ dvk9nG8aPUwnXMOHR00jDqrfYN68j+YxFmSAasUz00qohZyR4pbX9NZJzMAqTXp5JvTB kO+7g6zwY2ZOdbKH9kxyeHsW5xL28doH/0TkciaEZ/MopOO4jtkJSLMcNwsbk9hf+itR bpMvyqQU1Z/RR8SPq9nbbEwKy6qp1uydy77wsY78U1Zz/oxlnNb6/s3wZz2QHotWkMzq 8Wf3yTESmOQEsiYPUQbq3w3grti96qTjGu0f4RsFP1aQkktDLdC57yLAiEZO3+c9oPTu zW9A== X-Gm-Message-State: AElRT7GhgWUcG4GbJrL33A3kLIcbm0f8v4j7vRglyPPaBDFCLzbFxrS+ Ib8AHKVuB+kIKvoI7btHJTS7tu3uK6R1oWAPnV8Ph32l X-Google-Smtp-Source: AG47ELsNmBuNQPcycx2eMkR5Vz6Fz6YuBewtK03WyqTqU5nPdM4MM5s+KD3Mcadib+QYkIEYLhqgvWyLS7L0ma0KSEo= X-Received: by 10.28.214.2 with SMTP id n2mr4227018wmg.130.1521699837346; Wed, 21 Mar 2018 23:23:57 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Wed, 21 Mar 2018 23:23:56 -0700 (PDT) From: Adrian Chadd Date: Wed, 21 Mar 2018 23:23:56 -0700 X-Google-Sender-Auth: knVh8f8h5Z9Jz-9HvH0dWL_Qdlo Message-ID: Subject: crash with ipfw nat on mips32 To: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 06:23:59 -0000 hi, I'm updating my freebsd wifi bits in preparation for more work and ... well: ath1: using multicast key search random: harvesting attach, 8 bytes (4 bits) from ath1 .. ipfw ipfw2 initialized, divert loadable, nat loadable, default to accept, logging disabled .. ipfw_nat *** Setting kern.random.harvest.mask=511 kern.random.harvest.mask: 2047 -> 511 *** bringing up loopback .. Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) [ thread pid 11 tid 100010 ] Stopped at 0 db> bt Tracing pid 11 tid 100010 td 0x80673b40 dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 db> Has anyone seen this? FreeBSD 12.0-CURRENT #0 r331092M: Sun Mar 18 23:33:51 PDT 2018 adrian@test-2:/usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work/freebsd/head-embedded/src/mips.mips/sys/DIR-825C1 mips Thanks! -a From owner-freebsd-net@freebsd.org Thu Mar 22 06:36:50 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 980B2D1 for ; Thu, 22 Mar 2018 06:36:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward106j.mail.yandex.net (forward106j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19BCF8343B; Thu, 22 Mar 2018 06:36:49 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback6o.mail.yandex.net (mxback6o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::20]) by forward106j.mail.yandex.net (Yandex) with ESMTP id BF2681805E9B; Thu, 22 Mar 2018 09:36:38 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback6o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id FLYGlaRWFc-acIGCviX; Thu, 22 Mar 2018 09:36:38 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521700598; bh=qpGBmv7TosVfDVhmEBcZUh+f2fxbN4xgcyyLq8ZdLYQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=sCroAmth9sObwS3HDeLHqIxIjzY8UNmvkhY2pJ4AttP7lAkR33j7Mjpqc2dbI8CZR qWShuzaY/3xkVH4xgbwr32enx0OVTrH3Ww3W/Dx7Fl40XzWoZgARQue5eCQn/OC0YW QXSgNMmxO4Ci3++YKVmwlNM/BBUa/ZtCDYvlZtHQ= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ip3Ckwq2Rz-abFiSRYd; Thu, 22 Mar 2018 09:36:37 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521700598; bh=qpGBmv7TosVfDVhmEBcZUh+f2fxbN4xgcyyLq8ZdLYQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=sCroAmth9sObwS3HDeLHqIxIjzY8UNmvkhY2pJ4AttP7lAkR33j7Mjpqc2dbI8CZR qWShuzaY/3xkVH4xgbwr32enx0OVTrH3Ww3W/Dx7Fl40XzWoZgARQue5eCQn/OC0YW QXSgNMmxO4Ci3++YKVmwlNM/BBUa/ZtCDYvlZtHQ= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: crash with ipfw nat on mips32 To: Adrian Chadd , FreeBSD Net References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Thu, 22 Mar 2018 09:35:00 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NY8aTJIpPQWg1JtEeeuj2dby59l3W0Mly" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 06:36:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NY8aTJIpPQWg1JtEeeuj2dby59l3W0Mly Content-Type: multipart/mixed; boundary="W630iZveA2rH0rsnv78q07eAfaQ5fGBlC"; protected-headers="v1" From: "Andrey V. Elsukov" To: Adrian Chadd , FreeBSD Net Message-ID: Subject: Re: crash with ipfw nat on mips32 References: In-Reply-To: --W630iZveA2rH0rsnv78q07eAfaQ5fGBlC Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.03.2018 09:23, Adrian Chadd wrote: > Trap cause =3D 2 (TLB miss (load or instr. fetch) - kernel mode) > [ thread pid 11 tid 100010 ] > Stopped at 0 > db> bt > Tracing pid 11 tid 100010 td 0x80673b40 > dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 > dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 > itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 > softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 > db> Hi, this is not NAT related, it is ipfw's dynamic states. I'm not sure, but this is seems related to ConcurrencyKit. --=20 WBR, Andrey V. Elsukov --W630iZveA2rH0rsnv78q07eAfaQ5fGBlC-- --NY8aTJIpPQWg1JtEeeuj2dby59l3W0Mly Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlqzTpQACgkQAcXqBBDI oXr/owgAkS1Ewsnk2+NuAglvf2RcnsUm1kGAIZ3V0gQlw3/vYAkjGZ8rWZCj+OUP kS6chPLE0Ps4FBOe3TSy2oZdKc/UbpCPi18iEtsAMqCizstW8cTG+u/GiCpD5f3Q eKw7hB18qojEtfbpU1T8CcboP8W+lEKmSDOq4MEOfu3BiHFBHl/jo2uw2yLJtoL5 dCH+50os9SmTuxDHcJ2JIQntQdNc3BW7+a3qa6p9ZjHfTesxb9KNt8HcI3DcMeRE aNhGyHBhsxkkyoW9CBguFVayETQvSKyrI4o1afHBLuox+LG1YweawkQbWk5JfdHr F8JTUTJKpWB8i5uPbpObDjmamo79fQ== =Aneu -----END PGP SIGNATURE----- --NY8aTJIpPQWg1JtEeeuj2dby59l3W0Mly-- From owner-freebsd-net@freebsd.org Thu Mar 22 07:31:25 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3399AF4AD0B for ; Thu, 22 Mar 2018 07:31:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 ACFB085437 for ; Thu, 22 Mar 2018 07:31:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x233.google.com with SMTP id s10so7571089wra.13 for ; Thu, 22 Mar 2018 00:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=O7eggQCYzTCArOQ6F3uuffsVsph3ynIL4Ck8XLM16Ro=; b=SRZXTKk6ftufCo7x1O2a3UbTziTxvUyx2hXlMxhQhNa+ItS6wdcmQ0GkVk9rH0ZCZB n25qPwwACvHgHHS9UqiL/xmxEzUK5jGJXinsxN9pF7Qy/19siM0mWjlquFYtjUD8NW36 RKjDpjuv8w6XDOxcn4KqVi1QtzgLVdtmjr/o7yIKeMOTJARIudehp00MS/4qXkEXfJ/H 42+LXK6kGhu+VnoEQeqfpTsySHHpP1Dvyfp74JJ0NLOnl+Rq9LavWdZ3cSXUqHNTGyO1 JP5lSIcH3fgsTpc+q8Z0bgCtwL3Zy5j6ILQ8JGq+tdssWL3K2IZ9HN8Pgm8yEeato0Us IRMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=O7eggQCYzTCArOQ6F3uuffsVsph3ynIL4Ck8XLM16Ro=; b=gXnPvqHl1aG4JXXboeL2SvEtijQLiCPx0yFFXZskxuPKa05xs1LI7t+FCW39w0KuWf G1s2UbFPr7pjuBQYDNRdIfCtsG8qZwb6RNiMsWXYb3ysK7343LCaD3FD+a/9mLi9YxeA B0vKb/1lqlTt4Gca0IPFOeuGHVI8KjYFw8/iLt+snEjTsaSHt1SxKS6Swp1sMHdp0BAg sF1HMLT0s71nBKKNvrzNvNo0TaRX7dA/Ht/aIB8sKipkCQ6T0Z23NsZayBPXfUU3cqWr V7FGZYBz/2cqm2+8vkBeurf+Q2VNOqpeg8k2hcGeyGBAtnB+RyhzTmqBNUxb4Km/Ukdo Fv3w== X-Gm-Message-State: AElRT7EWSPFwHzjnKUmRfIHeQCrqGHBTg4DAR0GluUATdLDZwuJqcoZ0 e8UvPIF/L2lGF47EZ06lmLADY1j84yywXjm2KEY= X-Google-Smtp-Source: AG47ELv2c0jtq801dM9iB3RAzr0WObdJN+0kEhMKA9SlltNV9BDTndYEeCmgiCLYnx8iSuP+PVqIe5fo+0TrIT0je1I= X-Received: by 10.223.192.3 with SMTP id z3mr10816298wre.177.1521703883494; Thu, 22 Mar 2018 00:31:23 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Thu, 22 Mar 2018 00:31:22 -0700 (PDT) In-Reply-To: References: From: Adrian Chadd Date: Thu, 22 Mar 2018 00:31:22 -0700 X-Google-Sender-Auth: IapSGED6ZGsYdMo8aWcFxxD3JTw Message-ID: Subject: Re: crash with ipfw nat on mips32 To: "Andrey V. Elsukov" Cc: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 07:31:25 -0000 Erk. I'll go see if I can figure out what's going on. Thanks! This is really quite grr-y. -a On 21 March 2018 at 23:35, Andrey V. Elsukov wrote: > On 22.03.2018 09:23, Adrian Chadd wrote: >> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) >> [ thread pid 11 tid 100010 ] >> Stopped at 0 >> db> bt >> Tracing pid 11 tid 100010 td 0x80673b40 >> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 >> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 >> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 >> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 >> db> > > Hi, > > this is not NAT related, it is ipfw's dynamic states. > I'm not sure, but this is seems related to ConcurrencyKit. > > -- > WBR, Andrey V. Elsukov > From owner-freebsd-net@freebsd.org Thu Mar 22 12:54:40 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7315DF64021 for ; Thu, 22 Mar 2018 12:54:40 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::608]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC9BA72E80; Thu, 22 Mar 2018 12:54:39 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback15j.mail.yandex.net (mxback15j.mail.yandex.net [IPv6:2a02:6b8:0:1619::91]) by forward105o.mail.yandex.net (Yandex) with ESMTP id D96C744452AF; Thu, 22 Mar 2018 15:54:28 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback15j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id GioD68jJvL-sM8mqZaX; Thu, 22 Mar 2018 15:54:22 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521723262; bh=72GHHEEEt1fKzID1+xBbvyn0D4C6+64ckhqIzd3hQKo=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=aBCQZHjI10p/aPDaCgLljuy9s3VLwXjzr4heqnAtgBh/9FrT0MPJudektuscDX2Me I9BZpWRXi3TJ5j81GlCCXKiAChCIqCsCd8MpUqxzBKMffT2zE6ws5DVkFphQk1ZWLO 3Oz6aW0KGLtEP1fukjFODPf2z/m6cO6TczgGpxMM= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id fMCdSyq7Zy-sMoGZCnu; Thu, 22 Mar 2018 15:54:22 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521723262; bh=72GHHEEEt1fKzID1+xBbvyn0D4C6+64ckhqIzd3hQKo=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=aBCQZHjI10p/aPDaCgLljuy9s3VLwXjzr4heqnAtgBh/9FrT0MPJudektuscDX2Me I9BZpWRXi3TJ5j81GlCCXKiAChCIqCsCd8MpUqxzBKMffT2zE6ws5DVkFphQk1ZWLO 3Oz6aW0KGLtEP1fukjFODPf2z/m6cO6TczgGpxMM= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: crash with ipfw nat on mips32 To: Adrian Chadd Cc: FreeBSD Net , Olivier Houchard References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> Date: Thu, 22 Mar 2018 15:52:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="D7wjq2T60cjpnN55uKMVIZe4mdWA2Yd1h" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 12:54:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --D7wjq2T60cjpnN55uKMVIZe4mdWA2Yd1h Content-Type: multipart/mixed; boundary="SSs4mKMPOG3AAdIgCve7qa8QazOEEcsXl"; protected-headers="v1" From: "Andrey V. Elsukov" To: Adrian Chadd Cc: FreeBSD Net , Olivier Houchard Message-ID: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> Subject: Re: crash with ipfw nat on mips32 References: In-Reply-To: --SSs4mKMPOG3AAdIgCve7qa8QazOEEcsXl Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.03.2018 10:31, Adrian Chadd wrote: > Erk. I'll go see if I can figure out what's going on. >=20 > Thanks! This is really quite grr-y. >>> Trap cause =3D 2 (TLB miss (load or instr. fetch) - kernel mode) >>> [ thread pid 11 tid 100010 ] >>> Stopped at 0 >>> db> bt >>> Tracing pid 11 tid 100010 td 0x80673b40 >>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 >>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 >>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 >>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 >>> db> >> >> this is not NAT related, it is ipfw's dynamic states. >> I'm not sure, but this is seems related to ConcurrencyKit. It looks like CK doesn't declare support for mips. Probably we need to make compat shim, that uses old implementation for platforms, that are not supported by CK. --=20 WBR, Andrey V. Elsukov --SSs4mKMPOG3AAdIgCve7qa8QazOEEcsXl-- --D7wjq2T60cjpnN55uKMVIZe4mdWA2Yd1h Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlqzpxcACgkQAcXqBBDI oXpkBgf/TIt3+vstFr1ZfJ4mCA6QBvelghU/Gf94I+kwC9/bH1+m0zZNQ3XCUX4A 2JG1i7HNx7uDvIwXxS6m8Y8JpVgaZzQLn9hTo2geHv7XGOpIm/DN68lRGFpbW7iG 2igQfJ4DSRLzjrxXpD4eiaNBdnnOY3BDSkFhsZyxD/KvF9dfRz2RMlWj1WufdVJF Y+B2Ui3XqGNawq4ZOe+PzspIH5Dp8oReCalmMG1mClLW7ahkIVlJ8/6Iae1yQMXL V4t79Drnix3HQSHj3DDlEXULv0OGBRZKtJ4PHHHQPNnORgzTEl5/5peHHJ1+/VdO BODQ13I2qyuVPk0/d/ZcIQRrnRR8NQ== =KYa5 -----END PGP SIGNATURE----- --D7wjq2T60cjpnN55uKMVIZe4mdWA2Yd1h-- From owner-freebsd-net@freebsd.org Thu Mar 22 13:00:08 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4980BF648A2 for ; Thu, 22 Mar 2018 13:00:08 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (kanar.ci0.org [IPv6:2001:bc8:35e6::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sd-123398", Issuer "sd-123398" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BE238732DF; Thu, 22 Mar 2018 13:00:07 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.15.2/8.15.2) with ESMTPS id w2MD02fP065614 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Mar 2018 14:00:02 +0100 (CET) (envelope-from cognet@ci0.org) Received: (from doginou@localhost) by kanar.ci0.org (8.15.2/8.15.2/Submit) id w2MD02d7065613; Thu, 22 Mar 2018 14:00:02 +0100 (CET) (envelope-from cognet@ci0.org) X-Authentication-Warning: kanar.ci0.org: doginou set sender to cognet@ci0.org using -f Date: Thu, 22 Mar 2018 14:00:02 +0100 From: Olivier Houchard To: "Andrey V. Elsukov" Cc: Adrian Chadd , FreeBSD Net Subject: Re: crash with ipfw nat on mips32 Message-ID: <20180322130002.GA65574@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 13:00:08 -0000 On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: > On 22.03.2018 10:31, Adrian Chadd wrote: > > Erk. I'll go see if I can figure out what's going on. > > > > Thanks! This is really quite grr-y. > >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) > >>> [ thread pid 11 tid 100010 ] > >>> Stopped at 0 > >>> db> bt > >>> Tracing pid 11 tid 100010 td 0x80673b40 > >>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 > >>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 > >>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 > >>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 > >>> db> > >> > >> this is not NAT related, it is ipfw's dynamic states. > >> I'm not sure, but this is seems related to ConcurrencyKit. > > It looks like CK doesn't declare support for mips. > Probably we need to make compat shim, that uses old implementation for > platforms, that are not supported by CK. > Hi, mips should be supported by using the compiler builtins, as is riscv. If there is a crash, it is definitively a bug. Can you guys tell me which CK function dies that badly ? Regards, Olivier From owner-freebsd-net@freebsd.org Thu Mar 22 13:58:27 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BBE6F69AEA for ; Thu, 22 Mar 2018 13:58:27 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from mx1.101011010.xyz (mx1.101011010.xyz [94.130.97.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.101011010.xyz", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBFD475D3A for ; Thu, 22 Mar 2018 13:58:26 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: by mx1.101011010.xyz with ESMTPS id w2MDwI0o063422 for on Thu, 22 Mar 2018 15:58:18 +0200 (EET) X-Authentication-Warning: mx1.101011010.xyz: Host lan.relay.xx [192.168.210.25] claimed to be relay.xx Received: on behalf of honored client by relay.xx with ESMTPS id w2MDvLQG096620 for on Thu, 22 Mar 2018 15:57:22 +0200 (EET) From: "Zeus Panchenko" To: Subject: ether <-> wlan failover still is broken (was: is lagg (re+wlan) working on 11.0-RELEASE?) In-reply-to: Your message of Tue, 18 Oct 2016 14:43:13 +0300 <20161018144313.45827@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.6; nil; GNU Emacs 25.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2018 15:57:21 +0200 Message-ID: <20180322155721.96618@relay.xx> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 13:58:27 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, while having no any problem with separate (lagg less) mode, when I use ether or wlan without aggregating, I am still experiencing severe problem with ether <-> wlan failover after upgrade to 11.1 I decided to give another try to the handbook Example= 30.3. https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-la= gg-wired-and-wireless it still does *not* work for me after wlan MAC address change (to the one of the ethernet as it's described= in the handbook), wpa_supplicant becomes unable to associate with AP > uname -a FreeBSD 11.1-RELEASE-p8 #0 > pciconf -lv ath0@pci0:3:0:0: class=3D0x028000 card=3D0x1785103c chip=3D0x0032168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Qualcomm Atheros' device =3D 'AR9485 Wireless Network Adapter' class =3D network re0@pci0:7:0:0: class=3D0x020000 card=3D0x3387103c chip=3D0x816810ec rev=3D= 0x06 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll= er' class =3D network subclass =3D ethernet does anybody else face same trouble, please? =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrO2QQAKCRCveOk+D/ej KrUjAJoCx6H9QgcJH97lMklyQZfOy0PrnQCggDki8cJvqdQl+mgWCLkNGePC1Fc=3D =3DvSkJ =2D----END PGP SIGNATURE----- From owner-freebsd-net@freebsd.org Thu Mar 22 14:03:23 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0C84F6A35D for ; Thu, 22 Mar 2018 14:03:23 +0000 (UTC) (envelope-from snar@snar.spb.ru) Received: from staff.retn.net (staff.retn.net [IPv6:2a02:2d8:0:20ff:232a::8]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE7B76383 for ; Thu, 22 Mar 2018 14:03:23 +0000 (UTC) (envelope-from snar@snar.spb.ru) Received: from staff.retn.net (staff.retn.net [IPv6:2a02:2d8:0:20ff:232a::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: snarspb@) by staff.retn.net (Postfix) with ESMTPSA id 25010A82B; Thu, 22 Mar 2018 17:02:38 +0300 (MSK) Date: Thu, 22 Mar 2018 17:02:33 +0300 From: Alexandre Snarskii To: "Ronald F. Guilmette" Cc: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? Message-ID: <20180322140233.GA79266@staff.retn.net> References: <4903.1521667183@segfault.tristatelogic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4903.1521667183@segfault.tristatelogic.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 14:03:23 -0000 On Wed, Mar 21, 2018 at 02:19:43PM -0700, Ronald F. Guilmette wrote: [...] > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of differentiating > the two cases described above by looking at application layer responses > for some certain common applications. As far as I know however, it is > not possible to make the desired differentiation on the basis of > application layer responses for most typical network applications, > e.g. various makes and model numbers of servers for HTTP, HTTPS, > SMTP, SSH, DNS, etc. Of course, if I have simply missed something, > and if there is in fact a way to differentiate the two cases on the > basis of responses sent for any of these application protocols, then > I sure would like to know about that too. DNS: if both A and A' running open recursive DNS servers (bad idea in modern internet, but..) it's possible to use TTL field to differentiate. Scenario: create some DNS record with good enough TTL of one hour. Ask A about this record, get answer with TTL = 3600. Wait for ten seconds, then ask A' about the same record. If received TTL is about 3590 - it's really likely that A and A' is the same host. From owner-freebsd-net@freebsd.org Thu Mar 22 14:27:28 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AD55F6C13D for ; Thu, 22 Mar 2018 14:27:28 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward106o.mail.yandex.net (forward106o.mail.yandex.net [37.140.190.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90C1C77526 for ; Thu, 22 Mar 2018 14:27:27 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback20j.mail.yandex.net (mxback20j.mail.yandex.net [IPv6:2a02:6b8:0:1619::114]) by forward106o.mail.yandex.net (Yandex) with ESMTP id 85114784C83; Thu, 22 Mar 2018 17:27:18 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback20j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 8MtwvClvmd-RIXONjV6; Thu, 22 Mar 2018 17:27:18 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521728838; bh=gsB+bqzxWcndm30hmJa98VGE7QJYQQecO5ZZt0DkreM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=SDpyrT9nTKh4reQ0acaNTCajrJf7V7Jhvg5Dz9f1hffgbeG3y5sKQXBi8SLUmf9SN AneIBCk5T9Tbnu9rlmL6+sAkg8YQ6by170Vdj9Ky7ZqAaB/jccDl8X7NihcuWWCfrz XNs9tF/SqPTmpbHxlgPwELxJ/Xg6/9XKKBfzlqhE= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id bEl5BVhLcC-RHoGYDmH; Thu, 22 Mar 2018 17:27:17 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1521728837; bh=gsB+bqzxWcndm30hmJa98VGE7QJYQQecO5ZZt0DkreM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ZvS9snDRqj4fV/RdAifqsDUyQ0ctbeil7Onwuy0wDenGs3rvXUaBBh+1xuL0eP0oU BaQtQTDiPKpszN9j72kr3lGA2/62hvMCTFJdjkbsuCQ0PyxFe47U+W42c4+c2QKE2T my01nE2dE2X2nVOpdPWhFqrvpWvmsu+hDyesi2w4= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: ether <-> wlan failover still is broken To: Zeus Panchenko , freebsd-net@freebsd.org References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> Date: Thu, 22 Mar 2018 17:25:34 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180322155721.96618@relay.xx> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="A3y0jkqQQ4xk9HJeCyIEbhcMxlCKgtPb5" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 14:27:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --A3y0jkqQQ4xk9HJeCyIEbhcMxlCKgtPb5 Content-Type: multipart/mixed; boundary="iI0ENd9NmzPnU4P4hxO0Umr8OogWbVlG2"; protected-headers="v1" From: "Andrey V. Elsukov" To: Zeus Panchenko , freebsd-net@freebsd.org Message-ID: <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> Subject: Re: ether <-> wlan failover still is broken References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> In-Reply-To: <20180322155721.96618@relay.xx> --iI0ENd9NmzPnU4P4hxO0Umr8OogWbVlG2 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.03.2018 16:57, Zeus Panchenko wrote: > hi, >=20 > while having no any problem with separate (lagg less) mode, when I use > ether or wlan without aggregating, I am still experiencing severe probl= em > with ether <-> wlan failover >=20 > after upgrade to 11.1 I decided to give another try to the handbook Exa= mple 30.3. > https://www.freebsd.org/doc/handbook/network-aggregation.html#networkin= g-lagg-wired-and-wireless >=20 > it still does *not* work for me >=20 > after wlan MAC address change (to the one of the ethernet as it's descr= ibed in > the handbook), wpa_supplicant becomes unable to associate with AP It will work, if you will change ethernet's MAC address to one, what wlan interface have. --=20 WBR, Andrey V. Elsukov --iI0ENd9NmzPnU4P4hxO0Umr8OogWbVlG2-- --A3y0jkqQQ4xk9HJeCyIEbhcMxlCKgtPb5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlqzvN4ACgkQAcXqBBDI oXrBjwgAu5wsp5rY/rSP59N+kjZnSAqddD+T+JOvPRyTclGzKv7ShmM+ykTadFqt Um7DgiBxMeJExqHhC681NE9k3E6TkFT4ehhVmi9aPfkIn15jtuUlm67JSlZ4wlcW k3HqkMUPt3zRVmUY9u4eF+4Oh/2SIiBIGQEO9e6M/TSXtrzD23VfWoc2cFkQ0bG4 iyr9U242JZZQd0xA4cxRYeM9HnF0d0e+vKzv9Ojdxf8+XpbAG8zeVXuFzy1dheJT DgOxRBjDKizGCSiO18o7GvW7e/47UW2KFgxl+YCrg8WbqWYzQitUWKls/N2Ne7Sm Vwxx8+EiGXi4F/xpXIRkA0yDRRviwg== =xphI -----END PGP SIGNATURE----- --A3y0jkqQQ4xk9HJeCyIEbhcMxlCKgtPb5-- From owner-freebsd-net@freebsd.org Thu Mar 22 14:54:23 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D316F4ACA3 for ; Thu, 22 Mar 2018 14:54:23 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from mx1.101011010.xyz (mx1.101011010.xyz [94.130.97.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.101011010.xyz", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB39978DA7 for ; Thu, 22 Mar 2018 14:54:22 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: by mx1.101011010.xyz with ESMTPS id w2MEsKUg066405 on Thu, 22 Mar 2018 16:54:20 +0200 (EET) X-Authentication-Warning: mx1.101011010.xyz: Host lan.relay.xx [192.168.210.25] claimed to be relay.xx Received: on behalf of honored client by relay.xx with ESMTPS id w2MErnKa011600 on Thu, 22 Mar 2018 16:53:50 +0200 (EET) From: "Zeus Panchenko" To: "Andrey V. Elsukov" Cc: Subject: Re: ether <-> wlan failover still is broken In-reply-to: Your message of Thu, 22 Mar 2018 17:25:34 +0300 <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.6; nil; GNU Emacs 25.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2018 16:53:49 +0200 Message-ID: <20180322165349.11598@relay.xx> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 14:54:23 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrey V. Elsukov wrote: >=20 > It will work, if you will change ethernet's MAC address to one, what > wlan interface have. >=20 in my previous attempts it was working this way *only* when interface was in promiscious mode but I'll try it again, thanks =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrPDfQAKCRCveOk+D/ej KmpfAJ4p2DAn9hAVJjc2KqS1UdS+eN8hNgCfXrzZzefzSrBa6XquJhDru+hBBjU=3D =3D1maj =2D----END PGP SIGNATURE----- From owner-freebsd-net@freebsd.org Thu Mar 22 15:30:04 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA2BEF4E8DE for ; Thu, 22 Mar 2018 15:30:04 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 53ADC7AEA7 for ; Thu, 22 Mar 2018 15:30:04 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2MFTuEK099653 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 22 Mar 2018 16:29:56 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: zeus@ibs.dn.ua Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w2MFTpVN075376 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Mar 2018 22:29:51 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: ether <-> wlan failover still is broken To: Zeus Panchenko , freebsd-net@freebsd.org References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> From: Eugene Grosbein Message-ID: <5AB3CBEA.607@grosbein.net> Date: Thu, 22 Mar 2018 22:29:46 +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: <20180322155721.96618@relay.xx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 15:30:05 -0000 22.03.2018 20:57, Zeus Panchenko wrote: > while having no any problem with separate (lagg less) mode, when I use > ether or wlan without aggregating, I am still experiencing severe problem > with ether <-> wlan failover > > after upgrade to 11.1 I decided to give another try to the handbook Example 30.3. > https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless > > it still does *not* work for me > > after wlan MAC address change (to the one of the ethernet as it's described in > the handbook), wpa_supplicant becomes unable to associate with AP > >> uname -a > FreeBSD 11.1-RELEASE-p8 #0 > >> pciconf -lv > ath0@pci0:3:0:0: class=0x028000 card=0x1785103c chip=0x0032168c rev=0x01 hdr=0x00 > vendor = 'Qualcomm Atheros' > device = 'AR9485 Wireless Network Adapter' > class = network > re0@pci0:7:0:0: class=0x020000 card=0x3387103c chip=0x816810ec rev=0x06 hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' > class = network > subclass = ethernet > > > does anybody else face same trouble, please? lagg uses fabricated MAC by default and your WiFi connection does not seem like that. You should try forcing lagg to use MAC of wireless card instead of fabricated one: ifconfig lagg0 ether $(ifconfig wlan0 | awk '/hwaddr/ {print $2}') From owner-freebsd-net@freebsd.org Thu Mar 22 15:38:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7269F4F662 for ; Thu, 22 Mar 2018 15:38:25 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from mx1.101011010.xyz (mx1.101011010.xyz [94.130.97.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.101011010.xyz", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 698737B84F for ; Thu, 22 Mar 2018 15:38:24 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: by mx1.101011010.xyz with ESMTPS id w2MFcM3k068714 on Thu, 22 Mar 2018 17:38:23 +0200 (EET) X-Authentication-Warning: mx1.101011010.xyz: Host lan.relay.xx [192.168.210.25] claimed to be relay.xx Received: on behalf of honored client by relay.xx with ESMTPS id w2MFbqmR022715 on Thu, 22 Mar 2018 17:37:53 +0200 (EET) From: "Zeus Panchenko" To: "Andrey V. Elsukov" Cc: Subject: ether wlan lagg works only with hint.ath.0.macaddr set (was: ether <-> wlan failover still is broken) In-reply-to: Your message of Thu, 22 Mar 2018 17:25:34 +0300 <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.6; nil; GNU Emacs 25.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2018 17:37:52 +0200 Message-ID: <20180322173752.22713@relay.xx> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 15:38:26 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrey V. Elsukov wrote: >=20 > It will work, if you will change ethernet's MAC address to one, what > wlan interface have. >=20 yes, for me it works *only* if the interface is in promiscious mode, just have checked BUT! what finally helped me is this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207#c13 /boot/loader.conf hint.ath.0.macaddr=3D"MAC:ADDRESS:OF:THE:ETHERNET:INTERFACE" =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrPN0AAKCRCveOk+D/ej KqWqAKCd7GWqyXLMZtLWtOuWfR+eOVD6OQCg11ZcsR5SIsb5phXu3resUgTRnO0=3D =3Dy2sk =2D----END PGP SIGNATURE----- From owner-freebsd-net@freebsd.org Thu Mar 22 15:40:25 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 988D0F4F992 for ; Thu, 22 Mar 2018 15:40:25 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from mx1.101011010.xyz (mx1.101011010.xyz [94.130.97.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.101011010.xyz", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EC817BB0F for ; Thu, 22 Mar 2018 15:40:24 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: by mx1.101011010.xyz with ESMTPS id w2MFeN27068795 on Thu, 22 Mar 2018 17:40:23 +0200 (EET) X-Authentication-Warning: mx1.101011010.xyz: Host lan.relay.xx [192.168.210.25] claimed to be relay.xx Received: on behalf of honored client by relay.xx with ESMTPS id w2MFdYUl023274 on Thu, 22 Mar 2018 17:39:34 +0200 (EET) From: "Zeus Panchenko" To: "Eugene Grosbein" Cc: Subject: Re: ether <-> wlan failover still is broken In-reply-to: Your message of Thu, 22 Mar 2018 22:29:46 +0700 <5AB3CBEA.607@grosbein.net> References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> <5AB3CBEA.607@grosbein.net> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.6; nil; GNU Emacs 25.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2018 17:39:34 +0200 Message-ID: <20180322173934.23272@relay.xx> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 15:40:25 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eugene Grosbein wrote: >=20 > You should try forcing lagg to use MAC of wireless card instead of fabric= ated one: > ifconfig lagg0 ether $(ifconfig wlan0 | awk '/hwaddr/ {print $2}') >=20 as I wrote in previous message, it works *only* when interface is in promiscious mode ... alas =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrPONQAKCRCveOk+D/ej KlaJAJ98/YNjbI1XZwsn3RGHKP0Of/mfhACg7CgYCHpSR6e7NjG4CGLxMl2pV5Y=3D =3D+aRw =2D----END PGP SIGNATURE----- From owner-freebsd-net@freebsd.org Thu Mar 22 15:42:57 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 812C5F4FEC0 for ; Thu, 22 Mar 2018 15:42:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 2E0FF7BF0E for ; Thu, 22 Mar 2018 15:42:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 2180971805E; Thu, 22 Mar 2018 10:11:25 -0500 (CDT) Subject: Re: Same host or different? How can you tell "over the wire"? To: Alexandre Snarskii , "Ronald F. Guilmette" Cc: FreeBSD Net References: <4903.1521667183@segfault.tristatelogic.com> <20180322140233.GA79266@staff.retn.net> From: Valeri Galtsev Message-ID: <4ce048ad-873e-795e-aae0-8d795d9bb85c@kicp.uchicago.edu> Date: Thu, 22 Mar 2018 10:11:24 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180322140233.GA79266@staff.retn.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 15:42:57 -0000 On 03/22/18 09:02, Alexandre Snarskii wrote: > On Wed, Mar 21, 2018 at 02:19:43PM -0700, Ronald F. Guilmette wrote: > [...] >> P.S. It is my assumption that the kind of thing I'm looking for, if >> it exists at all, will be found somewhere below the application layer. >> I do not rule out however that there may be some way of differentiating >> the two cases described above by looking at application layer responses >> for some certain common applications. As far as I know however, it is >> not possible to make the desired differentiation on the basis of >> application layer responses for most typical network applications, >> e.g. various makes and model numbers of servers for HTTP, HTTPS, >> SMTP, SSH, DNS, etc. Of course, if I have simply missed something, >> and if there is in fact a way to differentiate the two cases on the >> basis of responses sent for any of these application protocols, then >> I sure would like to know about that too. > > DNS: if both A and A' running open recursive DNS servers (bad idea in > modern internet, but..) it's possible to use TTL field to differentiate. > Scenario: create some DNS record with good enough TTL of one hour. Ask A > about this record, get answer with TTL = 3600. Wait for ten seconds, then > ask A' about the same record. If received TTL is about 3590 - it's really > likely that A and A' is the same host. > If A and A' do resolve beyond their SOA for clients outside of their domain. That was vulnerable for abuse, and hardly anybody does that these days. Am I missing something? Valeri > _______________________________________________ > 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" > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-net@freebsd.org Thu Mar 22 16:09:15 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 409E5F52343 for ; Thu, 22 Mar 2018 16:09:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 AB08F7CF54 for ; Thu, 22 Mar 2018 16:09:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id 139so17220160wmn.2 for ; Thu, 22 Mar 2018 09:09:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jkfXRQ+oohWvjKJnYcON2Nxw/2TjKrCfKvEC4f8nqeM=; b=Ea8OnTuGmaH96MNMdxJFCYCBXO81Vy6Qi4U6qWpH19CTKDpUijPkSHrea+mjjKargf tfvC97R1EjIaf4t3ouhMnaprE66tqN3a+S1SxCn3GjOpTl7kpor9975bMCGdK1Z9qguf 7tn/olNfdSoyeC+gDH+8HG79uv8PdiHXYs5BjgTL0h9HfhZdpliK7nPBIpTq8I9gbmYA msAW9DRFL92GTRw+tqsdR9uTGPHNIJLyLA0XGTDIEJv26Xx/8kTfR93W3eR7uVX4/w5B LaI1z7PN8x82wQTejEdHP7W5uNLiTUDM7ety1fvl/StmKFzNyet5E64lv4xSfFM24jV7 ahCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jkfXRQ+oohWvjKJnYcON2Nxw/2TjKrCfKvEC4f8nqeM=; b=rsysD2CGWWEy3F3CID+4iQL2EJ/YbbGb4J67s63PRT9fiQ81Cj6I4BlcNcMg26Shgh HNuUxq2VKdXJuwH/mpLzUvFLs7fUwVRjDOwa+ON+rl8YTfZoOvk50r/wqeGVRLW8nPPx SwErv90cJA0HMInc91t0wD6a8dYYmsLtfAhO7GzeqIRW7u7njq/93fY0+hmDJnfgy1e8 jxkHaO5bLL0DM+84lGTefdQ8d0kJJs9+4wUF3qe2HoSumUuv5ryWm8pfWPXmz8HIyHYm 60ScxSq/jbFHwlQ/nsIFPQ93sSuB++HNzdp64mnq0XWB47ACRrs8sigxap4c0pmwi//U zaZQ== X-Gm-Message-State: AElRT7HjDifVwPW30sf/zjc3JWYQaCJqxdwM8UEgABPhtWiEf3mI3pqg QccLgo8XsprwMUPB8EpUyW5JylPbP57aYVVGr5I= X-Google-Smtp-Source: AG47ELu0cFc7k6Ylnok4cQnhf0zwfFdP3Dw4aouYPGbIeJ2TIdjtbBFDfxrcki71IfZUdaQfge9spKJTAgcOs1lJUV4= X-Received: by 10.28.214.2 with SMTP id n2mr5689288wmg.130.1521734953528; Thu, 22 Mar 2018 09:09:13 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Thu, 22 Mar 2018 09:09:12 -0700 (PDT) In-Reply-To: <20180322130002.GA65574@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> From: Adrian Chadd Date: Thu, 22 Mar 2018 09:09:12 -0700 X-Google-Sender-Auth: D5nAQsK2uRUGysQGYA253ivD9xU Message-ID: Subject: Re: crash with ipfw nat on mips32 To: Olivier Houchard Cc: "Andrey V. Elsukov" , FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 16:09:15 -0000 I dunno yet; this is a very embedded mips74k box. :) -a On 22 March 2018 at 06:00, Olivier Houchard wrote: > On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: >> On 22.03.2018 10:31, Adrian Chadd wrote: >> > Erk. I'll go see if I can figure out what's going on. >> > >> > Thanks! This is really quite grr-y. >> >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) >> >>> [ thread pid 11 tid 100010 ] >> >>> Stopped at 0 >> >>> db> bt >> >>> Tracing pid 11 tid 100010 td 0x80673b40 >> >>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 >> >>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 >> >>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 >> >>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 >> >>> db> >> >> >> >> this is not NAT related, it is ipfw's dynamic states. >> >> I'm not sure, but this is seems related to ConcurrencyKit. >> >> It looks like CK doesn't declare support for mips. >> Probably we need to make compat shim, that uses old implementation for >> platforms, that are not supported by CK. >> > > Hi, > > mips should be supported by using the compiler builtins, as is riscv. If there > is a crash, it is definitively a bug. Can you guys tell me which CK > function dies that badly ? > > Regards, > > Olivier From owner-freebsd-net@freebsd.org Thu Mar 22 16:09:40 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A99CF523FA for ; Thu, 22 Mar 2018 16:09:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (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 F3AD37CF98 for ; Thu, 22 Mar 2018 16:09:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x22f.google.com with SMTP id z73so9282787wrb.0 for ; Thu, 22 Mar 2018 09:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=go1kXLo0UQvyS6x4/ZE9HQkSpZ9AsiqQkxU3AObE+EA=; b=OKfsR8Gnvr1YQoHqS4oPRQa9sL9SAzaG6UDQNchWRdLoPlfA58A8emCUMtPCHt0guh cwsyBp56+Q3C0OvXEFwOCnYoYHT7ZwB1Z6Upn1dpIRPj87UQqu+Hui/IP29sgLzBNkTF rsPTHiVfeMavGJyY/2wPxscH7ZjfEgkGPqtVUJhZ6rOKn6T1aukdEofnxgHIyQeoBugu YSCWHn/UfN32pmswm+NSu+IPeZi975iJ4QP/DLZvFBa6cuZOsrMTfYHpBc/iprnIiLAl 0mUswX1mJCTWH4WzLjuFW1Pah72pgWRs8/DOL6lT/Oa8aEpglPz3cM8/ptBEKGiiJ5s9 u4tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=go1kXLo0UQvyS6x4/ZE9HQkSpZ9AsiqQkxU3AObE+EA=; b=oO5DWEalRCXDB4aMEozmqhAPt9aWUhoWd0c6S9vu/wj/tvm4xh1Wm+gXFF7ff3RLD2 XHm5vwwz16+dG7PnqlwjJPstW3acRBJEYHuch6EN5+0jnKH0smOZ4OO5Yu9l96sJIMMG 8+LvwUZoRhU5kaz6BJ31k+HzPqmjOxPP3XVU3ds195S7JIo5mqm4k19kuPfMAnQbno/v KqOz8+DhNBE1/vSDmj7UGyXDOVdBxk6ArsIvIfv0rooxpqCrkYcSsbr3u/Ckkd94UgXa g58xUxZcwuJ3aE4TIF1q2IQOQFz9FxCT6urszxc2+gbcC4SSaw7SQ5V2iEhMMiqQhK1t 20rw== X-Gm-Message-State: AElRT7HG2aH8+wLjUtwecH9X/V6/Bcc2YUUNwsXWo4XuFgD80QNw+4Hc tV5tzBbkXdZ/0+kdcFIEq6wxYBmRiYevFohEP1N2Cw== X-Google-Smtp-Source: AG47ELtm55EPmlY4MVXHeFP+fffcv5mOSoSBfxWMan8xOYXSA+12tHt6h3VfOlVmkr/jQBQvTM/92e9oewz4D1sJzp0= X-Received: by 10.223.138.214 with SMTP id z22mr19724430wrz.39.1521734978885; Thu, 22 Mar 2018 09:09:38 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Thu, 22 Mar 2018 09:09:37 -0700 (PDT) In-Reply-To: References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> From: Adrian Chadd Date: Thu, 22 Mar 2018 09:09:37 -0700 X-Google-Sender-Auth: xbTlb_ZF0j8tYTtJAANIaySIOR4 Message-ID: Subject: Re: crash with ipfw nat on mips32 To: Olivier Houchard Cc: "Andrey V. Elsukov" , FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 16:09:40 -0000 oh and xcompiled with gcc-6.x . -a On 22 March 2018 at 09:09, Adrian Chadd wrote: > I dunno yet; this is a very embedded mips74k box. :) > > > -a > > On 22 March 2018 at 06:00, Olivier Houchard wrote: >> On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: >>> On 22.03.2018 10:31, Adrian Chadd wrote: >>> > Erk. I'll go see if I can figure out what's going on. >>> > >>> > Thanks! This is really quite grr-y. >>> >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) >>> >>> [ thread pid 11 tid 100010 ] >>> >>> Stopped at 0 >>> >>> db> bt >>> >>> Tracing pid 11 tid 100010 td 0x80673b40 >>> >>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 >>> >>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 >>> >>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 >>> >>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 >>> >>> db> >>> >> >>> >> this is not NAT related, it is ipfw's dynamic states. >>> >> I'm not sure, but this is seems related to ConcurrencyKit. >>> >>> It looks like CK doesn't declare support for mips. >>> Probably we need to make compat shim, that uses old implementation for >>> platforms, that are not supported by CK. >>> >> >> Hi, >> >> mips should be supported by using the compiler builtins, as is riscv. If there >> is a crash, it is definitively a bug. Can you guys tell me which CK >> function dies that badly ? >> >> Regards, >> >> Olivier From owner-freebsd-net@freebsd.org Thu Mar 22 16:10:55 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27EB2F52608 for ; Thu, 22 Mar 2018 16:10:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 9964A7D0E3 for ; Thu, 22 Mar 2018 16:10:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id t7so17021421wmh.5 for ; Thu, 22 Mar 2018 09:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=J2T/I/Ja2ATJv3iBSHByjokL46LlJruSGmvCJveXft8=; b=lNNBOxw2084QPI//GFJOcaN86Wx7lr087Jtn3IDntczQmlLIm9kspK8aanJ5cHicbg pcNkNdvGJdKfSfG9Fb8HGTsn9GIaXvQQ4PidYph1rfc9xoGx9l1ddrhrcd9nZuKtgZoh Ylmanzv+PWLFUkgrHZHLiuh9cm/zhlaQO4QKxlp6S4MV5ulueRqhazGypVsZLoozm+Xy A3OkrUDiY7VodQiFHTML34F0FFADcSzvAt3aoUj9oeZWk6V2yt/AASBeAqFWGKybXGys D99Ece73oqIAUUaCwjwxDnLBaN6R7ONId+L3/vDWZhwMrJUutGRP1yzFaWUD2SqDRpew +pwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=J2T/I/Ja2ATJv3iBSHByjokL46LlJruSGmvCJveXft8=; b=NocyQQYS1Sv+3W2FFf47wQqLCjt/q1oI38ImMupLakvn7XMUn8gLwaDY/qLbrh5Ab5 VZxUMN8TRlHC4bMFPgoK0XTDA62N+OWi/zwT58lunc9WBZ4xX8GRk8ndS2+pKIfOaJNS H2Ng8F+ka5JIAniGc7ypvM3DZktd+Gzy1bq8KSmbujHwJILzp1ssDcOjtQEflMRJ+10O GxJbZPqXvXzIynt+1lvK3lxeqLBwnrptjnRkx5eBoG7y2oOvSUlw3c97JT37TTYFIVqy S7qyGwvku8L0Dq6XS9uQsBZb0AeJrcU+vXaJY+oqqQ+IeHFVRV0EXC8QwYK8AsEykp76 XdSg== X-Gm-Message-State: AElRT7F+3jqPnKwk9ccHaP49Zj8ULXNAF+xh4pZgsATum5G/+P4QYsvM DIDc5F+0DrQVEkKPKWDnSPz5rRG6uBMJ756yu7I= X-Google-Smtp-Source: AG47ELvvt/VAoxT/XQUL0EGnIJWvGYklIfGDvaPmlqiKcxmANJWTnNsmULcEF9xNyi24SDi8o5QF+GdlSeCllHbBPSs= X-Received: by 10.28.105.19 with SMTP id e19mr6365404wmc.3.1521735053559; Thu, 22 Mar 2018 09:10:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.4.12 with HTTP; Thu, 22 Mar 2018 09:10:52 -0700 (PDT) In-Reply-To: <20180322173752.22713@relay.xx> References: <20161018144313.45827@relay.ibs.dn.ua> <20180322155721.96618@relay.xx> <32531070-e38e-00ec-69fd-79330050b044@yandex.ru> <20180322173752.22713@relay.xx> From: Adrian Chadd Date: Thu, 22 Mar 2018 09:10:52 -0700 Message-ID: Subject: Re: ether wlan lagg works only with hint.ath.0.macaddr set (was: ether <-> wlan failover still is broken) To: Zeus Panchenko Cc: "Andrey V. Elsukov" , FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 16:10:55 -0000 Hi, I keep telling people that right now it's not something I at least have time to fix up. :) -a On 22 March 2018 at 08:37, Zeus Panchenko wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Andrey V. Elsukov wrote: >> >> It will work, if you will change ethernet's MAC address to one, what >> wlan interface have. >> > > yes, for me it works *only* if the interface is in promiscious mode, > just have checked > > BUT! what finally helped me is this: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207#c13 > > /boot/loader.conf > > hint.ath.0.macaddr="MAC:ADDRESS:OF:THE:ETHERNET:INTERFACE" > > - -- > Zeus V. Panchenko jid:zeus@im.ibs.dn.ua > IT Dpt., I.B.S. LLC GMT+2 (EET) > -----BEGIN PGP SIGNATURE----- > > iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrPN0AAKCRCveOk+D/ej > KqWqAKCd7GWqyXLMZtLWtOuWfR+eOVD6OQCg11ZcsR5SIsb5phXu3resUgTRnO0= > =y2sk > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Mar 22 16:15:49 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 930ECF52D93 for ; Thu, 22 Mar 2018 16:15:49 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (kanar.ci0.org [IPv6:2001:bc8:35e6::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sd-123398", Issuer "sd-123398" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12B597D5A3; Thu, 22 Mar 2018 16:15:48 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.15.2/8.15.2) with ESMTPS id w2MGFiRx066986 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Mar 2018 17:15:44 +0100 (CET) (envelope-from cognet@ci0.org) Received: (from doginou@localhost) by kanar.ci0.org (8.15.2/8.15.2/Submit) id w2MGFheA066985; Thu, 22 Mar 2018 17:15:43 +0100 (CET) (envelope-from cognet@ci0.org) X-Authentication-Warning: kanar.ci0.org: doginou set sender to cognet@ci0.org using -f Date: Thu, 22 Mar 2018 17:15:43 +0100 From: Olivier Houchard To: Adrian Chadd Cc: "Andrey V. Elsukov" , FreeBSD Net Subject: Re: crash with ipfw nat on mips32 Message-ID: <20180322161543.GA66967@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 16:15:49 -0000 On Thu, Mar 22, 2018 at 09:09:37AM -0700, Adrian Chadd wrote: > oh and xcompiled with gcc-6.x . > > I'm not very knowledgable with mips. Is it possible gcc wrongly generated an instruction that is not supported by mips74k ? I suppose not, or it wouldn't lead to a TLB miss. Olivier > > On 22 March 2018 at 09:09, Adrian Chadd wrote: > > I dunno yet; this is a very embedded mips74k box. :) > > > > > > -a > > > > On 22 March 2018 at 06:00, Olivier Houchard wrote: > >> On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: > >>> On 22.03.2018 10:31, Adrian Chadd wrote: > >>> > Erk. I'll go see if I can figure out what's going on. > >>> > > >>> > Thanks! This is really quite grr-y. > >>> >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) > >>> >>> [ thread pid 11 tid 100010 ] > >>> >>> Stopped at 0 > >>> >>> db> bt > >>> >>> Tracing pid 11 tid 100010 td 0x80673b40 > >>> >>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 > >>> >>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120 > >>> >>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88 > >>> >>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0 > >>> >>> db> > >>> >> > >>> >> this is not NAT related, it is ipfw's dynamic states. > >>> >> I'm not sure, but this is seems related to ConcurrencyKit. > >>> > >>> It looks like CK doesn't declare support for mips. > >>> Probably we need to make compat shim, that uses old implementation for > >>> platforms, that are not supported by CK. > >>> > >> > >> Hi, > >> > >> mips should be supported by using the compiler builtins, as is riscv. If there > >> is a crash, it is definitively a bug. Can you guys tell me which CK > >> function dies that badly ? > >> > >> Regards, > >> > >> Olivier From owner-freebsd-net@freebsd.org Thu Mar 22 17:27:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B45C2F5942E for ; Thu, 22 Mar 2018 17:27:26 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 525D480B65 for ; Thu, 22 Mar 2018 17:27:25 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 6216B3AE87 for ; Thu, 22 Mar 2018 10:27:19 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <4DB72389-D167-4152-A15F-4710C54B2E1A@your.org> Date: Thu, 22 Mar 2018 10:27:18 -0700 Message-ID: <9738.1521739638@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 17:27:26 -0000 In message <4DB72389-D167-4152-A15F-4710C54B2E1A@your.org>, Kevin Day wrote: >Does the ssh-keyscan tool do what you want? I never knew about that tool until now. But yes, indeed, that may be the exact kind of magic I was looking for. Thank you. From owner-freebsd-net@freebsd.org Thu Mar 22 17:32:48 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAF27F59CD2 for ; Thu, 22 Mar 2018 17:32:48 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 7577D8104F for ; Thu, 22 Mar 2018 17:32:48 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 95B993AE87 for ; Thu, 22 Mar 2018 10:32:47 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <201803220250.w2M2owMf024292@pdx.rh.CN85.dnsmgr.net> Date: Thu, 22 Mar 2018 10:32:47 -0700 Message-ID: <9754.1521739967@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 17:32:49 -0000 In message <201803220250.w2M2owMf024292@pdx.rh.CN85.dnsmgr.net>, "Rodney W. Grimes" wrote: >You are not going to prove the "control of the exact same Bad Actor" >without a warrant to search and seize. Well, as someone else noted, if two IP addresses yield the exact same SSH key, that is fairly definitive. If I planned to be going into a court of law, then yes, a warrant would be both appropriate and required. But going into court is not among my goals. >> >What you ask I believe could be done, but it non trivial and >> >would require a very good understanding of both forensics >> >and the differing ways that TCP/IP is implemented. >> >> I like to think that I am a quick learner. Please proceed with the >> lesson. > >The rates for lessons in Forensics start at reasonable enough >amounts, you can contact me off list if you wish to persue that. Thanks for your support. As i am doing what I am doing on a volunteer (unpaid) basis, I'm afraid that I will not be able to take you up on your generous offer. From owner-freebsd-net@freebsd.org Thu Mar 22 17:37:42 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D14CF5A211 for ; Thu, 22 Mar 2018 17:37:42 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF5F812FD for ; Thu, 22 Mar 2018 17:37:41 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 2D5D73AE87 for ; Thu, 22 Mar 2018 10:37:41 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <20180322140233.GA79266@staff.retn.net> Date: Thu, 22 Mar 2018 10:37:41 -0700 Message-ID: <9803.1521740261@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 17:37:42 -0000 In message <20180322140233.GA79266@staff.retn.net>, Alexandre Snarskii wrote: >DNS: if both A and A' running open recursive DNS servers (bad idea in >modern internet, but..) it's possible to use TTL field to differentiate. >Scenario: create some DNS record with good enough TTL of one hour. Ask A >about this record, get answer with TTL = 3600. Wait for ten seconds, then >ask A' about the same record. If received TTL is about 3590 - it's really >likely that A and A' is the same host. Thank you! Yes. This, and checking the SSH key, seem to both be very promising solutions to the problem. I will be investigating and trying both, to try to establish how well they might work in practice. It will be great if both work, because some bad actors will be running SSH (on a known or findable port) and others won't be. And likewise, some bad actors will be running their own name servrs and others won't be. So it will be Good to have several tools in the toolbox. From owner-freebsd-net@freebsd.org Thu Mar 22 17:44:10 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E5AEF5AB87 for ; Thu, 22 Mar 2018 17:44:10 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id D85A88185B for ; Thu, 22 Mar 2018 17:44:09 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 165673AE87 for ; Thu, 22 Mar 2018 10:44:09 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <4ce048ad-873e-795e-aae0-8d795d9bb85c@kicp.uchicago.edu> Date: Thu, 22 Mar 2018 10:44:08 -0700 Message-ID: <9859.1521740648@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 17:44:10 -0000 In message <4ce048ad-873e-795e-aae0-8d795d9bb85c@kicp.uchicago.edu>, Valeri Galtsev wrote: >If A and A' do resolve beyond their SOA for clients outside of their >domain. That was vulnerable for abuse, and hardly anybody does that >these days. Am I missing something? As I understand it, sadly, there are still a couple of zillion open recursive resolvers out there. I would anticipate that Bad Actors are neither more likely nor less likely than the general poulation to put such an abomination online. From owner-freebsd-net@freebsd.org Thu Mar 22 18:49:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF98EF6033A for ; Thu, 22 Mar 2018 18:49:26 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 072C284B24 for ; Thu, 22 Mar 2018 18:49:25 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w2MInETe023826 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=OK); Fri, 23 Mar 2018 05:49:20 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w2MIn8L6099922 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Fri, 23 Mar 2018 05:49:08 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w2MIn8OK099921; Fri, 23 Mar 2018 05:49:08 +1100 (AEDT) (envelope-from peter) Date: Fri, 23 Mar 2018 05:49:08 +1100 From: Peter Jeremy To: "Ronald F. Guilmette" Cc: FreeBSD Net Subject: Re: Raw Sockets: Two Questions Message-ID: <20180322184908.GB49338@server.rulingia.com> References: <5AB2C0B1.3020709@grosbein.net> <4802.1521665426@segfault.tristatelogic.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <4802.1521665426@segfault.tristatelogic.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 18:49:27 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Mar-21 13:50:26 -0700, "Ronald F. Guilmette" wrote: > >In message <5AB2C0B1.3020709@grosbein.net>,=20 >Eugene Grosbein wrote: > >>It does not mean you need to stick with raw sockets API. >>libpcap can be used too, as I've shown in previous letter. > >Thank you. If zmap ends up not suiting my needs, I will >definitely look into libpcap. Since no-one else has mentioned it, another option would be divert(4), which is part of IPFW. --=20 Peter Jeremy --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE2M6l8vfIeOACl4uUHZIUommfjLIFAlqz+qRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQ4 Q0VBNUYyRjdDODc4RTAwMjk3OEI5NDFEOTIxNEEyNjk5RjhDQjIACgkQHZIUommf jLLWtA//VLaiuUToCNJZeYOrgCASmE0F5je88EnxAmHmfgjibKK/0GHnFuH1K7t9 GBaqJFEW4qC7XbmezlvoL+/ieSW/a0zbrACyOEU7Ou9Vx4sv5e5eZ5a7KPGGH7Ij cukXd9ue5oQQzPBWD9j8GAApf0ve3GfxicV82vfVc8qQqk2iUIqKmdv8EYVzfUHa zoo54jLtMCjLB9vxvD7IaTMge8oT09zquEIpL1xvJ+vRkx6DJ4S8SzjUU5l2HHBo FIiF9eu2o3c11WWaiuOhFLSoXLKCQVS+VphJEYX14NbDJpcV6oHf2/dIfMAeb5fA gicjIRqRF+xU6emDp0Ft0Zhc6/wFO+PX3EsIIU+q2+p4kxc0GmJkFEuXU2Ta2zcs TWkrAH6uNbIbMwI/KAjT5BLUaF5ib6AMF6NJcjh6gXLDzYkUEGbUUCjbN37sNol4 1IrRRXb7t0lC4xX25iocMl+IdQlOz9S0NjSGN489lvV0XhpTOCFIK7m4S6yuCcb8 T8G5fEFewZNJ4+C4qhmlsI7NewUiVKzuEeA6E/ivNP8uNkRM+14dPRvh/+b+8pEw JHBTIbVk0lSa91saEIowLNyD6CJ8mbqyUChMtS1lkQpIu/zcbNY4pUxjTj4f4/fp S0GLO/yIQp2LwsCp0KqcRkcRLqTfsee11wyfnMjqIBpZ3TKXeAA= =lJ8p -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-net@freebsd.org Thu Mar 22 18:56:32 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B21DF60D26 for ; Thu, 22 Mar 2018 18:56:32 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 CB51E85058 for ; Thu, 22 Mar 2018 18:56:31 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2MIuRiO027693; Thu, 22 Mar 2018 11:56:27 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2MIuRjH027692; Thu, 22 Mar 2018 11:56:27 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803221856.w2MIuRjH027692@pdx.rh.CN85.dnsmgr.net> Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <9754.1521739967@segfault.tristatelogic.com> To: "Ronald F. Guilmette" Date: Thu, 22 Mar 2018 11:56:27 -0700 (PDT) CC: FreeBSD Net X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 18:56:32 -0000 > > In message <201803220250.w2M2owMf024292@pdx.rh.CN85.dnsmgr.net>, > "Rodney W. Grimes" wrote: > > >You are not going to prove the "control of the exact same Bad Actor" > >without a warrant to search and seize. > > Well, as someone else noted, if two IP addresses yield the exact same > SSH key, that is fairly definitive. Wrong, as someone else pointed out that is simply a mater of copying the /etc/ssh/*host* key files over to the other host. This also happens when people clone machines... so is actual more common than one might think. You can be pretty sure they are different machines, but you can not assertain they are the same machine with this information. You can assert nothing about control with this information. You can be pretty sure they are under the same control, but not provable. Anyone with elivated privledge access to A can copy the /etc/ssh/* files to A'. > If I planned to be going into a court of law, then yes, a warrant > would be both appropriate and required. But going into court is > not among my goals. > > >> >What you ask I believe could be done, but it non trivial and > >> >would require a very good understanding of both forensics > >> >and the differing ways that TCP/IP is implemented. > >> > >> I like to think that I am a quick learner. Please proceed with the > >> lesson. > > > >The rates for lessons in Forensics start at reasonable enough > >amounts, you can contact me off list if you wish to persue that. > > Thanks for your support. As i am doing what I am doing on a volunteer > (unpaid) basis, I'm afraid that I will not be able to take you up on > your generous offer. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Thu Mar 22 21:01:33 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CB08F6BADB for ; Thu, 22 Mar 2018 21:01:33 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id EA6C06B734 for ; Thu, 22 Mar 2018 21:01:32 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7E94C3AEF8 for ; Thu, 22 Mar 2018 14:01:31 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <201803221856.w2MIuRjH027692@pdx.rh.CN85.dnsmgr.net> Date: Thu, 22 Mar 2018 14:01:31 -0700 Message-ID: <10556.1521752491@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 21:01:33 -0000 In message <201803221856.w2MIuRjH027692@pdx.rh.CN85.dnsmgr.net>, "Rodney W. Grimes" wrote: >> Well, as someone else noted, if two IP addresses yield the exact same >> SSH key, that is fairly definitive. > >Wrong, as someone else pointed out that is simply a mater of >copying the /etc/ssh/*host* key files over to the other host. >This also happens when people clone machines... so is actual >more common than one might think. > >You can be pretty sure they are different machines, but you >can not assertain they are the same machine with this information. >You can assert nothing about control with this information. > >You can be pretty sure they are under the same control, but >not provable. Anyone with elivated privledge access to A >can copy the /etc/ssh/* files to A'. Your points are, of course, valid. However in the absence of the scenario where Bad Actor `B' has broken in to some machine which is under the control of Bad Actor `A', and where B has then absconded with a copy of A's SSH key (and then used that himself as an SSH key) for my limited purposes, at least, the sighting of two identical SSH keys on two different IP addresses strongly suggests a high likelihood that the two IP addreses are indeed under the control of a single party. (I should perhaps explain and emphasize that I personally am not by any means a member of law enforcement. I do not have the power to deprive any party of either life or freedom or property. I am thus, quite reasonably able to accept a level of "proof" which may be quite persuasive, even if it does not rise to the level of "beyond a reasonable doubt". I am just doing security research... not prosecuting anybody.) From owner-freebsd-net@freebsd.org Thu Mar 22 23:39:33 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44F01F53AC6 for ; Thu, 22 Mar 2018 23:39:33 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 C784C71EAF; Thu, 22 Mar 2018 23:39:32 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id h76so539496wme.4; Thu, 22 Mar 2018 16:39:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HG31GvAmgr1kUKTq6RP4xsqmcRLfHbdKRU+nY8DrBoQ=; b=CagM9zgMxxd5jlKvFP8aWN134klUjGSFugaB1g5YwdmWT9Zp3ipWxfwhAA+7c8Os/8 tZzav8kPh4TofEeniRyYJnKhLuyJ4mGJg+K7OwEUs1fUebav6DJYPxOTI9o53s6OAHyH bHi9JP1yzcbJi1o0iCuDmaZ5OfhRyYTnv2uhkTB7raVgvn+wQapInn3eWchUJHP7d3uV FU03coCxoIpBWHHrm/yx9+DgCGVejkT/2gM44n+hiK0x0Psn4O5uw/sVsK6eqd8UY5Ei H1DmxHwE3hxwgYWGOQHFtHPTrkpNFEhJcwHpoGIPSOCtOr9cEy/Wne8H1359bF8ZwouX bHTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HG31GvAmgr1kUKTq6RP4xsqmcRLfHbdKRU+nY8DrBoQ=; b=qKAZ17VDNnY1im5FkwP/hGENXElktsT+n9lvfDthxEFeZuj+8dWZixHC0Acm1ILwoW MREI9M+s65a/ASHVjTtnOqUTgRnW9UQlJC3l2pDkLWINZawc3xW52bIWnx2QCVbV7sT0 juhuaBwIfACT6FfnhhQXWQP17EK/hvYFSappAeyGA1oMlTcO/sFMmTtaEq/Q1S9qOSzG gCVBBGOF4nitFTmU5fWnzsmB6jT7Lkea2xX/woxb6XzeMSRRdR5FYv4v95Sq1La5BaUv mwhPsaaOGLXvpTJepTmU9jnCRuRUGhubdu3zIr8gE07bMCb33vnUb9IhuCPsn3PkGNRI EwKQ== X-Gm-Message-State: AElRT7Fu9/MGNDX37ZKMWzADH46mXwCuZQRL9ias0QSWi3341MLJR95H aqmtG7oP37BzwZ0qVKkshXOFM/XC X-Google-Smtp-Source: AG47ELsTcCRpBR/sZLKlR40PrVnNHE8uFbYgN9wNUzk1ye9o1M1NclrXNKX0r6tY6W8CEuvxx4z8IA== X-Received: by 10.80.146.97 with SMTP id j30mr22141731eda.134.1521761971355; Thu, 22 Mar 2018 16:39:31 -0700 (PDT) Received: from juntos.woohoo.ch ([2a02:168:681c:460:c1d6:42f5:a6b1:666e]) by smtp.gmail.com with ESMTPSA id a88sm5577724edf.64.2018.03.22.16.39.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 16:39:30 -0700 (PDT) Subject: Re: Multicast/SSDP not working (on VLAN interface) To: freebsd-net@freebsd.org References: <201803220015.w2M0FFbg023791@pdx.rh.CN85.dnsmgr.net> From: Andreas Scherrer Cc: sunpoet@FreeBSD.org Message-ID: Date: Fri, 23 Mar 2018 00:39:29 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803220015.w2M0FFbg023791@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 22 Mar 2018 23:39:33 -0000 @sunpoet@FreeBSD.org: as you are the (brand new?) maintainer of the miniDLNA port for FreeBSD, my hopes are with you :D tl;dr "setsockopt" should be replaced by "sourcefilter" (at least in minissdp.c's "AddMulticastMembership) On 22.03.18 01:15, Rodney W. Grimes wrote: ... > Try as a very first rules: > > ipfw add 1 log allow ip from any to 224.0.0.0/4 > ipfw add 2 log allow ip from 224.0.0.0/4 to any > > DO NOT put any restricting clauses on these.. if this makes things > work simply move them down a few rules until you find the point > at which things stop working. I tried this; to no avail. But it got me on the right track! MiniDLNA was actually (trying to) send IGMPv3 packets (224.0.0.22) back to the client but they were following the default route! The problem is here (please excuse if I do not get all the terminology right, I am not a network programmer): The function "AddMulticastMembership" in minissdp.c uses the "ip_mreqn" struct to call "setsockopt" for "IP_ADD_MEMBERSHIP". It is trying to use an interface index "imr.imr_ifindex = iface->ifindex" in "ip_mreqn". The code I am talking about can be found here: https://sourceforge.net/p/minidlna/git/ci/master/tree/minissdp.c#l69 Using an interface index for "IP_ADD_MEMBERSHIP" is not supported (since FreeBSD 7.0): ----- A host must become a member of a multicast group before it can receive datagrams sent to the group. To join a multicast group, use the IP_ADD_MEMBERSHIP option: struct ip_mreq mreq; setsockopt(s, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq)); where mreq is the following structure: struct ip_mreq { struct in_addr imr_multiaddr; /* IP multicast address of group */ struct in_addr imr_interface; /* local IP address of interface */ } imr_interface should be set to the IP address of a particular multicast- capable interface if the host is multihomed. It may be set to INADDR_ANY to choose the default interface, although this is not recommended; this is considered to be the first interface corresponding to the default route. Otherwise, the first multicast-capable interface configured in the system will be used. Prior to FreeBSD 7.0, if the imr_interface member is within the network range 0.0.0.0/8, it is treated as an interface index in the system interface MIB, as per the RIP Version 2 MIB Extension (RFC-1724). In versions of FreeBSD since 7.0, this behavior is no longer supported. Developers should instead use the RFC 3678 multicast source filter APIs; in particular, MCAST_JOIN_GROUP. ----- As documented here: https://www.freebsd.org/cgi/man.cgi?query=ip&apropos=0&sektion=4&manpath=FreeBSD+11.1-RELEASE&arch=default&format=html I have verified that things start to work when I forced the "other execution path" in "AddMulticastMembership" (using "ip_mreq" instead of "ip_mreqn"; I have achieved this by changing the "#ifdef HAVE_STRUCT_IP_MREQN" statement into it's negated form "#ifndef HAVE_STRUCT_IP_MREQN"). Unfortunately I am not qualified to (properly) fix this :( I read the statement that MCAST_JOIN_GROUP should be used (meaning replace "setsockopt" with "sourcefilter", if I get that correctly). But I do not really understand what that means/how to do that. https://www.freebsd.org/cgi/man.cgi?query=sourcefilter&apropos=0&sektion=3&manpath=FreeBSD+11.1-RELEASE&arch=default&format=html If someone could point me in the right direction (a tutorial how "sourcefilter" must be used for example), I might be able to come up with something that can be developed into a proper patch. Of course, if someone can fix this right away, that would be even better. Best regards andreas From owner-freebsd-net@freebsd.org Fri Mar 23 03:48:31 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA953F67759 for ; Fri, 23 Mar 2018 03:48:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 43A1E7DE28 for ; Fri, 23 Mar 2018 03:48:30 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-20-68.dyn.iinet.net.au [115.166.20.68]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w2N3R0VC092426 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Mar 2018 20:27:03 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: Need Netgraph Help [fixed] From: Julian Elischer To: John Lyon Cc: "freebsd-net@freebsd.org" , Eugene Grosbein References: <5A3225BF.6020205@omnilan.de> <5A32F63E.8010205@grosbein.net> <5A338C5A.20300@omnilan.de> <2e0525c8-2251-a5f5-45d1-fe44ebe318f7@freebsd.org> <4fee4ea6-9b35-afba-6d5d-24ecca3e28c6@freebsd.org> <3b8d46da-75e3-79f2-379c-b27a88e80733@freebsd.org> <47C0E33A-E815-4860-A25C-F29BBB8D6787@gmail.com> <9fe76b26-2d1c-939a-8ece-947f5140bc0f@freebsd.org> Message-ID: Date: Fri, 23 Mar 2018 11:26:54 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <9fe76b26-2d1c-939a-8ece-947f5140bc0f@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 23 Mar 2018 03:48:32 -0000 Hi John, did you ever try out my version? Julian On 7/1/18 4:06 am, Julian Elischer wrote: > On 7/1/18 4:02 am, John Lyon wrote: >> Thanks for the clarification and all the help. >> >> After Marko clarified that that edges/hooks are bidirectional, I >> was able to get it working WAN to LAN and LAN to WAN by using a >> pair of one2many and ETF nodes. >> >> The commands were (from memory): >> >> #Create Unfiltered WAN Path >> ngctl mkpeer igb0: one2many lower one >> ngctl name igb0:lower wanmux >> ngctl mkpeer wanmux: etf many0 downstream >> ngctl name wanmux:many0 wanfilter >> ngctl connect wanfilter: igb0: nomatch upper >> >> #Create Unfilter LAN Path >> ngctl mkpeer igb1: one2many lower one >> ngctl name igb1:lower lanmux >> ngctl mkpeer lanmux: etf many0 downstream >> ngctl name lanmux:many0 lanfilter >> ngctl connect lanfilter: igb1 nomatch upper >> >> #Cross Connect Two Paths >> ngctl connect wanfilter wanmux waneapout many1 >> ngctl connect lanfilter lanmux laneapout many1 >> >> #Filter Cross Connections >> ngctl msg wanfilter: 'setfilter { matchhook="waneapout" >> ethertype=0x888e }' >> ngctl msg lanfilter: 'setfilter { matchhook="laneapout" >> ethertype=0x888e }' >> >> The graph looks like this: >> >> igb0] <----> [mux0] <---> [etf0] <----> [igb0 >>                                \       / >>                                   X >>                                /      \ >> igb1] <----> [mux1] <---> [etf1] <----> [igb1 >> >> >> It was conceptually easier for me to wrap my head around and it >> appears to work (somewhat).  But if I can get it to work, I like >> Julian's approach better as it is simpler and uses fewer nodes. > > etf includes a mux/demux..  the link is bidirectional. > > >> >> Thanks again for all the help! >> >> -------------------------------- >> John L. Lyon >> PGP Key Available At: >> https://www.dropbox.com/s/skmedtscs0tgex7/02150BFE.asc >> >> On Sat, Jan 6, 2018 at 2:39 PM, Julian Elischer > > wrote: >> From owner-freebsd-net@freebsd.org Fri Mar 23 07:46:05 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9520DF4FB35 for ; Fri, 23 Mar 2018 07:46:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::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 09A4E85311 for ; Fri, 23 Mar 2018 07:46:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id s18so11099018wrg.9 for ; Fri, 23 Mar 2018 00:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=GgsQg4+1k+875LFo96I2VjTuHoxzm/4dhhGieEOVAU0=; b=QtzmLYP1IjuSNhye037rZP+rJl+a/PxSXCJjdoc2V7OWI4aQEuY116NFWO13XEgt5Y 7KpIcZk07Ehk7++i29N7IHwwc7D4k76q2cgykr/Jg2K26UI4T3HuYYaCoHx0+E6CNtjp 3Scj7Xc7R0Fy3WDLdQFV/gAuAp/t4D545kSn+m4y/UhDcpS7miCuKkqLiKM6VtF/fKHk JQS5QgT4ce1y/yIAFQ0DJOnkISgdh0ty4rio9iVqCrJI3lGY9zlOy/FyEc7gwN4bPz1R hOsN3NmxwHQ2bCEtLUOkObJDZHr+tpa5HM9SDsbhrlqaSbszMCqEcx3s+I6dmItzHTJV oI9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=GgsQg4+1k+875LFo96I2VjTuHoxzm/4dhhGieEOVAU0=; b=hL5i0cbFZIsdBS/NTTkXgt7/iQfITyj1tPMsqpvsrNfrYv5OIDPrWB74G8Ip9JAylI xGvnOwCxjbOe7xp6Os1pkHylo4iUiZK4NA/VQ485Bap/0gkuwcB4ccrjXlanwQB2i32E u9q/M6YQNCRP6Xz6lrkI/n1wy0TNMOtwnKOlGI7ltIimOpxJs1jnRZ0njhPKZnp1DIRK KSu66JwJ7Ryt9C0VyJakzEa10BEEz+oK50W6meHzQCsLXcnuYrXamFjZ+1Mg5uXNYpyj CIQAaI4pcB8usdHXuPGUPUrXuCGgLaL9hvBxYYqWkA+KqBZ86Dh1vz6SpEDqNvPOuAUA A+YA== X-Gm-Message-State: AElRT7FdTHKcRtNNTePucNjR9jeDHZPZzGx7fQCLIyCOGX8hEdb7V/lV 1KWEKZ1e/bBotDJsik5/KP9HSzAA0nDNO6DsNdbZD+Pp X-Google-Smtp-Source: AG47ELtp8Xysouu4PnRvlqa0qDUjq67jrQJx9DjU4QxPVG1z0C7e3i0HraWVXKtA7B0NaP80rMSnPbhQsJPVHodXJ8I= X-Received: by 10.223.138.214 with SMTP id z22mr21507616wrz.39.1521791164028; Fri, 23 Mar 2018 00:46:04 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Fri, 23 Mar 2018 00:46:02 -0700 (PDT) In-Reply-To: <20180322161543.GA66967@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> <20180322161543.GA66967@ci0.org> From: Adrian Chadd Date: Fri, 23 Mar 2018 00:46:02 -0700 X-Google-Sender-Auth: o_JY5MZTn8LuS5F0dmFAroIMCHU Message-ID: Subject: Re: crash with ipfw nat on mips32 To: Olivier Houchard Cc: "Andrey V. Elsukov" , FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 23 Mar 2018 07:46:05 -0000 Hi, The stack backtrace looks like a null pointer dereference. The concurrencykit website mentions ARM and MIPS as future ports. Is this actually true? Is concurrencykit supposed to actually run on ARM/MIPS? Did anyone test? Actual MIPS hardware that we run on is like $50. It's not exactly spendy to test out FreeBSD code on real hardware. :) I can't even build the regression suite from CK on github to run on mips32 hardware. I don't suppose anyone would be able to figure that particular mess out? I'd really like to work some more on wifi stack stuff on this embedded platform stuff and this just threw a spanner in my plans. I'd really appreciate some help here cause I don't have time to wade through more platform breakage just to do wifi stack / driver work. I have limited spare time as it is these days :( Thanks, -adrian From owner-freebsd-net@freebsd.org Fri Mar 23 13:02:12 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36912F6A70E for ; Fri, 23 Mar 2018 13:02:12 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (kanar.ci0.org [IPv6:2001:bc8:35e6::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sd-123398", Issuer "sd-123398" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B1B7772E6B; Fri, 23 Mar 2018 13:02:11 +0000 (UTC) (envelope-from cognet@ci0.org) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.15.2/8.15.2) with ESMTPS id w2ND24IV074321 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Mar 2018 14:02:04 +0100 (CET) (envelope-from cognet@ci0.org) Received: (from doginou@localhost) by kanar.ci0.org (8.15.2/8.15.2/Submit) id w2ND24H1074320; Fri, 23 Mar 2018 14:02:04 +0100 (CET) (envelope-from cognet@ci0.org) X-Authentication-Warning: kanar.ci0.org: doginou set sender to cognet@ci0.org using -f Date: Fri, 23 Mar 2018 14:02:04 +0100 From: Olivier Houchard To: Adrian Chadd Cc: "Andrey V. Elsukov" , FreeBSD Net Subject: Re: crash with ipfw nat on mips32 Message-ID: <20180323130204.GA74266@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> <20180322161543.GA66967@ci0.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 23 Mar 2018 13:02:12 -0000 Hi Adrian, On Fri, Mar 23, 2018 at 12:46:02AM -0700, Adrian Chadd wrote: > Hi, > > The stack backtrace looks like a null pointer dereference. > "Stopped at 0". Does that mean the PC is at 0, or just that we tried to load 0 ? > The concurrencykit website mentions ARM and MIPS as future ports. Is > this actually true? Is concurrencykit supposed to actually run on > ARM/MIPS? Did anyone test? Actual MIPS hardware that we run on is like > $50. It's not exactly spendy to test out FreeBSD code on real > hardware. :) > If the website states that then it is outdated. There is a native arm port for quite some time. As for mips, it only works using gcc builtins, but it has been tested at some point. > I can't even build the regression suite from CK on github to run on > mips32 hardware. I don't suppose anyone would be able to figure that > particular mess out? > How does it fail ? > I'd really like to work some more on wifi stack stuff on this embedded > platform stuff and this just threw a spanner in my plans. I'd really > appreciate some help here cause I don't have time to wade through more > platform breakage just to do wifi stack / driver work. I have limited > spare time as it is these days :( > > Thanks, I'm certainly willing to help you. I'll try to reproduce it with qemu or something. Can you tell me a bit more about your setup, so that I can get it to happen ? Unfortunately, I'll be away for the week-end, so probably won't be able to do so before at least sunday evening (french time). Regards, Olivier From owner-freebsd-net@freebsd.org Fri Mar 23 17:07:59 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DFCAF5AA85 for ; Fri, 23 Mar 2018 17:07:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 889537FFF1 for ; Fri, 23 Mar 2018 17:07:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x233.google.com with SMTP id l8so12841390wrg.5 for ; Fri, 23 Mar 2018 10:07:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=h5s9FPTSOAQ6fAEFFaJA76eSKTCIOsPpVa16YZsFmeM=; b=KyIQ/5TBoXtwl0zgCgvaJgl078rLcafrR8QRofVKC/poHwY9GAbw0pBYTSsGPC02jm kSromCTvwvMC3tQQuRzC8gRSZ+iMGLynoSGxpKysQ/kovlfEmqEukEJ9tKiGxDa6rz9u 2oB/bHGCR2yQ1XfKsg5kegO0Dcbv47d4Ge6DarsDNUz6PipdvM+MYGA675+TKpSNATSS FZeCAu0en7QzVF0B5k7J7cKV42/llqavG72WMGd3BRpytzcP4esfc3wChxAcdbqNBlHE WCi7+ijNwHnTxgsJCXeC1LkbJ4jbyAU9d2AhSORBoshB63eSIIPrti8Dy4pmlmqGV62h 48Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=h5s9FPTSOAQ6fAEFFaJA76eSKTCIOsPpVa16YZsFmeM=; b=UDCIem0jTVV9XslNjXtYpc+Ieche2g79B0hvPvn5CHLbwec0JGw6/zBHeIRclH1YjY BMbomh638BvtAeKWg2vP+QzfwxeOS+dZjeEoxF1yjrUg2xEq9Xi1o8+m35CsCHVSwQSb lCXJiKE1VusUbxwUSdXp+NEBs/XVP31KUqbw9NKlfTUeaoBo/fQowapoMJqjpIEbum6X 9njfBKl9L/haUtKQO7vqLKM7mnAdOh5LH+jZSmPnP7WTbKpsxN2YYrnDXBEsj9nZsAUr HlxhAuW/k34PTcsD2act/yXy3r/RSP3quALBWGtRPeSgp/iRv4K5wlAmDc/0T7p48Mk4 /8fw== X-Gm-Message-State: AElRT7Ek2qSFBPOo76YBTjXAxkgPPL78kg0FwY09IHmMXld7G+n2i97E alm1rbSiU/VXyKY/FeHr6OvWOX2Wy+I8Us02JjM= X-Google-Smtp-Source: AG47ELuTuJRMnbfpiXSTzwT9nsJoaLP670SRbD+qUUQVcdZ+3Wx23DXaLzpTd6IJ5D7I8LJ0XehZV6K8hq/RDoEw3dg= X-Received: by 10.223.195.116 with SMTP id e49mr23060530wrg.5.1521824876902; Fri, 23 Mar 2018 10:07:56 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.4.12 with HTTP; Fri, 23 Mar 2018 10:07:55 -0700 (PDT) In-Reply-To: <20180323130204.GA74266@ci0.org> References: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> <20180322130002.GA65574@ci0.org> <20180322161543.GA66967@ci0.org> <20180323130204.GA74266@ci0.org> From: Adrian Chadd Date: Fri, 23 Mar 2018 10:07:55 -0700 X-Google-Sender-Auth: 03GBt-XQwiJLnL7gEr6vGEi1C6s Message-ID: Subject: Re: crash with ipfw nat on mips32 To: Olivier Houchard Cc: "Andrey V. Elsukov" , FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 23 Mar 2018 17:07:59 -0000 Hi! Just to keep things up to date; I had a chat with people on IRC. * I got the regression suite in github compiling and running on amd64. I'm going to attempt to commit some makefile hilarity to get it to cross-compile against the copy in sys/contrib/ck * I'll go get more info when I next power up the AP in question -adrian From owner-freebsd-net@freebsd.org Fri Mar 23 22:53:50 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C3B0F52B67 for ; Fri, 23 Mar 2018 22:53:50 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 9B8F669414 for ; Fri, 23 Mar 2018 22:53:49 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id m13so272698wrj.5 for ; Fri, 23 Mar 2018 15:53:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=qPpkAZLXaFxl5DKZHlHauaDYAfMMn4FWJBUhkTl3vfg=; b=cmfY65medmLX/o07k4g0UOgr8kgrFTlwFmzpC/UxMZwk0JH7zq6hHU46fgPZQWTfsv keVJUbfeZ3KQ+SC5ub2aI+SdQiuV3SuR6dB/wQ4ZBuhZSQ3ZeMT3ZYaWhaiTLjevORKr opbk7SW3W3y8m7CUg8Uuc5Ne+87V+EhHVWGgSbu7zO6UlmseJQ9as6zvmlNSz6kQN4Vm jBl8sOhIpvcQln7eeVDdaKgPwLX0r+Xi28pmboB9CHHHdXo8zayq4FzgwVTy10rXxXHV 5EIZtV/E2aDknfyvmpaKJz+/DYm7ntgixAwkZi1w07yaflduF6s9YSxrBO5AH/ly0yGf 4tOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=qPpkAZLXaFxl5DKZHlHauaDYAfMMn4FWJBUhkTl3vfg=; b=JWNHwpaoy5LT1muORFkLVPFFqLKzC8R2DYA5DFPxT5jslSDyXuXyZv4UdAAsYrN6iq QMypR74H3gfo3lFgOoWZbF3SnAHN6GS+nOLxsHgYcUo4C+wzXYTr0UG8kxQjwjViA1xO Tblv/y0fEOo8stB9ce/bQVjjw7FCE7uM8trGJf2Em1nMO6w3sdgaVjuHTutmUrrl7nH5 XhcJs5qYq39rIzmPlRfn0IAgTAgohj8k5GY5xRiQpuq5tLe8RMc0NO+8Zezoeze8YJuy WJRLwfs7uh2PmEbN4SqiFTkTudKZF0A255MRFD0u8kIg4++E5ViLyAO6ajH+cwuibG5/ iNGg== X-Gm-Message-State: AElRT7G57drVi+ivcxHWgYorilRT3qymJPHbPpzXnZCP1kaSbN87LCow EY5mAv3pyFb2BtHFTAtz4hvX4sVo X-Google-Smtp-Source: AG47ELsHu0JuIbBtlju8GNKwcH7x5qYUEtz6EwwD/NC8psHB4PQOVQlTKXSPXL6WGMuYRO+6p38MlA== X-Received: by 10.223.195.58 with SMTP id n55mr22777332wrf.132.1521845628479; Fri, 23 Mar 2018 15:53:48 -0700 (PDT) Received: from juntos.woohoo.ch ([2a02:168:681c:460:4863:9831:e9a1:f132]) by smtp.gmail.com with ESMTPSA id c34sm9808344wrc.60.2018.03.23.15.53.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Mar 2018 15:53:47 -0700 (PDT) Subject: Re: Multicast/SSDP not working (on VLAN interface) To: freebsd-net@freebsd.org References: <201803220015.w2M0FFbg023791@pdx.rh.CN85.dnsmgr.net> From: Andreas Scherrer Message-ID: Date: Fri, 23 Mar 2018 23:53:46 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803220015.w2M0FFbg023791@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 23 Mar 2018 22:53:50 -0000 I have created a bug report for this. Thanks again to everyone who spent time on it until now. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226884 Best regards andreas From owner-freebsd-net@freebsd.org Sat Mar 24 16:21:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAED3F585A0 for ; Sat, 24 Mar 2018 16:21:03 +0000 (UTC) (envelope-from admin@yoonka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24888739EA for ; Sat, 24 Mar 2018 16:21:02 +0000 (UTC) (envelope-from admin@yoonka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w2OGL17C054180 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 24 Mar 2018 16:21:01 GMT (envelope-from admin@yoonka.com) To: freebsd-net@freebsd.org From: Grzegorz Junka Subject: Default network device Message-ID: <5237ec10-c906-db3c-f62f-cc7478a31dc0@yoonka.com> Date: Sat, 24 Mar 2018 16:21:01 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 16:21:03 -0000 Hi, In my laptop I have both, wlan0 and ue0 (ethernet). When both are connected, FreeBSD chooses to use wlan0 by default. Only when I disable wlan0 it switches to use ue0. Since ue0 is ethernet it's obviously much faster than wlan0. Why FreeBSD is selecting wlan rather than ue? How to configure the network so that wlan0 is only used when ue0 isn't available? Thanks GrzegorzJ From owner-freebsd-net@freebsd.org Sat Mar 24 17:47:58 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFCBDF5F7C8 for ; Sat, 24 Mar 2018 17:47:58 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 930C076E90 for ; Sat, 24 Mar 2018 17:47:58 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id w2OHlujg069760; Sat, 24 Mar 2018 17:47:57 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id w2OHlupR069759; Sat, 24 Mar 2018 17:47:56 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201803241747.w2OHlupR069759@donotpassgo.dyslexicfish.net> Date: Sat, 24 Mar 2018 17:47:56 +0000 Organization: Dyslexic Fish To: rfg@tristatelogic.com, freebsd-net@freebsd.org Subject: Re: Same host or different? How can you tell "over the wire"? References: <10556.1521752491@segfault.tristatelogic.com> In-Reply-To: <10556.1521752491@segfault.tristatelogic.com> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Sat, 24 Mar 2018 17:47:57 +0000 (GMT) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 17:47:59 -0000 Have you thought of examining the TCP timestamp field? Not necessarily for accurate uptime, but a way to determine if the hosts are the same. Or some of the other fingerprinting methods? nmap has options for uptime and other fingerprinting : https://nmap.org/book/osdetect-usage.html Of course, all this assumes the hosts are connected directly without any load balancing or some sort of firewall/proxy that fiddles with the packet data... cheers, Jamie From owner-freebsd-net@freebsd.org Sat Mar 24 18:38:15 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55E0AF64313 for ; Sat, 24 Mar 2018 18:38:15 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id AC15D791C4 for ; Sat, 24 Mar 2018 18:38:12 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 3C6353AEF2; Sat, 24 Mar 2018 11:38:06 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org, Jamie Landeg-Jones Subject: Re: Same host or different? How can you tell "over the wire"? In-Reply-To: <201803241747.w2OHlupR069759@donotpassgo.dyslexicfish.net> Date: Sat, 24 Mar 2018 11:38:05 -0700 Message-ID: <22999.1521916685@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 18:38:15 -0000 In message <201803241747.w2OHlupR069759@donotpassgo.dyslexicfish.net>, Jamie Landeg-Jones wrote: >Have you thought of examining the TCP timestamp field? Not necessarily >for accurate uptime, but a way to determine if the hosts are the same. No, I certainly didn't, but that appears to be the exact kind of thing I was looking for, so thanks! (I will have to look into it some more. I have just skimmed RFC 1323 for the very first time ever, and it will take me awhile to fully grok this stuff.) >Or some of the other fingerprinting methods? nmap has options for uptime >and other fingerprinting : https://nmap.org/book/osdetect-usage.html I'm not seeing a separate option just for the uptime, apart from the full blown OS detection. Did I just miss it?