From owner-freebsd-net@freebsd.org Sun May 28 01:25:34 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB98BD85FE8 for ; Sun, 28 May 2017 01:25:34 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BD981886 for ; Sun, 28 May 2017 01:25:33 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:52902] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 84/27-03935-6072A295; Sun, 28 May 2017 01:25:27 +0000 Date: Sun, 28 May 2017 01:25:16 +0000 Message-ID: <84.27.03935.6072A295@dnvrco-omsmta01> From: "Thomas Mueller" To: freebsd-net@freebsd.org CC: Yuri Subject: Re: dhclient vs. dhcpcd References: <97050ce3-ad75-c3dc-c106-3bd608e7aa8e@rawbw.com> <0758ef3c-c581-12ff-9310-81af40188236@rawbw.com> X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 01:25:34 -0000 > > NetBSD-current is on dhcpcd 7.0, ahead of FreeBSD ports version. > 7.0.0 isn't released yet, it is in rc1: > https://roy.marples.name/projects/dhcpcd > FreeBSD is at the latest released version. > Yuri I saw after I sent that last message that dhcpcd 7.0 was at rc1, but didn't check on what was the latest pre-7.0 version. I looked in NetBSD's SRCDIR/doc/CHANGES after sending that last message. I also just noticed that I got the wrong Subject: line, which I have corrected here. Tom From owner-freebsd-net@freebsd.org Sun May 28 07:24:36 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8009D8573E for ; Sun, 28 May 2017 07:24:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E1DFE1C1D; Sun, 28 May 2017 07:24:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA12038; Sun, 28 May 2017 10:24:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dEsYp-000L9j-TS; Sun, 28 May 2017 10:24:23 +0300 Subject: Re: svn commit: r314948 - in head: lib/libstand sys/boot/i386/libi386 To: Kamil Czekirda , Baptiste Daroussin Cc: Mariusz Zaborski , Steven Hartland , "George V. Neville-Neil" , Toomas Soome , freebsd-net@FreeBSD.org References: <201703090601.v2961OJx077853@repo.freebsd.org> <20170526210908.ykqalqbetxp4f27p@ivaldir.net> From: Andriy Gapon Message-ID: Date: Sun, 28 May 2017 10:23:27 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 07:24:36 -0000 On 28/05/2017 01:09, Kamil Czekirda wrote: > In initial revision I noticed, that I'm not sure it should be default behavior. > In a lot of installations pxeloader can base on the cache and doesn't require > second, full request with the same answer. In that situation we can switch off > bootp() and I think it would be nice to have this switch and give them to users. > Flag during compilation is sensible. > > In very simple and popular case we have chain with four requests for the same > information (!): > PXE (NIC) -> iPXE -> pxeloader -> dhclient > and it's possible to switch off request from iPXE and pxeloader without breaking > boot process. Well, the information given to PXE/NIC and iPXE is not exactly the same as bootfile must differ. Also, a nit: as far as I know, it's currently impossible to run dhclient on a network booted _diskless_ system. So, yeah, in some setups we can shave off a request from pxeboot and it probably makes sense to have that option. -- Andriy Gapon From owner-freebsd-net@freebsd.org Sun May 28 07:46:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEC8AD85FB1 for ; Sun, 28 May 2017 07:46:14 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::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 6751DD2F for ; Sun, 28 May 2017 07:46:14 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id l18so51811322oig.2 for ; Sun, 28 May 2017 00:46:14 -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=QslZ1hPseX2i+4OzxRja4Kjv7HX2gmvuQ99zxWmbFJQ=; b=ITH3JE3UtoaEh2nrxkhYj/KyagZS0FaHJxNfJXRTvfA7Si4rDdoboaJHXdYTaVCZhi QgI7wxeubwI4IhIScBTYa8ORqqxE+767YYMtMBSJuXVj0+1EKk0vy6m9Sf9D7YEusC8q mW3TWdRV8/17f19YdFqDnVGoxTL7i2xrYEw6sF35KWRc+rq1+YjQiGFcFqHsRNUxvq3y TyZ9M+Cmq/W/drn4HDX09Q5Rz5b3UEoxS3xERxU42bfbpkwHxNjTx0GJzW4XRY5k4uBw p/nqPapX75t5OQTdISHOz/2z3rurtPHuxED9qDWMRjenUbManQ1ysct0efGEf9lZ6Zih wegw== 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=QslZ1hPseX2i+4OzxRja4Kjv7HX2gmvuQ99zxWmbFJQ=; b=Bse35mmFAWouO2civm1IYwnwEz22M+uJz1QuKPDqSwQ5WRFQvvJ3+PwhkoD0Gr9WOf sK0A3vayea1G7itAEM5ek0DHywO9qlzzOEbTdOU/7/h25XLOlFCZShYJTSrmHAC3jeqq 6aNH5vqWfXIvLkmiyDq/52OvjXNCqCsub44R7Mmg4E8iW14euS9Yt6whe21zJ6D4bfaV JmYXO3tzoZ96q9IjOmE2aIb+GvPzIZSIj4Q4LusGw9VOipJU1IHcPUOVsYdVAvw6D5Gr iSLqbYnwwmUPgS02kB+0APXufndctmF5a6VtHu4YzCOTVvCnwLr7Mvf60wwmq78okPFy aM+Q== X-Gm-Message-State: AODbwcAawwLbndOMOUYNuznOHQAZ8HfVg6nNkCA7VC575Y5XFEDxCcDx ukplGzx6R2cnyJggjILus4Kcij7m9g== X-Received: by 10.157.56.88 with SMTP id r24mr4927629otd.57.1495957573553; Sun, 28 May 2017 00:46:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.17.59 with HTTP; Sun, 28 May 2017 00:46:12 -0700 (PDT) In-Reply-To: <59281DF8.20402@omnilan.de> References: <58CBCD7A.8060301@omnilan.de> <58CC23F5.7060507@omnilan.de> <58CFA394.8070901@omnilan.de> <5926EE96.1010000@omnilan.de> <5926F9F9.4040706@omnilan.de> <592701D6.7030301@omnilan.de> <592742A8.4010207@omnilan.de> <5927D560.10003@omnilan.de> <5927D77A.60502@omnilan.de> <5927E974.6060706@omnilan.de> <5927EF05.9040208@omnilan.de> <59281DF8.20402@omnilan.de> From: Vincenzo Maffione Date: Sun, 28 May 2017 09:46:12 +0200 Message-ID: Subject: Re: [panic] netmap(4) and if_lagg(4) To: Harry Schmalzbauer Cc: FreeBSD Net Content-Type: multipart/mixed; boundary="001a11493762c5774d055090c355" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 07:46:14 -0000 --001a11493762c5774d055090c355 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Harry, 2017-05-26 14:22 GMT+02:00 Harry Schmalzbauer : > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 26.05.2017 11:06 (localt= ime): > > Yes, it should integrate and compile out of the box, I've done that > > several times with FreeBSD-11.0 and 10.3. > > Impressive, it needed just a small addition to sys/conf/files to make > the linker happy :-) > Exactly! > > I also recomplied vale-ctl, but I get the following error when trying to > add em0 (lagg-unrelated): > 389.083433 [ 835] netmap_obj_malloc netmap_ring request size > 65792 too large > 389.091593 [1693] netmap_mem2_rings_create Cannot allocate RX_ring > It means that you are giving too many slot to each RX ring, probably 4096. Try to use less slots, or to increase the dev.netmap.ring_size sysctl (default value is less than 65792). > > Adding lagg still results in a panci, but with your latest > "return()"-patch, it's different: > > 0xffffffff8042aefb is in freebsd_generic_rx_handler > (/usr/local/share/deploy-tools/RELENG_11/src/sys/dev/ > netmap/netmap_freebsd.c:276). > 271 struct netmap_generic_adapter *gna =3D > 272 (struct netmap_generic_adapter *)NA(ifp); > 273 int stolen =3D generic_rx_handler(ifp, m); > 274 > 275 if (!stolen) { > 276 gna->save_if_input(ifp, m); > 277 } > 278 } > 279 > 280 /* > > KDB: stack backtrace: > #0 0xffffffff805e4a17 at kdb_backtrace+0x67 > #1 0xffffffff805a34b6 at vpanic+0x186 > #2 0xffffffff805a3323 at panic+0x43 > #3 0xffffffff808a49b2 at trap_fatal+0x322 > #4 0xffffffff808a4a09 at trap_pfault+0x49 > #5 0xffffffff808a4246 at trap+0x286 > #6 0xffffffff8088a521 at calltrap+0x8 > #7 0xffffffff806aa3e0 at vlan_input+0x1f0 > #8 0xffffffff8069b298 at ether_demux+0x128 > #9 0xffffffff8069bf3b at ether_nh_input+0x31b > #10 0xffffffff806b7c00 at netisr_dispatch_src+0xa0 > #11 0xffffffff8069b546 at ether_input+0x26 > #12 0xffffffff803a0278 at igb_rxeof+0x738 > #13 0xffffffff8039f63f at igb_msix_que+0x10f > #14 0xffffffff8056ae1c at intr_event_execute_handlers+0xec > #15 0xffffffff8056b106 at ithread_loop+0xd6 > #16 0xffffffff80568475 at fork_exit+0x85 > #17 0xffffffff8088aa5e at fork_trampoline+0xe > > Yeah, the same bug jist slipped back. Discard the previous patch and replace it with the attached one. Cheers, Vincenzo > Any hints how I can get adding em0 (lagg and vlan-less) via vale-ctl > again? (netmap_obj_malloc netmap_ring request size 65792 too large) > > Thanks, > > -harry > > > --=20 Vincenzo Maffione --001a11493762c5774d055090c355 Content-Type: text/x-patch; charset="US-ASCII"; name="2-bugfix.patch" Content-Disposition: attachment; filename="2-bugfix.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_j38egbvl0 ZGlmZiAtLWdpdCBhL3N5cy9kZXYvbmV0bWFwL25ldG1hcF9mcmVlYnNkLmMgYi9zeXMvZGV2L25l dG1hcC9uZXRtYXBfZnJlZWJzZC5jCmluZGV4IDY2ZDA2MzdmLi5mYTY0MjdlMCAxMDA2NDQKLS0t IGEvc3lzL2Rldi9uZXRtYXAvbmV0bWFwX2ZyZWVic2QuYworKysgYi9zeXMvZGV2L25ldG1hcC9u ZXRtYXBfZnJlZWJzZC5jCkBAIC0yNzAsOCArMjcwLDEzIEBAIGZyZWVic2RfZ2VuZXJpY19yeF9o YW5kbGVyKHN0cnVjdCBpZm5ldCAqaWZwLCBzdHJ1Y3QgbWJ1ZiAqbSkKIHsKIAlzdHJ1Y3QgbmV0 bWFwX2dlbmVyaWNfYWRhcHRlciAqZ25hID0KIAkJCShzdHJ1Y3QgbmV0bWFwX2dlbmVyaWNfYWRh cHRlciAqKU5BKGlmcCk7Ci0JaW50IHN0b2xlbiA9IGdlbmVyaWNfcnhfaGFuZGxlcihpZnAsIG0p OworCWludCBzdG9sZW47CiAKKyAgICAgICAgaWYgKCFOTV9OQV9WQUxJRChpZnApKSB7CisgICAg ICAgICAgICByZXR1cm47CisgICAgICAgIH0KKworICAgICAgICBzdG9sZW4gPSBnZW5lcmljX3J4 X2hhbmRsZXIoaWZwLCBtKTsKIAlpZiAoIXN0b2xlbikgewogCQlnbmEtPnNhdmVfaWZfaW5wdXQo aWZwLCBtKTsKIAl9Cg== --001a11493762c5774d055090c355-- From owner-freebsd-net@freebsd.org Sun May 28 08:58:46 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8666D7B9DC for ; Sun, 28 May 2017 08:58:46 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 8ABC917B9 for ; Sun, 28 May 2017 08:58:46 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v4S8wgOC094882; Sun, 28 May 2017 10:58:42 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 5647B66F; Sun, 28 May 2017 10:58:42 +0200 (CEST) Message-ID: <592A9141.4040002@omnilan.de> Date: Sun, 28 May 2017 10:58:41 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: FreeBSD Net Subject: Re: [panic] netmap(4) and if_lagg(4) References: <58CBCD7A.8060301@omnilan.de> <58CFA394.8070901@omnilan.de> <5926EE96.1010000@omnilan.de> <5926F9F9.4040706@omnilan.de> <592701D6.7030301@omnilan.de> <592742A8.4010207@omnilan.de> <5927D560.10003@omnilan.de> <5927D77A.60502@omnilan.de> <5927E974.6060706@omnilan.de> <5927EF05.9040208@omnilan.de> <59281DF8.20402@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 28 May 2017 10:58:42 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 08:58:46 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 28.05.2017 09:46 (localtime): >> >> I also recomplied vale-ctl, but I get the following error when trying to >> add em0 (lagg-unrelated): >> 389.083433 [ 835] netmap_obj_malloc netmap_ring request size >> 65792 too large >> 389.091593 [1693] netmap_mem2_rings_create Cannot allocate RX_ring >> > > It means that you are giving too many slot to each RX ring, probably 4096. > Try to use less slots, or to increase the dev.netmap.ring_size sysctl > (default value is less than 65792). Hmm, then thn I guess a default like dev.netmap.priv_ring_size has changed, because my em txd/rxd were default 4096, for both, native stable/11-netmap and HEAD-netmap... Reducing r/txd to 1024 solved the problem (hw.em.rxd in loader.conf). >> >> Adding lagg still results in a panci, but with your latest >> "return()"-patch, it's different: >> >> 0xffffffff8042aefb is in freebsd_generic_rx_handler … >> >> > Yeah, the same bug jist slipped back. Discard the previous patch and > replace it with the attached one. Thanks a lot! This patch avoids the panic :-) But unfortunately kills lagg (existing sockets break, nothing more tested yet) 488.896454 [ 394] nm_os_generic_find_num_desc called, in tx 1024 rx 1024 488.903445 [ 402] nm_os_generic_find_num_queues called, in txq 0 rxq 0 488.910424 [1252] generic_netmap_attach Created generic NA 0xfffff80036b26400 (prev 0) 488.971772 [ 448] generic_netmap_register Generic adapter 0xfffff80036b26400 goes on 488.980127 [ 495] generic_netmap_register RX ring 0 of generic adapter 0xfffff80036b26400 goes on 488.989917 [ 495] generic_netmap_register RX ring 1 of generic adapter 0xfffff80036b26400 goes on 488.999720 [ 502] generic_netmap_register TX ring 0 of generic adapter 0xfffff80036b26400 goes on 489.009504 [ 502] generic_netmap_register TX ring 1 of generic adapter 0xfffff80036b26400 goes on 489.019802 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings 490.579512 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings 491.781780 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings … Have a nice sunday, will try to find some time next week to do more investigation, must close for today, haven't even read the messages, just wanted to drop a note. thnaks, -harry From owner-freebsd-net@freebsd.org Sun May 28 15:39:10 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89356D84F59 for ; Sun, 28 May 2017 15:39:10 +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 59E7A19C1; Sun, 28 May 2017 15:39:09 +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 v4SFd1hI018339; Sun, 28 May 2017 08:39:01 -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 v4SFcxJ7018338; Sun, 28 May 2017 08:38:59 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201705281538.v4SFcxJ7018338@pdx.rh.CN85.dnsmgr.net> Subject: Re: svn commit: r314948 - in head: lib/libstand sys/boot/i386/libi386 In-Reply-To: To: Andriy Gapon Date: Sun, 28 May 2017 08:38:59 -0700 (PDT) CC: Kamil Czekirda , Baptiste Daroussin , "George V. Neville-Neil" , Steven Hartland , Toomas Soome , freebsd-net@freebsd.org, Mariusz Zaborski 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.23 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, 28 May 2017 15:39:10 -0000 > On 28/05/2017 01:09, Kamil Czekirda wrote: > > In initial revision I noticed, that I'm not sure it should be default behavior. > > In a lot of installations pxeloader can base on the cache and doesn't require > > second, full request with the same answer. In that situation we can switch off > > bootp() and I think it would be nice to have this switch and give them to users. > > Flag during compilation is sensible. > > > > In very simple and popular case we have chain with four requests for the same > > information (!): > > PXE (NIC) -> iPXE -> pxeloader -> dhclient > > and it's possible to switch off request from iPXE and pxeloader without breaking > > boot process. > > Well, the information given to PXE/NIC and iPXE is not exactly the same as > bootfile must differ. Also, a nit: as far as I know, it's currently impossible > to run dhclient on a network booted _diskless_ system. I dont think that is actually true. Infact dont we need to run dhclient on a diskless client if we intend to keep our dhcp lease beyond the initial issue time period, ie renewal ever X minutes? > So, yeah, in some setups we can shave off a request from pxeboot and it probably > makes sense to have that option. > > -- > Andriy Gapon > _______________________________________________ > 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 Sun May 28 21:00:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42954D85108 for ; Sun, 28 May 2017 21:00:44 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 378551A57 for ; Sun, 28 May 2017 21:00:44 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SL017N035962 for ; Sun, 28 May 2017 21:00:44 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201705282100.v4SL017N035962@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 28 May 2017 21:00:44 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 21:00:44 -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 | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic New | 213410 | [carp] service netif restart causes hang only whe New | 215874 | [patch] [icmp] [mbuf_tags] teach icmp_error() opt New | 217748 | sys/dev/ixgbe/if_ix.c: PVS-Studio: Assignment to Open | 173444 | socket: IPV6_USE_MIN_MTU and TCP is broken 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 | 211031 | [panic] in ng_uncallout when argument is NULL Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ Open | 218653 | Intel e1000 network link drops under high network 19 problems total for which you should take action. From owner-freebsd-net@freebsd.org Sun May 28 21:49:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 403ABD864E7 for ; Sun, 28 May 2017 21:49:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6B7CA1A3D; Sun, 28 May 2017 21:49:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA13247; Mon, 29 May 2017 00:49:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dF63g-000Lke-EA; Mon, 29 May 2017 00:49:08 +0300 Subject: Re: svn commit: r314948 - in head: lib/libstand sys/boot/i386/libi386 To: "Rodney W. Grimes" Cc: Kamil Czekirda , Baptiste Daroussin , "George V. Neville-Neil" , Steven Hartland , Toomas Soome , freebsd-net@FreeBSD.org, Mariusz Zaborski References: <201705281538.v4SFcxJ7018338@pdx.rh.CN85.dnsmgr.net> From: Andriy Gapon Message-ID: Date: Mon, 29 May 2017 00:48:12 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <201705281538.v4SFcxJ7018338@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 21:49:13 -0000 On 28/05/2017 18:38, Rodney W. Grimes wrote: >> On 28/05/2017 01:09, Kamil Czekirda wrote: >>> In initial revision I noticed, that I'm not sure it should be default behavior. >>> In a lot of installations pxeloader can base on the cache and doesn't require >>> second, full request with the same answer. In that situation we can switch off >>> bootp() and I think it would be nice to have this switch and give them to users. >>> Flag during compilation is sensible. >>> >>> In very simple and popular case we have chain with four requests for the same >>> information (!): >>> PXE (NIC) -> iPXE -> pxeloader -> dhclient >>> and it's possible to switch off request from iPXE and pxeloader without breaking >>> boot process. >> >> Well, the information given to PXE/NIC and iPXE is not exactly the same as >> bootfile must differ. Also, a nit: as far as I know, it's currently impossible >> to run dhclient on a network booted _diskless_ system. > > I dont think that is actually true. Infact dont we need to run > dhclient on a diskless client if we intend to keep our dhcp lease beyond the > initial issue time period, ie renewal ever X minutes? Well, just test it. >> So, yeah, in some setups we can shave off a request from pxeboot and it probably >> makes sense to have that option. -- Andriy Gapon From owner-freebsd-net@freebsd.org Sun May 28 23:10:03 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5718AD84B61 for ; Sun, 28 May 2017 23:10: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 mx1.freebsd.org (Postfix) with ESMTPS id 3B5DACA6 for ; Sun, 28 May 2017 23:10:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SNA32M035737 for ; Sun, 28 May 2017 23:10:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219625] Can't connect to Internet with Realtek 8111E/8168 Ethernet: both 11.0-STABLE and CURRENT Date: Sun, 28 May 2017 23:10:03 +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.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: 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.23 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, 28 May 2017 23:10:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219625 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --- Comment #1 from Mark Linimon --- Is this problem also in FreeBSD 10? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun May 28 23:48:45 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D1A9D8656A for ; Sun, 28 May 2017 23:48:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F48712B8 for ; Sun, 28 May 2017 23:48:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SNmjcT036230 for ; Sun, 28 May 2017 23:48:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 205592] TCP processing in IPSec causes kernel panic Date: Sun, 28 May 2017 23:48:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? 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.23 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, 28 May 2017 23:48:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205592 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org --- Comment #6 from Eugene Grosbein --- Please consider testing 11.1-PRERELEASE. It has network stack improved in m= any areas including new IPSEC implementation that is quite stable for me. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun May 28 23:55:04 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69AA5D86924 for ; Sun, 28 May 2017 23:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 593BCC0E for ; Sun, 28 May 2017 23:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SNt4T3055114 for ; Sun, 28 May 2017 23:55:04 GMT (envelope-from bugzilla-noreply@freebsd.org) 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: Sun, 28 May 2017 23:55:04 +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: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? 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.23 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, 28 May 2017 23:55:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199136 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org --- Comment #10 from Eugene Grosbein --- Please note that this problem now has solution in form of "ifconfig tap0 li= nk0" that keeps interface up on last close unconditionally. This feature is pres= ent in 12-CURRENT and 11.0 but has not been MFC'd to stable/10. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 29 00:02:50 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B380D86EF2 for ; Mon, 29 May 2017 00:02:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 895E81266 for ; Mon, 29 May 2017 00:02:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4T02nud091006 for ; Mon, 29 May 2017 00:02:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 203422] mpd/ppoe not working with re(4) with revision 285177 Date: Mon, 29 May 2017 00:02:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? X-Bugzilla-Changed-Fields: cc 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.23 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, 29 May 2017 00:02:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203422 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org Resolution|--- |FIXED Status|In Progress |Closed --- Comment #5 from Eugene Grosbein --- The fix was committed and merged to stable/10 long time ago and it is prese= nt in 10.3-RELEASE. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon May 29 01:14:39 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 874AFD77F44 for ; Mon, 29 May 2017 01:14:39 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6215E1FDF for ; Mon, 29 May 2017 01:14:38 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:59963] helo=localhost) by dnvrco-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 53/7A-27444-5B57B295; Mon, 29 May 2017 01:13:25 +0000 Date: Mon, 29 May 2017 01:13:12 +0000 Message-ID: <53.7A.27444.5B57B295@dnvrco-omsmta02> From: "Thomas Mueller" To: freebsd-net@freebsd.org Subject: [Bug 219625] Re: Can't connect to Internet with Realtek 8111E/8168 Ethernet: both 11.0-STABLE and CURRENT References: X-RR-Connecting-IP: 107.14.64.7:25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 01:14:39 -0000 --- Comment #1 from Mark Linimon --- Is this problem also in FreeBSD 10? This problem was in FreeBSD 10 but was fixed somewhere around the time of 10.2. As for possible relapse, I can't say, because I no longer have 10.x-STABLE on hard drive: updated to 11.0-STABLE. Tom From owner-freebsd-net@freebsd.org Mon May 29 06:27:00 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14383C7DE40 for ; Mon, 29 May 2017 06:27:00 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: from dedi548.your-server.de (dedi548.your-server.de [85.10.215.148]) (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 1DCBB98F for ; Mon, 29 May 2017 06:26:19 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: from [78.47.166.52] (helo=sslproxy04.your-server.de) by dedi548.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85_2) (envelope-from ) id 1dFE88-0006fv-U0 for freebsd-net@freebsd.org; Mon, 29 May 2017 08:26:16 +0200 Received: from [82.135.62.35] (helo=mail.embedded-brains.de) by sslproxy04.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFE88-0000ZG-NE for freebsd-net@freebsd.org; Mon, 29 May 2017 08:26:16 +0200 Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 7733C2A0929 for ; Mon, 29 May 2017 08:27:04 +0200 (CEST) Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id RyCnvNNSpgql for ; Mon, 29 May 2017 08:27:04 +0200 (CEST) Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 22DD22A160A for ; Mon, 29 May 2017 08:27:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at zimbra.eb.localhost Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id XZOZDrr0S6qn for ; Mon, 29 May 2017 08:27:04 +0200 (CEST) Received: from [192.168.96.129] (unknown [192.168.96.129]) by mail.embedded-brains.de (Postfix) with ESMTPSA id 029C82A0929 for ; Mon, 29 May 2017 08:27:03 +0200 (CEST) Subject: Re: Basic support for IEEE 802.3ae clause 45 phys? From: Sebastian Huber To: freebsd-net@freebsd.org References: <1b17f1a4-54ad-0d1d-32fc-09f781358a27@embedded-brains.de> Message-ID: Date: Mon, 29 May 2017 08:26:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1b17f1a4-54ad-0d1d-32fc-09f781358a27@embedded-brains.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: smtp-embedded@poldinet.de X-Virus-Scanned: Clear (ClamAV 0.99.2/23427/Mon May 29 02:59:42 2017) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 06:27:00 -0000 On 24/05/17 10:21, Sebastian Huber wrote: > Hello, > > is there some basic support for IEEE 802.3ae clause 45 phys planned in=20 > FreeBSD? It seems there was some activity in this area: https://reviews.freebsd.org/D4607 However, I cannot find any uses of the MDIO_READEXTREG and=20 MDIO_WRITEEXTREG methods. --=20 Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.huber@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine gesch=C3=A4ftliche Mitteilung im Sinne des EHUG= . From owner-freebsd-net@freebsd.org Mon May 29 06:50:37 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 786BECC23EF for ; Mon, 29 May 2017 06:50:37 +0000 (UTC) (envelope-from zbeeble@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 D0E301A47 for ; Mon, 29 May 2017 06:50:36 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id d127so45671682wmf.0 for ; Sun, 28 May 2017 23:50:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=GcF9uKY9YTMVGGSvAoShfONhXYuPMjJ5dC+D0ADuaOM=; b=WwXQqvcbG3UTWM7BQTM7ayKPTRuhNNIRdxMShRbDY3+H7FivM1ovly2k/IA1NfQsms q5Qt9d0JH+IZiQCY5b9ajmMCG7jzj7dX5qwvjDJMql56YRD7ASnGnnD9YQsg0pS8kaR/ LeVIiQq0t/ao4sfo9H06QzrMRjPsmQz30MYFuob0VJrZ/2FLILT13Od423AplrH5it+s LK8NufoGE9jT47T9gamR3Et/E+SVJkHibO+DPfkZFulnBVtQpTBfmAivAZp4GZC975xw A+Ebc+Dzm1euZH4otAK3+agPFRIPK3BzV3r0Mz9Ze8uAl0o0Jf4m3kiDsisyaTWbc344 COVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=GcF9uKY9YTMVGGSvAoShfONhXYuPMjJ5dC+D0ADuaOM=; b=NaTFD/cuX5RCxKdNktvc1iuyrF7W2PZ+BoloieFArA74oPLVGcULQ/ic0BHFMXYLcw or5bxQJo7GbE+PVbJRy+D5g3KXsy++xd38EwTiPveziSVZWf9FCbi97OboLIoiJpvcZn 0haOmkwXwEFWFkcr9848FYk3JlTwMwwEdZlbzvRe9GybrHXG6Dis1xvNLUv6qV54XClK O8ugVcavWcIaXD1WD8P6aBkKjvUamL2Uz6z2BUJOtL7I8H1Qj0GJkjnhoTGsUWOUqc6e A+Jnz5rbBXYcEkJZ8MqGfVJrzTFu6WqiALA+htUNn1NpXf1f7EG6JsBEMtmLfJTnHr+D NDbQ== X-Gm-Message-State: AODbwcCsUgRfnCqaoILg6f/yzSD8qNbjAbMi/vL944Ez/oe0QrxQYsPO DHEp74jQmWN2GASzV7OKvLPn4gfdCg== X-Received: by 10.80.167.4 with SMTP id h4mr11698496edc.142.1496040635347; Sun, 28 May 2017 23:50:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.186.24 with HTTP; Sun, 28 May 2017 23:50:34 -0700 (PDT) From: Zaphod Beeblebrox Date: Mon, 29 May 2017 02:50:34 -0400 Message-ID: Subject: OCD window scaling behavior on local network. To: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 06:50:37 -0000 so... I have some really OCD window scaling behavior on a GigE local network. The protocol is BGP, this is one session recorded. Nearly every payload packet is answered by both an 'ACK' and a 2nd window scaling packet. I have examined the packet counters: no errors reported by the box or the managed switch. Also, TCP-MD5 is not in use, if that matters. [image: Inline image 1] From owner-freebsd-net@freebsd.org Mon May 29 17:51:15 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 544FBD7C3E1 for ; Mon, 29 May 2017 17:51:15 +0000 (UTC) (envelope-from emorrasg@yahoo.es) Received: from n3-vm3.bullet.mail.ir2.yahoo.com (n3-vm3.bullet.mail.ir2.yahoo.com [212.82.98.205]) (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 C3768837E4 for ; Mon, 29 May 2017 17:51:14 +0000 (UTC) (envelope-from emorrasg@yahoo.es) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1496080124; bh=Lm1OoEo1L/BNSmpHxnmV6zkgojZ46yPS8+Bp2+Si4BU=; h=Date:From:To:Subject:From:Subject; b=TkrsnKiwzqJU0plmo5z9sawN5P+0Ja8CyFuiDLT3bwiICnt5gkgFbhxejzdUjdbhBLvnUuPlJQ4399jsI2OfemsT3/2LaBuQmFjzlIK9jsUSRml24qcZ18swYttiIqMjaIeB9mN/DTyQZoY22xFaaV/Et7Nkh1MWANT/I3vg1ow5/+cmyMRdHGOg0NrqG07Z4mR/vnGdXGFsSHCRHcv7CvcW587na/tjbao8joX8oaIvrGJCLb18OVjjx+50bV/1ir4otx8DrzvEdW9cCRLsssmA2DDkKYfmtOpMqB9nzwKb+T+zoH6dKMwG3wvfiAb5qaWYoarcorsDsujguLKshA== Received: from [46.228.39.24] by n3.bullet.mail.ir2.yahoo.com with NNFMP; 29 May 2017 17:48:44 -0000 Received: from [46.228.39.72] by t5.bullet.mail.ir2.yahoo.com with NNFMP; 29 May 2017 17:48:44 -0000 Received: from [127.0.0.1] by smtp109.mail.ir2.yahoo.com with NNFMP; 29 May 2017 17:48:44 -0000 X-Yahoo-Newman-Id: 192727.24485.bm@smtp109.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: VQHFdIcVM1lJb2amd4hNN1yTn4CVMor_ZR8sFGBs5IrwdOT h3I7lT7Y2OYb69FxJrxgvSOVIejLHQjAjHJTpSV6j8qwqaOgx9_VizHxWPpq 4yTirD9V9_ObHDpWF3Bpl8zDZkvNFBhEQzMnE7f53Rg1y8EkBuIRNLizim29 zdPASXZVTlLHKSh.Okk5oNgdEHHeS0tactEDERainz6kWGHyNUg3i2keKX3T XkmSiM127ffCixKoZQq_grwNZwaadp.7nyCP0KuS86rJSYIhXQp6EDHFh5Pv hnceCn.gGd6KU.wxbP2WQDwtsweY.vMr0v1GcJXwc4Ej4grcpn_Ro5oZcCNC HMJVlYJghlmzkSo36GsJ8_BMlIcYANHJR2gkbCf36DAPnA8fWnOmS4Z6.Rrd QkQDuxQF69B5HEUMD8huQljePBNy8Ghg9mf0jdapbuJruCYCp9W3sFgdV_44 .BgUIjCup1ZkQyJRvrN9ThWiYybjIGE6raC4sRfOlxZVvdzj2ezy0e4yz77L K576GmKhYXNGDr..DUg8lV2yDumz9tk2FZb8s7jSwi2YMkkmgTAsi_hLMkJX Br7IlFxnGMSxHA0Uf X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Mon, 29 May 2017 19:51:19 +0200 From: Eduardo Morras To: freebsd-net@freebsd.org Subject: Does sendfile support sctp? Message-Id: <20170529195119.4b2de37e2de21280327b72a3@yahoo.es> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) 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.23 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, 29 May 2017 17:51:15 -0000 Hello, Does sendfile support sctp protocol? The sendfile man page description says: "The sendfile() system call sends a regular file or shared memory object specified by descriptor fd out a stream socket specified by descriptor s." Without specifying TCP or UDP or other protocol. Must I assume it's only for tcp sockets? Thanks --- --- Eduardo Morras From owner-freebsd-net@freebsd.org Mon May 29 18:13:33 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CFAAD7CD4C for ; Mon, 29 May 2017 18:13:33 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (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 C9E358434F for ; Mon, 29 May 2017 18:13:32 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [192.168.1.204] (p57BB4FC1.dip0.t-ipconnect.de [87.187.79.193]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 2B1E1721E280D; Mon, 29 May 2017 20:13:21 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Does sendfile support sctp? From: Michael Tuexen In-Reply-To: <20170529195119.4b2de37e2de21280327b72a3@yahoo.es> Date: Mon, 29 May 2017 20:13:19 +0200 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <96BD1B4D-E296-4C30-9159-166DC1EA866E@lurchi.franken.de> References: <20170529195119.4b2de37e2de21280327b72a3@yahoo.es> To: Eduardo Morras X-Mailer: Apple Mail (2.3273) 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.23 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, 29 May 2017 18:13:33 -0000 > On 29. May 2017, at 19:51, Eduardo Morras via freebsd-net = wrote: >=20 >=20 > Hello, Does sendfile support sctp protocol? The sendfile man page = description says: >=20 > "The sendfile() system call sends a regular file or shared memory = object > specified by descriptor fd out a stream socket specified by descriptor = s." >=20 > Without specifying TCP or UDP or other protocol. >=20 > Must I assume it's only for tcp sockets? It works for TCP and worked for SCTP at one point of time. Not sure if = it still works since the sendfile implementation was changed at one point of = time. Best regards Michael >=20 > Thanks >=20 > --- --- > Eduardo Morras > _______________________________________________ > 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 Tue May 30 17:54:27 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 004BCB954FF for ; Tue, 30 May 2017 17:54:27 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 9653872F0D for ; Tue, 30 May 2017 17:54:26 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v4UHsNZT041911 for ; Tue, 30 May 2017 19:54:23 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 7B799A3C; Tue, 30 May 2017 19:54:23 +0200 (CEST) Message-ID: <592DB1CE.8000801@omnilan.de> Date: Tue, 30 May 2017 19:54:22 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: tools/netmap/pkt-gen: clang error Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 30 May 2017 19:54:23 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 17:54:27 -0000 Hello, after merging netmap code from head I can't compile pkt-gen from usr/src/tools/tools/netmap: cc -O2 -pipe -Werror -Wall -Wextra -march=ivybridge -g -std=gnu99 -fstack-protector-strong -Qunused-arguments -Qunused-arguments -std=gnu99 -fstack-protector-strong -Qunused-arguments -Qunused-arguments -c pkt-gen.c -o pkt-gen.o pkt-gen.c:650:19: error: taking address of packed member 'ip' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] struct ip *ip = &pkt->ip; ^~~~~~~ pkt-gen.c:651:24: error: taking address of packed member 'udp' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] struct udphdr *udp = &pkt->udp; ^~~~~~~~ pkt-gen.c:745:8: error: taking address of packed member 'ip' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] ip = &pkt->ip; ^~~~~~~ pkt-gen.c:762:9: error: taking address of packed member 'udp' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] udp = &pkt->udp; Quick hints highly appreciated. Thanks, -harry From owner-freebsd-net@freebsd.org Tue May 30 18:30:22 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1129CBD3167 for ; Tue, 30 May 2017 18:30:22 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDE9474634 for ; Tue, 30 May 2017 18:30:21 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pf0-x231.google.com with SMTP id m17so79577274pfg.3 for ; Tue, 30 May 2017 11:30:21 -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=wYmWECTy3gQglXemIXDnOB77PlINCVEExvKLnU2Qyzw=; b=eEcvOdIEcsjvi+w8OUUITnEEYdyDCheiNPRWeIGztC2JW7TSvzt0XpBYQJgtrUFyX5 EnA/srJd5Vs0msuUDg0x/MoV9/bk/IwjxlNOlcL5YM6iFc+mcdOjgqxMMmI7WU8X1chP Q7OHiVDXwjCx9/qFOvLKrFnMuY2ePTlNgOWwOrUsCy+753IHTJmSAB2ond5j1qtxUV55 718lEs4LJIZJIm5cwIeHPt8Lw/acm8ztWzqmJi4+5m6Fa+DO1G4CoJRPNTd7niNluJ03 njDyH4MBYKbeeS/Y09BmLbDaiDGjWowrqzgaBeiYQkPD1J3aBLC2dwXLjGBzBQJyaaWn RQ9Q== 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=wYmWECTy3gQglXemIXDnOB77PlINCVEExvKLnU2Qyzw=; b=flj0PHmX/LksiviRhPDe9wimg3eA7KXkyz1M2DahLbC+oRF7EIEyLLK358EF/vtqHM nh3iZZ3QgAKTupdAyHW1ustiGriZb+uEgD/Eoactgq7n0VJc/yp9djblLhNSD5cJGH+M 6Ir4TkEoFowq60tq5hTpvPaQZtNqvdgSHxVHhsDvcXh1u5u5xB5ykwbnRlpO+ZXO9faO 9J0i9i6HrUlEY8pFtcAsxpEzuNt6zv5NoDXKV8HMWTvy6LSsbBkQzVzeSsLl5lyY7+3U NdZIrk8R9+0Oy8cxbh9Xzc4ebvpCs818vk8jzlMuIABMuomnBqZ74dM+1rLUUcZkNtnJ tB1A== X-Gm-Message-State: AODbwcC74gU92fhqpca+UlEMGi+i2m/t85EXKfiPkaJfiGHsiMRSuJfZ zpHgQkYZjUm1ttsdcnFmEb3Yy/T3Kg== X-Received: by 10.99.127.73 with SMTP id p9mr27501146pgn.169.1496169021375; Tue, 30 May 2017 11:30:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.185.75 with HTTP; Tue, 30 May 2017 11:30:20 -0700 (PDT) In-Reply-To: <592DB1CE.8000801@omnilan.de> References: <592DB1CE.8000801@omnilan.de> From: Navdeep Parhar Date: Tue, 30 May 2017 11:30:20 -0700 Message-ID: Subject: Re: tools/netmap/pkt-gen: clang error To: Harry Schmalzbauer Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 18:30:22 -0000 You can suppress the warning with something like this: # cd /usr/src/tools/tools/netmap # WARNS=2 make Regards, Navdeep On Tue, May 30, 2017 at 10:54 AM, Harry Schmalzbauer wrote: > Hello, > > after merging netmap code from head I can't compile pkt-gen from > usr/src/tools/tools/netmap: > cc -O2 -pipe -Werror -Wall -Wextra -march=ivybridge -g -std=gnu99 > -fstack-protector-strong -Qunused-arguments -Qunused-arguments > -std=gnu99 -fstack-protector-strong -Qunused-arguments > -Qunused-arguments -c pkt-gen.c -o pkt-gen.o > pkt-gen.c:650:19: error: taking address of packed member 'ip' of class > or structure 'pkt' may result in an unaligned pointer value > [-Werror,-Waddress-of-packed-member] > struct ip *ip = &pkt->ip; > ^~~~~~~ > pkt-gen.c:651:24: error: taking address of packed member 'udp' of class > or structure 'pkt' may result in an unaligned pointer value > [-Werror,-Waddress-of-packed-member] > struct udphdr *udp = &pkt->udp; > ^~~~~~~~ > pkt-gen.c:745:8: error: taking address of packed member 'ip' of class or > structure 'pkt' may result in an unaligned pointer value > [-Werror,-Waddress-of-packed-member] > ip = &pkt->ip; > ^~~~~~~ > pkt-gen.c:762:9: error: taking address of packed member 'udp' of class > or structure 'pkt' may result in an unaligned pointer value > [-Werror,-Waddress-of-packed-member] > udp = &pkt->udp; > > Quick hints highly appreciated. > > Thanks, > > -harry > _______________________________________________ > 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 Tue May 30 21:10:59 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84BBABEDFA4 for ; Tue, 30 May 2017 21:10: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 mx1.freebsd.org (Postfix) with ESMTPS id 72BC57A36E for ; Tue, 30 May 2017 21:10:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4ULAxYn052214 for ; Tue, 30 May 2017 21:10:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Tue, 30 May 2017 21:10:59 +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.0-RELEASE X-Bugzilla-Keywords: 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: 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.23 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, 30 May 2017 21:10:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- 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 Wed May 31 02:43:07 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07B19BF394C for ; Wed, 31 May 2017 02:43: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 mx1.freebsd.org (Postfix) with ESMTPS id EA4DE84537 for ; Wed, 31 May 2017 02:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4V2h5ZH002992 for ; Wed, 31 May 2017 02:43:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 02:43:06 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 02:43:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org --- Comment #3 from Eugene Grosbein --- kern.ipc.soacceptqueue is SYSCTL_PROC defined in sys/kern/uipc_socket.c wit= hout CTLFLAG_VNET, so it is not VIMAGE/VNET-aware currently. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 05:29:41 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 422A2A92D47 for ; Wed, 31 May 2017 05:29: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 mx1.freebsd.org (Postfix) with ESMTPS id 300C364238 for ; Wed, 31 May 2017 05:29:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4V5TeSj003032 for ; Wed, 31 May 2017 05:29:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218894] Network dropouts on em(4) due to jumbo cluster failures Date: Wed, 31 May 2017 05:29:40 +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.0-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: kaho@elam.kais.kyoto-u.ac.jp 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: cc attachments.created 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.23 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, 31 May 2017 05:29:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218894 Kaho Toshikazu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaho@elam.kais.kyoto-u.ac.j | |p --- Comment #1 from Kaho Toshikazu --- Created attachment 183084 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183084&action= =3Dedit a patch for jumbo frame and others I don't have a trouble denied some packets temporarily but a trouble dropped many packets with jumbo frames. I use 12-current with a similar patch attac= hed this comment, and the patch does not make everything correct but makes better condition. I have three devices, 82574L, I217-V, I218-V. I don't have any trouble for I21[78] regardless with or without the patch when mtu is 1500. With 9k jumbo, without the patch, scp speed is very slow and dev.em.0.rx_overruns increases. On 82574L, dev.em.0.rx_overruns increases without the patch and dev.em.0.mac_stats.recv_no_buff increases with the patch. Above 6k jumbo, scp speed is almost 10kB/s without the patch and the speed is about 10MB/s with the patch. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 08:34:31 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79692AFA3BD for ; Wed, 31 May 2017 08:34:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67A2D6E54F for ; Wed, 31 May 2017 08:34:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4V8YVq3077731 for ; Wed, 31 May 2017 08:34:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219674] rpcbind -h breaks broadcast functionality Date: Wed, 31 May 2017 08:34:31 +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 Only Me X-Bugzilla-Who: avg@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: 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.23 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, 31 May 2017 08:34:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219674 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- 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 Wed May 31 12:29:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65323AFF7A5 for ; Wed, 31 May 2017 12:29:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 531B6764EB for ; Wed, 31 May 2017 12:29:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VCThsA058293 for ; Wed, 31 May 2017 12:29:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 12:29:44 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john.leo@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 12:29:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #4 from john.leo@gmail.com --- That makes more sense. Is there a way around this or a way to increase the connection queue in a jail that has VIMAGE enabled? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 13:21:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B36B5B79FFE for ; Wed, 31 May 2017 13:21:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A12A77963C for ; Wed, 31 May 2017 13:21:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VDLIGb021872 for ; Wed, 31 May 2017 13:21:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 13:21:19 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 13:21:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #5 from Eugene Grosbein --- (In reply to john.leo from comment #4) You could just patch sys/sys/socket.h and increase value on a line "#define SOMAXCONN 128" (this is used to specify initial value for a sysctl only). Or, if you are curious enough, you can add CTLFLAG_VNET flag to declaration= of soacceptqueue in sys/kern/uipc_socket.c and see if it will work or crash :-) That is, until SomeOne (TM) prepares complete solution. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:22:31 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A869FB7B436 for ; Wed, 31 May 2017 14:22:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9166F7C493 for ; Wed, 31 May 2017 14:22:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEMUwj099151 for ; Wed, 31 May 2017 14:22:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:22:30 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: attachments.created 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.23 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, 31 May 2017 14:22:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #6 from Eugene Grosbein --- Created attachment 183099 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183099&action= =3Dedit make per-VNET soacceptqueue/somaxconn and numopensockets At attempt to make sysctl soacceptqueue (somaxconn) and numopensockets per-VNET/VIMAGE instead of global. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:23:33 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CCA7B7B4B4 for ; Wed, 31 May 2017 14:23:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B2C27C580 for ; Wed, 31 May 2017 14:23:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VENXaM001434 for ; Wed, 31 May 2017 14:23:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:23:33 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 14:23:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #7 from Eugene Grosbein --- (In reply to john.leo from comment #4) You may also try attached patch. Beware, as it is compile-only tested. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:34:48 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB4C7B7B846 for ; Wed, 31 May 2017 14:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 999B77CB00 for ; Wed, 31 May 2017 14:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEYmPG029075 for ; Wed, 31 May 2017 14:34:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:34:48 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john.leo@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 14:34:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #8 from john.leo@gmail.com --- Thanks, would this be for the main OS itself or for use in the jail? Also = I'm having trouble finding that file within the OS, I couldn't find it at the p= ath you provided. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:40:22 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 621DAB7B9B2 for ; Wed, 31 May 2017 14:40:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FAC37CEF6 for ; Wed, 31 May 2017 14:40:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEeMrX037334 for ; Wed, 31 May 2017 14:40:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:40:22 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 14:40:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #9 from Eugene Grosbein --- (In reply to john.leo from comment #8) The patch is for sys/kern/uipc_socket.c - that is, for kernel. Jails do not have own kernels, there is only one kernel in running system. You need to rebuild and reinstall kernel after patch and reboot the system to apply changes. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:41:20 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA878B7BA48 for ; Wed, 31 May 2017 14:41:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D91E77D14E for ; Wed, 31 May 2017 14:41:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEfKcQ041235 for ; Wed, 31 May 2017 14:41:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:41:21 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 14:41:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #10 from Eugene Grosbein --- That is, for main OS and /usr/src/sys/kern/uipc_socket.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:44:40 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DAD4B7BC6E for ; Wed, 31 May 2017 14:44:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C0E87D3DB for ; Wed, 31 May 2017 14:44:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEid9i055082 for ; Wed, 31 May 2017 14:44:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:44:40 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john.leo@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 14:44:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #11 from john.leo@gmail.com --- Thanks, for some reason it is showing that /usr/src is an empty directory o= n my system. I think I'd also like to set up a dev system to test this out rath= er than run it in production. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 14:48:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FFE9B7BD60 for ; Wed, 31 May 2017 14:48:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E78C7D51A for ; Wed, 31 May 2017 14:48:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VEm8mF060865 for ; Wed, 31 May 2017 14:48:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 14:48: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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bz@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: 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.23 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, 31 May 2017 14:48:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 Bjoern A. Zeeb changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bz@FreeBSD.org --- Comment #12 from Bjoern A. Zeeb --- Making these variables per-VNET is not necessarily a good idea; it means a VNET-jail consumer could possibly DoS the system without the administrator having a chance to prevent this easily by exceeding resources. Need to be very careful. I'd hope if this should go into HEAD that there'l= l be a way to "cap" the values or reject excessive requests by some metric at le= ast. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 15:12:08 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED4B9B7C981 for ; Wed, 31 May 2017 15:12:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB5F17F9EC for ; Wed, 31 May 2017 15:12:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VFC8sM058042 for ; Wed, 31 May 2017 15:12:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] TCP Connection Limit Error - sonewconn: Listen queue overflow Date: Wed, 31 May 2017 15:12:08 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@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: 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.23 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, 31 May 2017 15:12:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 --- Comment #13 from Eugene Grosbein --- (In reply to Bjoern A. Zeeb from comment #12) These variables are global currently but this does not mean the limits they impose are "global" in any way: static u_int somaxconn is just default for per-socket backlog limit so->so_qlimit (struct socket *so) and this change makes it possible to assign different defaults per-jail. Yes, increase of such limit allows jailed root to get more space in the que= ue of not accepted yet sockets but theres is already plenty ways to consume su= ch resources (f.e. by creating listening socket and making tons of local connections). Perhaps, this sysctl should be made read-only for jailed root= , if possible. V_numopensockets is purely informational. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 31 19:59:34 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A062B88554 for ; Wed, 31 May 2017 19:59:34 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 C466C66566 for ; Wed, 31 May 2017 19:59:33 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v4VJxTvO062953 for ; Wed, 31 May 2017 21:59:29 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 65ACFCBE; Wed, 31 May 2017 21:59:29 +0200 (CEST) Message-ID: <592F20A0.4020702@omnilan.de> Date: Wed, 31 May 2017 21:59:28 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-net Subject: Re: ovs-netmap forgotten? References: <5926FFDB.7040900@omnilan.de> In-Reply-To: <5926FFDB.7040900@omnilan.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Wed, 31 May 2017 21:59:29 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 19:59:34 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 25.05.2017 18:01 (localtime): > Hello, > > I found lots of interesting papers about research and improvements > regarding Open vSwitch and netmap (on FreeBSD, e.g. > http://changeofelia.info.ucl.ac.be/pmwiki/uploads/SummerSchool/Program/poster_001.pdf) > > Again, University of Pisa with a famous team arround Luigi Rizzo did > some highly appreciated coding and presentation, the paper in the link > is from Gaetano Catalli (cc'd). > > But it seems that this work got lost in space... > openvswitch in ports is quiet old codebase without any > netmap-integration and a provided patch isn't in our netmap tree: > https://github.com/cnplab/ovs-netmap/blob/master/0001-datapath-Add-support-for-netmap-VALE.patch > > So I guess nobody uses ports/net/openvswitch these days anymore. > > I also found a FreeBSD kernel module was written back in 2014. But that > seems also got lost, which most likely was due to ovs-netmap replacement? > > Thanks for any hints, I made little progress answering my questions myself and still appreciate any hints, hopefully providing some hints for others getting into OVS/netmap. I found the ovs-netmap work, it's part of the standard netmap github repository (https://github.com/luigirizzo/netmap) under utils/switch-modules. In case someody is interested, I prepared a very draft net/openvswitch port, updated to 2.6.1 and extended by the ovs-netmap patch. Compiles and runs, but the result isn't fully tested yet nor is the port rellay correct istelf (haven't fired up portlint) or complete (wanted to integrate DPDK too...) Unfortunately it doesn't seem to be what I expected (a datapath/dataplane implementation). It seems on FreeBSD we still have to run Open vSwitch in userspace (which is described in INSTALL.userspace.md – all other documentation seem to assume you're running linux and have the kernel module loadad). The description in INSTALL.NETMAP, part of the mentioned patch, brings up more questions than answers for me, most likely due to a still considerable ammount of personal knwoledge absence. I don't get the idea of 'vale-ctl -n', which provides a netmap-only(?) interface, but even if I imagine one side of the interface to connect to arbitrary netmap-app, I have no idea what the other side connects to. And that's my problem with the Open vSwitch integration. I can access an ovs bridge via netmap-app. But this doesn't improve the severe OVS limitations running on FreeBSD (doing frame copies in userspace). Hope someone can confirm I'm wrong? Thanks, -harry P.S.: Like partly mentioned in multiple other questions I posted recently, I need a way to fire up bhyve with '-s 2,virtio-net,vale0:guestport', while vale0 only distributes frames filtered by 802.1Q tag. I don't care much where the filtering happens, but there's not much choice. Unfortunately, plugging a vlan(4) clone into vale doesn't work, frames never make it into vale (while using the parent shows results as expected, so basic setup soud be ok). Next idea was to utilize Open vSwitch, but that's the most painful solution to get vlan tags filtered (which could do the nic itself)... I hoped vale(4) could be utilized by Open vSwitch, but it seems that the ovs-netmap approach is a completely different thing... From owner-freebsd-net@freebsd.org Wed May 31 22:39:46 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B3BCB95FF1 for ; Wed, 31 May 2017 22:39:46 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F24386F4EC for ; Wed, 31 May 2017 22:39:45 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id o65so9157219oif.1 for ; Wed, 31 May 2017 15:39:45 -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=yNcBLpqNe8EfaurecsDTFPh8KOdDd72TOhLDB/jsNgY=; b=rVkYI/oo2MWRlyfWaucyXjgfiyAubnV5H1G8EeObTqtjvFGN1TfOhb5juRVkmXPdLq v23Mora8VxvLW4En1NvTqfbHR9X010eLlosBo2SFAa+2W0tYaIxLHFcfRYXE/kElJJiL yL3os+b2BnFIyn8RS+pZq88tsTIbFl+mzcdbtyNM8StHOF3hzmUivFGG6JRlFSOlzTgq 4cjumuSOOKB0rBsK3ASjhsy5j5k+AZx8TNSwC8pQsPtKsH2i4bUk5WetxYp3CQHZdP4r bYczoBhYnbKGwGk5PU0ucuRKX2I8ftuhZLPZdM1UhGH4AbD/beno3TsWANBQkkN+urnS 4nuw== 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=yNcBLpqNe8EfaurecsDTFPh8KOdDd72TOhLDB/jsNgY=; b=aUfh4OpztfepBU8hkjD1nVhqmG7VUE0egn4q6OxPrq8iq3+Ra/37XzF6KH/kn8A/Cy TsQ5B2lbVDZIIi0DhiHo9j7HmhiyzdstAHCINxM6OyvBcPre7OVmAEzP/eEUYY33eQmo AxVj49Koor0amZ13zwtaE/QNcq1hBqiETdxjJt3MKrRIlC3NRoAEzjPw2DKc2+IL2P71 sVUreNfthFq5rc3hIrAemp0ohQaRTTmhEwOTzhz9nLKcyomC352Vz/PM/nqfXQx/D5Dk 9mT3zAfzETNSkKGEkDY1s4XMROKyT/cLHlMnFSlKbvVdykka5bCabp5SWeVXez7Hw1B2 TcBA== X-Gm-Message-State: AODbwcAgcgivLEsqX/brZazzbPoGCTAvmGweEUnPYfaka0XRnfe5mUnA zMIEm+K7CNG0TOl/ihU7T0jzm6SA9w== X-Received: by 10.202.81.206 with SMTP id f197mr11740996oib.89.1496270385249; Wed, 31 May 2017 15:39:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.17.59 with HTTP; Wed, 31 May 2017 15:39:44 -0700 (PDT) In-Reply-To: <592F20A0.4020702@omnilan.de> References: <5926FFDB.7040900@omnilan.de> <592F20A0.4020702@omnilan.de> From: Vincenzo Maffione Date: Thu, 1 Jun 2017 00:39:44 +0200 Message-ID: Subject: Re: ovs-netmap forgotten? To: Harry Schmalzbauer Cc: freebsd-net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 22:39:46 -0000 Hi Harry, OVS integration with netmap is very patchy and Linux only. Most importantly, it is not the right way to go, for a number of reasons. The real solution would be to integrate netmap into OVS would be to follow the DPDK-OVS approach: this means implementing the switching logic completely in userspace, in this case using the netmap API. This has not been implemented nor sketched so far. `vale-ctl -n valeXXX:YYY` just creates a persistent VALE port (YYY) attached to the VALE switch XXX. There is no difference with an ephemeral VALE port, apart for the fact that the persistent one is visible with ifconfig. It does not really make sense to attach a VLAN interface to VALE, since the VLAN driver does not have netmap support, so you lose all the advantage of using netmap and VALE. In your case the best solution I see is to write a custom netmap application that forwards the packets between a netmap-supported NIC and one or more VMs, doing the VLAN stripping in software. Cheers, Vincenzo 2017-05-31 21:59 GMT+02:00 Harry Schmalzbauer : > Bez=C3=BCglich Harry Schmalzbauer's Nachricht vom 25.05.2017 18:01 > (localtime): > > Hello, > > > > I found lots of interesting papers about research and improvements > > regarding Open vSwitch and netmap (on FreeBSD, e.g. > > http://changeofelia.info.ucl.ac.be/pmwiki/uploads/ > SummerSchool/Program/poster_001.pdf) > > > > Again, University of Pisa with a famous team arround Luigi Rizzo did > > some highly appreciated coding and presentation, the paper in the link > > is from Gaetano Catalli (cc'd). > > > > But it seems that this work got lost in space... > > openvswitch in ports is quiet old codebase without any > > netmap-integration and a provided patch isn't in our netmap tree: > > https://github.com/cnplab/ovs-netmap/blob/master/0001- > datapath-Add-support-for-netmap-VALE.patch > > > > So I guess nobody uses ports/net/openvswitch these days anymore. > > > > I also found a FreeBSD kernel module was written back in 2014. But that > > seems also got lost, which most likely was due to ovs-netmap replacemen= t? > > > > Thanks for any hints, > > I made little progress answering my questions myself and still > appreciate any hints, hopefully providing some hints for others getting > into OVS/netmap. > > I found the ovs-netmap work, it's part of the standard netmap github > repository > (https://github.com/luigirizzo/netmap) under utils/switch-modules. > > In case someody is interested, I prepared a very draft net/openvswitch > port, updated to 2.6.1 and extended by the ovs-netmap patch. Compiles > and runs, but the result isn't fully tested yet nor is the port rellay > correct istelf (haven't fired up portlint) or complete (wanted to > integrate DPDK too...) > > Unfortunately it doesn't seem to be what I expected (a > datapath/dataplane implementation). > It seems on FreeBSD we still have to run Open vSwitch in userspace > (which is described in INSTALL.userspace.md =E2=80=93 all other documenta= tion > seem to assume you're running linux and have the kernel module loadad). > > The description in INSTALL.NETMAP, part of the mentioned patch, brings > up more questions than answers for me, most likely due to a still > considerable ammount of personal knwoledge absence. > > I don't get the idea of 'vale-ctl -n', which provides a netmap-only(?) > interface, but even if I imagine one side of the interface to connect to > arbitrary netmap-app, I have no idea what the other side connects to. > > And that's my problem with the Open vSwitch integration. I can access an > ovs bridge via netmap-app. But this doesn't improve the severe OVS > limitations running on FreeBSD (doing frame copies in userspace). Hope > someone can confirm I'm wrong? > > Thanks, > > -harry > > P.S.: Like partly mentioned in multiple other questions I posted > recently, I need a way to fire up bhyve with '-s > 2,virtio-net,vale0:guestport', while vale0 only distributes frames > filtered by 802.1Q tag. I don't care much where the filtering happens, > but there's not much choice. > Unfortunately, plugging a vlan(4) clone into vale doesn't work, frames > never make it into vale (while using the parent shows results as > expected, so basic setup soud be ok). > Next idea was to utilize Open vSwitch, but that's the most painful > solution to get vlan tags filtered (which could do the nic itself)... I > hoped vale(4) could be utilized by Open vSwitch, but it seems that the > ovs-netmap approach is a completely different thing... > _______________________________________________ > 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" --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Wed May 31 22:43:03 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34161BD3282 for ; Wed, 31 May 2017 22:43:03 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 E6EF46FA67 for ; Wed, 31 May 2017 22:43:02 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x232.google.com with SMTP id h4so33928277oib.3 for ; Wed, 31 May 2017 15:43: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=IdvqQLmu+9D+GSiKAk1MoEO6HAt4E2Yyp+bHhlMf234=; b=eRTr3vgSR1VS8cq4PT19az9F1+y7TfAf2C0fxbSyfd4ksBlllqs7wm9k1gbyA6Ju2r FjzMnAzYsue+RqsC5b3DkV9yc7zZsqZERSSl6aGHVK0UQ08Y1g5OyrQue3PG0SlBYbWZ 0z0mGRuk0fVboISmU53/5/6C+VLBE06n10lLbLn4TamFAaMHq6u9taY5CfQPnxoDUgN6 BKFpevHVIimqbLWMTo57iIo2ePsWtY/kqHtXUA/zTEwg+Z/YpZPEq/oe5Li0ztwZkipO hatn277SK64UutUSH6IAuk1Xhm872Z5G/BtlATmZeZp1N+0ialGGbFtCi6cJK6HX/3kP FQtA== 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=IdvqQLmu+9D+GSiKAk1MoEO6HAt4E2Yyp+bHhlMf234=; b=pkQ4jWH+bKxw5DePvRpVOcBnW6Wc+RHL4K9HaucyVlPbhasVv9YEt/2bH7trGtb1KT FTrkInk5jmsylxq+rkmrsHjbBaxtS/8UpYmI9VV+xLyr9Ezmc9/0SGLt2cDRet45mmZS LiGu9gZIfEaTqmn9OfTu8kLOskUbarQoJF8WWqRA7IyYM7oQveySAcfYBXJkzU6ht5Er BwRCFwDSwV1vExdMMHZKRB0gYNyaGpszenl0TiRQNtgh0lxEq2QGzav3dt0QnMKQ0gy1 DXZ5Hn4qo5xGyYsvmRJ86DZ7BxEtADGhH56VMOcnEX+44+D4bOkIlp2uKbaI79/AMVyW sLlQ== X-Gm-Message-State: AODbwcDeED28Te1ZmpvjAnKwI6UJs3PlNH+xyFIF7X5LliU+356lwhTF xEromwSjI4q+an3yVH3QMuMiYo1lIw== X-Received: by 10.202.50.213 with SMTP id y204mr14155793oiy.164.1496270582175; Wed, 31 May 2017 15:43:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.17.59 with HTTP; Wed, 31 May 2017 15:43:01 -0700 (PDT) In-Reply-To: <5926F74A.1000101@omnilan.de> References: <58CBA727.3040108@omnilan.de> <58CBBF7A.8050604@omnilan.de> <58CC26CF.5050708@omnilan.de> <58CFA606.7090306@omnilan.de> <58D02259.9010101@omnilan.de> <5926F74A.1000101@omnilan.de> From: Vincenzo Maffione Date: Thu, 1 Jun 2017 00:43:01 +0200 Message-ID: Subject: Re: vale uplink via vlan-if [Was: Re: Are ./valte-ctl and ./bridge friends or competitors?] To: Harry Schmalzbauer Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 22:43:03 -0000 If VLAN interface do not work properly with VALE/netmap that's a bug of the emulated adapter code in FreeBSD. But in any case the approach is not the right one, since using the emulated netmap adapter with VALE will make you lose most of the advantage of using netmap in the first place. (see my previous email). Cheers, Vincenzo 2017-05-25 17:24 GMT+02:00 Harry Schmalzbauer : > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 21.03.2017 19:05 (localt= ime): > > 2017-03-20 19:41 GMT+01:00 Harry Schmalzbauer : > > > >> Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 20.03.2017 12:50 > (localtime): > >> =E2=80=A6 > >>>> So to summarize for newbies exploring netmap(4) world in combination > >>>> with physical uplinks and virtual interfaces, it's important to do t= he > >>>> following uplink NIC configuration (ifconfig(8)): > >>>> -rxcsum -txcsum -rxcsum6 -txcsum6 -tso -lro promisc > >>>> > >>> > >>> Exactly. This is mentioned at the very end of netmap(4): > >>> > >>> "netmap does not use features such as checksum offloading, TCP > >> segmentation > >>> offloading, encryption, VLAN encapsulation/decapsulation, etc. When > >> using > >>> netmap to exchange packets with the host stack, make sure to disable > >> these > >>> features." > >>> > >>> But it is probably a good idea to add these example ifconfig > instructions > >>> somewhere (man page or at least the README in the netmap repo). > >>> > >>> > >>>> > >>>> I guess vlanhwtag, vlanhwfilter and vlanhwtso don't interfere, do > they? > >>>> > >>> > >>> Well, I think they interfere: if you receive a tagged packet and the > NIC > >>> strips the tag and puts it in the packet descriptor, then with netmap > you > >>> will see the untagged packet, and you wouldn't have a way to see the > tag. > > Sorry picking this up again, but I'm stuck getting vale(4) productive :-( > > I took lagg(4) out of the game and configured my desired setup using > if_bridge(4) at first. > > The physical uplink NIC is em0. > The bridge/vale uplink is em0.232. > > hostB --switch-- em0-hostA > | > '- em0.232 > | > bridge5-vmnet0 > | > vtnet0-GUESTa <-tcpdump: > > 17:07:28.423768 00:a0:98:73:9f:42 > ff:ff:ff:ff:ff:ff, ethertype ARP > (0x0806), length 42: Request who-has 172.21.34.10 tell 172.21.35.1, > length 28 > 17:07:28.424208 00:0c:29:40:3a:dd > 00:a0:98:73:9f:42, ethertype ARP > (0x0806), length 60: Reply 172.21.34.10 is-at 00:0c:29:40:3a:dd, length 4= 6 > > The same is visable on vmnet0 nad em0 of course. > > Now if I replace bridge5 by vale, leaving everything else unchanged > besides using netmap-vtnet with bhyve, I don't get ARP is-at answer. > I can see the who-has on all interfaces involved, and also the is-at > answer up to em0.232, but not at vtnet0 (the guest, connected via vale). > > To draw the same picture like with bridge: > > hostB --switch-- em0-hostA > | > '- em0.232 > | > vale232:em0.232-' > vale232:GUESTa--vtnet0-GUESTa <-tcpdump: > > 17:16:00.111868 00:a0:98:73:9f:42 > ff:ff:ff:ff:ff:ff, ethertype ARP > (0x0806), length 42: Request who-has 172.21.34.10 tell 172.21.35.1, > length 28 > ... no reply > > While tcpdump of em0.232 shows: > 17:16:01.119537 00:a0:98:73:9f:42 > ff:ff:ff:ff:ff:ff, ethertype ARP > (0x0806), length 60: Request who-has 172.21.34.10 tell 172.21.35.1, > length 46 > 17:16:01.119849 00:0c:29:40:3a:dd > 00:a0:98:73:9f:42, ethertype ARP > (0x0806), length 60: Reply 172.21.34.10 is-at 00:0c:29:40:3a:dd, length 4= 6 > > The reply made it up to vale's uplink, but not through vale. Am I > missing something? > Tagging, checksum-disabling etc. seems to be right, since utilizing > if_bridge(4) gives the expected result, but I have no idea why I can't > get packets via vale(4). > > Important note: Using em0.232 parent (vlandev em0) for vale uplink does > work! > So I guess if_em(4)'s native netmap support interferes with the vlan clon= e. > I'm out at this point, far too less knwoledge about the code paths... > Can anybody else help here? > > Thanks, > > -harry > --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Thu Jun 1 00:57:21 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CA47BEE5B1 for ; Thu, 1 Jun 2017 00:57:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A8727331E for ; Thu, 1 Jun 2017 00:57:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v510vJI5020903 for ; Thu, 1 Jun 2017 00:57:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219655] Per-VNET soacceptqueue/somaxconn and numopensockets possible? Date: Thu, 01 Jun 2017 00:57:19 +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.0-RELEASE X-Bugzilla-Keywords: feature, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status short_desc 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.23 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, 01 Jun 2017 00:57:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219655 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |feature, needs-qa, patch Status|New |Open Summary|TCP Connection Limit Error |Per-VNET |- sonewconn: Listen queue |soacceptqueue/somaxconn and |overflow |numopensockets possible? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 07:45:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D82A5BEE39C for ; Thu, 1 Jun 2017 07:45:19 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 86E866A0A3 for ; Thu, 1 Jun 2017 07:45:19 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v517jFgU075722; Thu, 1 Jun 2017 09:45:15 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 47646E22; Thu, 1 Jun 2017 09:45:15 +0200 (CEST) Message-ID: <592FC60A.1030308@omnilan.de> Date: Thu, 01 Jun 2017 09:45:14 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: freebsd-net Subject: Re: ovs-netmap forgotten? References: <5926FFDB.7040900@omnilan.de> <592F20A0.4020702@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Thu, 01 Jun 2017 09:45:15 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 07:45:19 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 01.06.2017 00:39 (localtime): > Hi Harry, > OVS integration with netmap is very patchy and Linux only. Most > importantly, it is not the right way to go, for a number of reasons. > The real solution would be to integrate netmap into OVS would be to > follow the DPDK-OVS approach: this means implementing the switching > logic completely in userspace, in this case using the netmap API. This > has not been implemented nor sketched so far. > > `vale-ctl -n valeXXX:YYY` just creates a persistent VALE port (YYY) > attached to the VALE switch XXX. > There is no difference with an ephemeral VALE port, apart for the fact > that the persistent one is visible with ifconfig. > > It does not really make sense to attach a VLAN interface to VALE, since > the VLAN driver does not have netmap support, so you lose all the > advantage of using netmap and VALE. > In your case the best solution I see is to write a custom netmap > application that forwards the packets between a netmap-supported NIC and > one or more VMs, doing the VLAN stripping in software. Thanks again, Vincenzo, for your highly appreciated support! I can only concur to your proposed solution. Problem is, I don't speak any programmin language well (besides sh maybe) and have abosuletely no budget/time to do any work out on my C skills (which I'd love to do) ;-) So ovs-netmap wasn't the right direction, but the difference between em0+if_brdige+vmnet|virtio-net+vtnet and vale:em0|vale:guest+vtnet is noticable. I haven't done any measuring, but just performing typical admin jobs via cli (ssh into the bhyve-guest, whith resorces via NFS (v4)) behave completely different – human-noticable much more snappy in the vale:guest case! I don't think this enormous efficiency advantge is soleley caused by em0-netmap/ring connection; More important, in the vale:em0|vale:guest+vtnet case, I gain excellent inter-vm efficiency (and much higher attainable performance of course, which is not crucial at the moment; but efficiency is!). Now replacing vale:em0 by vale:vlan0 will surely destroy one big efficiency advantage, but I still benefit from excellent inter-vm efficiency and most likely some small efficiency advantage left over the if_bridge picture. Also, ptnet is a very interisting area of optimization which is easy to explore with the vale:vlan scenario. In another post I described that the vale:vlan path doesn't work, while vale:em0 (the parent) with everything else untouched does work. Dou you think it's possible to fix the vale:vlan coupling without netmap experts setting up a test environment? Thanks, -harry From owner-freebsd-net@freebsd.org Thu Jun 1 08:09:57 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A725BF005A for ; Thu, 1 Jun 2017 08:09:57 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 CA94C6AC10 for ; Thu, 1 Jun 2017 08:09:56 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5189tFg075967; Thu, 1 Jun 2017 10:09:55 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id B0FC2E2C; Thu, 1 Jun 2017 10:09:54 +0200 (CEST) Message-ID: <592FCBD1.7020301@omnilan.de> Date: Thu, 01 Jun 2017 10:09:53 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" Subject: Re: vale uplink via vlan-if [Was: Re: Are ./valte-ctl and ./bridge friends or competitors?] References: <58CBA727.3040108@omnilan.de> <58CBBF7A.8050604@omnilan.de> <58CC26CF.5050708@omnilan.de> <58CFA606.7090306@omnilan.de> <58D02259.9010101@omnilan.de> <5926F74A.1000101@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Thu, 01 Jun 2017 10:09:55 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 08:09:57 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 01.06.2017 00:43 (localtime): > If VLAN interface do not work properly with VALE/netmap that's a bug of > the emulated adapter code in FreeBSD. > But in any case the approach is not the right one, since using the > emulated netmap adapter with VALE will make you lose most of the > advantage of using netmap in the first place. > (see my previous email). Hehe, just metioned this thread in the reply to our other mail – Thanks for your attention! Like mentioned there, I see at least two reasons why choosing the sub-optimal VALE:VLAN setup is still best option for me (considering the fact that I'm not able to write me a 802.1Q-netmap-tool: inter-vm efficiency, ptnet option, and maybe still better efficiency in the guest-nic path than with if_bridge). If you have any idea where to start identifying the VALE_VLAN problem, I'll do my best to provide useful info or test any debug-code. Like mentioned elswhere, I'm with HEAD's netmap code on stable/11, so any patch should be testable here. Thanks, -harry From owner-freebsd-net@freebsd.org Thu Jun 1 08:32:55 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0556DBF1F94 for ; Thu, 1 Jun 2017 08:32:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E689F6EF18 for ; Thu, 1 Jun 2017 08:32:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v518WrET029179 for ; Thu, 1 Jun 2017 08:32:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217637] One TCP connection accepted TWO times Date: Thu, 01 Jun 2017 08:32:54 +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: CURRENT X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 08:32:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 --- Comment #83 from commit-hook@freebsd.org --- A commit references this bug: Author: tuexen Date: Thu Jun 1 08:32:35 UTC 2017 New revision: 319400 URL: https://svnweb.freebsd.org/changeset/base/319400 Log: MFC r317208: Syncoockies can be used in combination with the syncache. If the cache overflows, syncookies are used. This patch restricts the usage of syncookies in this case: accept syncookies only if there was an overflow of the syncache recently. This mitigates a problem reported in PR217637, where is syncookie was accepted without any recent drops. Thanks to glebius@ for suggesting an improvement. PR: 217637 Reviewed by: gnn, glebius Differential Revision: https://reviews.freebsd.org/D10272 Changes: _U stable/11/ stable/11/sys/netinet/tcp_syncache.c stable/11/sys/netinet/tcp_syncache.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 11:23:47 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12C22AFA745 for ; Thu, 1 Jun 2017 11:23:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 011F2760A8 for ; Thu, 1 Jun 2017 11:23:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51BNkSU024356 for ; Thu, 1 Jun 2017 11:23:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219703] System freeze when creating bridge over vlan over lagg over ixgbe Date: Thu, 01 Jun 2017 11:23:47 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: 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.23 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, 01 Jun 2017 11:23:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219703 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- 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 Thu Jun 1 11:24:35 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3CE8AFA805 for ; Thu, 1 Jun 2017 11:24:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C23EE761CA for ; Thu, 1 Jun 2017 11:24:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51BOZAw025662 for ; Thu, 1 Jun 2017 11:24:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 11:24:35 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: assigned_to component 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.23 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, 01 Jun 2017 11:24:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-standards@FreeBSD.o |freebsd-net@FreeBSD.org |rg | Component|standards |kern --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 14:17:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65C0FAFDECB for ; Thu, 1 Jun 2017 14:17:19 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5E33C7B7B6; Thu, 1 Jun 2017 14:17:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA24947; Thu, 01 Jun 2017 17:17:15 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dGQuZ-000Po0-Lw; Thu, 01 Jun 2017 17:17:15 +0300 Subject: Re: svn commit: r314948 - in head: lib/libstand sys/boot/i386/libi386 To: Baptiste Daroussin Cc: Mariusz Zaborski , Steven Hartland , "George V. Neville-Neil" , Toomas Soome , freebsd-net@FreeBSD.org References: <201703090601.v2961OJx077853@repo.freebsd.org> <20170527125616.3c5h4iag3egvq32s@ivaldir.net> From: Andriy Gapon Message-ID: <385ad469-8c20-ada7-21b5-c8fedd6e201d@FreeBSD.org> Date: Thu, 1 Jun 2017 17:16:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170527125616.3c5h4iag3egvq32s@ivaldir.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 14:17:19 -0000 On 27/05/2017 15:56, Baptiste Daroussin wrote: > On Fri, May 26, 2017 at 12:27:45PM +0300, Andriy Gapon wrote: >> On 09/03/2017 08:01, Mariusz Zaborski wrote: >>> Author: oshogbo >>> Date: Thu Mar 9 06:01:24 2017 >>> New Revision: 314948 >>> URL: https://svnweb.freebsd.org/changeset/base/314948 >>> >>> Log: >>> Try to extract the RFC1048 data from PXE. If we get enough info we can skip >>> the bootp(). It removes unnecessary DHCP request from pxeloader. >>> >>> Submitted by: kczekirda >>> Sponsored by: Oktawave >>> Initiated by: Matthew Dillon >>> Reviewed by: smh, gnn, bapt, oshogbo >>> MFC after: 3 weeks >>> Differential Revision: https://reviews.freebsd.org/D9847 >> >> Sorry for being late to the party, but this being head hopefully not too late. >> >> I am not sure that I agree with the spirit of this change. >> >> There are network boot setups that do depend on the "unnecessary" DHCP request >> from pxeboot. For example, a DHCP server could be configured to return a >> different set of parameters depending on a particular PXE client. I personally >> use a configuration where the DCHP server sends a boot menu[*] to a PXE client >> that's built into network cards. If a FreeBSD boot is selected and pxeboot is >> started, then the server sends parameters required for the FreeBSD boot >> (root-path, etc) in response to the request from pxeboot. >> I don't see how I can keep that working after this change. >> >> Additionally, as far as I can tell, we only get cached >> PXENV_PACKET_TYPE_BINL_REPLY. This might cause a problem in environments where >> a separate PXE server (Proxy DHCP) is used. In that case the reply might not >> have the network configuration information which would actually be in >> PXENV_PACKET_TYPE_DHCP_ACK. >> An example of such a setup is described here: >> https://n0dy.com/blog/2014/09/14/network-booting-with-dnsmasq-in-proxy-mode/ >> Using a separate PXE server is not uncommon in corporate environments too. >> >> In general, I think that the change was not thought through to cover scenarios >> beyond the basic unattended, FreeBSD-only, single DHCP server network boots. >> That scenario is, of course, very common, but it is not the only one. >> >> At minimum, I would like to have a compile time option to control whether >> pxeboot should send a DHCP request of its own or rely entirely on the cached >> information. Or maybe pxeboot could be smart enough to do the former if the >> cached reply is missing some required information like the root-path. >> Right now, there is no bootp(BOOTP_PXE) under any conditions. >> >> And my apologies again for missing the original discussion. >> My focus was somewhere else at the time. >> >> [*] It uses PXE_BOOT_MENU and PXE_MENU_PROMPT vendor options for that. >> >> References: >> http://www.pix.net/software/pxeboot/archive/pxespec.pdf > > I should have been all fixed in head (including some sugar added) > > Can you confirm? Yes, I can. Thank you! My setup works again. I have some further local changes for which I will open a differential review (or a few of them) soon. -- Andriy Gapon From owner-freebsd-net@freebsd.org Thu Jun 1 19:22:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0164DB7CF9C for ; Thu, 1 Jun 2017 19:22:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2D883375 for ; Thu, 1 Jun 2017 19:22:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51JMhF7057998 for ; Thu, 1 Jun 2017 19:22:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 19:22:44 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rkoberman@gmail.com 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: 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.23 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, 01 Jun 2017 19:22:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 rkoberman@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rkoberman@gmail.com --- Comment #2 from rkoberman@gmail.com --- What is in your routing table? "netstat -rnf inet6" This should be collected what IPv6 is working (pings running) and when it's not. What about ndp? "ndp -a" and "ndp -p" Less important but possibly useful, what does your interface config look li= ke? "ifconfig vtnet0" --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 19:39:15 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C43E2B7D295 for ; Thu, 1 Jun 2017 19:39:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A89913F38 for ; Thu, 1 Jun 2017 19:39:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51JdFnZ093458 for ; Thu, 1 Jun 2017 19:39:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 19:39:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: paul@tmp.group X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 19:39:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #3 from Paul G Webster --- Thank you for the reply; the information you requested is as follows $ netstat -rnf inet6 you have mail Routing tables Internet6: Destination Gateway Flags N= etif Expire ::/96 ::1 UGRS = lo0 default 2a07:4580:b0d::1 UGS vt= net0 ::1 link#2 UH = lo0 ::ffff:0.0.0.0/96 ::1 UGRS = lo0 2a07:4580:b0d::/48 link#1 U vt= net0 2a07:4580:b0d:27e::1 link#1 UHS = lo0 fe80::/10 ::1 UGRS = lo0 fe80::%vtnet0/64 link#1 U vt= net0 fe80::216:3cff:fe81:38d8%vtnet0 link#1 UHS = lo0 fe80::%lo0/64 link#2 U = lo0 fe80::1%lo0 link#2 UHS = lo0 ff02::/16 ::1 UGRS = lo0 $ ndp -a Neighbor Linklayer Address Netif Expire S F= lags 2a07:4580:b0d::1 00:05:73:a0:00:09 vtnet0 23h59m59s S R mail.tmp.group 00:16:3c:81:38:d8 vtnet0 permanent R fe80::a693:4cff:fe63:547f%vtnet0 a4:93:4c:63:54:7f vtnet0 expired P 3 fe80::216:3cff:fe81:38d8%vtnet0 00:16:3c:81:38:d8 vtnet0 permanent R $ ndp -p 2a07:4580:b0d::/48 if=3Dvtnet0 flags=3DLO vltime=3Dinfinity, pltime=3Dinfinity, expire=3DNever, ref=3D1 No advertising router fe80::%vtnet0/64 if=3Dvtnet0 flags=3DLAO vltime=3Dinfinity, pltime=3Dinfinity, expire=3DNever, ref=3D0 No advertising router fe80::%lo0/64 if=3Dlo0 flags=3DLAO vltime=3Dinfinity, pltime=3Dinfinity, expire=3DNever, ref=3D0 No advertising router $ ifconfig vtnet0 vtnet0: flags=3D8843 metric 0 mtu 1= 500 =20=20=20=20=20=20=20 options=3D6c07bb ether 00:16:3c:81:38:d8 inet 185.157.232.30 netmask 0xffff0000 broadcast 185.157.255.255 inet6 fe80::216:3cff:fe81:38d8%vtnet0 prefixlen 64 scopeid 0x1 inet6 2a07:4580:b0d:27e::1 prefixlen 48 nd6 options=3D21 media: Ethernet 10Gbase-T status: active --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 22:01:04 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 203BEB7FAF0 for ; Thu, 1 Jun 2017 22:01:04 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 D133B6E7CD for ; Thu, 1 Jun 2017 22:01:03 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3wf1WJ5ZBlz2FS for ; Fri, 2 Jun 2017 00:01:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1496354455; x=1498946456; bh=Sq1 Ia8ONMcsJXpdTKLlYVAa3h9ng+lTXuu9imKoBs5A=; b=crJRCITZVDfjYUQSkOx UDwCtcsXt04+m/phcMRzaVs7G4h7gkyHxKaO9asIFD7+K+q+fqSpoWWy3tyfNUQm UiIvU1y20Pn9mIEPauEhjXAiLDPrJPVdduhFGJUy2ZCbbCgymO+WxdlTX75TDyec CDsZA1eI6jh+mHSLuFFSsrX0= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id 9qJbdZ0iPIzW for ; Fri, 2 Jun 2017 00:00:55 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3wf1WC70hvz2FP for ; Fri, 2 Jun 2017 00:00:55 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3wf1WC67QjzP6 for ; Fri, 2 Jun 2017 00:00:55 +0200 (CEST) Received: from www-proxy.ijs.si (2001:1470:ff80::3128:1) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Fri, 02 Jun 2017 00:00:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Jun 2017 00:00:55 +0200 From: Mark Martinec To: freebsd-net@FreeBSD.org Subject: reminder: [Bug 213276] port 502 is officially mbap (Modbus Application Protocol), /etc/services claims outdated asa-appl-proto Organization: Jozef Stefan Institute In-Reply-To: References: Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 22:01:04 -0000 Any chance of getting this simple fix of /etc/services into 11.1, or at least into CURRENT ? Mark Date: 2016-10-07 16:49 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213276 Bug ID: 213276 Summary: port 502 is officially mbap (Modbus Application Protocol), /etc/services claims outdated asa-appl-proto Product: Base System Version: 11.0-STABLE Severity: Affects Only Me Priority: --- Component: standards Assignee: freebsd-standards@FreeBSD.org Reporter: Mark.Martinec@ijs.si Created attachment 175500 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175500&action=edit patch for /etc/services: ports 502 and 802 The file /etc/services states that port 502 belongs to an asa-appl-proto service, but this is not true. The port is officially (IANA) assigned to "Modbus Application Protocol" since 2014-06-10. Apparently it was previously assigned to Cisco, but no longer is. Also a related port 802 entry is missing in /etc/services. http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=modbus mbap 502 tcp Modbus Application Protocol [modbus.org] [Dennis_Dube] 2014-06-10 mbap 502 udp Modbus Application Protocol [modbus.org] [Dennis_Dube] 2014-06-10 mbap-s 802 tcp Modbus Application Protocol Secure [modbus.org] [Dennis_Dube] mbap-s 802 udp Modbus Application Protocol Secure [modbus.org] [Dennis_Dube] See also: http://seclists.org/nmap-dev/2015/q3/373 From owner-freebsd-net@freebsd.org Thu Jun 1 22:44:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12A53B82445 for ; Thu, 1 Jun 2017 22:44:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E845B6FA2B for ; Thu, 1 Jun 2017 22:44:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51Mi8gT059214 for ; Thu, 1 Jun 2017 22:44:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 22:44:08 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rkoberman@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 22:44:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #4 from rkoberman@gmail.com --- (In reply to Paul G Webster from comment #3) At the time that you collected this, everything looks good. The default rou= te is pointing to the correct link. (link#1) and all ndp data looks correct. One suggestion is to accept router advertisements. To do this, add "accept_rtadv" to you ifconfig_vtnet0_ipv6 line in rc.conf. This will cause your system to accept router advertisements on your LAN. Unless you have another local system configured to do IPv6 routing, this should be fine. I = also doubt it will help, but it might be worth a try. (If it does not help, I'd remove it.) You might want to monitor the default route and the NDP for 2a07:4580:b0d:27e::1 to see if they are stable. It sure sounds like somethi= ng is flapping when the link is inactive for some period. My guess is NDP, but that is far from certain. N.B. I was very active in working with IPv6 for over 15 years, but I've been retired for six years and I'll admit that I am not as sharp on it as I once was. Worse, Frontier, my ISP about half the year does not yet support IPv6 customer connections. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 22:49:11 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1216AB82542 for ; Thu, 1 Jun 2017 22:49: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 mx1.freebsd.org (Postfix) with ESMTPS id D9E036FC0B for ; Thu, 1 Jun 2017 22:49:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51MnApO066615 for ; Thu, 1 Jun 2017 22:49:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 22:49:10 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: paul@tmp.group X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 22:49:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #5 from Paul G Webster --- root@mail:~ # ping6 google.com PING6(56=3D40+8+8 bytes) 2a07:4580:b0d:27e::1 --> 2a00:1450:4009:80f::200e 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D0 hlim=3D55 time=3D7.064= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D1 hlim=3D55 time=3D6.720= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D2 hlim=3D55 time=3D6.686= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D3 hlim=3D55 time=3D6.556= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D4 hlim=3D55 time=3D6.605= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D5 hlim=3D55 time=3D6.741= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D6 hlim=3D55 time=3D6.802= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D7 hlim=3D55 time=3D6.934= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D8 hlim=3D55 time=3D6.600= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D9 hlim=3D55 time=3D6.805= ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D10 hlim=3D55 time=3D6.67= 0 ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D11 hlim=3D55 time=3D6.66= 8 ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D12 hlim=3D55 time=3D7.08= 0 ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D25 hlim=3D55 time=3D6.86= 4 ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D26 hlim=3D55 time=3D6.72= 5 ms 16 bytes from 2a00:1450:4009:80f::200e, icmp_seq=3D27 hlim=3D55 time=3D6.66= 6 ms ^C --- google.com ping6 statistics --- 28 packets transmitted, 16 packets received, 42.9% packet loss round-trip min/avg/max/std-dev =3D 6.556/6.762/7.080/0.151 ms root@mail:~ # # Known working ifconfig_vtnet0_ipv6=3D"inet6 2a07:4580:b0d:27e::1/48 accept_rtadv" ipv6_defaultrouter=3D"2a07:4580:b0d::1" No love still the same fault after I comment out: root@mail:~ # cat /etc/rc.local daemon -f ping6 -i 2 -s 1 2a07:4580:b0d::1 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jun 1 22:49:37 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DF92B825D7 for ; Thu, 1 Jun 2017 22:49:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C3216FCB5 for ; Thu, 1 Jun 2017 22:49:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51Mnbir067357 for ; Thu, 1 Jun 2017 22:49:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Thu, 01 Jun 2017 22:49:37 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: paul@tmp.group X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 22:49:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #6 from Paul G Webster --- As an aside, I am on virgin media in the uk, they do not even have an upgra= de path for ipv6 yet :P so I feel your pain --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 00:16:12 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86B56B95565 for ; Fri, 2 Jun 2017 00:16:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 740F973A51 for ; Fri, 2 Jun 2017 00:16:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v520GBZU097922 for ; Fri, 2 Jun 2017 00:16:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217637] One TCP connection accepted TWO times Date: Fri, 02 Jun 2017 00:16:12 +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: CURRENT X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11+ X-Bugzilla-Changed-Fields: flagtypes.name 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.23 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, 02 Jun 2017 00:16:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |mfc-stable11+ --- Comment #84 from Kubilay Kocak --- Track merge to stable/11 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 00:18:28 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36A5FB95704 for ; Fri, 2 Jun 2017 00:18:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 23F6C73C35 for ; Fri, 2 Jun 2017 00:18:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v520IRBU040834 for ; Fri, 2 Jun 2017 00:18:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217637] One TCP connection accepted TWO times Date: Fri, 02 Jun 2017 00:18:28 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tuexen@freebsd.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11+ X-Bugzilla-Changed-Fields: cc flagtypes.name version 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.23 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, 02 Jun 2017 00:18:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-net@FreeBSD.org Flags| |mfc-stable10? Version|CURRENT |10.3-RELEASE Assignee|freebsd-net@FreeBSD.org |tuexen@freebsd.org --- Comment #85 from Kubilay Kocak --- Since the original report was on 10.3-RELEASE (comment 4) and 10.4 will be released, request/ask about merge to stable/10. While I'm here, assign to committer resolving. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 00:18:59 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BEBEB95790 for ; Fri, 2 Jun 2017 00:18: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 mx1.freebsd.org (Postfix) with ESMTPS id 3A97373D8A for ; Fri, 2 Jun 2017 00:18:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v520IwAH041649 for ; Fri, 2 Jun 2017 00:18:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217637] One TCP connection accepted TWO times Date: Fri, 02 Jun 2017 00:18:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tuexen@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.23 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, 02 Jun 2017 00:18:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 --- Comment #86 from Kubilay Kocak --- Previous comment was supposed to read " comment 7 " --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 00:45:48 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C134BD3179 for ; Fri, 2 Jun 2017 00:45:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A1F874D41 for ; Fri, 2 Jun 2017 00:45:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v520jm1c010842 for ; Fri, 2 Jun 2017 00:45:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 205706] Watchdog timeout on em driver under heavy traffic on a bridge configuration Date: Fri, 02 Jun 2017 00:45:48 +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: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: joshruehlig@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 00:45:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205706 --- Comment #5 from joshruehlig@gmail.com --- (In reply to Eugene Grosbein from comment #4) This finally happened to me again, shortly after a reboot for other reasons. Forcing link re-negotiation on the affected interface did not work. In this instance only 1 of my cameras (10.0.1.11) was unreachable, while the others worked as expected. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 00:46:40 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63836BD31ED for ; Fri, 2 Jun 2017 00:46:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 513E774E0F for ; Fri, 2 Jun 2017 00:46:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v520kek4012036 for ; Fri, 2 Jun 2017 00:46:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 205706] Watchdog timeout on em driver under heavy traffic on a bridge configuration Date: Fri, 02 Jun 2017 00:46:40 +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: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: joshruehlig@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 00:46:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205706 --- Comment #6 from joshruehlig@gmail.com --- (In reply to joshruehlig from comment #5) I'm thinking there was actually a problem with the camera in this case. Bec= ause rebooting the camera (and no the FreeBSD server) fixed it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jun 2 01:55:20 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00F4BBED782 for ; Fri, 2 Jun 2017 01:55:20 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [67.205.158.196]) by mx1.freebsd.org (Postfix) with ESMTP id CF8C576BC1 for ; Fri, 2 Jun 2017 01:55:19 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-61-187.pn.at.cox.net [68.1.61.187]) by colo1.denninger.net (Postfix) with ESMTP id 7638B27349 for ; Thu, 1 Jun 2017 21:49:40 -0400 (EDT) Received: from [192.168.10.20] (D10.Denninger.Net [192.168.10.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id 298073A539B for ; Thu, 1 Jun 2017 20:49:39 -0500 (CDT) To: freebsd-net@freebsd.org From: Karl Denninger Subject: Ipv6 / DNS questions Message-ID: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> Date: Thu, 1 Jun 2017 20:49:29 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms080207030709010103050109" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 01:55:20 -0000 This is a cryptographically signed message in MIME format. --------------ms080207030709010103050109 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Perusing through the various documentation I've not yet found an answer to this, and figure someone might know where to point me before I start banging code beyond a shell script or three. Assuming we have a "dual stack" system on the Internet; the provider is willing to allocate us anywhere from a /56 to a /64 off stateless Ipv6 which our gateway (running FreeBSD), and that is working using dhcp6c.=20 Said gateway then (typically) gets said /56 and allocates a /64 on the internal interface, and runs rtadvd. The clients run rtsold and are getting addresses just fine. Windows clients, Android phones and similar are also having no problems. Now posit a host "inside" the gateway that I wish to have an exposed service on the Internet. In the IPv4 world I run NAT, the DMZ'd host is on a private address, and I port-twist at the gateway (e.g. a connection to TCP port 5050 on the gateway goes to x.x.x.x:5050 on the internal host.) The external client is none the wiser; he only sees the single outside IP. For IPv6 of course the internal address is routable, but this leads to a problem -- how does the outside guy know where it is? Is there a dynamic DNS update method associated with Ipv6's address assignment system? Since the assignment is "stateless" it obviously (and does, in my experience!) move. I can deal with it via a couple of shell scripts, and there are only a couple of hosts where it matters, but this would dramatically simplify the IPv4 gameplaying that's necessary to have something behind a gateway router while on a "globally visible", but possibly changing "at whim", IpV6 address. I assume someone has gone after this issue by now so if there's "prior art" a pointer would be appreciated. Thanks in advance! --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms080207030709010103050109 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzA2MDIwMTQ5MjlaME8GCSqGSIb3DQEJBDFCBEB91M55 UBZer7XlL3sT8nF1iClbYC1wgtXrQ5kEIUNk3m/lAL3DEt+3igdGQlR6CFGIx0gewzubq/Rs n57Ki4ZrMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIARyO8hA7TPoM3 G5CHrfoZZTxCETGuzOWwlDbUjF+EWnWVtARTzVDqr0iMSbymX9aWBTpDnxScsu2sz2z0scK6 xUpGsTcGED+/1zdc682xBGQfpizmQe9jcpPsi10iMJjl6uJg5nYnVs/JATAs8IAUDWppBov0 wuGL4s6HGOhAwPfeggD8KoaVT/prNdfXqSUECNC8O9mFA3oGzRTCwhSKgqUofE+dPU1HSMgp zg1q6O/ZI/amfFQUB4+OFtEc+ScOClmOqFsG3fNlW1kz9wuJ3j1dEuIwewhv5RNVnvIMGS/M G8EKqRC5l3hq91Q9ieYdnHIRlRZy9owUaPgShS37x4l+yIyfVyXkhtuptVlwYdbZJHNRGC3t /3UlwjGfKO4oVGu3Qo4/p+7MASecCVLEF7irzJA1mecAHMelhwd2kBpEc2+Cdsh5xGAXCp54 gYAE5DdqZWd7/pMO0GOw7hINvX99+vUfbQQVAAsg03PzTzBSIlz6vTv8RjbyOwG47894Id5A zLXGceTiUUAq8wpGwTLYpJoZu93hMt0kQTGlyCSwkEIFtsUBSySXBKoV7dnLoLFvmNAYNy2B C5ENZN2IluW8CdUPLOWRwKtPXvmGAIa8Xs4O3dSk6L8EU9pFeLARK7nE/AY/zyEcyTvYBS9h bvQs8loo4FZJQCQIsLEENVcAAAAAAAA= --------------ms080207030709010103050109-- From owner-freebsd-net@freebsd.org Fri Jun 2 08:00:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CBAEBF2371 for ; Fri, 2 Jun 2017 08:00:09 +0000 (UTC) (envelope-from alarig@swordarmor.fr) Received: from togepi.gozmail.bzh (togepi.gozmail.bzh [IPv6:2a00:5884:124::1]) (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 4409B7ED25 for ; Fri, 2 Jun 2017 08:00:08 +0000 (UTC) (envelope-from alarig@swordarmor.fr) Received: from mew.swordarmor.fr (mew.swordarmor.fr [IPv6:2a00:5884:102:1::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alarig@swordarmor.fr) by togepi.gozmail.bzh (Postfix) with ESMTPSA id 755291A0080 for ; Fri, 2 Jun 2017 10:00:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=swordarmor.fr; s=default; t=1496390404; bh=abAJdr7Ovek/YrXOFlf+n+FSgNmYGeFyGyNpkoeNjuc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=W+ZHW6FqMm0pS+c3jw4xqDBQsyO2Ji3nGGhcwBA1tBTulzS1svFSJVXWQxcqTlCbw aPlScOEMlOca2fESu3nNWemIjlrN5HWU+uz+KI4e40SWHAsY6lM3KLhT77OvKr9E2y jRrCjdN7q5DKJgpV62PwXpP1SyXkykHn7IR7zh90= Date: Fri, 2 Jun 2017 10:00:03 +0200 From: Alarig Le Lay To: freebsd-net@freebsd.org Subject: Re: Ipv6 / DNS questions Message-ID: <20170602080003.ahnqx34cfdgbkrnw@mew.swordarmor.fr> References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s2akfrzuptyo3gbs" Content-Disposition: inline In-Reply-To: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> User-Agent: NeoMutt/20170428 (1.8.2) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 08:00:09 -0000 --s2akfrzuptyo3gbs Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On jeu. 1 juin 20:49:29 2017, Karl Denninger wrote: > Is there a dynamic DNS update method associated with Ipv6's address > assignment system? Since the assignment is "stateless" it obviously > (and does, in my experience!) move. I can deal with it via a couple of > shell scripts, and there are only a couple of hosts where it matters, > but this would dramatically simplify the IPv4 gameplaying that's > necessary to have something behind a gateway router while on a "globally > visible", but possibly changing "at whim", IpV6 address. Hi, Why don=E2=80=99t you just simply assign a static IPv6? ifconfig_vtnet0=3D"inet 89.234.186.212/28" defaultrouter=3D"89.234.186.209" ifconfig_vtnet0_ipv6=3D"inet6 2a00:5884:102:1::4/64" ipv6_defaultrouter=3D"fe80::209%vtnet0" And then, you can publish those A/AAAA records in DNS. --=20 alarig --s2akfrzuptyo3gbs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+2yGwT0H0n57WkRbrzhKwWsgK4gFAlkxGwAACgkQrzhKwWsg K4hPZgf+Op47je42tQyYu9CcAgNT9D6tEuqhO4/jXM5MniApT4I7+C+KWKWVQvEX hitf/ZryzT9EsYJMJGg9ta0gpPdWoRCAG3VmcnfFb+Gd5G7kX92rL1RcAaYZFoJn HpGgYCgL3sY+gsAtBJkGyoyMNhIg1w3VpakP4C8oXtPvTbYsINeyQQwwMfm0w4TB Ds+7VEUrdn5GZDOelYmHSmNoHm+ZjE6svmD3MX2IYZ+Wf39CkweakPXvRAplH/F5 uC3XOxjpwlOscGVV4mDDFeuBZyAyhkMm9HbQIcHBVOa+SVbaZzRmjersjRKlUjyq GCmjw8tBslIAAPX7yKEAHCD2nCRBxw== =uil8 -----END PGP SIGNATURE----- --s2akfrzuptyo3gbs-- From owner-freebsd-net@freebsd.org Fri Jun 2 08:56:47 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AE1BBF2ED2 for ; Fri, 2 Jun 2017 08:56:47 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E3F6B80300 for ; Fri, 2 Jun 2017 08:56:46 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 1057537F3 for ; Fri, 2 Jun 2017 08:56:44 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/1057537F3; dkim=none; dkim-atps=neutral Subject: Re: Ipv6 / DNS questions To: freebsd-net@freebsd.org References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> From: Matthew Seaman Message-ID: <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> Date: Fri, 2 Jun 2017 09:56:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BsQ36w94oJ5Rk4M9h2fA0ahX020KUwVAV" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 08:56:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BsQ36w94oJ5Rk4M9h2fA0ahX020KUwVAV Content-Type: multipart/mixed; boundary="6JqjUNsLXjU8bKUtuiee5FOqbQ4E3acI0"; protected-headers="v1" From: Matthew Seaman To: freebsd-net@freebsd.org Message-ID: <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> Subject: Re: Ipv6 / DNS questions References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> In-Reply-To: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> --6JqjUNsLXjU8bKUtuiee5FOqbQ4E3acI0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 06/02/17 02:49, Karl Denninger wrote: > Is there a dynamic DNS update method associated with Ipv6's address > assignment system? Since the assignment is "stateless" it obviously > (and does, in my experience!) move. I can deal with it via a couple of= > shell scripts, and there are only a couple of hosts where it matters, > but this would dramatically simplify the IPv4 gameplaying that's > necessary to have something behind a gateway router while on a "globall= y > visible", but possibly changing "at whim", IpV6 address. Assuming that you always get the same /64 assigned to your gateway, then the address SLAAC assigns to your server will be constant so long as you're on the same hardware, since the SLAAC address is generated from the network prefix and the MAC address of the NIC. In that case, it often suffices to update the DNS manually. If that doesn't work for you, then while there isn't a DNS update mechanism built into SLAAC, there is one in DHCP6. That relies on the dhcp server being able to make dynamic DNS updates via nsupdate(1). Of course, if you have all the keys etc. set up to be able to use nsupdate(1) you could fairly easily add a 'dns-update' rc script on your host to push the hosts' IPv6 address into the DNS. The other fairly common approach would be to use a network configuration system like ansible or puppet that can gather facts about a machine (such as the IPv6 address) write them into a DNS zone file. Cheers, Matthew --6JqjUNsLXjU8bKUtuiee5FOqbQ4E3acI0-- --BsQ36w94oJ5Rk4M9h2fA0ahX020KUwVAV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlkxKDwACgkQAFE/EOCp 5OfzMxAAmpU60yn3tJbwPCZURvAcf9G1DSFv82kpmfcRL11giFmlVXoeo8CrjPFY 6Mj3gt7f6iLsgK/egJUotxQjDMySbmmoPXN8uREgQAoXKLOY0eqCSmyiKiWBJBa2 i3yBG0vkCkmpTRlwdvvqqhIlnyD0kP32DC2Gn2G+XN14RcKeJD9Fl9A26yP6KOm5 78zFI1t10MZS+kPNh2AieCY4zytu0wLThC59Hi1r2KUdVPNB10CsY79g0BtBL7fY 5HlDfiSbtO+OT6hWVzSukFRawjoILWIeHyT6WjS4JK2bZ/g2ju6AvI8KlmDg3dS1 ERgU/dHJqPsU8iv+DzI3kfpvqShGSEj1PY8ppP7eFPujFsx00J5KOt3TR15Rn6lc VQjhpc9W9bfmaNqbMPvt6Qj6io1QsvSyx/+NmfVcpgwlPFdpaaZXQsujktfi0hs5 bjsHGoie+h6AlCeLWG1dg8fdnQGiAbv9t2omEpeNp946/qCbe/LOeVe+hmKs82uc D3Y2xBPhJLP8+fhls9rArDlIy3RCIajlSDsLf/yjdh+4rvoIRGY1fwTxVmcbqmga ARwBXItHt7qEXqnfWHfm1CGA3J3RN9OYyE8WxsDrZtKtO406BhdRjAf3S0PDtZtZ FwDyFWYE4/SwSyc8zqT3DgAkBf7KPhSubcuPfQdRxMF5cLpuB9Q= =WZH8 -----END PGP SIGNATURE----- --BsQ36w94oJ5Rk4M9h2fA0ahX020KUwVAV-- From owner-freebsd-net@freebsd.org Fri Jun 2 11:30:12 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 680E6BF5CDC for ; Fri, 2 Jun 2017 11:30:12 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.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 359CA848F3; Fri, 2 Jun 2017 11:30:12 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dGkmQ-0008p3-EH; Fri, 02 Jun 2017 12:30:10 +0100 Date: Fri, 2 Jun 2017 12:30:10 +0100 From: Gary Palmer To: Matthew Seaman Cc: freebsd-net@freebsd.org Subject: Re: Ipv6 / DNS questions Message-ID: <20170602113010.GA74033@in-addr.com> References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 11:30:12 -0000 On Fri, Jun 02, 2017 at 09:56:28AM +0100, Matthew Seaman wrote: > On 06/02/17 02:49, Karl Denninger wrote: > > Is there a dynamic DNS update method associated with Ipv6's address > > assignment system? Since the assignment is "stateless" it obviously > > (and does, in my experience!) move. I can deal with it via a couple of > > shell scripts, and there are only a couple of hosts where it matters, > > but this would dramatically simplify the IPv4 gameplaying that's > > necessary to have something behind a gateway router while on a "globally > > visible", but possibly changing "at whim", IpV6 address. > > Assuming that you always get the same /64 assigned to your gateway, then > the address SLAAC assigns to your server will be constant so long as > you're on the same hardware, since the SLAAC address is generated from > the network prefix and the MAC address of the NIC. In that case, it > often suffices to update the DNS manually. Only if ipv6_privacy="YES" is not set. Regards, Gary > > If that doesn't work for you, then while there isn't a DNS update > mechanism built into SLAAC, there is one in DHCP6. That relies on the > dhcp server being able to make dynamic DNS updates via nsupdate(1). Of > course, if you have all the keys etc. set up to be able to use > nsupdate(1) you could fairly easily add a 'dns-update' rc script on your > host to push the hosts' IPv6 address into the DNS. > > The other fairly common approach would be to use a network configuration > system like ansible or puppet that can gather facts about a machine > (such as the IPv6 address) write them into a DNS zone file. > > Cheers, > > Matthew > From owner-freebsd-net@freebsd.org Fri Jun 2 11:38:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C234BF5F84 for ; Fri, 2 Jun 2017 11:38:14 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 857D884DD5; Fri, 2 Jun 2017 11:38:13 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from host-4-75.office.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 6F0463823; Fri, 2 Jun 2017 11:38:11 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/6F0463823; dkim=none; dkim-atps=neutral Subject: Re: Ipv6 / DNS questions To: Gary Palmer References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> <20170602113010.GA74033@in-addr.com> Cc: freebsd-net@freebsd.org From: Matthew Seaman Message-ID: Date: Fri, 2 Jun 2017 12:38:04 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170602113010.GA74033@in-addr.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cuxcoPCk6PCALLeMI2BmJgh3kaKup03aJ" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 11:38:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cuxcoPCk6PCALLeMI2BmJgh3kaKup03aJ Content-Type: multipart/mixed; boundary="JggAtEjsus8JWJJf5nwXIH8fmDxEaobOi"; protected-headers="v1" From: Matthew Seaman To: Gary Palmer Cc: freebsd-net@freebsd.org Message-ID: Subject: Re: Ipv6 / DNS questions References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> <20170602113010.GA74033@in-addr.com> In-Reply-To: <20170602113010.GA74033@in-addr.com> --JggAtEjsus8JWJJf5nwXIH8fmDxEaobOi Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/02 12:30, Gary Palmer wrote: >> Assuming that you always get the same /64 assigned to your gateway, th= en >> the address SLAAC assigns to your server will be constant so long as >> you're on the same hardware, since the SLAAC address is generated from= >> the network prefix and the MAC address of the NIC. In that case, it >> often suffices to update the DNS manually. > Only if >=20 > ipv6_privacy=3D"YES" >=20 > is not set. Ah, but ipv6_privacy is intended for use on personal laptops and other devices where you'ld prefer not to have your MAC address available as a tracking cookie when acting as a web client. It's not intended for use on a web server. Even if you do turn it on IIRC the effect is to add alias IPs on that network interface, alongside the standard address that SLAAC would generate anyhow. Cheers, Matthew --JggAtEjsus8JWJJf5nwXIH8fmDxEaobOi-- --cuxcoPCk6PCALLeMI2BmJgh3kaKup03aJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZMU4iXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnIBEP/3kxRmcVIdJu49YO49zXEcR5 KOnJT+8AV3XeAzEyUx+KaAd9PVNiQWaT1XOJZuD3Y/jU8Tsp/HZllfnScYEB4ko6 QlLiOYT23aO1oq00G0VEQA7lTsftbLdBzFgXin056VS56yMAwUiY4R35v/zo9t0S bnjhmiP8P8trJgrsYOlSp7vgld+N6XL6zscj/MKI+4SYqNcb2Q1Y2tA/5IJrWYle VI8VR3VK+Zt36yabWYnYz48dlH9hozCs3zIeLS0hw/KRyMXxoz5u9GCXOzlCxEBu OlyGho27AuEBYa0zJKqGrgpPP6oFSSAVKjk35wb/AVpNiuk2bkQ9UITvvHXecoZW bEZxDsoQUbaMQ4S3XzH1lwf2phheen7UOPKJh3gd69RsPK8fYSNiEB1ulnLh4KIK YBc8hIP5YawW3OBPiCmFidjuhKXHFltceWKLPjg7pkRh/zRipCoII5G/GFbWCe2i C2a3rECkOjS3ennL3HYlWgSTKY1W5i2roKnoXLojoILTZGOLSOAvb9wRNnbSW1GJ kJcFX41ARF3qSsU5wkBSAFFd0GRsPZJGwRg2R6PbDeEMsm/p0ufDa08ii2wIq68N bjSEtpQ+o0BwP9Mz0jYLHndvNx5D+OwCa23Q2jYhZeyYLH3mgHptTV0S8V8559qA 0+o11xv+ZIKN5u6jo9Ir =Nq19 -----END PGP SIGNATURE----- --cuxcoPCk6PCALLeMI2BmJgh3kaKup03aJ-- From owner-freebsd-net@freebsd.org Fri Jun 2 12:38:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88F8CBF720C for ; Fri, 2 Jun 2017 12:38:19 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 3E734C2B; Fri, 2 Jun 2017 12:38:19 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3wfNzX2NQBzSX; Fri, 2 Jun 2017 14:38:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1496407091; x=1498999092; bh=TNQ /gA8L9LPETHyumHznd2geiyGMqe4VmgGjutAlTC4=; b=Wg0VahLWeb8+h37SQMa ySID2+qfwLBx2Bw5fct3RHTnJc5Ul4eKRZXJv1Qo0C7moa+qeGw+/0aQnVuYm+Ot XipqfqxssrqozeldiuTWA5daWy7Rona215Ltcpg7SECIYQd4DsUi4BdgA+TuT/g9 +G6X59Ew307wSGAHGEx66GXc= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id XVTXAOYS0if8; Fri, 2 Jun 2017 14:38:11 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3wfNzR66Z0zSS; Fri, 2 Jun 2017 14:38:11 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3wfNzR5sVdz10l; Fri, 2 Jun 2017 14:38:11 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Fri, 02 Jun 2017 14:38:11 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Jun 2017 14:38:11 +0200 From: Mark Martinec To: freebsd-net@freebsd.org Cc: Gary Palmer , Matthew Seaman Subject: Re: Ipv6 / DNS questions Organization: Jozef Stefan Institute In-Reply-To: References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> <7b0eda86-34d3-9bf7-df5f-45060a956942@freebsd.org> <20170602113010.GA74033@in-addr.com> Message-ID: <1c7e8836f1df2f95a8a7ce8a903ddfa5@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 12:38:19 -0000 I wish FreeBSD would adopt the dhcpcd daemon from the NetBSD project (2-clause BSD license) as a standard DHCP client for IPv4 and IPv6, as some other OSes have done by now. It is currently available in FreeBSD ports as net/dhcpcd. Among other features it supports RFC 7217, i.e. stable privacy address, which should be as easy to configure in FreeBSD as is now the (mostly undesirable) ipv6_privacy="YES", but is currently much too complicated for an average user. Mark 2017-06-02 13:38, Matthew Seaman wrote: > On 2017/06/02 12:30, Gary Palmer wrote: >>> Assuming that you always get the same /64 assigned to your gateway, >>> then >>> the address SLAAC assigns to your server will be constant so long as >>> you're on the same hardware, since the SLAAC address is generated >>> from >>> the network prefix and the MAC address of the NIC. In that case, it >>> often suffices to update the DNS manually. > >> Only if >> ipv6_privacy="YES" >> is not set. > > Ah, but ipv6_privacy is intended for use on personal laptops and other > devices where you'ld prefer not to have your MAC address available as a > tracking cookie when acting as a web client. > > It's not intended for use on a web server. Even if you do turn it on > IIRC the effect is to add alias IPs on that network interface, > alongside > the standard address that SLAAC would generate anyhow. > Cheers, > Matthew From owner-freebsd-net@freebsd.org Sat Jun 3 02:05:08 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00EB0B79DB9 for ; Sat, 3 Jun 2017 02:05:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E353E7E862 for ; Sat, 3 Jun 2017 02:05:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v53257jm038269 for ; Sat, 3 Jun 2017 02:05:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219428] em network driver broken in current Date: Sat, 03 Jun 2017 02:05:07 +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: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gitdev@kippona.net 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: 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.23 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, 03 Jun 2017 02:05:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219428 gitdev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gitdev@kippona.net --- Comment #4 from gitdev --- I confirm the problem with em on freebsd 12-CURRENT r319167. The board is = an Atom D525 with an ICH8M system chip. pciconf shows em5@pci0:7:0:0: class=3D0x020000 card=3D0x00008086 chip=3D0x150c8086 rev=3D= 0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82583V Gigabit Network Connection' class =3D network subclass =3D ethernet --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jun 3 07:25:53 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7C0AB95528 for ; Sat, 3 Jun 2017 07:25:53 +0000 (UTC) (envelope-from woodsb02@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 550A02E90 for ; Sat, 3 Jun 2017 07:25:53 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id 7so39730487wmo.1 for ; Sat, 03 Jun 2017 00:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=cQ1oHG5HgUxcGA7CXG1aelxvZQTqLKFToPkhIXJDc+w=; b=u9vim2hEYZcgwt9yH0UweyAdtHP5FC7486S51kQSo0KxfDfcaf6Zs9+NlAWjk6bu16 1t16Ud6Q9LDB8QuvlslY3YGOcLdbFkVk99nxABSJOvHnYvinurbOHaSW8Y/v7xl4+U40 q/49Xt8Dmazcy7wmTLsJjxiTKdAqoUVopbNCt4CP4SFvSaB85cNaqSfMXYrjpV7Nck0/ ON9rWOYKMqd0kNW/AGQqFKBZo/mYnthnmukTswW4OT3COV+rcJnTq1tBAK0sSPf1PkYt zCZKX5c8Gs6ZU4NCrRP2s2aRSlAMxdRnpd9SA9jLLEVSWYRGx7r6jJ1KGHsR9Ix25tKU sNdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cQ1oHG5HgUxcGA7CXG1aelxvZQTqLKFToPkhIXJDc+w=; b=Uo+Ksbzo8gAyRt8/0T207e7Zfmik1tHoofdZgnMfe3n6QDug/7r1+Idg8RMzIgRsjj 0YyoBc0Y/Ndn8LgFgVhZe5Qx/UGd/u8goig1Nwul+DTA8G3TxBbXqzDsqUH2+aw+d+jE PluG7wYYuXMJRTqNO1DK9IDIvB9y0WF4UaNuRUaehOAm+8dPz2XtzrwzKVd38LPqxRbH JcVYJoiiPyJeRa+kwnJvYRsjpCrVXYEisY+ZLj6gt5NpQHmjZj51iCSxRgMss5+9T+rE fhn6HqjDoJWtFVu8RpAW70Zki8tj8q3TCmnGDqSv6xeRExgO9w3QmvQA7Iyz/LcQkOK8 BcQA== X-Gm-Message-State: AODbwcD22Z1mMWkleks3GwjvqZcH06IvzkuoSzqz2npw1o05gZmY3SbV F0kY+Fee1vxnULbLP0YBQ9XYrelFbYPlIXU= X-Received: by 10.80.134.170 with SMTP id r39mr1782170eda.77.1496474751843; Sat, 03 Jun 2017 00:25:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.151.34 with HTTP; Sat, 3 Jun 2017 00:25:51 -0700 (PDT) From: Ben Woods Date: Sat, 3 Jun 2017 15:25:51 +0800 Message-ID: Subject: igb stats double counting in 12-CURRENT r319025 To: freebsd-net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 07:25:53 -0000 Hi everyone, I have noticed my networking statistics appear to be double counting on two of my FreeBSD 12-CURRENT boxes running r319025. Could someone please help me to find the problem (I believe it is likely to be a bug in the networking driver). I discovered the double counting by comparing the output of "systat -ifstat" (which reports 988 KB/s) with the output of "iftop -B" (which reports 491 KB/s). I know that iftop is the correct one, because my internet speed only gives me around ~500 KB/s unfortunately. # systat -ifstat -match igb0 ... Interface Traffic Peak Total igb0 in 988.008 KB/s 988.008 KB/s 36.295 GB out 16.953 KB/s 16.953 KB/s 295.774 GB # iftop -i igb0 -B ... TX: cum: 31.7KB peak: 9.69KB rates: 9.69KB 7.92KB 7.92KB RX: 1.54MB 491KB 491KB 394KB 394KB The two interfaces in these boxes are: $ pciconf -lvv | grep igb1 -A4 igb1@pci0:4:0:0: class=0x020000 card=0x00008086 chip=0x15398086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet $ pciconf -lvv | grep igb0 -A4 igb0@pci0:8:0:0: class=0x020000 card=0x15331849 chip=0x15338086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I210 Gigabit Network Connection' class = network subclass = ethernet Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-net@freebsd.org Sat Jun 3 18:39:57 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83CABBF7065 for ; Sat, 3 Jun 2017 18:39:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7265D7A0D0 for ; Sat, 3 Jun 2017 18:39:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v53Idv1X056325 for ; Sat, 3 Jun 2017 18:39:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Sat, 03 Jun 2017 18:39:57 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: paul@tmp.group X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 18:39:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #7 from Paul G Webster --- A little more on this fault; with the help of the host we have a working solution, from the host them self: --quote FreeBSD appears to use the link local address on the interface to send neig= hbor advertisements for the addresses it would like to be routed towards it, unfortunately our side only allows you to send neighbor advertisements from= an allowed allocated prefix not an fe80:: address. I have added an exception for this, could you try stopping your work around= for now and seeing if IPv6 carries on working? --/quote To cut a story short and many tickets later yes in fact the work around did work, the host is using 'ebtables' on there host; they have contacted the p= anel provider hoping they can patch the upstream. Will update if I can get a little more detail on what the patch was or a co= py of it hopefully :) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jun 3 19:16:55 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DC1CBF7A52 for ; Sat, 3 Jun 2017 19:16:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3C1367B3E1 for ; Sat, 3 Jun 2017 19:16:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v53JGsph074244 for ; Sat, 3 Jun 2017 19:16:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Date: Sat, 03 Jun 2017 19:16:55 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: paul@tmp.group X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 19:16:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #8 from Paul G Webster --- The host provided the following information for what they had to do with ebtables to get freebsd working;=20 --quote We use ebtables on the hosts to prevent IP stealing. We have a chain setup for each VM which basically says "this VMs mac can on= ly use these IPs", this is what was dropping your v6 NA's. The patch to allow the link local address is simply: ebtables -A kvm922.0 -p IPv6 --ip6-src fe80::/10 -j ACCEPT With kvm922.0 being the chain that your VM belongs to. --/quote --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jun 3 20:02:55 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9644EBF84AB for ; Sat, 3 Jun 2017 20:02:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84CA77C911 for ; Sat, 3 Jun 2017 20:02:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v53K2sd2029083 for ; Sat, 3 Jun 2017 20:02:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219428] em network driver broken in current Date: Sat, 03 Jun 2017 20:02:54 +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: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gitdev@kippona.net 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: attachments.created 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.23 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, 03 Jun 2017 20:02:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219428 --- Comment #5 from gitdev --- Created attachment 183184 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183184&action= =3Dedit dmesg from affected system Boot output from affected system, amd64 with atom D525 booting 12-CURRENT r319167. There should be em0-em5 ethernet devices recognized, and em3-em5 configured as a bridge. --=20 You are receiving this mail because: You are the assignee for the bug.=