From owner-freebsd-net@freebsd.org Sun Mar 26 08:57:52 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 A3023D1EB34 for ; Sun, 26 Mar 2017 08:57:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92E5C11CC for ; Sun, 26 Mar 2017 08:57:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2Q8vqbB085123 for ; Sun, 26 Mar 2017 08:57:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217721] axge(4) hangs while link goes offline Date: Sun, 26 Mar 2017 08:57:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lozovoy.ep+bugsfreebsd@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: Sun, 26 Mar 2017 08:57:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217721 --- Comment #6 from Eugene Lozovoy --- (In reply to Pyun YongHyeon from comment #5) Same issue with if_axge.c@304336 and if_axgereg.h@304458 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Mar 26 16:26: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 381CCD1E234 for ; Sun, 26 Mar 2017 16:26:13 +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 272731443 for ; Sun, 26 Mar 2017 16:26:13 +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 v2QGQCrX065044 for ; Sun, 26 Mar 2017 16:26:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218113] igb(4) panic on guest passthrough of i340 Date: Sun, 26 Mar 2017 16:26: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: 11.0-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sbruno@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, 26 Mar 2017 16:26:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218113 Sean Bruno changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |sbruno@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Mar 26 21:00:25 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 937FED1FB86 for ; Sun, 26 Mar 2017 21:00:25 +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 8298C1E10 for ; Sun, 26 Mar 2017 21:00:25 +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 v2QL012W069669 for ; Sun, 26 Mar 2017 21:00:25 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201703262100.v2QL012W069669@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, 26 Mar 2017 21:00:25 +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, 26 Mar 2017 21:00:25 -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 Open | 148807 | [panic] "panic: sbdrop" and "panic: sbsndptr: soc 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_ 17 problems total for which you should take action. From owner-freebsd-net@freebsd.org Mon Mar 27 07:35: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 D101BD1FB71 for ; Mon, 27 Mar 2017 07:35:59 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB4EE115D for ; Mon, 27 Mar 2017 07:35:59 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-ot0-x22d.google.com with SMTP id y88so24896313ota.2 for ; Mon, 27 Mar 2017 00:35:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=W3U/hrmSCe37SrnM39V8XYF7PimsUnm0grKNzfiQeAA=; b=jYy3M1djCfAW00NlnCjTTFO3LDbwlJIFs1qQ/xzVi/5dFfHZeeTH0qhhlEqZMdjVIp ArOiFG1ncw7LGsnyV1K8UlMxc9C51ctlinKJq7dr88w/tmXEvYIUEnkNuo5GPwjZm8yb kipKXZZnQP3kT9SD2mfqmyAgI0BuM06iQr2uE= 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=W3U/hrmSCe37SrnM39V8XYF7PimsUnm0grKNzfiQeAA=; b=lZaxpeSEbGGQSrkY/Ut+QTMoZKC6hxahtYukVJjoL3aHpOsjVCJpRDGgZw1f1cvmEt tD2QnlRpqSeUIr1y4lSO1X21QU7aPZvB0fv+DYct2nQ6z09ypiXY1ntsuLf0lcisOfsL BTuoDWPW5tplTxjAsWN0YWKGMWweUWagTloOiA6HYtAWdy/F0NfOTh2Da+UUySUl/eUb BbIhUx4w4kRtAxDJBOjKaHiXxsAJgGawX0GeR3n/E/Q4XhoHp1xfWaIs6VsXRMQ2WUZR n7k6u8voBYMUD3i+jqDxbloOfLW2VbLenGrpYjidZzzzDU4VLb9s6GwaESAAeDQx307F o4mA== X-Gm-Message-State: AFeK/H2tuBZpvxgl5O32nIZs8MSNffv7EEFnaG3CIvCD67/GBIUYUNEQIcU2u/624QNR6ccoh5cSp2qCUUxaqw== X-Received: by 10.157.14.195 with SMTP id 61mr9859488otj.115.1490600158815; Mon, 27 Mar 2017 00:35:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.30.196 with HTTP; Mon, 27 Mar 2017 00:35:58 -0700 (PDT) In-Reply-To: References: From: Kevin Bowling Date: Mon, 27 Mar 2017 00:35:58 -0700 Message-ID: Subject: Re: interface down, console output: igb3: TX(7) desc avail = 41, pidx = 308 To: Ben Woods Cc: 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, 27 Mar 2017 07:35:59 -0000 Try turning TSO off.. i.e. ifconfig igb3 -tso or sysctl net.inet.tcp.tso=0 The transition to iflib has exposed much jankiness in the Intel "shared code" of the e1000 drivers. In particular, the locking contracts may not align with FreeBSD locking primitives. I have boxes running the legacy driver that are clearly reliant on the watchdog reset for steady state which is unacceptable. We are actively looking into this at LLNW, but additional reports and help are appreciated. Regards, On Fri, Mar 24, 2017 at 6:33 PM, Ben Woods wrote: > Morning! > > Since my recent update from FreeBSD12-current r313908 to r315466, I have > noticed some strange behaviour with one of my network interfaces. > > The interface seems to work fine for a day or so, but on a number of > occasions I have found it to be down, and constantly outputting the > following message to the console every few seconds: > igb3: TX(7) desc avail = 41, pidx = 308 > igb3: TX(7) desc avail = 41, pidx = 308 > igb3: TX(7) desc avail = 41, pidx = 308 > ... > > The problem is quickly worked around by issuing the following commands: > # service netif stop igb3 > # service netif start igb3 > > Details of this particular network interface card: > $ pciconf -lv | grep igb3 -A4 > igb3@pci0:0:20:1: class=0x020000 card=0x1f418086 chip=0x1f418086 rev=0x03 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection I354' > class = network > subclass = ethernet > > Any ideas what this could be, or how to investigate further? > > Regards, > Ben > > -- > From: Benjamin Woods > woodsb02@gmail.com > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Mon Mar 27 07:48: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 AB47AD1FEDF for ; Mon, 27 Mar 2017 07:48:20 +0000 (UTC) (envelope-from kevin.bowling@kev009.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 7193916D8 for ; Mon, 27 Mar 2017 07:48:20 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-oi0-x232.google.com with SMTP id o67so8348504oib.1 for ; Mon, 27 Mar 2017 00:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=R9Vvxc6xxxOzZDmQP0Ud6iKHS/wBEEvOP5Tiywv1wW4=; b=AotEtq4P70CchDoBSOHEgJfvs3wJp/7KEWYazyV5c+PBdBVjAUOyeDKokvKK/vl60P zP1rF4SciwKxwHcsXKAGnoo0OBo6m7YqdDKG9BBpD91UR8Km/ScoBh6zeOot7zS2AZNo 0YJL0uvCZWII+9DM23G1chxsDc0mcYGSU1UgE= 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=R9Vvxc6xxxOzZDmQP0Ud6iKHS/wBEEvOP5Tiywv1wW4=; b=Dl3nJ0zQAwerAz+OvZBKMusdGVnqiM3It05UK2Vp3PuOgFKZWWOs38ASklUnGA5lJS 3kEJeKmwc9j3B9DmHirGapRM9+pMLBPSTXPSf74avZvmA9drGWKR2nAXi1Qr5pVTgI1h v4moA1e8mjPw/mri7pgwcr0qUPSQU+wh9174zDeas6PsL57zLCOvuomSViBgC+YyM6D/ b9ZpLWX0q6kW5nQa3uZdHF6oVBNZ/va9G4f6ne8NlpyLG5k4vM7+GW3NrRYZIC7CxJtK 6or5hDDpGFCXvdp3qTulpfjkuYVTuxgvP9h0/wbbLEHQat7U8DG7znpsnMwwfgz/1EdR gXHg== X-Gm-Message-State: AFeK/H1uyYMHNt4JlCIKy13fb7bpuIyhn+yjagujp2zQWEix0f1gY6mkxPSQf/K29MbTkzkQB1/eyXFVTxYiGw== X-Received: by 10.202.82.9 with SMTP id g9mr10895771oib.13.1490600899757; Mon, 27 Mar 2017 00:48:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.30.196 with HTTP; Mon, 27 Mar 2017 00:48:19 -0700 (PDT) In-Reply-To: References: From: Kevin Bowling Date: Mon, 27 Mar 2017 00:48:19 -0700 Message-ID: Subject: Re: Error at the time of compiling netmap-fwd on -CURRENT To: "Caraballo-vega, Jordan A. (GSFC-6062)[COMPUTER SCIENCE CORP]" Cc: 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, 27 Mar 2017 07:48:20 -0000 Hi, The DPRINTF macro in netmap-fwd is defined as #define *DPRINTF*(_fmt, args...) if (verbose) dprintf(_fmt, ## args) while dprintf is defined as dprintf(int fd, const char * restrict format, ...); in stdio.h You could try, simplistically, to change DPRINTF macro to #define *DPRINTF*(_fmt, args...) if (verbose) printf(_fmt, ## args) to get going but there is likely more to the story. Regards, On Fri, Mar 24, 2017 at 4:19 PM, Caraballo-vega, Jordan A. (GSFC-6062)[COMPUTER SCIENCE CORP] wrote: > Hello, > > I am trying to compile netmap-fwd from git > (https://github.com/Netgate/netmap-fwd) on a Dell PE 530 with -CURRENT > updated from today (03/24/17). With the dependencies installed ( # pkg > install libucl libevent2 ) I run make and get the following error > followed by 8 warnings: > > cc -O2 -fPIC -g -Wall -Wshadow -Wcast-qual -Wwrite-strings > -Wredundant-decls -Wnested-externs -Winline -I/usr/local/include -c arp.c > In file included from arp.c:51: > ./util.h:33:5: error: conflicting types for 'dprintf' > int dprintf(const char *, ...); > ^ > /usr/include/stdio.h:364:6: note: previous declaration is here > int dprintf(int, const char * __restrict, ...) __printflike(2, 3); > ^ > arp.c:394:11: warning: incompatible pointer to integer conversion > passing 'const char [44]' to parameter of type 'int' > [-Wint-conversion] > DPRINTF("%s: discarding the packet, too short (%d).\n", > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ./util.h:29:54: note: expanded from macro 'DPRINTF' > > > Any idea or feedback would be greatly appreciated. > > Cheers, > > Jordan > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Mon Mar 27 08:28: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 A3C4DD1FED2 for ; Mon, 27 Mar 2017 08:28:34 +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 938861CCE for ; Mon, 27 Mar 2017 08:28:34 +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 v2R8SXVj019767 for ; Mon, 27 Mar 2017 08:28:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Mon, 27 Mar 2017 08:28: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 Some People X-Bugzilla-Who: aiko@torrentkino.de 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: Mon, 27 Mar 2017 08:28:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #14 from Aiko Barz --- Maybe nothing you like to hear, but I tried the pufferfish. It is running for some days now without issues so far and it handles the workload quite well. We cannot utilize the full 10Gbit/s at the moment anyw= ay because of other bottlenecks. So you might close the bug report because maybe it was just us. I don't kno= w. Nevertheless I needed a solution right now. I'm sorry. Kind regards, Aiko --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 27 16:38: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 60058D205A3 for ; Mon, 27 Mar 2017 16:38: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 4F666242 for ; Mon, 27 Mar 2017 16:38: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 v2RGcLcT063841 for ; Mon, 27 Mar 2017 16:38:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration Date: Mon, 27 Mar 2017 16:38:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ale@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 27 Mar 2017 16:38:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 Alex Dupre changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ale@FreeBSD.org --- Comment #7 from Alex Dupre --- Does this mean that StrongSwan will finally work OOTB on FreeBSD 11.1? :-) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Mar 27 17:25: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 8F758D20556 for ; Mon, 27 Mar 2017 17:25:36 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 4A0FBB43 for ; Mon, 27 Mar 2017 17:25:36 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id i34so43737974qtc.0 for ; Mon, 27 Mar 2017 10:25:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=tZHiRZRW4RJ7nt9vUKJWO892Ew8FqgBBNJuk9D9szZ4=; b=eq17R9RN+hErLdgZOUbQ8qj8ejqevljs20Dbbxb2ICn6jJ+o45uyfMiZvtKlpxn4nf aAn39r+FXlEc04i2GXVm1gSxy4U4mS0U0iIYsrdj0JTrSY9HV227AN7Wtbpmy8h7A8Zf rM0gEuE3tpsrqMJBdgw++iY2dHsL9EADrfvNDsu9OdWchboePZyEODWN3loNoNDR/spT f2NUZH3u0slWCe1e8NxN6M++JiYRtpbKhf5Tou5LYzydkodAI2r8E4Ukg8SOpbUQErs2 hd+gP4lRLa3BaDx5I8jQd0uRBiMoBrEH2ixbp3j4ahQVizu/v0YiwwCzUhSQtxTrNev9 om6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=tZHiRZRW4RJ7nt9vUKJWO892Ew8FqgBBNJuk9D9szZ4=; b=IzXkiQZpPBrHj1wWr4czagmgSp7ybtJraugx+3cv0v2ptCKYm3nBZgBcQFw545kULK xcKygjZh+MaymUHCKzO+ZpGa81cb06rGhZDWETNq/tCeKzIrNdegMSSPNNAoAp3kx0z0 IKhx85T6Gkloev+C+1+ampt4D7Qv5fMEpMdqYAdg9ISccW/8XzsYH4sHELq/Vu/PeJtp 5tSOiOjlBgTNgj9hpoLrYakub+nWP7gYubyZW5CBqZT+qFVkHZtJoQBU9/s7zh4dRWyH 9FDeZhHrMg0WH7Ds4h5eIP0utQXfVc9r8B/qehly7h9n+aBznPkf1OwBT2bSNccuZwgt Hraw== X-Gm-Message-State: AFeK/H0HkkiuXJBUGWpjFe/aXXKDo+TA0Z1nZpAtoy/I5MhYzEbDp2T5y20f+xeGoIXOeQ== X-Received: by 10.200.40.42 with SMTP id 39mr21616471qtq.149.1490635535198; Mon, 27 Mar 2017 10:25:35 -0700 (PDT) Received: from [10.1.28.127] ([198.119.59.10]) by smtp.googlemail.com with ESMTPSA id q188sm795324qkf.20.2017.03.27.10.25.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Mar 2017 10:25:34 -0700 (PDT) Subject: Re: Error at the time of compiling netmap-fwd on -CURRENT To: freebsd-net@freebsd.org References: From: John Jasen Message-ID: Date: Mon, 27 Mar 2017 13:25:33 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 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, 27 Mar 2017 17:25:36 -0000 FreeBSD 11 and prior, dprintf in stdio.h had to be specifically called by setting particular defines. These were removed in -CURRENT, which caused dprintf from /usr/include/stdio.h to coflict with the declarations in netmap-fwd. Commenting out the #define and the int dprintf statements in netmap-fwd/util.h and util.c allowed it to compile and mostly work. From owner-freebsd-net@freebsd.org Mon Mar 27 17:30: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 7C7FAD2077C for ; Mon, 27 Mar 2017 17:30:36 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 2F021F6A; Mon, 27 Mar 2017 17:30:36 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: by mail-qk0-x22a.google.com with SMTP id r142so15965248qke.2; Mon, 27 Mar 2017 10:30:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=8kmpfTKIjcAnZXO9FgWhfUkKioDiLOFx5A9qjPsLHQU=; b=cRCCw5oVLyEpZ40GkH4PaDfmyLyUZmTrfgjY112ayfoH13SnBkkO1Crut/4Uwp+SID seJSfwfXuTC67aSaXlstW9Gj3YEEXdC4Gu+dcAvCSJOzsSvupe30OY/o01TY7ZG9ubAa uCeGdB8WqATTfNfjKrJm4a4qLc8XofuJKM9RqRVu3snctndNRRcXZX3XClN0c/mP3CWH bqRYr7zUyqm+SB9KqAB5FQ/KLvxdKkqXEmQxeKmcRE0NjwdodT362cfuhvqYxTwWOyjP CKOz1ER7eGxi4OZUqqC05Wrbnzq9Pp+HEc95hQQv5PtENZWYysTdvdwu/an7zyILbcdk xHXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8kmpfTKIjcAnZXO9FgWhfUkKioDiLOFx5A9qjPsLHQU=; b=faTTmMbC5WRjK854MtY84sHnhz1i2kpEvk9MmX5/PzE59XbijE4Q2eRNv2SGsZdQE3 CPskFhPdoW//Hp/sSEmGBnai1THC7XDkcXW08ymXekM5NsrPT77I3l6Pg4xJ4/7lIZdH Ca+h+CRewpV3kaoAnpNN5MIJ2U9yzoGHD+cdpKwcRdRwxnMROHn6XRJeA+aPCUaNArdp Bv/K6RoBMmFmJStzm3WK3UyQclsE4Cwn8qvfW+JaPmKSMzVw2Hq6DCggWQ7mebkbLwKI KUVCsFU4UwYLYZDjl+8umS9o/AKQfVhZ7uV5pWeJgJs7mwjXm5DPxGyRsn4ZUqetVeQM E+sg== X-Gm-Message-State: AFeK/H18rZPe+CWt+ZyC58Nt3Bh2wVm1sF03MgOC5DMbP2mtkiKy20BlqzejEJoJQFf1fw== X-Received: by 10.55.105.6 with SMTP id e6mr20423311qkc.252.1490635835243; Mon, 27 Mar 2017 10:30:35 -0700 (PDT) Received: from [10.1.28.127] ([198.119.59.10]) by smtp.googlemail.com with ESMTPSA id p184sm805754qkb.17.2017.03.27.10.30.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Mar 2017 10:30:34 -0700 (PDT) Subject: Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 To: Navdeep Parhar , "Caraballo-vega, Jordan A. (GSFC-6062)[COMPUTER SCIENCE CORP]" References: <20170312231826.GV15630@zxy.spb.ru> <74654520-b8b6-6118-2e46-902a8ea107ac@gmail.com> <173fffac-7ae2-786a-66c0-e9cd7ab78f44@gmail.com> <20170317100814.GN70430@zxy.spb.ru> <9924b2d5-4a72-579c-96c6-4dbdacc07c95@gmail.com> <9694e9f2-daec-924d-e9f6-7b22a634acb5@gmail.com> <20170318052837.GA21730@ox> <0a4e3073-bf5f-9bf8-533f-bd9ec3c0f60c@FreeBSD.org> Cc: freebsd-net@freebsd.org, slw@zxy.spb.ru From: John Jasen Message-ID: <06a0309b-8e5a-8857-4394-3a714d251cda@gmail.com> Date: Mon, 27 Mar 2017 13:30:34 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 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, 27 Mar 2017 17:30:36 -0000 On 03/24/2017 08:51 PM, Navdeep Parhar wrote: > On 03/24/2017 16:53, Caraballo-vega, Jordan A. (GSFC-6062)[COMPUTER > SCIENCE CORP] wrote: >> It looks like netmap is there; however, is there a way of figuring out >> if netmap is being used? > > If you're not running netmap-fwd or some other netmap application, > it's not being used. You have just 1 txq/rxq and that would explain > the difference between cxl and vcxl. Using netmap-fwd, we seem to hover between 2.2m and 3.6m pps, depending on luck and how many streams. netmap-fwd does complain often about running out of tx rings and/or buffer space during these runs. CPU usage clocks in at about 10%-12% across CPUs engaged with a queue. > > # sysctl -a | grep tx_pause Pause was enabled, but allegedly silent during the netmap tests. From owner-freebsd-net@freebsd.org Mon Mar 27 18:54: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 0E83DD200D6 for ; Mon, 27 Mar 2017 18:54: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 F1FC8A58 for ; Mon, 27 Mar 2017 18:54: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 v2RIse2J003242 for ; Mon, 27 Mar 2017 18:54:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration Date: Mon, 27 Mar 2017 18:54:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: 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: Mon, 27 Mar 2017 18:54:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 --- Comment #8 from Andrey V. Elsukov --- (In reply to Alex Dupre from comment #7) > Does this mean that StrongSwan will finally work OOTB on FreeBSD 11.1? :-) You can test and report. I have one report about panics with strongswan on stable/11, but no debugging info currently. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 28 06:30:25 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 5C342D22232 for ; Tue, 28 Mar 2017 06:30:25 +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 47D38E69 for ; Tue, 28 Mar 2017 06:30:25 +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 v2S6UOoX097724 for ; Tue, 28 Mar 2017 06:30:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217721] axge(4) hangs while link goes offline Date: Tue, 28 Mar 2017 06:30:25 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yongari@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: Tue, 28 Mar 2017 06:30:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217721 --- Comment #7 from Pyun YongHyeon --- (In reply to Eugene Lozovoy from comment #6) Added Kevin(driver author) to CC list. Let's see whether he has a better idea on the issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Mar 28 10:30:23 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 B747DD201E6 for ; Tue, 28 Mar 2017 10:30:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EF9134D for ; Tue, 28 Mar 2017 10:30:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2SAUMGa010190 for ; Tue, 28 Mar 2017 10:30:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration Date: Tue, 28 Mar 2017 10:30:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ale@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: 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: Tue, 28 Mar 2017 10:30:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 --- Comment #9 from Alex Dupre --- Just built a 11-STABLE kernel over an AWS AMI 11.0-RELEASE and the tunnel w= ent up fine (IKEv1/ESP, tunnel mode, very low traffic). It's been running for a= few minutes without issues, but I don't know what could be the conditions that trigger the panic. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Mar 29 10:50:54 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 12B50D223F5 for ; Wed, 29 Mar 2017 10:50:54 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C02267D7B for ; Wed, 29 Mar 2017 10:50:52 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (net206-94.perm.ertelecom.ru [46.146.206.94] (may be forged)) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v2TAoi8n065609 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 29 Mar 2017 15:50:46 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-net From: "Eugene M. Zheganin" Subject: my dummynet adventures (spoiler alert: everyone just dies at the end) Message-ID: <6258ec04-a0d6-750e-6619-4237f744434b@norma.perm.ru> Date: Wed, 29 Mar 2017 15:50:44 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [1.56 / 25.00] HFILTER_HOSTNAME_UNKNOWN(2.50)[] RBL_SPAMHAUS_PBL(2.00)[94.206.146.46.zen.spamhaus.org : 127.0.0.10] BAYES_HAM(-2.94)[99.75%] MIME_GOOD(-0.10)[text/plain] R_SPF_SOFTFAIL(0.00)[~all] R_DKIM_NA(0.00)[] FROM_EQ_ENVFROM(0.00)[] RCPT_COUNT_1(0.00)[] DMARC_NA(0.00)[norma.perm.ru] RCVD_COUNT_1(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] FROM_HAS_DN(0.00)[] ONCE_RECEIVED(0.10)[] TO_DN_ALL(0.00)[] RECEIVED_SPAMHAUS(0.00)[94.206.146.46.zen.spamhaus.org] MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.70 X-Rspamd-Queue-ID: v2TAoi8n065609 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, 29 Mar 2017 10:50:54 -0000 Hi, Recently I had to move from Ultimate and Perfect pf (because it's not the Ultimate and Perfect when it comes to gigabit/s speeds, due to legacy TX in Intel drivers and associated problems) [back] to ipfw. I was terribly disappointed, because after 10 years with pf I felt myself like being traveled to a stone age, with relic and unuseable spears and arrows instead of pulse rifles and railguns. Seems like nothing changed for 10 years there: - "ipfw pipe show" still isn't documented. Like at all. - "ipfw pipe show" output is weird and cryptic and nobody understands it without reading sources. Even after reading sources few understand it (I don't). Our local FreeBSD guru is able to explain the output field meaning, but first time he explains it wrong, then he consult the sources (and does it each time), then he explains again, correcting the mistakes (and the guy really rocks, I mean - if it's not intuitive to him, who could understand it). Looks like nobody of the ipfw developers haven't seen "pfctl -vvvs queue show" output (which is a state of the art, really), so everyone who's using ipfw pipes have to cut and torture themselves. I asked same local FreeBSD guru "How can I prove to myself that this thing even works ?" and I've been told to just .... measure the traffic after it has flown through the shaper ! Same thing with drops measuring. "ipfw pipe show" shows zero drops (although I expect some), so I've been told to add the counter rules after pipe ones, and to switch the net.inet.ip.fw.one_pass to 0. Just to count the drops (it really counts it, so it's a mystery why the "ipfw pipe show" does show nothing). Furthermore, "ipfw pipe show" shows almost nothing when there's no traffic going through the pipe - and it really would be just logical to store the cumulative statistics there. Concluding, ipfw dummynet interface resembles an unfinished student work, it's stuck in early 2000's, and it really does not look like something of a production-ready system. I know that nobody owes noone anything, bit it really looks like both "modern" FreeBSD packet filters are lying in ruins, and people using ipfw had to scavenge some long ago broken instruments on the junkyards (like in Mad max series) and use sun and stars just to determine whether it's working or not. I didn't mention that both still use 32-bit integers, thus limiting the actual bandwidth to 4 Gigs/sec. Jesus. Eugene. From owner-freebsd-net@freebsd.org Wed Mar 29 18:38: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 9CB75D24E02 for ; Wed, 29 Mar 2017 18:38: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 89A8B1B7F for ; Wed, 29 Mar 2017 18:38: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 v2TIc8ZD007734 for ; Wed, 29 Mar 2017 18:38:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211643] ixgbe(4) does not reliably bring up 10G links with ZyXEL XS1920 switches Date: Wed, 29 Mar 2017 18:38: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: 10.3-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nwhitehorn@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, 29 Mar 2017 18:38:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211643 --- Comment #6 from Nathan Whitehorn --- Is the SuperMicro firmware update released? I have never had any luck with autoconfiguration either. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Mar 29 19:04: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 26512D23A3A for ; Wed, 29 Mar 2017 19:04: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 0B5C533C for ; Wed, 29 Mar 2017 19:04: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 v2TJ4aNC076687 for ; Wed, 29 Mar 2017 19:04:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211643] ixgbe(4) does not reliably bring up 10G links with ZyXEL XS1920 switches Date: Wed, 29 Mar 2017 19:04: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: 10.3-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pi@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, 29 Mar 2017 19:04:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211643 --- Comment #7 from Kurt Jaeger --- As far as I understand the firmware is not publicly released. Please go to https://webpr3.supermicro.com/Support/login.aspx? open a ticket, reference the ticket SM1703233787 and ask for the patch. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Mar 30 02:47:05 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 1C0BED25941 for ; Thu, 30 Mar 2017 02:47:05 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [IPv6:2001:19f0:5801:2ba:5400:ff:fe59:15d6]) (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 BCA13CF9; Thu, 30 Mar 2017 02:47:04 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: by lauren.room52.net (Postfix) with ESMTPSA id BD2F429105; Thu, 30 Mar 2017 13:46:57 +1100 (AEDT) Subject: Re: IPv6: "xxx::x already configured" in logs... why? To: freebsd-net@freebsd.org References: <20140612202349.GA65079@thebighonker.lerctr.org> <20140619.181129.1279477227287764712.hrs@allbsd.org> <20140619140801.GA65420@thebighonker.lerctr.org> <20140620.130812.1612764660960146940.hrs@allbsd.org> Cc: Hiroki Sato , ler@lerctr.org From: Lawrence Stewart Message-ID: Date: Wed, 29 Mar 2017 21:46:51 -0500 User-Agent: Not your concern MIME-Version: 1.0 In-Reply-To: <20140620.130812.1612764660960146940.hrs@allbsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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, 30 Mar 2017 02:47:05 -0000 [resurrecting an old thread] On 19/06/2014 23:08, Hiroki Sato wrote: > Larry Rosenman wrote > in <20140619140801.GA65420@thebighonker.lerctr.org>: > > le> > le> Ideas? (I may be an idiot, so any criticism welcomed). > le> > le> > le> > le> if you need the 1841's config, I can supply that as well. It's using a Hurricane > le> > le> electric Tunnel. > le> > > le> > How frequent were the log message added into /var/log/messages? And > le> > when did it start to happen after boot. Just after lagg0 is > le> > configured? > le> > > le> > -- Hiroki > le> Looks like: > le> > le> Jun 12 07:00:01 thebighonker kernel: in6_ifadd: 2001:470:1f0f:3ad:223:7dff:fe9e:6e8a is already configured > > Thank you. Three more questions: > > 1. output of "ifconfig lagg0", "ifconfig bce0", and "ifconfig bce1". > > 2. output of "netstat -s -i". > > 3. output of "ndp -p". > > The cause of the message is that the automatically-configured address > is not recognized as "configured" one and FreeBSD IPv6 stack is > trying to add it every time a Router Advertisement message is > received. I am still not sure why it happened, but the above three > would help for further investigation. I've recently set up a VPS with v6 and am seeing the same "in6_ifadd: is already configured" messages in response to periodically received router advertisements every 5-10 mins. The host is a KVM-based virtual machine with vtnet-based NIC. v6 is fully functional with the statically assigned v6 address, but the spam in /var/log/messages is annoying. FreeBSD revision: FreeBSD lauren 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315059: Sun Mar 12 20:44:50 AEDT 2017 root@builder-head-amd64:/usr/obj/lauren/usr/src/sys/GENERIC-NODEBUG amd64 Relevant bits from /etc/rc.conf: rtsold_enable="YES" ipv6_activate_all_interfaces="YES" rtsold_flags="-aF" ifconfig_vtnet0_ipv6="inet6 prefixlen 64" Interface: vtnet0: flags=8843 metric 0 mtu 1500 options=6c07bb ether inet netmask 0xfffffe00 broadcast inet6 %vtnet0 prefixlen 64 scopeid 0x1 inet6 prefixlen 64 nd6 options=23 media: Ethernet 10Gbase-T status: active I would have thought rtsold should be able to play nice with statically assigned v6 addresses... any ideas? Cheers, Lawrence From owner-freebsd-net@freebsd.org Thu Mar 30 02:50: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 7523ED25BA1 for ; Thu, 30 Mar 2017 02:50:15 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 5A3BBF9B; Thu, 30 Mar 2017 02:50:15 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0ONL00600WQO1C00@mr11p00im-asmtp003.me.com>; Thu, 30 Mar 2017 02:49:59 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1490842199; bh=CRTnuyKveqEF0TCgNyVEsXYXzoYR3EcnqF1BRrpmy2w=; h=MIME-version:Content-type:Message-id:Subject:From:To:Date; b=iQT0MkW+D+UteOM7K0J5OGJg2l8sgPAFL04O9VwAIWHexs+9PWJNxcnTCeu6j2O2g sPFfSjgcBXqaOG9pzoohzg0Q4eQdVjHPuhlr98Y50eUY8khStHFdcVOy/tZDzPgTBs WChsMr3tTSOMs+m9i/dn4e3mtYVKGrjNyJdEKpe4p5kGCgsMlD8bfk6XJs2F0UPPnI S02UBini/7JC2geKwbGNFyPIxn0tFxZs4nzwnu655KZTHH26Ats33lgflSpRyrO8lZ 8+XmEGSZzR106PhN+SPqYDeVR0mvzzYmYqDdcu4tZcYejzhqmF9FTtCewHAV1qy8Ko iSlCWzYjIJXfw== MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0ONL00M9RX77XY30@mr11p00im-asmtp003.me.com>; Thu, 30 Mar 2017 02:49:56 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-30_01:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1703300025 Message-id: <1490842195.3260.35.camel@me.com> Subject: Re: IPv6: "xxx::x already configured" in logs... why? From: Rui Paulo To: Lawrence Stewart , freebsd-net@freebsd.org Cc: Hiroki Sato , ler@lerctr.org Date: Wed, 29 Mar 2017 19:49:55 -0700 In-reply-to: References: <20140612202349.GA65079@thebighonker.lerctr.org> <20140619.181129.1279477227287764712.hrs@allbsd.org> <20140619140801.GA65420@thebighonker.lerctr.org> <20140620.130812.1612764660960146940.hrs@allbsd.org> X-Mailer: Evolution 3.22.5-1 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, 30 Mar 2017 02:50:15 -0000 On Wed, 2017-03-29 at 21:46 -0500, Lawrence Stewart wrote: > [resurrecting an old thread] > > On 19/06/2014 23:08, Hiroki Sato wrote: > > Larry Rosenman wrote > >   in <20140619140801.GA65420@thebighonker.lerctr.org>: > > > > le> > le> Ideas? (I may be an idiot, so any criticism welcomed). > > le> > le> > > le> > le> if you need the 1841's config, I can supply that as > > well.  It's using a Hurricane > > le> > le> electric Tunnel. > > le> > > > le> >  How frequent were the log message added into > > /var/log/messages?  And > > le> >  when did it start to happen after boot.  Just after lagg0 is > > le> >  configured? > > le> > > > le> > -- Hiroki > > le> Looks like: > > le> > > le> Jun 12 07:00:01 thebighonker kernel: in6_ifadd: > > 2001:470:1f0f:3ad:223:7dff:fe9e:6e8a is already configured > > > >  Thank you.  Three more questions: > > > >  1. output of "ifconfig lagg0", "ifconfig bce0", and "ifconfig > > bce1". > > > >  2. output of "netstat -s -i". > > > >  3. output of "ndp -p". > > > >  The cause of the message is that the automatically-configured > > address > >  is not recognized as "configured" one and FreeBSD IPv6 stack is > >  trying to add it every time a Router Advertisement message is > >  received.  I am still not sure why it happened, but the above > > three > >  would help for further investigation. > > I've recently set up a VPS with v6 and am seeing the same "in6_ifadd: > is already configured" messages in response to periodically > received router advertisements every 5-10 mins. The host is a KVM- > based > virtual machine with vtnet-based NIC. v6 is fully functional with the > statically assigned v6 address, but the spam in /var/log/messages is > annoying. > > > FreeBSD revision: >   FreeBSD lauren 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315059: Sun > Mar > 12 20:44:50 AEDT 2017 > root@builder-head-amd64:/usr/obj/lauren/usr/src/sys/GENERIC- > NODEBUG  amd64 > > > Relevant bits from /etc/rc.conf: >   rtsold_enable="YES" >   ipv6_activate_all_interfaces="YES" >   rtsold_flags="-aF" >   ifconfig_vtnet0_ipv6="inet6 prefixlen 64" > > > Interface: >   vtnet0: flags=8843 metric 0 > mtu 1500 > > options=6c07bb WCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> >         ether >         inet netmask 0xfffffe00 broadcast >         inet6 %vtnet0 prefixlen 64 scopeid 0x1 >         inet6 prefixlen 64 >         nd6 options=23 >         media: Ethernet 10Gbase-T >         status: active > > > I would have thought rtsold should be able to play nice with > statically > assigned v6 addresses... any ideas? Hmm, why would it? If you setup an IPv6 address and then there's a router solicitation advertising the same address, the log message makes sense. I don't think you should run rtsold if you have a static IPv6 address. -- Rui Paulo From owner-freebsd-net@freebsd.org Thu Mar 30 02:57: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 7FEFFD251DA for ; Thu, 30 Mar 2017 02:57:10 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [IPv6:2001:19f0:5801:2ba:5400:ff:fe59:15d6]) (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 C634AA48; Thu, 30 Mar 2017 02:57:09 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: by lauren.room52.net (Postfix) with ESMTPSA id D820829116; Thu, 30 Mar 2017 13:56:57 +1100 (AEDT) Subject: Re: IPv6: "xxx::x already configured" in logs... why? To: Rui Paulo , freebsd-net@freebsd.org References: <20140612202349.GA65079@thebighonker.lerctr.org> <20140619.181129.1279477227287764712.hrs@allbsd.org> <20140619140801.GA65420@thebighonker.lerctr.org> <20140620.130812.1612764660960146940.hrs@allbsd.org> <1490842195.3260.35.camel@me.com> Cc: Hiroki Sato , ler@lerctr.org From: Lawrence Stewart Message-ID: <56d1a947-a0a1-0297-7151-4e36ab53cff1@freebsd.org> Date: Wed, 29 Mar 2017 21:56:52 -0500 User-Agent: Not your concern MIME-Version: 1.0 In-Reply-To: <1490842195.3260.35.camel@me.com> Content-Type: text/plain; charset=utf-8 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, 30 Mar 2017 02:57:10 -0000 On 29/03/2017 21:49, Rui Paulo wrote: > On Wed, 2017-03-29 at 21:46 -0500, Lawrence Stewart wrote: >> [resurrecting an old thread] >> >> On 19/06/2014 23:08, Hiroki Sato wrote: >>> Larry Rosenman wrote >>> in <20140619140801.GA65420@thebighonker.lerctr.org>: >>> >>> le> > le> Ideas? (I may be an idiot, so any criticism welcomed). >>> le> > le> >>> le> > le> if you need the 1841's config, I can supply that as >>> well. It's using a Hurricane >>> le> > le> electric Tunnel. >>> le> > >>> le> > How frequent were the log message added into >>> /var/log/messages? And >>> le> > when did it start to happen after boot. Just after lagg0 is >>> le> > configured? >>> le> > >>> le> > -- Hiroki >>> le> Looks like: >>> le> >>> le> Jun 12 07:00:01 thebighonker kernel: in6_ifadd: >>> 2001:470:1f0f:3ad:223:7dff:fe9e:6e8a is already configured >>> >>> Thank you. Three more questions: >>> >>> 1. output of "ifconfig lagg0", "ifconfig bce0", and "ifconfig >>> bce1". >>> >>> 2. output of "netstat -s -i". >>> >>> 3. output of "ndp -p". >>> >>> The cause of the message is that the automatically-configured >>> address >>> is not recognized as "configured" one and FreeBSD IPv6 stack is >>> trying to add it every time a Router Advertisement message is >>> received. I am still not sure why it happened, but the above >>> three >>> would help for further investigation. >> >> I've recently set up a VPS with v6 and am seeing the same "in6_ifadd: >> is already configured" messages in response to periodically >> received router advertisements every 5-10 mins. The host is a KVM- >> based >> virtual machine with vtnet-based NIC. v6 is fully functional with the >> statically assigned v6 address, but the spam in /var/log/messages is >> annoying. >> >> >> FreeBSD revision: >> FreeBSD lauren 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315059: Sun >> Mar >> 12 20:44:50 AEDT 2017 >> root@builder-head-amd64:/usr/obj/lauren/usr/src/sys/GENERIC- >> NODEBUG amd64 >> >> >> Relevant bits from /etc/rc.conf: >> rtsold_enable="YES" >> ipv6_activate_all_interfaces="YES" >> rtsold_flags="-aF" >> ifconfig_vtnet0_ipv6="inet6 prefixlen 64" >> >> >> Interface: >> vtnet0: flags=8843 metric 0 >> mtu 1500 >> >> options=6c07bb> WCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> >> ether >> inet netmask 0xfffffe00 broadcast >> inet6 %vtnet0 prefixlen 64 scopeid 0x1 >> inet6 prefixlen 64 >> nd6 options=23 >> media: Ethernet 10Gbase-T >> status: active >> >> >> I would have thought rtsold should be able to play nice with >> statically >> assigned v6 addresses... any ideas? > > Hmm, why would it? If you setup an IPv6 address and then there's a > router solicitation advertising the same address, the log message makes > sense. > > I don't think you should run rtsold if you have a static IPv6 address. How would the host learn about router(s) on the network and other addresses it might want? (In my particular environment, I'm pretty sure they don't change so could be statically configured, but interested in understanding if (and why) these are mutually exclusive modes of operation). From owner-freebsd-net@freebsd.org Thu Mar 30 03:22: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 767CFD17554 for ; Thu, 30 Mar 2017 03:22:27 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id E0D55219 for ; Thu, 30 Mar 2017 03:22:25 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39655258 for freebsd-net@freebsd.org; Thu, 30 Mar 2017 09:17:54 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.14.9/8.14.9) with ESMTP id v2U3MNkV018782 for ; Thu, 30 Mar 2017 10:22:23 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.14.9/8.14.9/Submit) id v2U3MM27018781 for freebsd-net@freebsd.org; Thu, 30 Mar 2017 10:22:22 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Thu, 30 Mar 2017 10:22:22 +0700 From: Victor Sudakov To: freebsd-net@freebsd.org Subject: OpenVPN and policy routing Message-ID: <20170330032222.GA18053@admin.sibptus.transneft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.7.1 (2016-10-04) 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, 30 Mar 2017 03:22:27 -0000 Dear Colleagues, Anyone experienced with OpenVPN on FreeBSD? What would be the best way to policy route a network into OpenVPN? A routing decision must be based on the src IP address, not the dst IP address. Imagine an OpenVPN client with 3 interfaces: fxp0 is the outside interface towards the OpenVPN server, fxp1 is for LAN1 and fxp2 for LAN2. From LAN1, some private networks are reachable through OpenVPN (tun0), this is done via the regular route commands (pulled from the OpenVPN server). From LAN2, *everything* should be reachable only through OpenVPN. Which is the best way to accomplish this? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-net@freebsd.org Thu Mar 30 04:12: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 B8D0AD257CB for ; Thu, 30 Mar 2017 04:12:45 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.allbsd.org", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9567EB0; Thu, 30 Mar 2017 04:12:44 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail-d.allbsd.org (p2027-ipbf1605funabasi.chiba.ocn.ne.jp [123.225.191.27]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id v2U4CIhT091415 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) (Client CN "/OU=GT07882699/OU=See+20www.rapidssl.com/resources/cps+20+28c+2915/OU=Domain+20Control+20Validated+20-+20RapidSSL+28R+29/CN=*.allbsd.org", Issuer "/C=US/O=GeoTrust+20Inc./CN=RapidSSL+20SHA256+20CA+20-+20G3"); Thu, 30 Mar 2017 13:12:38 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from alph.allbsd.org (alph.allbsd.org [192.168.0.10]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id v2U4B2Oi045630 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 Mar 2017 13:11:02 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.15.2/8.15.2) with ESMTPA id v2U4B0js045627; Thu, 30 Mar 2017 13:11:02 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Thu, 30 Mar 2017 13:09:03 +0900 (JST) Message-Id: <20170330.130903.1652530769294174766.hrs@allbsd.org> To: lstewart@freebsd.org Cc: rpaulo@me.com, freebsd-net@freebsd.org, ler@lerctr.org Subject: Re: IPv6: "xxx::x already configured" in logs... why? From: Hiroki Sato In-Reply-To: <56d1a947-a0a1-0297-7151-4e36ab53cff1@freebsd.org> References: <1490842195.3260.35.camel@me.com> <56d1a947-a0a1-0297-7151-4e36ab53cff1@freebsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_Mar_30_13_09_03_2017_179)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.4.3 (mail.allbsd.org [133.31.130.32]); Thu, 30 Mar 2017 13:12:40 +0900 (JST) X-Spam-Status: No, score=-97.9 required=13.0 tests=CONTENT_TYPE_PRESENT, QENCPTR1,URIBL_SC2_SURBL,URIBL_XS_SURBL,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on gatekeeper.allbsd.org 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, 30 Mar 2017 04:12:45 -0000 ----Security_Multipart(Thu_Mar_30_13_09_03_2017_179)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lawrence Stewart wrote in <56d1a947-a0a1-0297-7151-4e36ab53cff1@freebsd.org>: ls> On 29/03/2017 21:49, Rui Paulo wrote: ls> > On Wed, 2017-03-29 at 21:46 -0500, Lawrence Stewart wrote: ls> >> [resurrecting an old thread] ls> >> ls> >> On 19/06/2014 23:08, Hiroki Sato wrote: ls> >>> Larry Rosenman wrote ls> >>> in <20140619140801.GA65420@thebighonker.lerctr.org>: ls> >>> ls> >>> le> > le> Ideas? (I may be an idiot, so any criticism welcomed). ls> >>> le> > le> ls> >>> le> > le> if you need the 1841's config, I can supply that as ls> >>> well. It's using a Hurricane ls> >>> le> > le> electric Tunnel. ls> >>> le> > ls> >>> le> > How frequent were the log message added into ls> >>> /var/log/messages? And ls> >>> le> > when did it start to happen after boot. Just after lagg0 is ls> >>> le> > configured? ls> >>> le> > ls> >>> le> > -- Hiroki ls> >>> le> Looks like: ls> >>> le> ls> >>> le> Jun 12 07:00:01 thebighonker kernel: in6_ifadd: ls> >>> 2001:470:1f0f:3ad:223:7dff:fe9e:6e8a is already configured ls> >>> ls> >>> Thank you. Three more questions: ls> >>> ls> >>> 1. output of "ifconfig lagg0", "ifconfig bce0", and "ifconfig ls> >>> bce1". ls> >>> ls> >>> 2. output of "netstat -s -i". ls> >>> ls> >>> 3. output of "ndp -p". ls> >>> ls> >>> The cause of the message is that the automatically-configured ls> >>> address ls> >>> is not recognized as "configured" one and FreeBSD IPv6 stack is ls> >>> trying to add it every time a Router Advertisement message is ls> >>> received. I am still not sure why it happened, but the above ls> >>> three ls> >>> would help for further investigation. ls> >> ls> >> I've recently set up a VPS with v6 and am seeing the same "in6_ifadd: ls> >> is already configured" messages in response to periodically ls> >> received router advertisements every 5-10 mins. The host is a KVM- ls> >> based ls> >> virtual machine with vtnet-based NIC. v6 is fully functional with the ls> >> statically assigned v6 address, but the spam in /var/log/messages is ls> >> annoying. ls> >> ls> >> ls> >> FreeBSD revision: ls> >> FreeBSD lauren 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315059: Sun ls> >> Mar ls> >> 12 20:44:50 AEDT 2017 ls> >> root@builder-head-amd64:/usr/obj/lauren/usr/src/sys/GENERIC- ls> >> NODEBUG amd64 ls> >> ls> >> ls> >> Relevant bits from /etc/rc.conf: ls> >> rtsold_enable="YES" ls> >> ipv6_activate_all_interfaces="YES" ls> >> rtsold_flags="-aF" ls> >> ifconfig_vtnet0_ipv6="inet6 prefixlen 64" ls> >> ls> >> ls> >> Interface: ls> >> vtnet0: flags=8843 metric 0 ls> >> mtu 1500 ls> >> ls> >> options=6c07bb >> WCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ls> >> ether ls> >> inet netmask 0xfffffe00 broadcast ls> >> inet6 %vtnet0 prefixlen 64 scopeid 0x1 ls> >> inet6 prefixlen 64 ls> >> nd6 options=23 ls> >> media: Ethernet 10Gbase-T ls> >> status: active ls> >> ls> >> ls> >> I would have thought rtsold should be able to play nice with ls> >> statically ls> >> assigned v6 addresses... any ideas? ls> > ls> > Hmm, why would it? If you setup an IPv6 address and then there's a ls> > router solicitation advertising the same address, the log message makes ls> > sense. ls> > ls> > I don't think you should run rtsold if you have a static IPv6 address. ls> ls> How would the host learn about router(s) on the network and other ls> addresses it might want? (In my particular environment, I'm pretty sure ls> they don't change so could be statically configured, but interested in ls> understanding if (and why) these are mutually exclusive modes of operation). As Rui already pointed out, I guess you manually configured exactly the same address as the auto-configured EUI-64 address such as 2001:db8::211:85ff:fefe:d6db/64 where the upper 64 bits are equal to your IPv6 global prefix and the lower 64 bits are the same as ones in . I do not think this manual configuration is required here. Only ifconfig_vtnet0_ipv6="inet6 accept_rtadv" line instead of the four lines in your rc.conf should work. Because most of RA options are handled in the kernel, just enabling "accept_rtadv" in $ifconfig_IF_ipv6 is sufficient. Enabling rtsold is required only when 1) an IPv6 router on your subnet is sending DNS information in RAs and you want to receive it to configure /etc/resolv.conf automatically or 2) an IPv6 router on your subnet requires DHCPv6 to IPv6 host nodes on the subnet. In both cases, some userland program has to handle the RA options. The rtsold daemon is exactly for this purpose. The other information in RAs including default routers, prefixes, MTUs, and etc. is directly handled in the kernel. Configuring a static address and enabling accept_rtadv/rtsold are not mutually exclusive. The problem is that you are using the auto-configured address manually. If you need it for some reason, you can add "autoconf" flag to the rc.conf line like this: ifconfig_vtnet0_ipv6="inet6 prefixlen 64 autoconf accept_rtadv" This per-address flag means whether the address is auto-configured or not. Although normally this is set only by the kernel, you can set it by using ifconfig. If the address has this flag, the kernel thinks it has been configured by RAs and does not emit the warning messages. -- Hiroki ----Security_Multipart(Thu_Mar_30_13_09_03_2017_179)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAljchN8ACgkQTyzT2CeTzy32aACg2nmYnli+8/KneCO5SNbztsss bSQAn2HSYYVk1HaqxmPxGAKH4FZ/1KyK =S3UV -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Mar_30_13_09_03_2017_179)---- From owner-freebsd-net@freebsd.org Thu Mar 30 07:12:51 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 F1FEBD25A36 for ; Thu, 30 Mar 2017 07:12:51 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp207.alice.it (smtp207.alice.it [82.57.200.103]) by mx1.freebsd.org (Postfix) with ESMTP id 89DF6783 for ; Thu, 30 Mar 2017 07:12:51 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (82.52.25.226) by smtp207.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 588F42830BE1F6F6; Thu, 30 Mar 2017 09:12:27 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v2U7CQrm032368; Thu, 30 Mar 2017 09:12:29 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: OpenVPN and policy routing To: Victor Sudakov , freebsd-net@freebsd.org References: <20170330032222.GA18053@admin.sibptus.transneft.ru> From: Andrea Venturoli Message-ID: <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> Date: Thu, 30 Mar 2017 09:12:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <20170330032222.GA18053@admin.sibptus.transneft.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 30 Mar 2017 07:12:52 -0000 On 03/30/17 05:22, Victor Sudakov wrote: > Dear Colleagues, > > Anyone experienced with OpenVPN on FreeBSD? > > What would be the best way to policy route a network into OpenVPN? A > routing decision must be based on the src IP address, not the dst IP > address. > > Imagine an OpenVPN client with 3 interfaces: fxp0 is the outside > interface towards the OpenVPN server, fxp1 is for LAN1 and fxp2 for > LAN2. > > From LAN1, some private networks are reachable through OpenVPN > (tun0), this is done via the regular route commands (pulled from the > OpenVPN server). > > From LAN2, *everything* should be reachable only through OpenVPN. > Which is the best way to accomplish this? > Possibly pf's "route-to" rules: I've used those in the past, but as I've reported, sometimes pf gets stuck and only stopping and starting it again unblocks the network. Other ideas could be jails or setfib, but I've not thinked those out. Maybe other people will come up with smarter ideas. bye av. From owner-freebsd-net@freebsd.org Thu Mar 30 07:46: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 0E83BD25342 for ; Thu, 30 Mar 2017 07:46:21 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 751C7F27 for ; Thu, 30 Mar 2017 07:46:19 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39655453; Thu, 30 Mar 2017 13:41:47 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.14.9/8.14.9) with ESMTP id v2U7kH0Y025192; Thu, 30 Mar 2017 14:46:17 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.14.9/8.14.9/Submit) id v2U7kF06025191; Thu, 30 Mar 2017 14:46:15 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Thu, 30 Mar 2017 14:46:15 +0700 From: Victor Sudakov To: Andrea Venturoli Cc: freebsd-net@freebsd.org Subject: Re: OpenVPN and policy routing Message-ID: <20170330074615.GA25049@admin.sibptus.transneft.ru> References: <20170330032222.GA18053@admin.sibptus.transneft.ru> <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.7.1 (2016-10-04) 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, 30 Mar 2017 07:46:21 -0000 Andrea Venturoli wrote: > > > > Anyone experienced with OpenVPN on FreeBSD? > > > > What would be the best way to policy route a network into OpenVPN? A > > routing decision must be based on the src IP address, not the dst IP > > address. > > > > Imagine an OpenVPN client with 3 interfaces: fxp0 is the outside > > interface towards the OpenVPN server, fxp1 is for LAN1 and fxp2 for > > LAN2. > > > > From LAN1, some private networks are reachable through OpenVPN > > (tun0), this is done via the regular route commands (pulled from the > > OpenVPN server). > > > > From LAN2, *everything* should be reachable only through OpenVPN. > > Which is the best way to accomplish this? > > > > Possibly pf's "route-to" rules: I've used those in the past, but as I've > reported, sometimes pf gets stuck and only stopping and starting it > again unblocks the network. Will "ipfw fwd" do the trick? I could "ipfw fwd" the packets into the tun0 interface, but will OpenVPN understand that? > > Other ideas could be jails or setfib, but I've not thinked those out. > Of course, fxp2 could be placed in a dedicated fib, but I need fxp0 and fxp1 to remain in the main fib, and which fib will tun0 be in ? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-net@freebsd.org Thu Mar 30 14:10: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 E9229D266EA for ; Thu, 30 Mar 2017 14:10:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8BBC8FE for ; Thu, 30 Mar 2017 14:10: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 v2UEAAhf071525 for ; Thu, 30 Mar 2017 14:10:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Thu, 30 Mar 2017 14:10: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: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marka@isc.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 30 Mar 2017 14:10:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #6 from marka@isc.org --- (In reply to Hiren Panchasara from comment #5) My test system died years ago but I believe that it still is a problem. It should be trivial to check. create a IPv6 TCP socket. set IPV6_USE_MIN_MTU=3D1 using setsockopt connect to a data sink write 1400 bytes to the socket in a single operation Examine the packets sent with tcpdump. There should be no fragmented packets being sent as TCP is supposed to take into account MTU information. Mark --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Mar 30 14:32: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 9632ED26E4B for ; Thu, 30 Mar 2017 14:32:37 +0000 (UTC) (envelope-from deborah.perry@datadynamicsit.biz) Received: from mail-qk0-x247.google.com (mail-qk0-x247.google.com [IPv6:2607:f8b0:400d:c09::247]) (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 5E81B10F for ; Thu, 30 Mar 2017 14:32:37 +0000 (UTC) (envelope-from deborah.perry@datadynamicsit.biz) Received: by mail-qk0-x247.google.com with SMTP id p22so17378755qka.4 for ; Thu, 30 Mar 2017 07:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datadynamicsit-biz.20150623.gappssmtp.com; s=20150623; h=mime-version:message-id:date:subject:from:to; bh=20FrDi7sxQ+gZ2a5LqttyqfkbArQiI9BLJ24ayfCA2I=; b=RralqXWvdkBxlE6r0gZwMEjVklPGujcW6RR/gwEQPOsrGfPW9EGb5lX/D4sLH6qZVJ KIevgZrV2sV3vptlBVbs/M3wFhFLBDD2JU8f2IgUOkwjp7tBKYMD73wqXWBKC2seSU3Y 5tMK2mhkGuHSCzBp/KZsiogaHlPFm/oRORkwPhA8tBh06uOUX7v34vEZ7551ROMWECXt yYhkJSUrPW+uD1x1wA1WjZqvrmLGPrtaPbWmM4EYJGj1+aFt15VR9MfYMC/qoKtTmWTV h7nhW+j3IbcrvlyF3MWWlH3mCRNpZvYHpNWvhJPmW/HIUyaqhKSpJkje2kcL2fSgClvr EnLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:message-id:date:subject:from:to; bh=20FrDi7sxQ+gZ2a5LqttyqfkbArQiI9BLJ24ayfCA2I=; b=JBTI4huflamcY12G1SVQp0WsG3juvD0pOtE7N++mkkB1mMDaZhsPN5C+A8xL0QWs9L gpQdeSIWRfU4Bk9T40eDSWXxtN+KagNZKcaQ7BY6W+AwetM9C7zq+hV94TTSTdCHW1aY M3p7m3MlB5fDimPWu6htbucXsLrLjPeUqGufuIidbtZoZNVT+rFx1PLD6eAZE7ShDqnY mRcajb7czNID7cRKW1/2as7VbDhzLp5Tdi2IV8A4kCNER/zdh2cRawB25axgN6GuSwpK CMHcym6BMIl2XYLRXquCaMi8I/1RTIcbRzJo8x05s0TCchw2XjJwBK8R4zQs/QKKE5JV 8Xhg== X-Gm-Message-State: AFeK/H1Q8HdHxLdc8d4alKs1JFzfwZXt/pxdc5t3MfXO9Qv1tUcU/lqqhMcdjaxcGKQBKUz7/HFrF7qKiqZItQ== MIME-Version: 1.0 X-Received: by 10.200.35.250 with SMTP id r55mr3655qtr.39.1490884356389; Thu, 30 Mar 2017 07:32:36 -0700 (PDT) Message-ID: <001a1140289476efb9054bf39004@google.com> Date: Thu, 30 Mar 2017 14:32:36 +0000 Subject: Re:Follow up: Embedded Systems Users List From: deborah.perry@datadynamicsit.biz To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: base64 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: Thu, 30 Mar 2017 14:32:37 -0000 DQoNCkhpLA0KDQpIb3BlIHlvdSBoYWQgYSBjaGFuY2UgdG8gcmV2aWV3IG15IHByZXZpb3VzIGVt YWlsLiBQbGVhc2UgbGV0IG1lIGtub3cgaWYNCnlvdSB3b3VsZCBiZSBpbnRlcmVzdGVkIGluIHJl dmlld2luZyBhIHNhbXBsZSBvZiB5b3VyIHRhcmdldCBhdWRpZW5jZS4NCg0KVGhhbmsgeW91LCBo b3BlIHRvIGhlYXIgZnJvbSB5b3UuDQoNClRoYW5rcyAmIHJlZ2FyZHMsDQoqRGVib3JhaCBQZXJy eSoNCk1hcmtldGluZyBBbmFseXN0DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0K DQoNCg0KDQpIaSwNCg0KQSBxdWljayBmb2xsb3cgdXAgdG8ga25vdyBpZiB5b3Ugd291bGQgYmUg aW50ZXJlc3RlZCBpbiAqRW1iZWRkZWQgU3lzdGVtcyoNClVzZXJzIGxpc3QgZm9yIHlvdXIgbWFy a2V0aW5nIGNhbXBhaWduPw0KDQoqTGlzdCBDb250YWluczoqIE5hbWUsIENvbXBhbnkncyBOYW1l LCBQaG9uZSBOdW1iZXIsIEZheCBOdW1iZXIsIEpvYiBUaXRsZSwNCkVtYWlsIGFkZHJlc3MsIENv bXBsZXRlIE1haWxpbmcgQWRkcmVzcywgU0lDIGNvZGUsIENvbXBhbnkgcmV2ZW51ZSwgc2l6ZSwN CldlYiBhZGRyZXNzIGV0Yy4NCg0KU3BlY2lhbHRpZXM6IFZMU0ksIE1pY3JvIENvbnRyb2xsZXIs IEdlbmVyYWwgY29tcHV0aW5nIHN5c3RlbXMsIE5ldHdvcmtpbmcsDQpQTEMsIFdlYiBEZXZlbG9w bWVudA0KDQoNCg0KTGV0IG1lIGtub3cgeW91ciB0aG91Z2h0cyBvciBwYXNzIG9uIHRoZSBtZXNz YWdlIHRvIHRoZSByaWdodCBwZXJzb24gaW4NCnlvdXIgY29tcGFueS4NCg0KDQpJZiB5b3UgYXJl IGxvb2tpbmcgZm9yIGFueSBvdGhlciB0ZWNobm9sb2dpZXMgcGxlYXNlIGxldCBtZSBrbm93IHlv dXINCmNyaXRlcmlhIEkgd2lsbCBnZXQgYmFjayB0byB5b3Ugd2l0aCB0aGUgc2FtZSB0YXJnZXQu DQoNClRoYW5rcyAmIHJlZ2FyZHMsDQpEZWJvcmFoIFBlcnJ5DQpNYXJrZXRpbmcgQW5hbHlzdA0K DQpJZiB5b3UgZG9u4oCZdCB3YW50IHRvIHJlY2VpdmUgYW55IG1lc3NhZ2UgZnJvbSB1cyB0aGVu IHBsZWFzZSB0eXBlIOKAnE9QVCBPVVTigJ0NCmluIHRoZSBTdWJqZWN0IExpbmUuDQo= From owner-freebsd-net@freebsd.org Thu Mar 30 15:43: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 09775D26C06 for ; Thu, 30 Mar 2017 15:43:33 +0000 (UTC) (envelope-from kongkhemara32@outlook.com) Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253090.outbound.protection.outlook.com [40.92.253.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F4F0812 for ; Thu, 30 Mar 2017 15:43:32 +0000 (UTC) (envelope-from kongkhemara32@outlook.com) Received: from HK2APC01FT026.eop-APC01.prod.protection.outlook.com (10.152.248.51) by HK2APC01HT033.eop-APC01.prod.protection.outlook.com (10.152.249.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1005.5; Thu, 30 Mar 2017 15:43:29 +0000 Received: from SG2PR0201MB2143.apcprd02.prod.outlook.com (10.152.248.53) by HK2APC01FT026.mail.protection.outlook.com (10.152.248.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1005.5 via Frontend Transport; Thu, 30 Mar 2017 15:43:29 +0000 Received: from SG2PR0201MB2143.apcprd02.prod.outlook.com ([10.170.131.12]) by SG2PR0201MB2143.apcprd02.prod.outlook.com ([10.170.131.12]) with mapi id 15.01.0991.022; Thu, 30 Mar 2017 15:43:29 +0000 From: kong khemara To: freebsd-net Subject: !!!! Greetings !!!! Thread-Topic: !!!! Greetings !!!! Thread-Index: AQHSqWxhJQJ9iKDVUUOGLIAkS7yQ6g== Date: Thu, 30 Mar 2017 15:43:29 +0000 Message-ID: Reply-To: "Mr. Kong Khemara" Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:D4668E6C7ED9552FC9C4659A04E1C108AA5E420227BFE8FAE2727BD02DA690B5; UpperCasedChecksum:389DBF37596F704212A0582FA2B7515F365F35DA07D4EDD0A506C333798BBAD5; SizeAsReceived:7757; Count:39 x-ms-exchange-messagesentrepresentingtype: 1 x-microsoft-exchange-diagnostics: 1; HK2APC01HT033; 5:dKdnNTBSVdi6+g0Q+W7VxQemvb8qpUSSzIMFvi1m8wUAMm8vuzdhlWjYg/jRVrtKBblJeDtXHW+4XkzNvXds0TDD/1XynYZeejKwcKnvRUUonAravy+Bs5fVa+rgvE8wqZzF4V9CSNesX2oKDWiXTA==; 24:gFLW/otPZ29mgYM8P350Zvm6TaU1smY97chxdMDJbnLn/rWxbxYnIcHxp9iuSZyyBVfpE4Z/re/aVbLBB9W2P8IW1ocmKazCkS1T47xBvmU=; 7:DH6V0Mwkgjk3OjnhBRQtfcPpXDiDpj+h+Ie1L5Pud7of+ffUKZ0NrCDEMMX9LPaosLoTq6mDQ+iE4J6bXWS8dUiqEFFPaW2Rt0JyojLBLDRjb7rQb0MFsgz23Axx2980znqYMNn+HSMeaphXKaLGxT0ALmIHWd66FmudmhyHNcbFEaXNfvl+srZyjGQBeYxO8fpEolVy+v2g91F9/XJ8z9LlfomuEbshHBC+QYUy6YtACvfN94k3a3oAmJ1Acs/MbZWTK5r788PU14FTDvm1rM28+ZfwU+++rhFOb2Xnb5NaqysGeLAzulDkuMcjKaOg x-incomingheadercount: 39 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HK2APC01HT033; H:SG2PR0201MB2143.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 792d9320-745d-4a3d-350a-08d4778381d9 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:HK2APC01HT033; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HK2APC01HT033; BCL:0; PCL:0; RULEID:; SRVR:HK2APC01HT033; x-forefront-prvs: 02622CEF0A spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 15:43:29.8453 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT033 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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: Thu, 30 Mar 2017 15:43:33 -0000 SGVsbG8sDQpJIGFtIEJhcnIgS29uZyBLaGVtYXJhLCBJIGh1bWJseSBhc2sgaWYgeW91IGFyZSBy ZWxhdGVkIHRvIG15IGNsaWVudCB3aG8gZGllZCBjb3VwbGUgb2YNCnllYXJzIGFnbyBpbiBhIGNh ciBhY2NpZGVudCBoZXJlIGluIG15IGNvdW50cnkgQ2FtYm9kaWEuIEkgd2lzaCB0byBhbHNvIGlu cXVpcmUgaWYNCml0IGlzIHBvc3NpYmxlIHRvIGhhdmUgZGlmZmVyZW50IGZhbWlsaWVzIHdpdGgg dGhlIHNhbWUgbGFzdCBuYW1lIGFzIHlvdXJzIGJ5IGNvaW5jaWRlbmNlDQp3aG8gZG8gbm90IHNo YXJlIHRoZSBzYW1lIGNvbW1vbiByb290cz8gS2luZGx5IGdldCBiYWNrIHRvIG1lIGlmIHlvdXIg ZW1haWwgaXMgc3RpbGwNClZhbGlkIHRvIGVuYWJsZSBtZSBnaXZlIHlvdSB0aGUgZGV0YWlscyBv ZiBteSBtZXNzYWdlIG9yIG1ha2UgaGVhZHdheSBpbiBteSBzZWFyY2guDQpSZWdhcmRzLA0KS29u ZyBLaGVtYXJhDQo= From owner-freebsd-net@freebsd.org Thu Mar 30 16:25: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 96183D26956 for ; Thu, 30 Mar 2017 16:25:15 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp205.alice.it (smtp205.alice.it [82.57.200.101]) by mx1.freebsd.org (Postfix) with ESMTP id 2D786897 for ; Thu, 30 Mar 2017 16:25:14 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (82.52.25.226) by smtp205.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 588F425B0EAC682B; Thu, 30 Mar 2017 18:24:50 +0200 Received: from guardian.ventu (bane.local.netfence.it [10.1.2.15]) (authenticated bits=0) by soth.ventu (8.15.2/8.15.2) with ESMTPSA id v2UGOKXk051464 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 30 Mar 2017 18:24:26 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host bane.local.netfence.it [10.1.2.15] claimed to be guardian.ventu Subject: Re: OpenVPN and policy routing To: Victor Sudakov Cc: freebsd-net@freebsd.org References: <20170330032222.GA18053@admin.sibptus.transneft.ru> <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> <20170330074615.GA25049@admin.sibptus.transneft.ru> From: Andrea Venturoli Message-ID: Date: Thu, 30 Mar 2017 18:24:17 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170330074615.GA25049@admin.sibptus.transneft.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.1.2.13 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, 30 Mar 2017 16:25:15 -0000 On 03/30/17 09:46, Victor Sudakov wrote: > Will "ipfw fwd" do the trick? I could "ipfw fwd" the packets into the > tun0 interface, but will OpenVPN understand that? Never tried this, sorry. bye av. From owner-freebsd-net@freebsd.org Thu Mar 30 17:04:51 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 03E2FD26EE8 for ; Thu, 30 Mar 2017 17:04:51 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B29DCD2 for ; Thu, 30 Mar 2017 17:04:50 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mail-qk0-x236.google.com with SMTP id d10so45800558qke.1 for ; Thu, 30 Mar 2017 10:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X1a8JP9M5R9BIPuZB1AaYJieSTRueap9AyLIafPj6g4=; b=u4JTJXo8Cd5nz8TAIb/dUBK03+zdfbRm5UTCVLrFle2Tx46Su2DpkXPm2Hp4ylIieU 2kTjZjCm9YU6sGGSjt7PrgVblSBjnUZZAFUSU6TxlRFKjVMg6MX+0Yh2PX2C5A9ouHYl zIpVIcxpsVZr8ZhbGFhBCdtfSQJVCF2S/Bh2gzmLhk6hQQa04sWxxIRSCq3FV2R74p52 IQjZhIxyuTHzWcGUIr2w6egKeRdg9cYRIoA/3/O6gL7OEqTtI72zuNyZT5nD3vcv2akN lNDQCqRI4y16R0HsniVgGMCxKx5chomxlnO5/NIzpIMSfJfM4btKhh6TeQac6ctTj+GK F0uA== 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=X1a8JP9M5R9BIPuZB1AaYJieSTRueap9AyLIafPj6g4=; b=B90q6cdUVnR6cCFG9NmCXzliUXt3ATikNoWEr7fbPuQ7dRyjhiLwHg6Lq6MHJGK2k/ n6JMtkAvjsDvrMMwidVhYdPnatYjg4hodOi3+9k6uEaKlC7oMyMYq6Qc8md751Vooenn 0CPjqYcpd5628pBiJ9yMdFNbV/wE8pFz0ERUqEO2FoWuXXB4SbCNOlcPFWkPvwOxGJR2 8MdcLbKr3WrO0usKgIrJ99RiMOMqwEphQEY3EzUJUUo6KHXckjYRKmDhu3iv/9JrlRCr AVfo4lNHHWfyZpJ3lU2psNoknUe5kUdBfA0+mgIsVgcZxk6h/sCprgimudFZO6hRBkBy K+mQ== X-Gm-Message-State: AFeK/H2tYedNfneTnrUC5FxbXqZ2z3NPHrTVGMBLwhTRAWJxNwTtlmuQ9TyGzQpEhg5rKZ/KQjh2ObuPVx4HUmfx X-Received: by 10.55.155.141 with SMTP id d135mr743418qke.75.1490893489451; Thu, 30 Mar 2017 10:04:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.39.182 with HTTP; Thu, 30 Mar 2017 10:04:49 -0700 (PDT) In-Reply-To: References: <20170330032222.GA18053@admin.sibptus.transneft.ru> <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> <20170330074615.GA25049@admin.sibptus.transneft.ru> From: Michael Sierchio Date: Thu, 30 Mar 2017 10:04:49 -0700 Message-ID: Subject: Re: OpenVPN and policy routing To: Andrea Venturoli Cc: Victor Sudakov , 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: Thu, 30 Mar 2017 17:04:51 -0000 I use different FIBs in the ipfw ruleset to accomplish policy based routing, including via a tun interface. - M On Thu, Mar 30, 2017 at 9:24 AM, Andrea Venturoli wrote: > On 03/30/17 09:46, Victor Sudakov wrote: > > Will "ipfw fwd" do the trick? I could "ipfw fwd" the packets into the >> tun0 interface, but will OpenVPN understand that? >> > > Never tried this, sorry. > > bye > av. > > _______________________________________________ > 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 "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent person requires only two thousand five hundred." - The Mah=C4=81bh=C4=81rata From owner-freebsd-net@freebsd.org Thu Mar 30 18:21: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 0CFC7D26F1D for ; Thu, 30 Mar 2017 18:21: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 F0DE5C09 for ; Thu, 30 Mar 2017 18:21: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 v2UIL8n2020072 for ; Thu, 30 Mar 2017 18:21:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Thu, 30 Mar 2017 18:21: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: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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, 30 Mar 2017 18:21:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #7 from Andrey V. Elsukov --- (In reply to marka from comment #6) > (In reply to Hiren Panchasara from comment #5) > My test system died years ago but I believe that it still is a problem. >=20 > It should be trivial to check. >=20 > create a IPv6 TCP socket. > set IPV6_USE_MIN_MTU=3D1 using setsockopt > connect to a data sink > write 1400 bytes to the socket in a single operation >=20 > Examine the packets sent with tcpdump. There should be no fragmented > packets being sent as TCP is supposed to take into account MTU > information. According to RFC3542 this is what the kernel should do - do IP fragmentatio= n as application requested. https://tools.ietf.org/html/rfc3542#section-11.1 "If the packet is larger than the minimum MTU and this feature has been ena= bled the IP layer will fragment to the minimum MTU." --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Mar 30 18:28:42 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 046AAD26237 for ; Thu, 30 Mar 2017 18:28:42 +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 E8646131 for ; Thu, 30 Mar 2017 18:28: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 v2UISfQ9038287 for ; Thu, 30 Mar 2017 18:28:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Thu, 30 Mar 2017 18:28:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 30 Mar 2017 18:28:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #8 from Andrey V. Elsukov --- And this is what always pisses me off. If we have 10/50/100G link with 9k M= TU, bind always does IPv6 fragmentation due to this option. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Mar 30 20:46: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 057E2D264E5 for ; Thu, 30 Mar 2017 20:46: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 E9231A39 for ; Thu, 30 Mar 2017 20:46:14 +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 v2UKkEY2086428 for ; Thu, 30 Mar 2017 20:46:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Thu, 30 Mar 2017 20:46:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marka@isc.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 30 Mar 2017 20:46:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #9 from marka@isc.org --- (In reply to Andrey V. Elsukov from comment #7) RFC 6691 o As a result, when the effective MTU of an interface varies, TCP SHOULD use the smallest effective MTU of the interface to calculate the value to advertise in the MSS option. IPV6_USE_MIN_MTU=3D1 changes the effective MTU of the interface for this socket. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Mar 30 20:46: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 9F1AED26549 for ; Thu, 30 Mar 2017 20:46: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 8EEC2AE2 for ; Thu, 30 Mar 2017 20:46: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 v2UKkfwK087106 for ; Thu, 30 Mar 2017 20:46:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Thu, 30 Mar 2017 20:46:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marka@isc.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 30 Mar 2017 20:46:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #10 from marka@isc.org --- (In reply to Andrey V. Elsukov from comment #8) So what! Most DNS/TCP response is a few of packets. What does it matter if it is the 3 or 4 packets. What matters is avoiding PMTUD as it is NOT reliable. Setting the IPv6 packet size to 1280 avoids triggering PMTUD issues. Limiting the packet size avoids timeout and retransmissions due to PTB not been generated due to rate limiting or being lost due to stupid load balancers and firewalls that drop ICMP. Go put your validating resolvers behind a IPv6 in IPv4 link then come back and say this is not needed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 01:02: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 59DDDD234C9 for ; Fri, 31 Mar 2017 01:02:36 +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 43773B3E for ; Fri, 31 Mar 2017 01:02:36 +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 v2V12Zw5068514 for ; Fri, 31 Mar 2017 01:02:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 01:02:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 31 Mar 2017 01:02:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #11 from Andrey V. Elsukov --- (In reply to marka from comment #9) > (In reply to Andrey V. Elsukov from comment #7) > RFC 6691 >=20 > o As a result, when the effective MTU of an interface varies, TCP > SHOULD use the smallest effective MTU of the interface to calculate > the value to advertise in the MSS option. >=20 > IPV6_USE_MIN_MTU=3D1 changes the effective MTU of the interface for this > socket. This is socket option and it doesn't change interface's MTU value and doesn= 't affect MSS value, as I see. It just instructs the kernel explicitly do IPv6 fragmentation exactly as described in the RFC3542. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 01:10: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 EB2A1D23625 for ; Fri, 31 Mar 2017 01:10: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 DADEADEC for ; Fri, 31 Mar 2017 01:10: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 v2V1AbFi082255 for ; Fri, 31 Mar 2017 01:10:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 01:10:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 31 Mar 2017 01:10:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #12 from Andrey V. Elsukov --- (In reply to marka from comment #10) > (In reply to Andrey V. Elsukov from comment #8) > So what! Most DNS/TCP response is a few of packets. What does it > matter if it is the 3 or 4 packets. Zone transfers need a lot of such few packets. > What matters is avoiding PMTUD as it is NOT reliable. Setting the > IPv6 packet size to 1280 avoids triggering PMTUD issues. Limiting > the packet size avoids timeout and retransmissions due to PTB not > been generated due to rate limiting or being lost due to stupid > load balancers and firewalls that drop ICMP. >=20 > Go put your validating resolvers behind a IPv6 in IPv4 link then > come back and say this is not needed. When I build the network in the DC, I know better what MTU can be used in my network. And forcing 1280 bytes size for the network, where 9k is the defau= lt MTU is at least strange in the 2017. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 02:36:18 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 426EDD26A40 for ; Fri, 31 Mar 2017 02:36:18 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id ABDC2DAD for ; Fri, 31 Mar 2017 02:36:16 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39656343; Fri, 31 Mar 2017 08:31:44 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.14.9/8.14.9) with ESMTP id v2V2aE5o037695; Fri, 31 Mar 2017 09:36:14 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.14.9/8.14.9/Submit) id v2V2aB9P037693; Fri, 31 Mar 2017 09:36:11 +0700 (KRAT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Fri, 31 Mar 2017 09:36:11 +0700 From: Victor Sudakov To: Michael Sierchio Cc: Andrea Venturoli , freebsd-net@freebsd.org Subject: Re: OpenVPN and policy routing Message-ID: <20170331023611.GA37113@admin.sibptus.transneft.ru> References: <20170330032222.GA18053@admin.sibptus.transneft.ru> <81f24563-1abb-e804-d2a3-7fa772a0c78d@netfence.it> <20170330074615.GA25049@admin.sibptus.transneft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.7.1 (2016-10-04) 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, 31 Mar 2017 02:36:18 -0000 Michael Sierchio wrote: > I use different FIBs in the ipfw ruleset to accomplish policy based > routing, including via a tun interface. I've just found out that even when tun0 is in fib 0, you can use it as a gateway from a different fib, and it works: root@km:~ # netstat -rn -4 -F1 Routing tables (fib: 1) Internet: Destination Gateway Flags Netif Expire default 192.168.154.5 UGS tun0 95.170.158.128/27 link#2 U rl1 127.0.0.1 link#4 UH lo0 192.168.11.0/24 link#3 U ste0 192.168.14.0/24 link#1 U rl0 192.168.154.5 link#5 UH tun0 root@km:~ # root@km:~ # ifconfig tun0 tun0: flags=8051 metric 0 mtu 1500 options=80000 inet6 fe80::2e0:4cff:feb0:6dd4%tun0 prefixlen 64 scopeid 0x5 inet 192.168.154.6 --> 192.168.154.5 netmask 0xffffffff nd6 options=21 Opened by PID 717 root@km:~ # I.e. all directly connected networks are available from all fibs, not just the default one. It probably depends on the net.add_addr_allfibs systcl setting. So, my task would be best solved by "ifconfig fxp2 fib 1". Thanks to all who replied. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-net@freebsd.org Fri Mar 31 02: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 2DE2AD26B14 for ; Fri, 31 Mar 2017 02: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 1D056EC3 for ; Fri, 31 Mar 2017 02: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 v2V2dE7e002827 for ; Fri, 31 Mar 2017 02:39:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 02:39:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: 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: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: short_desc keywords bug_status 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, 31 Mar 2017 02:39:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[socket] [patch] |socket: IPV6_USE_MIN_MTU |IPV6_USE_MIN_MTU and TCP is |and TCP is broken |broken | Keywords| |needs-qa, patch Status|In Progress |Open Flags| |mfc-stable10?, | |mfc-stable11? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 02:40: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 123EED26BBB for ; Fri, 31 Mar 2017 02:40:13 +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 0148FFB8 for ; Fri, 31 Mar 2017 02:40:13 +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 v2V2eC4s004422 for ; Fri, 31 Mar 2017 02:40:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 02:40: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: 8.3-STABLE X-Bugzilla-Keywords: 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: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: attachments.ispatch attachments.isobsolete attachments.mimetype 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, 31 Mar 2017 02:40:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #129461|0 |1 is patch| | Attachment #129461|0 |1 is obsolete| | Attachment #129461|application/octet-stream |text/plain mime type| | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 02:40:30 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 44B64D26C44 for ; Fri, 31 Mar 2017 02:40:30 +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 3405785 for ; Fri, 31 Mar 2017 02:40:30 +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 v2V2eTWr004896 for ; Fri, 31 Mar 2017 02:40:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 02:40:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: 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: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: attachments.mimetype attachments.ispatch 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, 31 Mar 2017 02:40:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #129462|application/octet-stream |text/plain mime type| | Attachment #129462|0 |1 is patch| | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 02:50:38 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 04DD9D23117 for ; Fri, 31 Mar 2017 02:50:38 +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 E85808F7 for ; Fri, 31 Mar 2017 02:50: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 v2V2obr8028334 for ; Fri, 31 Mar 2017 02:50:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken Date: Fri, 31 Mar 2017 02:50: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: 8.3-STABLE X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marka@isc.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@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, 31 Mar 2017 02:50:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444 --- Comment #13 from marka@isc.org --- (In reply to Andrey V. Elsukov from comment #11) Read the words "effective MTU" that I quoted. The "effective MTU" is 1280 = with this option set. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 02:57: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 ACF57D23690 for ; Fri, 31 Mar 2017 02:57: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 983C8FE9 for ; Fri, 31 Mar 2017 02:57: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 v2V2v5Ol048130 for ; Fri, 31 Mar 2017 02:57:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Fri, 31 Mar 2017 02:57:05 +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-STABLE X-Bugzilla-Keywords: crash, 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: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? 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, 31 Mar 2017 02:57:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #43 from Kubilay Kocak --- @All For issues where the 'described problem' and the 'thing(s) that need t= o be changed' are not one and the same, to retain all history/contextual informa= tion and not cause confusion (renaming titles, etc), the correct process is as follows: 1) Leave the 'original description/report of symptoms' issues 'as is'. 2) Create a blocking (depends on) issue for each area/component within Free= BSD that requires a change/fix (em, igb, etc). Alternatively, if multiple areas require fixing/changes but these will be resolved by a single person or maintainer (the assignee), then a single blocking issue is fine. Notes: The assignee of the blocked (parent) issue (ie 'the original report') can be changed to the person(s) responsible (assignee) to the blocking (sub) issue= .=20 Alternatively, the assignee of the parent issue can also be a person who wa= nts to/will 'see it through', coordinating and updating issue metadata until all sub-tasks are closed, including any relevant MFC's and documentation tasks. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 09:37:58 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 250BED268E4 for ; Fri, 31 Mar 2017 09:37:58 +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 139EB978 for ; Fri, 31 Mar 2017 09:37:58 +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 v2V9btAF070232 for ; Fri, 31 Mar 2017 09:37:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Fri, 31 Mar 2017 09:37:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rwatson@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? 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, 31 Mar 2017 09:37:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #44 from Robert Watson --- It's probably best to be clear: the bugs being described by various reporte= rs over the years are *different* (and likely entirely *independent*) bugs that happen to have the same visible symptom as a result of being detected by the same check. Putting these differences problems in the same open bug report, and keeping it open, is very much like putting all kernel panics in the same bug report because they share the word "panic" and involve a crash (which is pretty much what is happening here). As a result, there's a bug report that describes many different problems fixed in many different ways at many different times, and is never closed. Not only that, but prior debugging may shed no light on more recent problems, and could in fact obscure understand= ing, since it's not progress being made on one bug, but observations of several likely independent problems. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 17:25:06 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 B6659D27AA3 for ; Fri, 31 Mar 2017 17:25:06 +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 A50C1B40 for ; Fri, 31 Mar 2017 17:25: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 v2VHOxpo003092 for ; Fri, 31 Mar 2017 17:25:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Fri, 31 Mar 2017 17:25:00 +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-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mandrews@bit0.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? 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, 31 Mar 2017 17:25:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #45 from Mike Andrews --- As the guy that filed the original bug report almost 7 years ago, I'd tend = to agree with Robert Watson here. I'll see if Bugzilla will let me close it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 17:25: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 D09CDD27AB9 for ; Fri, 31 Mar 2017 17:25:14 +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 BEF82BAE for ; Fri, 31 Mar 2017 17:25:14 +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 v2VHPEos003449 for ; Fri, 31 Mar 2017 17:25:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Fri, 31 Mar 2017 17:25:14 +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-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mandrews@bit0.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 31 Mar 2017 17:25:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 Mike Andrews changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Open |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 18:14:52 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 71321D22A1D for ; Fri, 31 Mar 2017 18:14:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5FBB1CFF for ; Fri, 31 Mar 2017 18:14:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2VIEoUS002021 for ; Fri, 31 Mar 2017 18:14:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Fri, 31 Mar 2017 18:14:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rwatson@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? 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, 31 Mar 2017 18:14:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #46 from Robert Watson --- I've opened a new #218270 for the sbsndptr() crash. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Mar 31 18:40: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 98A32D260BF for ; Fri, 31 Mar 2017 18:40:53 +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 88761BA4 for ; Fri, 31 Mar 2017 18:40:53 +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 v2VIeoqG092599 for ; Fri, 31 Mar 2017 18:40:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218270] panic: sbsndptr: sockbuf (...) and mbuf (...) clashing Date: Fri, 31 Mar 2017 18:40: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: 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: Fri, 31 Mar 2017 18:40:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218270 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 Sat Apr 1 07:21:26 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 88C18D29911 for ; Sat, 1 Apr 2017 07:21:26 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 5BA2ED7E for ; Sat, 1 Apr 2017 07:21:26 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 2534820945; Sat, 1 Apr 2017 07:21:26 +0000 (UTC) Date: Sat, 1 Apr 2017 07:21:26 +0000 To: freebsd-net@freebsd.org From: "ale (Alex Dupre)" Reply-to: D9270+325+bbd470fd257eef1b@reviews.freebsd.org Subject: [Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE Message-ID: <1d181c75b0b80f7235a4dca58490b3a2@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D9270: Add support for user-supplied Host-Uniq tag in Netgraph PPPoE X-Herald-Rules: <28>, <8> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTZkNjQzYWQxOGQ3MGJlZTIzOGZhZmQ4NGNmIFjfVPY= MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2017 07:21:26 -0000 YWxlIGFkZGVkIGEgY29tbWVudC4KVGhpcyByZXZpc2lvbiBub3cgcmVxdWlyZXMgcmV2aWV3IHRv IHByb2NlZWQuCgoKICBXaG8gaXMgZ29pbmcgdG8gY29tbWl0IGl0IGluIHRoZSBzcmMgdHJlZSBh bmQgbWVyZ2UgaW4gMTEgYnJhbmNoPwoKUkVQT1NJVE9SWQogIHJTIEZyZWVCU0Qgc3JjIHJlcG9z aXRvcnkKClJFVklTSU9OIERFVEFJTAogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9EOTI3 MAoKRU1BSUwgUFJFRkVSRU5DRVMKICBodHRwczovL3Jldmlld3MuZnJlZWJzZC5vcmcvc2V0dGlu Z3MvcGFuZWwvZW1haWxwcmVmZXJlbmNlcy8KClRvOiBhbGUsICNtYW5wYWdlcywgd2Jsb2NrLCAj bmV0d29yaywganVsaWFuLCBtYXYsIGFkcmlhbgpDYzogd2Jsb2NrLCBtYXYsIHBvb2xyb29tX2dt YWlsLmNvbSwgbWFuZHJlZSwgaW1wLCBmcmVlYnNkLW5ldC1saXN0Cg== From owner-freebsd-net@freebsd.org Sat Apr 1 14:44: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 A8642D28B1A for ; Sat, 1 Apr 2017 14:44:48 +0000 (UTC) (envelope-from java33daemon@gmail.com) Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::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 779AE85B for ; Sat, 1 Apr 2017 14:44:48 +0000 (UTC) (envelope-from java33daemon@gmail.com) Received: by mail-vk0-x232.google.com with SMTP id z204so109640490vkd.1 for ; Sat, 01 Apr 2017 07:44:48 -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=JKxJqTaj+DiwGqn2UnO5rtHD6GKh5J5vrsoaTklhme0=; b=fXsm1JprUqwUJoyi2OGPoXQfV88IAB0UvSgtunTF1TZnU0DLT45ESFCpoC5m2PgfTu B/rxxUFeGEhF0ZDUNYdJOYhqu0Dw/ogRkuFRBPJ0vXDi7qFr3Rqm4FSSacHNpAvC09wq p72DhCLhi+7U0QGcIa9aRhl79diQ8S6wS6dybPZSrTnv+CgQTwMFRuN4yZ1Mre2B09tg c+BIgvUOayRGgLWDnmiYBEDv9aV1OXRkvppHHF1SvNi2xcrfqedbg2miS+19nrb484mV ILVcRGVuNh6Gim4HitPUWWjAvVSV+s2UuK3iQeFBkeKBzEO/3QPDyc1Esq1yud5XruQo OTng== 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=JKxJqTaj+DiwGqn2UnO5rtHD6GKh5J5vrsoaTklhme0=; b=Nzrk/Fha8/i7LHsmgvkHKs243iGWOBStJw7GXUoX1oyKH5XD9NnkXruraHm8/q7t2o JNh6IOhkBGg6HYsRBDUGK978qCSw/VAuYkaniCvwWR6oxRc+sSwLEYl/kirmKLkmfZL9 OIGco/LzpuxBsPz6jFpZMqBAnXRtvdJv5GdrHqGLQbyZU0Ody5z4X7wGKwh6Jzb2FLip KZ1uyT1Oy32puT7iwkPultbBJjWRFtPNchRT0JRpC5uPC8VbZNVL95xXuFXZ9stXWs3k jL9istWdshJ5dU4g7CvttLQaLyfeBnT9j8FJ7F2moop8olv3pSLMBgSQvuOjetJjBYQz DQNw== X-Gm-Message-State: AFeK/H2J1rOI5nvzO/pBm0S1WcT2DbChA9p/Nn7SFaJv7Q4ZsdqXL//rdxDuVJ0ttU09W1KG79mNzP4RiKGrHg== X-Received: by 10.31.192.11 with SMTP id q11mr3147556vkf.13.1491057887222; Sat, 01 Apr 2017 07:44:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.167.129 with HTTP; Sat, 1 Apr 2017 07:44:46 -0700 (PDT) From: kdev code Date: Sat, 1 Apr 2017 21:44:46 +0700 Message-ID: Subject: MPLS protocol on FreeBSD To: freebsd-net@freebsd.org 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, 01 Apr 2017 14:44:48 -0000 I search how to enable MPLS on FreeBSD but I found it seem not yet implement as follow link https://wiki.freebsd.org/Networking even though it has been implemented in 2008 as follow link https://wiki.freebsd.org/RyanFrench/Implementation%20of%20MPLS%20in%20FreeBSD my question is - What MPLS status on FreeBSD ? - If MPLS not yet implement.How should start implement it on FreeBSD kernel ? Best Regards. From owner-freebsd-net@freebsd.org Sat Apr 1 15:46: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 831CAD29D57 for ; Sat, 1 Apr 2017 15:46:44 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AC1AE6E for ; Sat, 1 Apr 2017 15:46:44 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id t189so19346839wmt.1 for ; Sat, 01 Apr 2017 08:46:44 -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=DcB0P9XJkkg6wWqltUOK6o0O3qEoHpeRxuYKTMsH+tY=; b=Ac8O/HvE18XktZbDJ0EAVNwZph+Fvv2VfO49I7aE4fd/q/P/nkFz7FfxLRATJ+Ar17 eL24M5oB+7cUCBDwAiU98vYHvqSbWfdagiSm5IF8CzQFrnNXlCMDJaNzRi8afQUG1KKt kZyYMAMIu7f8wEN+dVZv6LhO/pnfwhYpDzHuFkqoKWz/0JuonFSXkvaNc66V1MS+QHmx jrux+yN6IKQrODWT8WU8fykUUfOcr8R45Cx9deZLK7XjYtNaHiJOvY01A7t/F3UNv3Ou iED+d1tBemFiReL8rpb/Bb2Ndc+DxkcOJ1rG/kxb0H8zLGnzp7sw4P/Vd4LmjDwWQrf7 TwMA== 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=DcB0P9XJkkg6wWqltUOK6o0O3qEoHpeRxuYKTMsH+tY=; b=efoAJcIyH7oqepOjd/lWzPFx9oNaz5RO/DYlDeZR3PEy9k9smxUUC+awijfG4veCgA qjlsPDdnOuBKsXrBvotWXE6wP2iAbAzKuGIQfdqsBR/vSZ2gc01VcNxWZ0E73N+jOlXd 3CWnUO0jhPC1sVG+tBKqxr4gS05L1WiWyEhBxCVScuRo/HEOGLL6ZCnUNyHccw3Ikz7r 5kDZjHRsPaAloH7Q64mDipTrqb/3VYYkAgHpXcf0wUR2NIHA0zx/zH8N4f80PMAS1bsq xkDkWVRzkA6iDgXMjWfauASSpdpi0LZTWtZL+svA5eNRHw25wgFGRH+zWLJNDHSknwBp OULg== X-Gm-Message-State: AFeK/H3A3j1quEjHK54FOIrx6YU6pudjDo6jI8Cg2SAnKamRugO0YNN0MLGqBkaYbmIysNjfXpuSFyxWkEd4rw== X-Received: by 10.28.90.66 with SMTP id o63mr2922000wmb.97.1491061602405; Sat, 01 Apr 2017 08:46:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.173.45 with HTTP; Sat, 1 Apr 2017 08:46:41 -0700 (PDT) Received: by 10.223.173.45 with HTTP; Sat, 1 Apr 2017 08:46:41 -0700 (PDT) In-Reply-To: References: From: Sami Halabi Date: Sat, 1 Apr 2017 18:46:41 +0300 Message-ID: Subject: Re: MPLS protocol on FreeBSD To: kdev code 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: Sat, 01 Apr 2017 15:46:44 -0000 Hi, I Asked several times about getting mpls into freebsd but seems its not gonna happen. Alexander Chernikov work was not completed (not i know of otherwise) and even his site for that matter seems down for long time. Sami =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 1 =D7=91=D7=90=D7=A4=D7=A8=D7=B3 2017 = 05:45 PM,=E2=80=8F "kdev code" =D7=9B=D7=AA=D7=91: I search how to enable MPLS on FreeBSD but I found it seem not yet implement as follow link https://wiki.freebsd.org/Networking even though it has been implemented in 2008 as follow link https://wiki.freebsd.org/RyanFrench/Implementation% 20of%20MPLS%20in%20FreeBSD my question is - What MPLS status on FreeBSD ? - If MPLS not yet implement.How should start implement it on FreeBSD kernel ? Best Regards. _______________________________________________ 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"