From owner-freebsd-net@FreeBSD.ORG Sun Sep 9 12:56:40 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40A4F1065672 for ; Sun, 9 Sep 2012 12:56:40 +0000 (UTC) (envelope-from september@autotrader.com) Received: from nm9.access.bullet.mail.mud.yahoo.com (nm9.access.bullet.mail.mud.yahoo.com [66.94.237.210]) by mx1.freebsd.org (Postfix) with SMTP id E4EAD8FC0A for ; Sun, 9 Sep 2012 12:56:39 +0000 (UTC) Received: from [66.94.237.197] by nm9.access.bullet.mail.mud.yahoo.com with NNFMP; 09 Sep 2012 12:54:35 -0000 Received: from [98.137.12.179] by tm8.access.bullet.mail.mud.yahoo.com with NNFMP; 09 Sep 2012 12:54:35 -0000 Received: from [127.0.0.1] by smtp104.biz.mail.gq1.yahoo.com with NNFMP; 09 Sep 2012 12:54:35 -0000 X-Yahoo-Newman-Id: 281879.12330.bm@smtp104.biz.mail.gq1.yahoo.com Message-ID: <281879.12330.bm@smtp104.biz.mail.gq1.yahoo.com> X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: esKKEwAVM1mSnp83qoAlcm0u782XyypQyvAbXVmCpWNyB2l R5J5iTAo.Pw2h7VrC72Xq6nRnhPl3QG6LMTazXGG0ZpYJOayztQPvslnn9sh pvoPJINK7..R.To4ifpI.fQ4WZ1y8nhJLiRdfVkcgJf1aOCg7CbOYAQa3P07 LKgvyhfAtIuT1RK4GHkFfK8mKTaIKnnmSHvEgT4c23NLnBgYWi_n3coV0s4n .BwBBwcZrHJqGYIBuBI5_wrLwOwZurMYH6v0WnRI5SUXgLUmiW3HOUwg5eyz se.vNQOYjg0vMh2121GpXtnH1b0GCgi9ECymvhJ5FnvHB2haxhb2ikEpM0yG 0rnbJ52iHGzphM.3WY_Dwk1O7gov7pT_Hyw8sxDEa1M9tjuws44HD1YJ_D1x GmPffXshk79pfwlrkJLO8hspfY_.ZZqHRFucrJCspUF_kIA.C284ibp5Kv0k 31V7ohsjexTogAZ53DLPCBbIP4eDi.FmkTftuy_WxAP4kqmV_gMMj58MtJJH dPGrsW1BRh3703zEaI9b_Yc7UfeA0sOccjNghrU5OEJJAYhdGROQYsMhoWm0 qbFjVjB8kjaT5uBgGvkgcTbprmGDcp5WWBFraeoEGvco7WDHWHZlKdRC5mgg 9Cdvr86SJAykLj5ctAopj5psCrPD7ScpCmcv6lhiMg5DLcNvvfskV.srjiV6 JPDyhJ1mVA.L61GpABv_.zBvq1rrIBI6eJMo9rJvl_bnvd8NgF3i1KgIXPzC o90CvZoj0a4AcVLv0nGKiC9y1QSSohPcnA4B5EloVRJHfI4zwpWtiMvh2pHc dHdxBE.ycLTCGcQ4QfYg61KjK390Mm_hC9qt8zgmICidkPSVpZ2CrQQMqF6n fXAuyc5B2LG3aO.g.LbcGzKZAqWHf0QYV5syyJ4FeDOimhThqDkoUBdqJ6v6 YXidR3C7K1n9anEGtGdmXSCl9BLQ9s853kkBmzgjlwfeKhkuZYV7kUZR8TVt nBi2P8kvr6Iu5K6WEDglQqAMmva6grGajStjnncJvUCHV4Wr7Bw5GdTxzqCH lDQINtM_AK1ETwq4wZOpELDV3UjDIzur5hsg8AF1Pr.s3GmfieyKN6oqNP5p OtqxY29kO6z818WFb6jeVLKOZKiRmx4VjV9JqNQGYjhfXgaGC6roDtkobgyK 4C8yMB97CUqGDmWR5XnWkaWHsIGEFqTriVtzIwkBuXw9UFa0- X-Yahoo-SMTP: JOr.Rf2swBAn86WG9uQMSCNdXvE- Received: from [192.168.2.110] (september@172.190.126.188 with login) by smtp104.biz.mail.gq1.yahoo.com with SMTP; 09 Sep 2012 05:54:29 -0700 PDT MIME-Version: 1.0 To: freebsd-net@freebsd.org From: "AutoTrader" Date: Sun, 09 Sep 2012 05:55:20 -0700 X-Mailer: TurboMailer 2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 2000 Jeep Wrangler SPORT/TJ (4.0L I6 SFI) $5,795 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: september@autotrader.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 12:56:40 -0000 = To be sure our email reaches your inbox, please add AutoTrader.com to yo= ur address book. = = = = = = = = = Vehicle Information = = Photos (17) = = Used 2000 Jeep Wrangler SPORT/TJ 4x4 $5,795 = = = = = Seller Information = = Email This Seller (210) 468-0398 = = = (function($, window, undefined) { $(function() { atc.create(atcui.compo= nent.overlay, $.extend({ id: "more_info_0", jsfId: "j_id610291288_3_543835b= 2-j_id870071934_54101788-j_id1968262331_54101245-j_id1067736250_54101263-0-= j_id443940090_7f5bd996-more_info_0", classNames:"", autoOpen:false, resizab= le:false, modal: true, title:"", draggable: false, url: "", width:0, gridWi= dth:16, printable: false }, {})).init(); }); })(jQuery, window); (functi= on($, window, undefined) { $(function() { atc.create(atcui.component.overla= y, $.extend({ id: "more_info_1", jsfId: "j_id610291288_3_543835b2-j_id87007= 1934_54101788-j_id1968262331_54101245-j_id1067736250_54101263-1-j_id4439400= 90_7f5bd996-more_info_1", classNames:"", autoOpen:false, resizable:false, m= odal: true, title:"", draggable: false, url: "", width:0, gridWidth:16, pri= ntable: false }, {})).init(); }); })(jQuery, window); = = = = = = Primary information about this vehicle: = = Price $5,795 = Mileage 121,471 = Body Style Sport Utility = Transmission Manual = Engine 6 Cylinder = Drive Type 4 wheel drive = Fuel Type Gasoline = Doors Two Door = = Vehicle Description = Seller's Description and Comments: = 2000 JEEP WRANGLER SPORT/TJ 4X4 IN VERY NICE CONDITION. ORIGINAL MILES ,= ABOUT 90% WAS HIGHWAY USE. 4.0 6CYL. ENGINE, 5 SPEED TRANSMISSION.CRUISE C= ONTROL AND AIR CONDITIONING. THE NV3550 TRANSMISSION WAS JUST REBUILT INCLU= DING NEW CLUTCH AND THROWOUT BEARING. UPGRADES ARE AIRAID INTAKE. 33-10.50-= 15 BFG ALL TERRAIN TIRES. 4" RANCHO LIFT WITH BRAND NEW RANCHO RS7000 SHOCK= S,SWAY BAR QUICK DISCONNECTS.CHANGED OUT THE DANA 35REAR END TO A DANA 44. = NEW BEARINGS AND 373 GEARS FRONT AND BACK.NP 231 TRANSFER CASE WITH AN AD= VANCED ADAPTER SLIP YOKE ELIMINATOR KIT AND CV DRIVE SHAFT. CURRIE CURRECT= LYNC HEAVY DUTY TIE ROD AND DRAG LINK STEERING SYSTEM WITH NEW STEERING GEA= R BOX. JKS ADJUSTABLE FRONT TRACK BAR SO IT CAN BE ALIGNED PROPERLY. NEW UP= PER AND LOWER BALL JOINTS.POLYURETHANE UPPER AND LOWER CONTROL ARM BUSHINGS= . BUSHWAKER FENDER FLARES. LOCKING GAS CAP COVER.HEAVY DUTY STEEL FRONT BUM= PER.BODY ARMOR REAR BUMPER WITH TRAILER HITCH AND REAR TIRE SWING OUT MOUNT= THAT YOU CAN ATTACH TWO GAS CANS AND A HIGH LIFT JACK TO. TOYS BY TROY ST= EEL ROCKER PANELS WITH STEP. H.I.D. HEADLIGHTS AND LED TAIL LIGHT CONVERSIO= N. NEW FRONT BRAKES AND ROTORS. THE BODY AND PAINT IS BEAUTIFUL. THE INTE= RIOR IS IN VERY CLEAN CONDITION. LOOK AT PICS. HAS ALPINE CD PLAYER. THE J= EEP RUNS SUPER STRONG AND DRIVES LIKE NEW AND HAS NEVER BEEN ABUSED. REGIST= RATION GOOD UNTIL JULY 2013. MORE PICTURES AVAILABLE. PLEASE CONTACT WITH A= NY REASONABLE OFFER. = THANK YOU. = = This email was sent by: AutoTrader.com, Inc. 3003 Summit Blvd. Suite 200 Atlanta, GA, 30319, United States = We respect your right to privacy - click here to view our policy. = = = =20 From owner-freebsd-net@FreeBSD.ORG Sun Sep 9 17:01:51 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 278301065702; Sun, 9 Sep 2012 17:01:51 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id C61588FC12; Sun, 9 Sep 2012 17:01:50 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 0DCBE25D37D1; Sun, 9 Sep 2012 17:01:48 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 08F10BE84AE; Sun, 9 Sep 2012 17:01:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id jUlbun_yCz94; Sun, 9 Sep 2012 17:01:46 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 99421BE84AD; Sun, 9 Sep 2012 17:01:46 +0000 (UTC) Date: Sun, 9 Sep 2012 17:01:45 +0000 (UTC) From: "Bjoern A. Zeeb" To: Gleb Smirnoff In-Reply-To: <20120905115140.GF15915@FreeBSD.org> Message-ID: References: <20120905115140.GF15915@FreeBSD.org> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pf@FreeBSD.org, net@FreeBSD.org Subject: Re: [HEADS UP] merging projects/pf into head X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Sep 2012 17:01:51 -0000 On Wed, 5 Sep 2012, Gleb Smirnoff wrote: Hi, > Thus, I plan to merge projects/pf/head to head this weekend, and > this is a HEADS UP email! You have been warned. :) thanks for the work and handling the fallout:) > What I'd like to do next: > > 1) Move pf out of contrib. I'd rather wait a bit with that so that other things can settle. I am also not happy with where other firewalls etc currently live and stuff so I think having a better understanding on where all this will move would be good. > 2) Refactor the pfvar.h into pf.h and pf_var.h. Provide stable > kernel<->pfctl ABI. And probably other clean up tasks. Yes, and being extensible is really important. > ... > 3) ... too far to build any plans, yet. :) Ah, NAT64, Proper V_irtualization handling for what you might not have done (I should go back and look), frag6 support, ... a bugfix from Apple/Open we need to implement, ... more cherry picking on some changes ....;-) -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-net@FreeBSD.ORG Sun Sep 9 18:55:07 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D46A1065670; Sun, 9 Sep 2012 18:55:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E54428FC12; Sun, 9 Sep 2012 18:55:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q89It6ET084091; Sun, 9 Sep 2012 18:55:06 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q89It6Dt084067; Sun, 9 Sep 2012 18:55:06 GMT (envelope-from linimon) Date: Sun, 9 Sep 2012 18:55:06 GMT Message-Id: <201209091855.q89It6Dt084067@freefall.freebsd.org> To: cdtelting@gmail.com, linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/171508: [epair] [request] Add the ability to name epair devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Sep 2012 18:55:07 -0000 Old Synopsis: Add the ability to name epair devices New Synopsis: [epair] [request] Add the ability to name epair devices State-Changed-From-To: open->suspended State-Changed-By: linimon State-Changed-When: Sun Sep 9 18:54:18 UTC 2012 State-Changed-Why: Reclassify. Mark suspended until someone comes up with some patches. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Sep 9 18:54:18 UTC 2012 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=171508 From owner-freebsd-net@FreeBSD.ORG Sun Sep 9 20:00:36 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C11B106568D for ; Sun, 9 Sep 2012 20:00:34 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1FC228FC15 for ; Sun, 9 Sep 2012 20:00:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q89K0ETU089519 for ; Sun, 9 Sep 2012 20:00:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q89K0ETo089506; Sun, 9 Sep 2012 20:00:14 GMT (envelope-from gnats) Date: Sun, 9 Sep 2012 20:00:14 GMT Message-Id: <201209092000.q89K0ETo089506@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Bjoern A. Zeeb" Cc: Subject: Re: kern/171508: [epair] [request] Add the ability to name epair devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Bjoern A. Zeeb" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 20:00:36 -0000 The following reply was made to PR kern/171508; it has been noted by GNATS. From: "Bjoern A. Zeeb" To: bug-followup@FreeBSD.org, cdtelting@gmail.com Cc: Subject: Re: kern/171508: [epair] [request] Add the ability to name epair devices Date: Sun, 9 Sep 2012 19:57:57 +0000 (UTC) I think either ifconfig name or the new jail management config file should be used. So you have any other uses cases that really need special magic? -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 04:31:07 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4B1C106564A; Mon, 10 Sep 2012 04:31:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA3E8FC08; Mon, 10 Sep 2012 04:31:06 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1894800pbb.13 for ; Sun, 09 Sep 2012 21:31:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=scwNEPwSnYETpqn4L43ooSYV+EhE9fel+n6b1rf9uwA=; b=l5RhKKb3NI8jiniVGQbKZwErLM++VrJREAhYZCK+BVpeZYMAAnXYjpXBM7IU+Rb36+ XNs9mwwToY8+qaziJCGel0a6bB2HwhhssKJrb97B0bm9pd1V1pAfcFHU4OZYr8Az+R/f tOosWW0Fl5WCAbQVDMzehlLl8ncHvuL+RgT5ZniiTS83egg2yBNTej+hIZYL4/ro5iKD 35+nBbNzG2FAqBDWqNQLwCC2zMzDSplq2bxtbZSORJoOFffVl7lx9ucDoC3sDn/D3RE0 a2DqhLtLpZzbj8UQQe9bVIyRsyc35aPheMR7obbbqcl4S3ew5inEoYCNlA9P/Xec+OsI SXdQ== Received: by 10.68.241.228 with SMTP id wl4mr3922486pbc.51.1347251465689; Sun, 09 Sep 2012 21:31:05 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id tw5sm1276355pbc.48.2012.09.09.21.31.02 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Sep 2012 21:31:04 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 10 Sep 2012 13:30:54 -0700 From: YongHyeon PYUN Date: Mon, 10 Sep 2012 13:30:54 -0700 To: Sean Bruno Message-ID: <20120910203054.GA3557@michelle.cdnetworks.com> References: <20120816165651.GA39870@FreeBSD.org> <1347050759.3479.8.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1347050759.3479.8.camel@powernoodle.corp.yahoo.com> User-Agent: Mutt/1.4.2.3i Cc: John , David Christensen , "freebsd-net@freebsd.org" Subject: Re: Dell PowerEdge R820 Broadcom BCM57800 support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 04:31:07 -0000 On Fri, Sep 07, 2012 at 01:45:59PM -0700, Sean Bruno wrote: > On Thu, 2012-08-16 at 09:56 -0700, John wrote: > > Hi Folks, > > > > I have an R820 I'm testing. The system seems to boot up fine, but > > no network adapters show up. From pciconf -l : > > > > none4@pci0:1:0:0: class=0x020000 card=0x1f5c1028 chip=0x168a14e4 rev=0x10 hdr=0x00 > > none5@pci0:1:0:1: class=0x020000 card=0x1f5c1028 chip=0x168a14e4 rev=0x10 hdr=0x00 > > none6@pci0:1:0:2: class=0x020000 card=0x1f671028 chip=0x168a14e4 rev=0x10 hdr=0x00 > > none7@pci0:1:0:3: class=0x020000 card=0x1f671028 chip=0x168a14e4 rev=0x10 hdr=0x00 > > > > which appears to be these: > > > > Broadcom BCM57800 NetXtreme II 10 GigE 1f5c > > Broadcom BCM57800 NetXtreme II 1 GigE 1f67 The chipid is 0x168a14e4 which indicates vendor is Broadcom and device is NetXtreme II BCM57800 10G gigabit ethernet. I guess bxe(4) would be right driver to pick up the controller but it seems there is no support for BCM57800 in bxe(4) at this moment. Probably David can add more comment on this(CCed). > > > > Does anyone have any experience with these? > > > > Thanks, > > John > > > > John: > > Hey, I'm currently testing a patchset that enables the use of the 1Gig > adapter via bge(4). I'm not sure about the 10Gig adapter though, is > that bxe(4) > > At this time, there no functional version of bge(4) that works on a > stable release. You'd have the best luck in compiling your own kernel > from stable/9 and applying the following updates from > > > > http://people.freebsd.org/~yongari/bge/if_bge.c > > > http://people.freebsd.org/~yongari/bge/if_bgereg.h > > > http://people.freebsd.org/~yongari/bge/brgphy.c > > You'll need to overwrie brgphy.c in sys/dev/mii and move if_bge.c > if_bgereg.h to sys/dev/bge and recompile your kernel. bge(4) does not support Broadcom NetXtreme II BCM57800 controllers. It wouldn't make any difference. From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 09:09:21 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BD6B1065672 for ; Mon, 10 Sep 2012 09:09:21 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [IPv6:2607:f2f8:a450::66]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED9D8FC16 for ; Mon, 10 Sep 2012 09:09:21 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [IPv6:2610:10:20:214::6]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id 3BB97E606F for ; Mon, 10 Sep 2012 02:09:15 -0700 (PDT) Received: from [127.0.0.1] (c-76-27-220-79.hsd1.wa.comcast.net [76.27.220.79]) by vivi.cat.pdx.edu (Postfix) with ESMTPSA id 6214924CDE for ; Mon, 10 Sep 2012 02:09:14 -0700 (PDT) Message-ID: <504DAE39.3040204@bluerosetech.com> Date: Mon, 10 Sep 2012 02:09:13 -0700 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: isc-dhcp42-server "no route to host" error due to fe80::/10 route X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 09:09:21 -0000 I have isc-dhcp42-server-4.2.4_1 installed from ports on an amd64 8.3-p3 machine acting as an IPv6 router using SLAAC and stateless DHCPv6. When machines do DHCPv6 Information Requests (per the RA's O flag), I can see in the DHCPv6 server logging the requests like this: Sep 10 01:20:31 chombo dhcpd: Information-request message from fe80::e812:4ecc:5220:8206 port 546, transaction ID 0x5A5CE500 Sep 10 01:20:31 chombo dhcpd: Sending Reply to fe80::e812:4ecc:5220:8206 port 546 Sep 10 01:20:31 chombo dhcpd: send_packet6: No route to host Sep 10 01:20:31 chombo dhcpd: dhcpv6: send_packet6() sent -1 of 92 bytes I used tcpdump to watch the exchange and the replies never make it onto the wire. Looking at my route table[1], I see the usual scoped link-local routes, plus this one: Destination Gateway Flags Netif Expire fe80::/10 ::1 UGRS lo0 Okay, so it looks like link-local is routed to the loopback by default. As a test, I changed that to the lan interface: # route delete -inet6 fe80:: -prefixlen 10 delete net fe80:: # route add -inet6 fe80:: -prefixlen 10 -iface lan add net fe80::: gateway lan Which fixes the "No route to host" problem (machines now get DHCPv6 just fine). The rub is, I will need to do DHCPv6 on fxp0 as well. Why would there be that fe80::/10 via lo0 route in the first place? How do I get the DHCPv6 replies to go out the interfaces on which the requests came in? Is this a bug in isc-dhcp42-server such that it isn't correctly setting the interface scope on its replies? 1: http://pastie.org/4694484 From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 11:09:57 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64C0310656B3 for ; Mon, 10 Sep 2012 11:09:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4BEAC8FC1A for ; Mon, 10 Sep 2012 11:09:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8AB9voO069476 for ; Mon, 10 Sep 2012 11:09:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8AB9tCx069090 for freebsd-net@FreeBSD.org; Mon, 10 Sep 2012 11:09:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Sep 2012 11:09:55 GMT Message-Id: <201209101109.q8AB9tCx069090@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 11:09:57 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/171508 net [epair] [request] Add the ability to name epair device o kern/171228 net [re] [patch] if_re - eeprom write issues o kern/170713 net [cxgb] Driver must be loaded after boot due to timing o kern/170701 net [ppp] killl ppp or reboot with active ppp connection c o kern/170267 net [ixgbe] IXGBE_LE32_TO_CPUS is probably an unintentiona o kern/170081 net [fxp] pf/nat/jails not working if checksum offloading o kern/169898 net ifconfig(8) fails to set MTU on multiple interfaces. o kern/169676 net [bge] [hang] system hangs, fully or partially after re o kern/169664 net [bgp] Wrongful replacement of interface connected net o kern/169634 net [bge] Network unavailable when booting directly to Fre o kern/169620 net [ng] [pf] ng_l2tp incoming packet bypass pf firewall o kern/169459 net [ppp] umodem/ppp/3g stopped working after update from o kern/169438 net [ipsec] ipv4-in-ipv6 tunnel mode IPsec does not work o kern/169399 net [re] RealTek RTL8168/8111/8111c network interface not p kern/168294 net [ixgbe] [patch] ixgbe driver compiled in kernel has no o kern/168246 net [em] Multiple em(4) not working with qemu o kern/168245 net [arp] [regression] Permanent ARP entry not deleted on o kern/168244 net [arp] [regression] Unable to manually remove permanent o kern/168183 net [bce] bce driver hang system o kern/168152 net [xl] Periodically, the network card xl0 stops working o kern/167947 net [setfib] [patch] arpresolve checks only the default FI o kern/167603 net [ip] IP fragment reassembly's broken: file transfer ov o kern/167500 net [em] [panic] Kernel panics in em driver o kern/167325 net [netinet] [patch] sosend sometimes return EINVAL with o kern/167202 net [igmp]: Sending multiple IGMP packets crashes kernel o kern/167059 net [tcp] [panic] System does panic in in_pcbbind() and ha o kern/166940 net [ipfilter] [panic] Double fault in kern 8.2 o kern/166462 net [gre] gre(4) when using a tunnel source address from c o kern/166372 net [patch] ipfilter drops UDP packets with zero checksum o kern/166285 net [arp] FreeBSD v8.1 REL p8 arp: unknown hardware addres o kern/166255 net [net] [patch] It should be possible to disable "promis o kern/165963 net [panic] [ipf] ipfilter/nat NULL pointer deference o kern/165903 net mbuf leak o kern/165643 net [net] [patch] Missing vnet restores in net/if_ethersub o kern/165622 net [ndis][panic][patch] Unregistered use of FPU in kernel s kern/165562 net [request] add support for Intel i350 in FreeBSD 7.4 o kern/165526 net [bxe] UDP packets checksum calculation whithin if_bxe o kern/165488 net [ppp] [panic] Fatal trap 12 jails and ppp , kernel wit o kern/165305 net [ip6] [request] Feature parity between IP_TOS and IPV6 o kern/165296 net [vlan] [patch] Fix EVL_APPLY_VLID, update EVL_APPLY_PR o kern/165181 net [igb] igb freezes after about 2 weeks of uptime o kern/165174 net [patch] [tap] allow tap(4) to keep its address on clos o kern/165152 net [ip6] Does not work through the issue of ipv6 addresse o kern/164495 net [igb] connect double head igb to switch cause system t o kern/164490 net [pfil] Incorrect IP checksum on pfil pass from ip_outp o kern/164475 net [gre] gre misses RUNNING flag after a reboot o kern/164265 net [netinet] [patch] tcp_lro_rx computes wrong checksum i o kern/163903 net [igb] "igb0:tx(0)","bpf interface lock" v2.2.5 9-STABL o kern/163481 net freebsd do not add itself to ping route packet o kern/162927 net [tun] Modem-PPP error ppp[1538]: tun0: Phase: Clearing o kern/162926 net [ipfilter] Infinite loop in ipfilter with fragmented I o kern/162558 net [dummynet] [panic] seldom dummynet panics o kern/162153 net [em] intel em driver 7.2.4 don't compile o kern/162110 net [igb] [panic] RELENG_9 panics on boot in IGB driver - o kern/162028 net [ixgbe] [patch] misplaced #endif in ixgbe.c o kern/161381 net [re] RTL8169SC - re0: PHY write failed o kern/161277 net [em] [patch] BMC cannot receive IPMI traffic after loa o kern/160873 net [igb] igb(4) from HEAD fails to build on 7-STABLE o kern/160750 net Intel PRO/1000 connection breaks under load until rebo o kern/160693 net [gif] [em] Multicast packet are not passed from GIF0 t o kern/160293 net [ieee80211] ppanic] kernel panic during network setup o kern/160206 net [gif] gifX stops working after a while (IPv6 tunnel) o kern/159817 net [udp] write UDPv4: No buffer space available (code=55) o kern/159629 net [ipsec] [panic] kernel panic with IPsec in transport m o kern/159621 net [tcp] [panic] panic: soabort: so_count o kern/159603 net [netinet] [patch] in_ifscrubprefix() - network route c o kern/159601 net [netinet] [patch] in_scrubprefix() - loopback route re o kern/159294 net [em] em watchdog timeouts o kern/159203 net [wpi] Intel 3945ABG Wireless LAN not support IBSS o kern/158930 net [bpf] BPF element leak in ifp->bpf_if->bif_dlist o kern/158726 net [ip6] [patch] ICMPv6 Router Announcement flooding limi o kern/158694 net [ix] [lagg] ix0 is not working within lagg(4) o kern/158665 net [ip6] [panic] kernel pagefault in in6_setscope() o kern/158635 net [em] TSO breaks BPF packet captures with em driver f kern/157802 net [dummynet] [panic] kernel panic in dummynet o kern/157785 net amd64 + jail + ipfw + natd = very slow outbound traffi o kern/157418 net [em] em driver lockup during boot on Supermicro X9SCM- o kern/157410 net [ip6] IPv6 Router Advertisements Cause Excessive CPU U o kern/157287 net [re] [panic] INVARIANTS panic (Memory modified after f o kern/157209 net [ip6] [patch] locking error in rip6_input() (sys/netin o kern/157200 net [network.subr] [patch] stf(4) can not communicate betw o kern/157182 net [lagg] lagg interface not working together with epair o kern/156877 net [dummynet] [panic] dummynet move_pkt() null ptr derefe o kern/156667 net [em] em0 fails to init on CURRENT after March 17 o kern/156408 net [vlan] Routing failure when using VLANs vs. Physical e o kern/156328 net [icmp]: host can ping other subnet but no have IP from o kern/156317 net [ip6] Wrong order of IPv6 NS DAD/MLD Report o kern/156283 net [ip6] [patch] nd6_ns_input - rtalloc_mpath does not re o kern/156279 net [if_bridge][divert][ipfw] unable to correctly re-injec o kern/156226 net [lagg]: failover does not announce the failover to swi o kern/156030 net [ip6] [panic] Crash in nd6_dad_start() due to null ptr o kern/155772 net ifconfig(8): ioctl (SIOCAIFADDR): File exists on direc o kern/155680 net [multicast] problems with multicast s kern/155642 net [request] Add driver for Realtek RTL8191SE/RTL8192SE W o kern/155597 net [panic] Kernel panics with "sbdrop" message o kern/155420 net [vlan] adding vlan break existent vlan o kern/155177 net [route] [panic] Panic when inject routes in kernel p kern/155030 net [igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net [msk] ntfs-3g via iscsi using msk driver cause kernel o kern/154943 net [gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net [request]: Port brcm80211 driver from Linux to FreeBSD o kern/154850 net [netgraph] [patch] ng_ether fails to name nodes when t o kern/154679 net [em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154600 net [tcp] [panic] Random kernel panics on tcp_output o kern/154557 net [tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net [if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154255 net [nfs] NFS not responding o kern/154214 net [stf] [panic] Panic when creating stf interface o kern/154185 net race condition in mb_dupcl o kern/154169 net [multicast] [ip6] Node Information Query multicast add o kern/154134 net [ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net [netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net [vlan] [patch] change to way of auto-generatation of v o kern/153937 net [ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net [ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net [ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net [ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153497 net [netgraph] netgraph panic due to race conditions o kern/153454 net [patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net [em] em interface use 100% cpu o kern/153244 net [em] em(4) fails to send UDP to port 0xffff o kern/152893 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net [em] tftpd (and likely other udp traffic) fails over e o kern/152828 net [em] poor performance on 8.1, 8.2-PRE o kern/152569 net [net]: Multiple ppp connections and routing table prob o kern/152235 net [arp] Permanent local ARP entries are not properly upd o kern/152141 net [vlan] [patch] encapsulate vlan in ng_ether before out o kern/152036 net [libc] getifaddrs(3) returns truncated sockaddrs for n o kern/151690 net [ep] network connectivity won't work until dhclient is o kern/151681 net [nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net [igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net [ixgbe][igb] Panic when packets are dropped with heade o kern/150557 net [igb] igb0: Watchdog timeout -- resetting o kern/150251 net [patch] [ixgbe] Late cable insertion broken o kern/150249 net [ixgbe] Media type detection broken o bin/150224 net ppp(8) does not reassign static IP after kill -KILL co f kern/149969 net [wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net [ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149643 net [rum] device not sending proper beacon frames in ap mo o kern/149609 net [panic] reboot after adding second default route o kern/149117 net [inet] [patch] in_pcbbind: redundant test o kern/149086 net [multicast] Generic multicast join failure in 8.1 o kern/148018 net [flowtable] flowtable crashes on ia64 o kern/147912 net [boot] FreeBSD 8 Beta won't boot on Thinkpad i1300 11 o kern/147894 net [ipsec] IPv6-in-IPv4 does not work inside an ESP-only o kern/147155 net [ip6] setfb not work with ipv6 o kern/146845 net [libc] close(2) returns error 54 (connection reset by f kern/146792 net [flowtable] flowcleaner 100% cpu's core load o kern/146719 net [pf] [panic] PF or dumynet kernel panic o kern/146534 net [icmp6] wrong source address in echo reply o kern/146427 net [mwl] Additional virtual access points don't work on m f kern/146394 net [vlan] IP source address for outgoing connections o bin/146377 net [ppp] [tun] Interface doesn't clear addresses when PPP o kern/146358 net [vlan] wrong destination MAC address o kern/146165 net [wlan] [panic] Setting bssid in adhoc mode causes pani o kern/146082 net [ng_l2tp] a false invaliant check was performed in ng_ o kern/146037 net [panic] mpd + CoA = kernel panic o kern/145825 net [panic] panic: soabort: so_count o kern/145728 net [lagg] Stops working lagg between two servers. p kern/145600 net TCP/ECN behaves different to CE/CWR than ns2 reference f kern/144917 net [flowtable] [panic] flowtable crashes system [regressi o kern/144882 net MacBookPro =>4.1 does not connect to BSD in hostap wit o kern/144874 net [if_bridge] [patch] if_bridge frees mbuf after pfil ho o conf/144700 net [rc.d] async dhclient breaks stuff for too many people o kern/144616 net [nat] [panic] ip_nat panic FreeBSD 7.2 f kern/144315 net [ipfw] [panic] freebsd 8-stable reboot after add ipfw o kern/144231 net bind/connect/sendto too strict about sockaddr length o kern/143846 net [gif] bringing gif3 tunnel down causes gif0 tunnel to s kern/143673 net [stf] [request] there should be a way to support multi s kern/143666 net [ip6] [request] PMTU black hole detection not implemen o kern/143622 net [pfil] [patch] unlock pfil lock while calling firewall o kern/143593 net [ipsec] When using IPSec, tcpdump doesn't show outgoin o kern/143591 net [ral] RT2561C-based DLink card (DWL-510) fails to work o kern/143208 net [ipsec] [gif] IPSec over gif interface not working o kern/143034 net [panic] system reboots itself in tcp code [regression] o kern/142877 net [hang] network-related repeatable 8.0-STABLE hard hang o kern/142774 net Problem with outgoing connections on interface with mu o kern/142772 net [libc] lla_lookup: new lle malloc failed f kern/142518 net [em] [lagg] Problem on 8.0-STABLE with em and lagg o kern/142018 net [iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net [wi] data garbled with WEP and wi(4) with Prism 2.5 f kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140682 net [netgraph] [panic] random panic in netgraph o kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL p kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR if_adata/ o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 f kern/138029 net [bpf] [panic] periodically kernel panic and reboot o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 p bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o conf/132851 net [patch] rc.conf(5): allow to setfib(1) for service run o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o kern/131601 net [ipfilter] [panic] 7-STABLE panic in nat_finalise (tcp o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o bin/131365 net route(8): route add changes interpretation of network f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129517 net [ipsec] [panic] double fault / stack overflow f kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by p kern/127360 net [socket] TOE socket options missing from sosetopt() o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126339 net [ipw] ipw driver drops the connection o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o kern/123758 net [panic] panic while restarting net/freenet6 o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices f kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup ieee o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] [security] ppp(8): fix local stack overflow in o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111537 net [inet6] [patch] ip6_input() treats mbuf cluster wrong o kern/111457 net [ral] ral(4) freeze o kern/110284 net [if_ethersubr] Invalid Assumption in SIOCSIFADDR in et o kern/110249 net [kernel] [regression] [patch] setsockopt() error regre o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106444 net [netgraph] [panic] Kernel Panic on Binding to an ip to o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o kern/102540 net [netgraph] [patch] supporting vlan(4) by ng_fec(4) o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working o kern/97306 net [netgraph] NG_L2TP locks after connection with failed o conf/97014 net [gif] gifconfig_gif? in rc.conf does not recognize IPv f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87421 net [netgraph] [panic]: ng_ether + ng_eiface + if_bridge o kern/86871 net [tcp] [patch] allocation logic for PCBs in TIME_WAIT s o kern/86427 net [lor] Deadlock with FASTIPSEC and nat o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ p kern/85320 net [gre] [patch] possible depletion of kernel stack in ip o bin/82975 net route change does not parse classfull network as given o kern/82881 net [netgraph] [panic] ng_fec(4) causes kernel panic after o kern/82468 net Using 64MB tcp send/recv buffers, trafficflow stops, i o bin/82185 net [patch] ndp(8) can delete the incorrect entry o kern/81095 net IPsec connection stops working if associated network i o kern/78968 net FreeBSD freezes on mbufs exhaustion (network interface o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o kern/77341 net [ip6] problems with IPV6 implementation s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time a kern/71474 net [route] route lookup does not skip interfaces marked d o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/68889 net [panic] m_copym, length > size of mbuf chain o kern/66225 net [netgraph] [patch] extend ng_eiface(4) control message o kern/65616 net IPSEC can't detunnel GRE packets after real ESP encryp s kern/60293 net [patch] FreeBSD arp poison patch a kern/56233 net IPsec tunnel (ESP) over IPv6: MTU computation is wrong s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31940 net ip queue length too short for >500kpps o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c f kern/24959 net [patch] proper TCP_NOPUSH/TCP_CORK compatibility o conf/23063 net [arp] [patch] for static ARP tables in rc.network o kern/21998 net [socket] [patch] ident only for outgoing connections o kern/5877 net [socket] sb_cc counts control data as well as data dat 417 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 13:57:11 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6664106564A for ; Mon, 10 Sep 2012 13:57:11 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id 37A3B8FC0C for ; Mon, 10 Sep 2012 13:57:11 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id E69D650963; Mon, 10 Sep 2012 09:29:46 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 94E9D508A4 for ; Mon, 10 Sep 2012 09:29:46 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Mon, 10 Sep 2012 09:29:46 -0400 From: Dominic Blais To: "freebsd-net@freebsd.org" Date: Mon, 10 Sep 2012 09:29:44 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2PWFbXYRy6eyxJRKWzzsz6mxKILw== Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 13:57:11 -0000 Hi, We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It used= to work very well for 6 weeks and now the "Internet traffic" stops almost = each day. Symptoms: - I still can ssh to the server from the LAN. - The users connected to mpd by PPPoE can't access Internet. - I tried to do a "whois 65.59.233.102" to know where it's from and the who= is server doesn't answer probably because the request never get sent. I tried to restart mpd, the users are reconnecting but they still can't acc= ess the Internet. I need to reboot to recover from that. Note that, each da= y it happened, it's always the same IP address (65.59.233.102) that's in th= e error message. That error appears up to 5 times per second. Actually, this server has only 1 NIC (bge0). It has an IP on that internet = and also a vlan interface (vlan0 [pvid 2]) that's used for PPPoE between mp= d and the pppoe clients. -- Dominic Blais From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 14:03:03 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85ECD106566B for ; Mon, 10 Sep 2012 14:03:03 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id F09D88FC12 for ; Mon, 10 Sep 2012 14:03:02 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8AE31xT068257; Mon, 10 Sep 2012 18:03:01 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8AE31jF068256; Mon, 10 Sep 2012 18:03:01 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 10 Sep 2012 18:03:01 +0400 From: Gleb Smirnoff To: Dominic Blais Message-ID: <20120910140300.GV44854@FreeBSD.org> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-net@freebsd.org" Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 14:03:03 -0000 On Mon, Sep 10, 2012 at 09:29:44AM -0400, Dominic Blais wrote: D> Hi, D> D> We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It used to work very well for 6 weeks and now the "Internet traffic" stops almost each day. D> D> Symptoms: D> D> - I still can ssh to the server from the LAN. D> - The users connected to mpd by PPPoE can't access Internet. D> - I tried to do a "whois 65.59.233.102" to know where it's from and the whois server doesn't answer probably because the request never get sent. D> D> D> I tried to restart mpd, the users are reconnecting but they still can't access the Internet. I need to reboot to recover from that. Note that, each day it happened, it's always the same IP address (65.59.233.102) that's in the error message. That error appears up to 5 times per second. D> D> Actually, this server has only 1 NIC (bge0). It has an IP on that internet and also a vlan interface (vlan0 [pvid 2]) that's used for PPPoE between mpd and the pppoe clients. I'm not sure that this message is directly related to connectivity problems. Have you tried common debugging sequence when internet connectivity breaks: tcpdumping, looking at ARP table, route table, etc? -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 16:31:05 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E237B1065674; Mon, 10 Sep 2012 16:31:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B1C758FC1E; Mon, 10 Sep 2012 16:31:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8AGV59D087831; Mon, 10 Sep 2012 16:31:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8AGV5OF087813; Mon, 10 Sep 2012 16:31:05 GMT (envelope-from linimon) Date: Mon, 10 Sep 2012 16:31:05 GMT Message-Id: <201209101631.q8AGV5OF087813@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/171520: [alc] alc network driver + tso + vlan does not work. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 16:31:06 -0000 Old Synopsis: alc network driver + tso + vlan does not work. New Synopsis: [alc] alc network driver + tso + vlan does not work. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Sep 10 16:30:46 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171520 From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 16:33:14 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFD98106566B; Mon, 10 Sep 2012 16:33:14 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 943968FC08; Mon, 10 Sep 2012 16:33:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8AGXECC016661; Mon, 10 Sep 2012 16:33:14 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8AGXEvQ016644; Mon, 10 Sep 2012 16:33:14 GMT (envelope-from linimon) Date: Mon, 10 Sep 2012 16:33:14 GMT Message-Id: <201209101633.q8AGXEvQ016644@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 16:33:14 -0000 Old Synopsis: ipmi driver crashes kernel by reboot or shutdown New Synopsis: [ipmi] ipmi driver crashes kernel by reboot or shutdown Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Sep 10 16:32:46 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171524 From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 17:03:19 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F2271065675 for ; Mon, 10 Sep 2012 17:03:19 +0000 (UTC) (envelope-from foldersyh056@ups.com) Received: from mail.redsa.com.ar (mail.redsa.com.ar [200.89.184.26]) by mx1.freebsd.org (Postfix) with ESMTP id 911F88FC0C for ; Mon, 10 Sep 2012 17:03:18 +0000 (UTC) Received: from [181.2.169.86] (helo=knkewobmzwzs.mrhvqtg.va) by mail.redsa.com.ar with esmtpa (Exim 4.69) (envelope-from ) id 1MMBT4-4075jp-C4 for freebsd-net@freebsd.org; Mon, 10 Sep 2012 14:03:17 -0300 From: "UPS Quantum View" To: Date: Mon, 10 Sep 2012 14:03:17 -0300 MIME-Version: 1.0 X-Priority: 3 X-Mailer: ceobpwjq_18 Message-ID: <4585790935.74Z9P5B4263253@lykzdrtq.gunwrjk.biz> Content-Type: multipart/mixed; boundary="----=mpoint__mscb_68_04_53" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Delivery Notification UPS Mon, 10 Sep 2012 14:03:17 -0300 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 17:03:19 -0000 ------=mpoint__mscb_68_04_53 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable --> This message was sent to you at the request of Anil Ltd to notify you t= hat the electronic shipment information below has been transmitted to UPS= The physical package(s) may or may not have actually been tendered to U= PS for shipment.Important Delivery InformationScheduled Delivery: 12-Sept= ember-2012Number of Packages:1 UPS Service:EXPEDITED Weight:1,0 LBS Tracking Number:7R19090S5852399435 Invoice Number:ORDER#5942 Purchase Order Number:SUPPLIES Please refer to attached file____25@2@@20orYbuh____ © 2012 United Parcel Service of America, Inc. UPS,=A0 Contact UPS ------=mpoint__mscb_68_04_53-- From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 19:18:17 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90277106566C for ; Mon, 10 Sep 2012 19:18:17 +0000 (UTC) (envelope-from return@bounces.fanbridge.com) Received: from r86-m4.fanbridge.com (r86-m4.fanbridge.com [208.101.11.86]) by mx1.freebsd.org (Postfix) with ESMTP id 630868FC18 for ; Mon, 10 Sep 2012 19:18:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=r86-m4; d=fanbridge.com; h=From:To:Subject:Message-ID:Sender:List-Unsubscribe:List-Id:Date:Content-Type:MIME-Version; i=noreply@fanbridge.com; bh=P/qF308x7dwH5Y1tkvu+MjtxqcU=; b=dLvykVzBmJejHpeh5A/gQY6A5eQC9OI8sNLho6WfvMmmrA9gst6FoSVtF9au9bIONqy0SY6A/QIZ mC/n3k5uNA== DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=r86-m4; d=fanbridge.com; b=fGv/MnKI4Uk9OSJB1auczSo+B6DmW68KfbZF9++D/56ZQPJTW4MG/bTU9biNnVpkRwZhAdBdVMDU eN3fyTmRDg==; Received: from 127.0.0.1 (173.193.22.34) by r86-m4.fanbridge.com id h9oufi1cibcr for ; Mon, 10 Sep 2012 15:05:40 -0400 (envelope-from ) From: "RCBC(Rizal Commercial Banking)" To: freebsd-net@freebsd.org Message-ID: <12678e6cbf396e854cdbdfe9b2352f26@fanbridge.com> Sender: FanBridge X-fbridge-uid: 176282 X-fbridge-sid: 204505454 X-fbridge-cfc: krK7hae1K3hh4B9621a7XXbhhP X-fbridge-cid: 901772 X-rpcampaign: fbridge176282901772 Date: Mon, 10 Sep 2012 15:05:40 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Email Alert: Review Account (Account is Suspended) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 19:18:17 -0000 Now=20 =09 IMPORTANT ALERT MSSAGE =20 =09Dear Valued RCBC Customer, Your account was disabled due to a recent security profile upgrade. We require you to confirm your details now. NOTE: Inactive accounts will be disabled after 3 hours of notice for security reasons. Activate: ----- http://rcbcaccessone.com/security-network-/acvtivate-now [1]profile/user Notice: ----- Activation is Required Now.profile/user Thank you,=20 =09 RCBC=20 ------ [1] http://www.pintursa.es/wp-admin/js/appss/RetailSignOn.htm ---------------------------------------- RCBC(Rizal Commercial Banking) sent this email to freebsd-net@freebsd.or= g Questions? Contact enterpricewillboat@yahoo.com or RCBC(Rizal Commercial= Banking), c/o FanBridge, Inc. - 14525 SW Millikan Way, #16910, Beaverto= n, Oregon 97005, United States Update Your Information - http://fburls.com/updt/176282|krK7hae1K3hh4B96= 21a7XXbhhP|freebsd-net@freebsd.org|901772 Forward to a friend - http://fburls.com/fwrd/176282|krK7hae1K3hh4B9621a7= XXbhhP|204505454|901772 Unsubscribe - http://fburls.com/usub/176282|krK7hae1K3hh4B9621a7XXbhhP|2= 04505454|901772 Privacy Policy - http://www.fanbridge.com/learn/privacy.php This email message is powered by FanBridge: http://www.fanbridge.com/b.php?id=3D176282&src=3Dcampaign_footer_text&ut= m_source=3Demail_text&utm_medium=3Dmail_footer_link&utm_campaign=3Dpower= ed_by&utm_content=3D176282 Powering Valuable Fan Relationships From owner-freebsd-net@FreeBSD.ORG Mon Sep 10 20:45:57 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB0D21065673; Mon, 10 Sep 2012 20:45:57 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.freebsd.org (Postfix) with ESMTP id A70438FC1C; Mon, 10 Sep 2012 20:45:57 +0000 (UTC) Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Mon, 10 Sep 2012 13:42:00 -0700 X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2 Received: from IRVEXCHMB11.corp.ad.broadcom.com ( [fe80::9cdd:3a57:8694:f610]) by IRVEXCHCAS06.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0355.002; Mon, 10 Sep 2012 13:43:26 -0700 From: "David Christensen" To: "pyunyh@gmail.com" , "Sean Bruno" Thread-Topic: Dell PowerEdge R820 Broadcom BCM57800 support Thread-Index: AQHNe9BHJ4Q7aTFbIUOKCCHb5TBlt5d/8UqAgASyyAD//4tQYA== Date: Mon, 10 Sep 2012 20:43:25 +0000 Message-ID: <3A5015FE9E557D448AF7238AF0ACE20A225550@IRVEXCHMB11.corp.ad.broadcom.com> References: <20120816165651.GA39870@FreeBSD.org> <1347050759.3479.8.camel@powernoodle.corp.yahoo.com> <20120910203054.GA3557@michelle.cdnetworks.com> In-Reply-To: <20120910203054.GA3557@michelle.cdnetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.208.64] MIME-Version: 1.0 X-WSS-ID: 7C508F123NK26383391-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: John , Gary Zambrano , David Christensen , "freebsd-net@freebsd.org" Subject: RE: Dell PowerEdge R820 Broadcom BCM57800 support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2012 20:45:58 -0000 > > > I have an R820 I'm testing. The system seems to boot up fine, but > > > no network adapters show up. From pciconf -l : > > > > > > none4@pci0:1:0:0: class=3D0x020000 card=3D0x1f5c1028 > chip=3D0x168a14e4 rev=3D0x10 hdr=3D0x00 > > > none5@pci0:1:0:1: class=3D0x020000 card=3D0x1f5c1028 > chip=3D0x168a14e4 rev=3D0x10 hdr=3D0x00 > > > none6@pci0:1:0:2: class=3D0x020000 card=3D0x1f671028 > chip=3D0x168a14e4 rev=3D0x10 hdr=3D0x00 > > > none7@pci0:1:0:3: class=3D0x020000 card=3D0x1f671028 > chip=3D0x168a14e4 rev=3D0x10 hdr=3D0x00 > > > > > > which appears to be these: > > > > > > Broadcom BCM57800 NetXtreme II 10 GigE 1f5c > > > Broadcom BCM57800 NetXtreme II 1 GigE 1f67 >=20 > The chipid is 0x168a14e4 which indicates vendor is Broadcom and > device is NetXtreme II BCM57800 10G gigabit ethernet. I guess > bxe(4) would be right driver to pick up the controller but it seems > there is no support for BCM57800 in bxe(4) at this moment. > Probably David can add more comment on this(CCed). No committed plans to update bxe(4) to support BCM57712 or=20 BCM578XX at the moment. If you have a near term need for 10Gb=20 controllers on this platform you'll need to select an alternate rNDC=20 adapter when you order the system. I posted a request on freebsd-jobs last month looking for someone who would be interested in the work if you can recommend someone. Not all of the documentation=20 required for the effort is publically available so an NDA will likely be required to do the work. http://lists.freebsd.org/pipermail/freebsd-jobs/2012-August/000809.html Dave From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 13:20:06 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37FA1106566B; Tue, 11 Sep 2012 13:20:06 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id EFECA8FC1B; Tue, 11 Sep 2012 13:20:05 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id A549C50943; Tue, 11 Sep 2012 09:20:04 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 522D4508A4; Tue, 11 Sep 2012 09:20:04 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Tue, 11 Sep 2012 09:20:04 -0400 From: Dominic Blais To: Gleb Smirnoff Date: Tue, 11 Sep 2012 09:19:59 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2PXQCC1PV2P2ShQvKHE9iF1fwn1wAwtVEQ Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> In-Reply-To: <20120910140300.GV44854@FreeBSD.org> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 13:20:06 -0000 Hi! I just noticed that it is my default route that is changing for the aforeme= ntioned in the subject IP address. What the "$?% could cause that? Could MP= D push that route as default? For what reason? That IP address doesn't even= belong to us. -- -----Message d'origine----- De=A0: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Envoy=E9=A0: 10 septembre 2012 10:03 =C0=A0: Dominic Blais Cc=A0: freebsd-net@freebsd.org Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On Mon, Sep 10, 2012 at 09:29:44AM -0400, Dominic Blais wrote: D> Hi, D>=20 D> We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It u= sed to work very well for 6 weeks and now the "Internet traffic" stops almo= st each day. D>=20 D> Symptoms: D>=20 D> - I still can ssh to the server from the LAN. D> - The users connected to mpd by PPPoE can't access Internet. D> - I tried to do a "whois 65.59.233.102" to know where it's from and the = whois server doesn't answer probably because the request never get sent. D>=20 D>=20 D> I tried to restart mpd, the users are reconnecting but they still can't = access the Internet. I need to reboot to recover from that. Note that, each= day it happened, it's always the same IP address (65.59.233.102) that's in= the error message. That error appears up to 5 times per second. D>=20 D> Actually, this server has only 1 NIC (bge0). It has an IP on that intern= et and also a vlan interface (vlan0 [pvid 2]) that's used for PPPoE between= mpd and the pppoe clients. I'm not sure that this message is directly related to connectivity problems= . Have you tried common debugging sequence when internet connectivity breaks: tcpdumping, looking at ARP table, route table, etc? --=20 Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 13:36:54 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65769106566B for ; Tue, 11 Sep 2012 13:36:54 +0000 (UTC) (envelope-from krzysiek@airnet.opole.pl) Received: from base.airnet.opole.pl (ns2.airmax.pl [176.111.128.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1458C8FC18 for ; Tue, 11 Sep 2012 13:36:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by base.airnet.opole.pl (Postfix) with ESMTP id 133767FF02E for ; Tue, 11 Sep 2012 15:30:54 +0200 (CEST) Received: from base.airnet.opole.pl ([127.0.0.1]) by localhost (mail.airnet.opole.pl [127.0.0.1]) (maiad, port 10024) with ESMTP id 22316-01 for ; Tue, 11 Sep 2012 15:30:53 +0200 (CEST) Received: from [10.10.11.223] (unknown [176.111.138.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: krzysiek@airnet.opole.pl) by base.airnet.opole.pl (Postfix) with ESMTPSA id DB8FE7FF020 for ; Tue, 11 Sep 2012 15:30:53 +0200 (CEST) Message-ID: <504F3D0B.4000703@airnet.opole.pl> Date: Tue, 11 Sep 2012 15:30:51 +0200 From: Krzysztof Barcikowski User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 13:36:54 -0000 W dniu 2012-09-11 15:19, Dominic Blais pisze: > Hi! > > I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us. > > Hi! I have similar problems with 3 machines running FBSD9 as routers... and I do not use MPD at all. http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html The default route is also changing from time to time. Best regards! KB From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 14:23:58 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54DBF106564A for ; Tue, 11 Sep 2012 14:23:58 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id C20278FC14 for ; Tue, 11 Sep 2012 14:23:57 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8BENuno078239; Tue, 11 Sep 2012 18:23:56 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8BENtf7078238; Tue, 11 Sep 2012 18:23:55 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 11 Sep 2012 18:23:55 +0400 From: Gleb Smirnoff To: Dominic Blais Message-ID: <20120911142355.GM44854@glebius.int.ru> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-net@freebsd.org" Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 14:23:58 -0000 On Tue, Sep 11, 2012 at 09:19:59AM -0400, Dominic Blais wrote: D> Hi! D> D> I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us. Really weird... I'd suggest you to run 'route monitor' to see exact message that inserts the route into the kernel and run periodically 'fstat | grep route' to catch the application that opens routing socket. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 16:02:03 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 108141065677; Tue, 11 Sep 2012 16:02:03 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id CEC348FC1E; Tue, 11 Sep 2012 16:02:01 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id D63035091E; Tue, 11 Sep 2012 12:01:54 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 85F8A508B1; Tue, 11 Sep 2012 12:01:54 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Tue, 11 Sep 2012 12:01:54 -0400 From: Dominic Blais To: Gleb Smirnoff Date: Tue, 11 Sep 2012 12:01:49 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QKRcO/pk3LnYLQbqksMP/vfPChQADVmLw Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> In-Reply-To: <20120911142355.GM44854@glebius.int.ru> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 16:02:03 -0000 I could do something about the route monitor but not the fstat | grep route= ... I mean, I would have to run it in a loop endlessly until the bug happen= s... Even with it, it's not even sure I would catch it... Is there some way we can fstat everything so I don't miss what's happening = between 2 calls to fstat? -- -----Message d'origine----- De=A0: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Envoy=E9=A0: 11 septembre 2012 10:24 =C0=A0: Dominic Blais Cc=A0: freebsd-net@freebsd.org Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On Tue, Sep 11, 2012 at 09:19:59AM -0400, Dominic Blais wrote: D> Hi! D>=20 D> I just noticed that it is my default route that is changing for the afor= ementioned in the subject IP address. What the "$?% could cause that? Could= MPD push that route as default? For what reason? That IP address doesn't e= ven belong to us. Really weird... I'd suggest you to run 'route monitor' to see exact message that inserts th= e route into the kernel and run periodically 'fstat | grep route' to catch = the application that opens routing socket. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 17:29:47 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D432B106564A; Tue, 11 Sep 2012 17:29:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7CDF08FC1B; Tue, 11 Sep 2012 17:29:46 +0000 (UTC) Received: by obbun3 with SMTP id un3so1507479obb.13 for ; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ubCVJP+h1joc3Zby+rn+qM6UCyrQU0DMMXXBtIvXEys=; b=bEmLe/9Xat9OFR5UijTaM5w842s9XM/+xteshDqYxkT5kqulPcbB91+DdpNMuOoD1+ PsBoKMt14KTBcAOYo7fkoQ9sb1Nwc9wbN4ICuR5QtZYHccqbmbCr5+nRcwgr/va94Cnx 8AfebB2rfchlQ5F+/ROn0ARdc8jBqoJQK2WL1SYUCYX8kprAqni5bllXHwbMjFAmLm++ z+g5GVgHy9CLDd/H+5/wb9hrVeUT57V0CGrW7fjvNRUkJEvb+Un3Go9Cra0bw2GCYIvA bjC8NWHM5ab2Khon/jMWsf5c5jUgcZJBKOsBCkTMcn2VQuaUcZZMwY9MeQFoLUtf/l6B PCRw== MIME-Version: 1.0 Received: by 10.182.43.40 with SMTP id t8mr19315307obl.93.1347384586301; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.76.8.98 with HTTP; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> Date: Tue, 11 Sep 2012 10:29:46 -0700 X-Google-Sender-Auth: Yx4NDsHiaqEOuz768YR3E3cXozw Message-ID: From: Adrian Chadd To: Dominic Blais Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 17:29:47 -0000 On 11 September 2012 09:01, Dominic Blais wrote: > I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it... The route monitor is a good idea. It should tell us whether it's from some tool/program/network event sending a routing table update, or whether it's just plain memory corruption. adrian From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 17:35:27 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 305AB106566C; Tue, 11 Sep 2012 17:35:27 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 888008FC18; Tue, 11 Sep 2012 17:35:26 +0000 (UTC) Received: by eeke52 with SMTP id e52so706136eek.13 for ; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UUWM2lZP8B90sbE7zXxerUGJlHl00iA9xFS8gTw2ELA=; b=ohjYH7vGHfRmKUZ4Y47jJrSbvbH+kBZZz1aKGucoOkpm93PALTg2kql9wHgBqy6Zh4 KwvJ/H/8YI2ihjG5jCth3gbt9TJH2xLQvoNc+oq3EHUwPW1OSyTYwprr0XQdDPdvz8Ew OQHPLYCfjiPHA+bPBK//9AKc5DkUaI2Ot6P8ipNzEUEqiNkcIkEwZGlrQ5+6smtwXUnw H7qbokWfLT9IMwXl9A/0BEH2tDpivsFyS1d95NvN+8lsuoVzr9oGd5roU4TePEq9Oala mz+pGdOOxhhgNwDZMYKdkriOhl/Lp1MOKXrq2cQC9MsxOvk2C7mSajcw1E1Xkib97owr yiPg== MIME-Version: 1.0 Received: by 10.14.224.4 with SMTP id w4mr27072461eep.21.1347384925699; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) Received: by 10.14.219.134 with HTTP; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) In-Reply-To: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> Date: Tue, 11 Sep 2012 10:35:25 -0700 Message-ID: From: Vijay Singh To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" , Dominic Blais Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 17:35:27 -0000 On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrote: > On 11 September 2012 09:01, Dominic Blais wrote: >> I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it... > > The route monitor is a good idea. It should tell us whether it's from > some tool/program/network event sending a routing table update, or > whether it's just plain memory corruption. Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 17:36:00 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 278FF106568C; Tue, 11 Sep 2012 17:36:00 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id DC7678FC0C; Tue, 11 Sep 2012 17:35:59 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id AB60B5091E; Tue, 11 Sep 2012 13:35:58 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 584025086B; Tue, 11 Sep 2012 13:35:58 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Tue, 11 Sep 2012 13:35:58 -0400 From: Dominic Blais To: Adrian Chadd Date: Tue, 11 Sep 2012 13:35:52 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QQwsIb8M1OFC1QLO0edYnvI4yVwAALTKA Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDBA@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> In-Reply-To: Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 17:36:00 -0000 Ok, I'll try the route monitor. Please note that Krzysztof Barcikowski alre= ady did it and got nothing: http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html -- -----Message d'origine----- De=A0: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la part de= Adrian Chadd Envoy=E9=A0: 11 septembre 2012 13:30 =C0=A0: Dominic Blais Cc=A0: Gleb Smirnoff; freebsd-net@freebsd.org Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On 11 September 2012 09:01, Dominic Blais wrote: > I could do something about the route monitor but not the fstat | grep rou= te... I mean, I would have to run it in a loop endlessly until the bug happ= ens... Even with it, it's not even sure I would catch it... The route monitor is a good idea. It should tell us whether it's from some = tool/program/network event sending a routing table update, or whether it's = just plain memory corruption. adrian From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 19:58:39 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18CD8106564A; Tue, 11 Sep 2012 19:58:39 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC6B8FC14; Tue, 11 Sep 2012 19:58:38 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8BJwbTf080035; Tue, 11 Sep 2012 23:58:37 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8BJwavb080034; Tue, 11 Sep 2012 23:58:36 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 11 Sep 2012 23:58:36 +0400 From: Gleb Smirnoff To: Vijay Singh Message-ID: <20120911195836.GQ44854@FreeBSD.org> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-net@freebsd.org" , Adrian Chadd , Dominic Blais Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 19:58:39 -0000 On Tue, Sep 11, 2012 at 10:35:25AM -0700, Vijay Singh wrote: V> On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrote: V> > On 11 September 2012 09:01, Dominic Blais wrote: V> >> I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it... V> > V> > The route monitor is a good idea. It should tell us whether it's from V> > some tool/program/network event sending a routing table update, or V> > whether it's just plain memory corruption. V> V> Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 Why do you suspect this one? -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 20:00:21 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB36D106564A for ; Tue, 11 Sep 2012 20:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9CF208FC20 for ; Tue, 11 Sep 2012 20:00:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8BK0LEZ057217 for ; Tue, 11 Sep 2012 20:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8BK0LCk057201; Tue, 11 Sep 2012 20:00:21 GMT (envelope-from gnats) Date: Tue, 11 Sep 2012 20:00:21 GMT Message-Id: <201209112000.q8BK0LCk057201@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Sean Bruno Cc: Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sean Bruno List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 20:00:21 -0000 The following reply was made to PR kern/171524; it has been noted by GNATS. From: Sean Bruno To: bug-followup@FreeBSD.org, dhojnik@brainbits.net Cc: Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown Date: Tue, 11 Sep 2012 12:56:16 -0700 It looks like the fix is not in releng_91 for release. http://svnweb.freebsd.org/base/stable/9/sys/dev/ipmi/ipmi.c?revision=239920&view=markup You can either patch the system by hand by applying this change to your local tree or update to stable/9 to fix this. http://www.wonkity.com/~wblock/docs/html/stable.html Sean From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 20:03:58 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA5381065670; Tue, 11 Sep 2012 20:03:58 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id E5AD98FC15; Tue, 11 Sep 2012 20:03:57 +0000 (UTC) Received: by eeke52 with SMTP id e52so816413eek.13 for ; Tue, 11 Sep 2012 13:03:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2mrzeUOJNFtJUv2rKO0trVZQ9UOhe3WEhWjEV4kJ888=; b=oOECFJC9HohAbR52WbZEfCRlgXqkNKH6xPFMEz/FN0K9mOtOSwhHGNKJTkLGlTpEvV J/fZDYCB+iiZeIql2/3Kl+R6MZiwwXMVrr9ji+C68zwdKTs2CSys0JSsAp6qaTx7n5Nx Msn+gr3ieYFHtvz9c0B84tavKwEFNd0X7qqunDJFEAiADrxNSDGdyiwxOGY64N2LiUsY sKmzhGcaAx1YJc1PkjNK8FqHFZ8OI086iLvsPng9YI1B9g4tQr0NyTpx+Kjb90obmpdB Q6Wm/H2+RcnLYpNVwkd6+2JNYOo5YaGRAI7CsZZeFH0+1XFs0pp9wvuEroWpSeaaAdtT dfSQ== MIME-Version: 1.0 Received: by 10.14.180.68 with SMTP id i44mr27579449eem.20.1347393836888; Tue, 11 Sep 2012 13:03:56 -0700 (PDT) Received: by 10.14.219.134 with HTTP; Tue, 11 Sep 2012 13:03:56 -0700 (PDT) In-Reply-To: <20120911195836.GQ44854@FreeBSD.org> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> Date: Tue, 11 Sep 2012 13:03:56 -0700 Message-ID: From: Vijay Singh To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" , Adrian Chadd , Dominic Blais Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 20:03:58 -0000 > V> > V> Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 > > Why do you suspect this one? I was hitting a similar issue in 8.2. After down/up on the interface to the default gateway, I saw this message and arpresolve would never complete. I was able to step through gdb to see that the RTF_GATEWAY check was causing the problem. -vijay From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 20:05:46 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC5BA1065670; Tue, 11 Sep 2012 20:05:46 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 5C6328FC0C; Tue, 11 Sep 2012 20:05:46 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8BK5jhB080127; Wed, 12 Sep 2012 00:05:45 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8BK5jD4080126; Wed, 12 Sep 2012 00:05:45 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 12 Sep 2012 00:05:45 +0400 From: Gleb Smirnoff To: Vijay Singh Message-ID: <20120911200545.GT44854@glebius.int.ru> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-net@freebsd.org" , Adrian Chadd , Dominic Blais Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 20:05:47 -0000 On Tue, Sep 11, 2012 at 01:03:56PM -0700, Vijay Singh wrote: V> > V> V> > V> Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 V> > V> > Why do you suspect this one? V> V> I was hitting a similar issue in 8.2. After down/up on the interface V> to the default gateway, I saw this message and arpresolve would never V> complete. I was able to step through gdb to see that the RTF_GATEWAY V> check was causing the problem. Hmm, interesting. We need more debugging here. But where from could 65.59.233.102 appear? -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 21:11:06 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12AF21065670; Tue, 11 Sep 2012 21:11:06 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE8D8FC17; Tue, 11 Sep 2012 21:11:05 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 794D0761BF; Tue, 11 Sep 2012 23:03:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id l83ILkMaGR0A; Tue, 11 Sep 2012 23:03:55 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id 00ED3761B1; Tue, 11 Sep 2012 23:03:54 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 3E98319C5A2; Tue, 11 Sep 2012 11:18:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id 3i2Ys1yXIIKc; Tue, 11 Sep 2012 11:18:10 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id 1AF0519C59E; Tue, 11 Sep 2012 11:18:07 +0200 (CEST) Message-ID: <504FA735.709@zirakzigil.org> Date: Tue, 11 Sep 2012 23:03:49 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 21:11:06 -0000 Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --------------------------------------------------- ifconfig_igb0="inet ..." ifconfig_igb1="up" ifconfig_igb2="up" ifconfig_igb3="up" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24" sshd_enable="YES" --------------------------------------------------- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. This installation is a zfs root, but I don't think this has anything to do with this. Yes, I think that the maintainer of igb and/or lagg driver should absolutely look into this... On 09/07/2012 12:01 PM, Simon Dick wrote: > We've had similar problems with lagg at work, each lagg is made up of > one igb and one em port, sometimes for no apparent reason they seem to > stop passing through traffic. The easiest way we've found to get it > working again is ifconfig down and up on one of the physical > interfaces. This is on 8.1 > > On 3 September 2012 19:25, Giulio Ferro wrote: >> No idea anybody why this bug happens? Patches? >> >> >> >> On 08/29/2012 10:22 PM, Giulio Ferro wrote: >>> >>> On 08/28/2012 11:12 AM, Damien Fleuriot wrote: >>>> >>>> Hi Giulio, >>>> >>>> >>>> >>>> Just to clear things up: >>>> igb0: 192.168.9.60/24 >>>> lagg0: 192.168.12.21/24 >>>> >>> >>> Yes. >>> Actually I notice now that the lagg0 address is different from what >>> I wrote below in my rc.conf (192.168.12.7). I've just made many test >>> with different configuration, but no matter, it just doesn't work... >>> >>> >>>> >>>> What's the IP of the host you're trying ssh connections from ? >>> >>> >>> I'm just trying to connect to and from management interface igb0 >>> (192.168.9.60). >>> From external pc I do : ssh myuser@192.168.9.60 >>> From that server I do : ssh myuser@pcaddress >>> >>> Just to be more precise, the consequences are: >>> 1) daemon sshd on the server gets stuck and becomes unkillable >>> 2) the first connection may work, but then the program ssh on the >>> server becomes unresponsive and unkillable >>> >>> If I don't create a lagg0 interface and just connect (say) igb1 to >>> the data switch, I've no problem and everything works. >>> >>> Just to answer others' question, I connect igb1, igb2 and igb3 to the >>> same data switch in ports configured for aggregation. >>> I connect igb0 to another management switch (of course not configured >>> for aggregation) >>> >>> >>>> >>>> Also, just in case, did you enable any firewall ? (PF, ipfw) >>> >>> >>> As I already said, no. Nothing is working/active on this server, just >>> sshd. >>> >>> Thank you. >>> >>> >>>> >>>> >>>> >>>> On 27 August 2012 21:22, Giulio Ferro wrote: >>>>> >>>>> Hi, thanks for the answer >>>>> >>>>> Here is what you asked for: >>>>> >>>>> # ifconfig igb0 >>>>> igb0: flags=8843 metric 0 mtu >>>>> 1500 >>>>> >>>>> >>>>> options=4401bb >>>>> >>>>> ether ... >>>>> inet 192.168.9.60 netmask 0xffffff00 broadcast 192.168.9.255 >>>>> inet6 .... prefixlen 64 scopeid 0x1 >>>>> nd6 options=29 >>>>> media: Ethernet autoselect (1000baseT ) >>>>> status: active >>>>> >>>>> >>>>> >>>>> # netstat -rn >>>>> Routing tables >>>>> >>>>> Internet: >>>>> Destination Gateway Flags Refs Use Netif >>>>> Expire >>>>> default 192.168.9.1 UGS 0 0 igb0 >>>>> 127.0.0.1 link#12 UH 0 0 lo0 >>>>> 192.168.9.0/24 link#1 U 0 14 igb0 >>>>> 192.168.9.60 link#1 UHS 0 0 lo0 >>>>> 192.168.12.0/24 link#13 U 0 109 lagg0 >>>>> 192.168.12.21 link#13 UHS 0 0 lo0 >>>>> >>>>> Internet6: >>>>> Destination Gateway Flags >>>>> Netif Expire >>>>> ::/96 ::1 >>>>> UGRS lo0 >>>>> ::1 link#12 >>>>> UH lo0 >>>>> ::ffff:0.0.0.0/96 ::1 >>>>> UGRS lo0 >>>>> fe80::/10 ::1 >>>>> UGRS lo0 >>>>> fe80::%igb0/64 link#1 U >>>>> igb0 >>>>> fe80::ea39:35ff:feb6:a0d4%igb0 link#1 >>>>> UHS lo0 >>>>> fe80::%igb1/64 link#2 U >>>>> igb1 >>>>> fe80::ea39:35ff:feb6:a0d5%igb1 link#2 >>>>> UHS lo0 >>>>> fe80::%igb2/64 link#3 U >>>>> igb2 >>>>> fe80::ea39:35ff:feb6:a0d6%igb2 link#3 >>>>> UHS lo0 >>>>> fe80::%igb3/64 link#4 U >>>>> igb3 >>>>> fe80::ea39:35ff:feb6:a0d7%igb3 link#4 >>>>> UHS lo0 >>>>> fe80::%lo0/64 link#12 U >>>>> lo0 >>>>> fe80::1%lo0 link#12 >>>>> UHS lo0 >>>>> fe80::%lagg0/64 link#13 U >>>>> lagg0 >>>>> fe80::ea39:35ff:feb6:a0d5%lagg0 link#13 >>>>> UHS lo0 >>>>> ff01::%igb0/32 fe80::ea39:35ff:feb6:a0d4%igb0 >>>>> U igb0 >>>>> ff01::%igb1/32 fe80::ea39:35ff:feb6:a0d5%igb1 >>>>> U igb1 >>>>> ff01::%igb2/32 fe80::ea39:35ff:feb6:a0d6%igb2 >>>>> U igb2 >>>>> ff01::%igb3/32 fe80::ea39:35ff:feb6:a0d7%igb3 >>>>> U igb3 >>>>> ff01::%lo0/32 ::1 U >>>>> lo0 >>>>> ff01::%lagg0/32 fe80::ea39:35ff:feb6:a0d5%lagg0 U >>>>> lagg0 >>>>> ff02::/16 ::1 >>>>> UGRS lo0 >>>>> ff02::%igb0/32 fe80::ea39:35ff:feb6:a0d4%igb0 >>>>> U igb0 >>>>> ff02::%igb1/32 fe80::ea39:35ff:feb6:a0d5%igb1 >>>>> U igb1 >>>>> ff02::%igb2/32 fe80::ea39:35ff:feb6:a0d6%igb2 >>>>> U igb2 >>>>> ff02::%igb3/32 fe80::ea39:35ff:feb6:a0d7%igb3 >>>>> U igb3 >>>>> ff02::%lo0/32 ::1 U >>>>> lo0 >>>>> ff02::%lagg0/32 fe80::ea39:35ff:feb6:a0d5%lagg0 U >>>>> lagg0 >>>>> >>>>> >>>>> >>>>> # netstat -aln | grep 22 >>>>> tcp4 0 0 *.22 *.* LISTEN >>>>> tcp6 0 0 *.22 *.* LISTEN >>>>> >>>>> Note that I already tried to only listen on igb0 interface >>>>> (192.168.9.60) in >>>>> sshd_config, but the results are exactly >>>>> the same described below. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 08/25/2012 01:22 PM, Damien Fleuriot wrote: >>>>>> >>>>>> >>>>>> In the meantime kindly post: >>>>>> >>>>>> >>>>>> Ifconfig for your igb0 >>>>>> Netstat -rn >>>>>> Netstat -aln | grep 22 >>>>>> >>>>>> >>>>>> >>>>>> On 25 Aug 2012, at 13:18, Damien Fleuriot wrote: >>>>>> >>>>>>> I'll get back to you regarding link aggregation when I'm done with >>>>>>> groceries. >>>>>>> >>>>>>> We use it here in production and it works flawlessly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 25 Aug 2012, at 09:54, Giulio Ferro wrote: >>>>>>> >>>>>>>> No answer, so it seems that link aggregation doesn't really work in >>>>>>>> freebsd, >>>>>>>> this may help others with the same problem... >>>>>>>> >>>>>>>> I reverted back to one link for management and one for service, >>>>>>>> and ssh >>>>>>>> works as it should... >>>>>>>> >>>>>>>> >>>>>>>> On 08/21/2012 11:18 PM, Giulio Ferro wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 >>>>>>>>> nic >>>>>>>>> (igb) >>>>>>>>> >>>>>>>>> 1 nic is connected standalone to the management switch, the 3 other >>>>>>>>> nics >>>>>>>>> are connected to a switch configured for aggregation. >>>>>>>>> >>>>>>>>> If I configure the first nic (igb0) there is no problem, I can >>>>>>>>> operate >>>>>>>>> as I normally do and sshd functions normally. >>>>>>>>> >>>>>>>>> The problems start when I configure the 3 other nics for >>>>>>>>> aggregation: >>>>>>>>> >>>>>>>>> in /etc/rc.conf >>>>>>>>> ... >>>>>>>>> ifconfig_igb1="up" >>>>>>>>> ifconfig_igb2="up" >>>>>>>>> ifconfig_igb3="up" >>>>>>>>> >>>>>>>>> cloned_interfaces=lagg0 >>>>>>>>> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport >>>>>>>>> igb3 192.168.12.7/24" >>>>>>>>> ... >>>>>>>>> >>>>>>>>> I restart the server and the aggregation seems to work correctly, in >>>>>>>>> fact ifconfig returns the correct lagg0 interface with the >>>>>>>>> aggregated >>>>>>>>> links, the correct protocol (lacp) and the correct ip address and >>>>>>>>> the >>>>>>>>> status is active. I can ping other IPs on the aggregated link. >>>>>>>>> >>>>>>>>> Also the other (standalone) link seems to work correctly. I can ping >>>>>>>>> that address from other machines, and I can ping other IPs from that >>>>>>>>> server. >>>>>>>>> >>>>>>>>> DNS lookups work ok too I can also use telnet to connect to pop3 >>>>>>>>> servers so there seems to be no problem on the network stack. >>>>>>>>> >>>>>>>>> But if I try to connect to the sshd service on that server, it hangs >>>>>>>>> indefinitely. On the server I find two sshd processes: >>>>>>>>> /usr/sbin/sshd >>>>>>>>> /usr/sbin/sshd -R >>>>>>>>> >>>>>>>>> There is no message in the logs. >>>>>>>>> >>>>>>>>> If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays >>>>>>>>> there >>>>>>>>> forever waiting for the pid to die (it never does) >>>>>>>>> >>>>>>>>> Even ssh client doesn't seem to work. In fact, if I try to >>>>>>>>> connect to >>>>>>>>> another server, the ssh client may start to work correctly, then >>>>>>>>> soon >>>>>>>>> or later it just hangs there forever, and I can't kill it with >>>>>>>>> ctrl-c. >>>>>>>>> >>>>>>>>> No firewall is configured, there is nothing else working on this >>>>>>>>> server. >>>>>>>>> >>>>>>>>> Thanks for any suggestions... >>>>>>>>> _______________________________________________ >>>>>>>>> freebsd-stable@freebsd.org mailing list >>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>>>>>>> To unsubscribe, send any mail to >>>>>>>>> "freebsd-stable-unsubscribe@freebsd.org" >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> freebsd-stable@freebsd.org mailing list >>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>>>>>> To unsubscribe, send any mail to >>>>>>>> "freebsd-stable-unsubscribe@freebsd.org" >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> freebsd-net@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 21:35:06 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9D31065687; Tue, 11 Sep 2012 21:35:04 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7492B8FC14; Tue, 11 Sep 2012 21:35:02 +0000 (UTC) Received: by lage12 with SMTP id e12so800495lag.13 for ; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SVzeH5cmM2D0ZPhsfhkp7Gv5uAsZy841C3JfYr/6dQw=; b=E/58jLEHRy+gw0fww1QzO5TjVAZwa8STbHtxuyP6wa4fwSKMQngG0dUYT8SWLiHXSz Ow899UsQCZZ3HE8PoJWmFEZaiW0HFSYJNTJrf6Y3DHc3Asc8fMrBY70w6/n8F/7H5fEC 5GsGdFYAly13n2NuNhoXWzZFVwCriz2+3RaZb3D5x1p64RsNFR09H3nkB71YNwcTv61V 8ebe7MglymIjeOtWoXWGpUhNZbnYBfjV8tVDu8DGQrOAeLo3Frn3pg6aLeRnnniE/B1L s+c63pt2Xd8vVXJR+GMqYuCcBKNE0MZjNbI2ExNJMSIlRGQ4g6nuAW0iit8frX/5mTf1 cq9g== MIME-Version: 1.0 Received: by 10.152.103.11 with SMTP id fs11mr16903975lab.23.1347399296233; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) In-Reply-To: <504FA735.709@zirakzigil.org> References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> Date: Tue, 11 Sep 2012 14:34:56 -0700 Message-ID: From: Freddie Cash To: Giulio Ferro Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 21:35:06 -0000 On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: > > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24" > > sshd_enable="YES" > --------------------------------------------------- > > This doesn't even manage to start sshd, it just hangs there at boot. > > Disabling lagg configuration everything works correctly. > Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0="laggproto ..." ifconfig_lagg0_alias0="inet 192..." I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 22:09:35 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BB87106566B; Tue, 11 Sep 2012 22:09:35 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id D0C068FC08; Tue, 11 Sep 2012 22:09:34 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.5/8.14.5/NETPLEX) with ESMTP id q8BM9R3r038987; Tue, 11 Sep 2012 18:09:27 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.7 (mail.netplex.net [204.213.176.10]); Tue, 11 Sep 2012 18:09:28 -0400 (EDT) Date: Tue, 11 Sep 2012 18:09:27 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Giulio Ferro In-Reply-To: <504FA735.709@zirakzigil.org> Message-ID: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 22:09:35 -0000 On Tue, 11 Sep 2012, Giulio Ferro wrote: > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0="ether 01:02:03:04:05:06" wlans_ath0=wlan0 ifconfig_wlan0="ssid SSID_FOO_NAME WPA" ifconfig_xl0="up" closed_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport xl0 laggport wlan0" ifconfig_lagg0_alias0="inet 10.0.0.4 netmask 0xffffff00" I use aliasX to add the address and netmask. -- DE From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 22:12:16 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BD011065673; Tue, 11 Sep 2012 22:12:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0A59A8FC0A; Tue, 11 Sep 2012 22:12:15 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.5/8.14.5/NETPLEX) with ESMTP id q8BMCFDq041313; Tue, 11 Sep 2012 18:12:15 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.7 (mail.netplex.net [204.213.176.10]); Tue, 11 Sep 2012 18:12:15 -0400 (EDT) Date: Tue, 11 Sep 2012 18:12:15 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Freddie Cash In-Reply-To: Message-ID: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 22:12:16 -0000 On Tue, 11 Sep 2012, Freddie Cash wrote: > On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: >> >> cloned_interfaces="lagg0" >> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 > 192.168.x.x/24" >> >> sshd_enable="YES" >> --------------------------------------------------- >> >> This doesn't even manage to start sshd, it just hangs there at boot. >> >> Disabling lagg configuration everything works correctly. >> > > Just curious: does it work if you split the lagg configuration from the IP > config: > > ifconfig_lagg0="laggproto ..." > ifconfig_lagg0_alias0="inet 192..." > > I've had problems in the past with cloned interfaces not working right if > you do everything in one ifconfig line. Never spent much time debugging it, > though, as the split config always worked. This was my experience too, though it's been quite a while since I tried it combined onto the same ifconfig line. -- DE From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 23:33:19 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2353A1065672 for ; Tue, 11 Sep 2012 23:33:19 +0000 (UTC) (envelope-from returns@a.eb04.executivemailingservices.com) Received: from a.eb04.executivemailingservices.com (a.eb04.executivemailingservices.com [204.14.111.66]) by mx1.freebsd.org (Postfix) with ESMTP id CE7A18FC16 for ; Tue, 11 Sep 2012 23:33:18 +0000 (UTC) Received: by a.eb04.executivemailingservices.com (Postfix, from userid 0) id 181A263FCD; Wed, 12 Sep 2012 01:17:58 +0200 (SAST) To: freebsd-net@freebsd.org Message-ID: <1347405478_SectionID-1182759_HitID-1347400007850_SiteID-205248_EmailID-146747893_DB-2_SID-1@eb04.executivemailingservices.com> X-Report-Abuse: Please report abuse for this campaign here: http://a.eb04.executivemailingservices.com/reportabuse.aspx?stid=205248&hitid=1347400007850&sec=1182759&email=freebsd-net@freebsd.org&EmID=146747893&SID=1&token=0e3934e1622a93ef448eb5ce65cccdae4a14888c DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=eb04.executivemailingservices.com; i=@eb04.executivemailingservices.com; q=dns/txt; s=ebmailerd; t=1347405394; h=From; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; l=0; b=Ur4KNVqGW6nkC+KN/Qu+4XQ8V2SfRKI7N/UsNiaQGM1THaJwbGON9Jb1WoGXw8Q+hq5goWD1Bel7b80a/W+Y3U4dyZ0oZu1Z7uGZvmMOkr9z1YCO36wO5kln4IujyAs8unXHcQagTXAW6pmozl389ELJUGhD6nRHOLLKALLAd4o= From: "RCBC" Mime-Version: 1.0 Date: Wed, 12 Sep 2012 01:17:58 +0200 (SAST) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Account Closed * (SECURITY NOTICE) * X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2012 23:33:19 -0000 =0AYour email program does not support HTML. To view an online version of = this email, please click the link below.=0Ahttp://a.eb04.executivemailingse= rvices.com/new/en_send_preview_iframe2.aspx?SID=3D1&NewsletterID=3D1182759&= SiteID=3D205248&EmailID=3D146747893&HitID=3D1347400007850&token=3D0e3934e16= 22a93ef448eb5ce65cccdae4a14888c=0A=0ATo unsubscribe, click the link below.= =0Ahttp://a.eb04.executivemailingservices.com/RWCode/subscribe.asp?SID=3D1&= SiteID=3D205248&Email=3Dfreebsd-net@freebsd.org&HitID=3D1347400007850 From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 06:07:10 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FFD41065672 for ; Wed, 12 Sep 2012 06:07:10 +0000 (UTC) (envelope-from oppermann@networx.ch) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id C370E8FC1A for ; Wed, 12 Sep 2012 06:07:09 +0000 (UTC) Received: (qmail 88989 invoked from network); 12 Sep 2012 07:52:35 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Sep 2012 07:52:35 -0000 Message-ID: <50502682.4010103@networx.ch> Date: Wed, 12 Sep 2012 08:06:58 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Jeremiah Lott References: <201204270607.q3R67TiO026862@freefall.freebsd.org> <8339513D-6727-4343-A86E-4F5BB1F9827D@averesystems.com> In-Reply-To: <8339513D-6727-4343-A86E-4F5BB1F9827D@averesystems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/167325: [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 06:07:10 -0000 On 07.09.2012 23:44, Jeremiah Lott wrote: > On Apr 27, 2012, at 2:07 AM, linimon@FreeBSD.org wrote: > >> Old Synopsis: sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC New Synopsis: >> [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=167325 > > I did an analysis of this pr a while back and I figured I'd share. Definitely looks like a real > problem here, but at least in 8.2 it is difficult to hit it. First off, vlan tagging is not > required to hit this. The code is question does not account for any amount of link-local header, > so you can reproduce the bug even without vlans. > > In order to trigger it, the tcp stack must choose to send a tso "packet" with a total size > (including tcp+ip header and options, but not link-local header) between 65522 and 65535 bytes > (because adding 14 byte link-local header will then exceed 64K limit). In 8.1, the tcp stack > only chooses to send tso bursts that will result in full mtu-size on-wire packets. To achieve > this, it will truncate the tso packet size to be a multiple of mss, not including header and tcp > options. The check has been relaxed a little in head, but the same basic check is still there. > None of the "normal" mtus have multiples falling in this range. To reproduce it I used an mtu of > 1445. When timestamps are in use, every packet has a 40 bytes tcp/ip header + 10 bytes for the > timestamp option + 2 bytes pad. You can get a packet length 65523 as follows: > > 65523 - (40 + 10 + 2) = 65471 (size of tso packet data) 65471 / 47 = 1393 (size of data per > on-wire packet) 1393 + (40 + 10 + 2) = 1445 (mtu is data + header + options + pad) > > Once you set your mtu to 1445, you need a program that can get the stack to send a maximum sized > packet. With the congestion window that can be more difficult than it seems. I used some python > that sends enough data to open the window, sleeps long enough to drain all outstanding data, but > not long enough for the congestion window to go stale and close again, then sends a bunch more > data. It also helps to turn off delayed acks on the receiver. Sometimes you will not drain the > entire send buffer because an ack for the final chunk is still delayed when you start the second > transmit. When the problem described in the pr hits, the EINVAL from bus_dmamap_load_mbuf_sg > bubbles right up to userspace. > > At first I thought this was a driver bug rather than stack bug. The code in question does what > it is commented to do (limit the tso packet so that ip->ip_len does not overflow). However, it > also seems reasonable that the driver limit its dma tag at 64K (do we really want it allocating > another whole page just for the 14 byte link-local header). Perhaps the tcp stack should ensure > that the tso packet + max_linkhdr is < 64K. Comments? Thank you for the analysis. I'm looking into it. > As an aside, the patch attached to the pr is also slightly wrong. Taking the max_linkhdr into > account when rounding the packet to be a multiple of mss does not make sense, it should only take > it into account when calculating the max tso length. -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 09:05:51 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A7CB1065672; Wed, 12 Sep 2012 09:05:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 954518FC08; Wed, 12 Sep 2012 09:05:50 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:31e6:f1e:dd72:edd6]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 4A1054AC2D; Wed, 12 Sep 2012 13:05:49 +0400 (MSK) Date: Wed, 12 Sep 2012 13:05:45 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <416897292.20120912130545@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <1865271844.20120829131610@serebryakov.spb.ru> <1807373989.20120829223125@serebryakov.spb.ru> <20120830152726.A33776@sola.nimnet.asn.au> <534292400.20120830131158@serebryakov.spb.ru> <20120831180721.GB3208@michelle.cdnetworks.com> <50404F91.8080302@rdtc.ru> <20120903184049.GB3730@michelle.cdnetworks.com> <50443888.9080400@rdtc.ru> <20120903214333.GC3730@michelle.cdnetworks.com> <5044772C.8090302@rdtc.ru> <5046FE57.3050903@rdtc.ru> <5048D7A7.1030708@rdtc.ru> <5048DFF8.50405@smeets.im> <10710514011.20120906220055@serebryakov.spb.ru> <1828371828.20120906221136@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Scheduler KTR traces for 4 variants (ULE, 4BSD)x(PREEMPTION, NOPREEMPTION) on small hardware (net5501) with network traffic (Was: vr(4) troubles for AMD Geode CS5536 chipset) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 09:05:51 -0000 Hello, Adrian. You wrote 6 =D3=C5=CE=D4=D1=C2=D2=D1 2012 =C7., 22:12:04: AC> On 6 September 2012 11:11, Lev Serebryakov wrote: >> Hello, Adrian. >> You wrote 6 =D3=C5=CE=D4=D1=C2=D2=D1 2012 =C7., 22:07:08: >> >> AC> Oh don't worry about polling just yet. I just want to see what >> AC> preempt/no-preempt does with ULE and 4BSD on these little single-CPU >> AC> platforms. >> Ok, I'll do it. Should I post 4 outputs from ktrdump? Again, I don't >> understand how to interpret these data by myself. AC> Yes. Here: http://lev.serebryakov.spb.ru/ktrs/ Tarball with all 4 outputs and all configs are placed. Setup and results are described in "readme.txt". Results are strange: no visible WiFi slowdown but wired traffic slowdown now and bad freezes in all combinations but 4BSD + PREEMPTION _enabled_. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 09:13:51 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D4BC5106566C for ; Wed, 12 Sep 2012 09:13:51 +0000 (UTC) (envelope-from adpacifyer@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 947888FC08 for ; Wed, 12 Sep 2012 09:13:51 +0000 (UTC) Received: by obbun3 with SMTP id un3so2841066obb.13 for ; Wed, 12 Sep 2012 02:13:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=epHM+r2bT+Yvg4OVacEes4qwpW6uY9cWhHqoWmOiJ9I=; b=OGW6lRo4eomfdfuEDcyiKvrK6tkA+7hP0fRBvLKqJngO/efGqQi9JzQW4bw+XRN1IF wcLB3fxYSwYVNlum1MNE9HoZxDyNjE0h1RZgFR2fd64ijOuRsSadCH9d6RSK8RA8I8TM s2xdJ++Ep72sliQOVOc9jK1w3iSxy6Xo3YQ3iv6yy+wRikPcAtWx5GPNYzAjWIzToKbJ miGK4DZoUpNpEMGwl5/t0qNZbNih25kpuWTC/IQvp8u6QpRTHe/tNSuULPfkgE5cHXuP lWqYcy9ryzfGN32DCP7Ggwr2HfY4+iBEjdvek0gipil1z6g5OIy34pI7C/Lm7vBrwaTG JzIA== MIME-Version: 1.0 Received: by 10.60.31.39 with SMTP id x7mr21758055oeh.66.1347441230706; Wed, 12 Sep 2012 02:13:50 -0700 (PDT) Received: by 10.76.11.10 with HTTP; Wed, 12 Sep 2012 02:13:50 -0700 (PDT) Date: Wed, 12 Sep 2012 12:13:50 +0300 Message-ID: From: Oleg Tarasov To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IPFW NAT instances sharing same aliasing table problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 09:13:51 -0000 Hi all, I have a network with two gateways. GW1 is primary gateway and GW2 is secondary. I need to be able to map GW2 port to a service inside of my network. That is done using redirect_port NAT directive but the problem is that all computers inside the network have a default gateway pointing to GW1 so returning packets are routed through GW1 and the goal is not achieved. So the solution to this situation is a second NAT instance on GW2 masquarading sender IP address with the internal address of GW2. Here is the picture. Internet | | | em0 (a.b.c.d) GW2 | em1 (192.168.0.2) | | | 192.168.0.111 Service So basicly what comes into mind: ipfw nat 1 config ip a.b.c.d redirect_port 192.168.0.111:80 80 ipfw nat 2 config ip 192.168.0.2 ... ipfw add 300 nat 1 all from any to any via em0 ipfw add 301 nat 2 all from any to 192.168.0.111 80 out via em1 ipfw add 302 nat 2 all from 92.168.0.111 80 to me in via em1 ... I have given an example (which will probably not work) just to give a basic idea of how can the goal be achieved. But here we meet something unexpected. When the packets are passed to nat 2 they probably meet already existing entry formed by nat 1 and no actual action is performed. I have been struggling against a wall to make this work but could not get it working thist way. But one day I tried replacing nat 2 instance with natd daemon divert and everything instantly started working. So it seems ipfw nat instances share the same aliasing table like it should do when using global option. IMO this should be fixed. P.S. Maybe I was missing some unclear option to prevent this from happening? From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 09:15:14 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 080411065680; Wed, 12 Sep 2012 09:15:14 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6D98FC19; Wed, 12 Sep 2012 09:15:13 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.5/8.14.5) with ESMTP id q8C9FBxu063402 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 12 Sep 2012 10:15:12 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <5050529F.20900@unsane.co.uk> Date: Wed, 12 Sep 2012 10:15:11 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Giulio Ferro References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> In-Reply-To: <504FA735.709@zirakzigil.org> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 09:15:14 -0000 On 11/09/2012 22:03, Giulio Ferro wrote: > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > igb3 192.168.x.x/24" > > sshd_enable="YES" > --------------------------------------------------- > > This doesn't even manage to start sshd, it just hangs there at boot. > > Disabling lagg configuration everything works correctly. For what is worth its working fine for me on 8.3-RELEASE using failover. ifconfig_igb0="up" ifconfig_igb1="up" cloned_interfaces="lagg0 lagg0.53 lagg0.52 lagg0.66" ifconfig_lagg0="laggproto failover laggport igb0 laggport igb1 85.233.xxx.xxx/23" ifconfig_lagg0_53="inet 192.168.xxx.226/24" ifconfig_lagg0_52="inet 192.168.xxx.254/24" ifconfig_lagg0_66="inet 192.168.xxx.250/24" ipv4_addrs_lagg0_52="192.168.xxx.254/24 192.168.0.70/24" lagg0: flags=8843 metric 0 mtu 1500 options=401bb ether 00:25:90:39:64:76 inet 85.233.xx.xx netmask 0xfffffe00 broadcast 85.233.xx.255 media: Ethernet autoselect status: active laggproto failover laggport: igb1 flags=0<> laggport: igb0 flags=5 Vince From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 10:28:25 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A1A71065672; Wed, 12 Sep 2012 10:28:25 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id EEF7E8FC18; Wed, 12 Sep 2012 10:28:24 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id 4448850916; Wed, 12 Sep 2012 06:28:23 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id D0E1E508B4; Wed, 12 Sep 2012 06:28:22 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Wed, 12 Sep 2012 06:28:21 -0400 From: Dominic Blais To: Gleb Smirnoff , Vijay Singh Date: Wed, 12 Sep 2012 06:28:15 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QV9hNg6yz3+vBTKid2eQK9MzOqAAeR3oQ Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDC6@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> In-Reply-To: <20120911195836.GQ44854@FreeBSD.org> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Adrian Chadd Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 10:28:25 -0000 Hi! Here's what I got seconds prior/while it happened this morning: got message of size 24 on Wed Sep 12 00:15:49 2012 RTM_IFANNOUNCE: interface arrival/departure: len 24, if# 37, what: arrival got message of size 168 on Wed Sep 12 00:15:49 2012 RTM_IFINFO: iface status change: len 168, if# 37, link: unknown, flags: got message of size 184 on Wed Sep 12 00:15:49 2012 RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default default default ### <- This looks normal, I usually = see it when customers connect to ### pppoe from MPD. got message of size 100 on Wed Sep 12 00:15:49 2012 RTM_DELADDR: address being removed from iface: len 100, metric 0, flags: sockaddrs: default ng30 default default got message of size 184 on Wed Sep 12 00:15:49 2012 RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default default default got message of size 108 on Wed Sep 12 00:15:49 2012 RTM_DELADDR: address being removed from iface: len 108, metric 0, flags: sockaddrs: 255.255.255.255 ng30 default default got message of size 116 on Wed Sep 12 00:15:49 2012 RTM_NEWADDR: address being added to iface: len 116, metric 0, flags: sockaddrs: 255.255.255.255 ng30 10.0.0.1 192.168.50.29 got message of size 224 on Wed Sep 12 00:15:49 2012 RTM_ADD: Add Route: len 224, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: 192.168.50.29 got message of size 88 on Wed Sep 12 00:15:49 2012 RTM_NEWMADDR: new multicast group membership on iface: len 88, sockaddrs: ng30 224.0.0.1 got message of size 148 on Wed Sep 12 00:15:49 2012 RTM_NEWADDR: address being added to iface: len 148, metric 0, flags: sockaddrs: ffff:ffff:ffff:ffff:: ng30 fe80::223:7dff:fee0:54de%ng30 default got message of size 272 on Wed Sep 12 00:15:49 2012 RTM_ADD: Add Route: len 272, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: fe80::223:7dff:fee0:54de%ng30 0.0.0.0.0.0 ffff:ffff:ffff:ffff:: got message of size 104 on Wed Sep 12 00:15:49 2012 RTM_NEWMADDR: new multicast group membership on iface: len 104, sockaddrs: ng30 ff02::1:ffe0:54de%ng30 got message of size 104 on Wed Sep 12 00:15:49 2012 RTM_NEWMADDR: new multicast group membership on iface: len 104, sockaddrs: ng30 ff02::1%ng30 got message of size 104 on Wed Sep 12 00:15:49 2012 RTM_NEWMADDR: new multicast group membership on iface: len 104, sockaddrs: ng30 ff02::2:5f65:5bb1%ng30 got message of size 104 on Wed Sep 12 00:15:49 2012 RTM_NEWMADDR: new multicast group membership on iface: len 104, sockaddrs: ng30 ff01:25::1 got message of size 344 on Wed Sep 12 00:15:49 2012 RTM_ADD: Add Route: len 344, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: fe80::%ng30 (255) ffff ffff ffff ffff ffff ffff ffff ng30 fe80::223:7dff:= fee0:54de%ng30 -- -----Message d'origine----- De=A0: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Envoy=E9=A0: 11 septembre 2012 15:59 =C0=A0: Vijay Singh Cc=A0: Adrian Chadd; freebsd-net@freebsd.org; Dominic Blais Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On Tue, Sep 11, 2012 at 10:35:25AM -0700, Vijay Singh wrote: V> On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrot= e: V> > On 11 September 2012 09:01, Dominic Blais wrote: V> >> I could do something about the route monitor but not the fstat | grep= route... I mean, I would have to run it in a loop endlessly until the bug = happens... Even with it, it's not even sure I would catch it... V> > V> > The route monitor is a good idea. It should tell us whether it's=20 V> > from some tool/program/network event sending a routing table=20 V> > update, or whether it's just plain memory corruption. V>=20 V> Could this be=20 V> http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=3D226120&r2=3D22= 6 V> 224&pathrev=3D226331 Why do you suspect this one? -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 12:19:35 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C57D106566C for ; Wed, 12 Sep 2012 12:19:35 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (smtp.zeninc.net [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4FBBD8FC12 for ; Wed, 12 Sep 2012 12:19:34 +0000 (UTC) Received: from ken (ken.zen.inc [192.168.1.4]) by smtp.zeninc.net (smtpd) with ESMTP id D2CD92798BC; Wed, 12 Sep 2012 14:19:27 +0200 (CEST) Received: by ken (Postfix, from userid 1000) id A92D34040; Wed, 12 Sep 2012 14:19:27 +0200 (CEST) Date: Wed, 12 Sep 2012 14:19:27 +0200 From: VANHULLEBUS Yvan To: Andreas Longwitz Message-ID: <20120912121927.GA3968@zeninc.net> References: <50474D5C.4020003@incore.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50474D5C.4020003@incore.de> User-Agent: All mail clients suck. This one just sucks less. Cc: freebsd-net@freebsd.org Subject: Re: Support for IPSec VPN's: some patches for netipsec/key.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 12:19:35 -0000 Hi. On Wed, Sep 05, 2012 at 03:02:20PM +0200, Andreas Longwitz wrote: [...] > The last patch makes it possible for a transport mode client to open a > new connection to the server immediately after closing an old > connection. Without this patch the client must wait for the routers to > forget all there NAT entries. > > @@ -4065,10 +4084,12 @@ > /* > * If NAT-T is enabled, check ports for tunnel mode. > * Do not check ports if they are set to zero in the SPD. > - * Also do not do it for transport mode, as there is no > + * Also do not do it for native transport mode, as there is no > * port information available in the SP. > */ > - if (saidx1->mode == IPSEC_MODE_TUNNEL && > + if ((saidx1->mode == IPSEC_MODE_TUNNEL || > + (saidx1->mode == IPSEC_MODE_TRANSPORT && > + saidx1->proto == IPPROTO_ESP)) && > saidx1->src.sa.sa_family == AF_INET && > saidx1->dst.sa.sa_family == AF_INET && > ((const struct sockaddr_in *)(&saidx1->src))->sin_port && Sorry for the delay, I just commited it on HEAD. Thanks for the patch, I'll try to take time to have a look at your other patches/issues ASAP, feel free to send updated versions, mail me, etc.... Yvan. From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 12:34:59 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C84B9106564A; Wed, 12 Sep 2012 12:34:59 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 414CE8FC12; Wed, 12 Sep 2012 12:34:59 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8CCYvmc086362; Wed, 12 Sep 2012 16:34:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8CCYvuM086361; Wed, 12 Sep 2012 16:34:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 12 Sep 2012 16:34:57 +0400 From: Gleb Smirnoff To: net@FreeBSD.org, luigi@FreeBSD.org Message-ID: <20120912123457.GC85604@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "Bjoern A. Zeeb" Subject: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 12:34:59 -0000 Hi, we (me and Bjoern) would like to establish a single place for all kinds of pfil(9) consumers, for current ones and for future as well. The place chosen is sys/netpfil. On first round we'd like to move there our Tier-1 firewalls: ipfw and pf. This also includes moving pf out of contrib. The plan of movement is the following: sys/contrib/pf/net/*.c -> sys/netpfil/pf/ sys/contrib/pf/net/*.h -> sys/net/ [1] contrib/pf/pfctl/*.c -> sbin/pfctl contrib/pf/pfctl/*.h -> sbin/pfctl contrib/pf/pfctl/pfctl.8 -> sbin/pfctl contrib/pf/pfctl/*.4 -> share/man/man4 contrib/pf/pfctl/*.5 -> share/man/man5 sys/netinet/ipfw -> sys/netpfil/ipfw That's all. [1] This line is arguable, however the future plan is to: - split pfvar.h into pf.h and pf_var.h - kill if_pfsync.h and if_pflog.h as soon as they stop being ifnets - kill pf_mtag.h moving its declaration to mbuf.h or pf_var.h So, all new stuff in sys/net would dissolve soon. Notice that current movement doesn't affect software in ports, but above plans would. So decision is just put pf stuff into sys/net for now to avoid breaking ports twice. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 18:08:16 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 282991065678; Wed, 12 Sep 2012 18:08:16 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id D92ED8FC27; Wed, 12 Sep 2012 18:08:15 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id BE97050974; Wed, 12 Sep 2012 14:08:08 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 6713F50905; Wed, 12 Sep 2012 14:08:08 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Wed, 12 Sep 2012 14:08:08 -0400 From: Dominic Blais To: Gleb Smirnoff , Vijay Singh Date: Wed, 12 Sep 2012 14:08:02 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QWNbQMXlKQfrdQmm9xakaf6NNdQAuBqmw Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDCC@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <20120911200545.GT44854@glebius.int.ru> In-Reply-To: <20120911200545.GT44854@glebius.int.ru> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Adrian Chadd Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 18:08:16 -0000 Hi, I just made a script that does the following: 5 times do if default_route !=3D PROPER_GATEWAY delete_default_route() create_default_route_with_proper_gateway() fi sleep 10 seconds done It worked well and replaced the default route within 10 seconds (mean 5). What's interesting is that route monitor shows that I delete and create the= default route but doesn't show anything prior to it. So I think it really = confirms it's some kind of a bug somewhere that takes an IP address that's = in memory in put it as the default gateway. -- -----Message d'origine----- De=A0: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Envoy=E9=A0: 11 septembre 2012 16:06 =C0=A0: Vijay Singh Cc=A0: Adrian Chadd; freebsd-net@freebsd.org; Dominic Blais Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On Tue, Sep 11, 2012 at 01:03:56PM -0700, Vijay Singh wrote: V> > V> V> > V> Could this be=20 V> > V> http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=3D226120&r V> > V> 2=3D226224&pathrev=3D226331 V> > V> > Why do you suspect this one? V>=20 V> I was hitting a similar issue in 8.2. After down/up on the interface=20 V> to the default gateway, I saw this message and arpresolve would never=20 V> complete. I was able to step through gdb to see that the RTF_GATEWAY=20 V> check was causing the problem. Hmm, interesting. We need more debugging here. But where from could 65.59.2= 33.102 appear? -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 19:22:54 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67A54106564A; Wed, 12 Sep 2012 19:22:54 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0D68FC08; Wed, 12 Sep 2012 19:22:53 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 9ACDC7770F; Wed, 12 Sep 2012 21:22:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id w-DwA_sevC_M; Wed, 12 Sep 2012 21:22:49 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id 9767877701; Wed, 12 Sep 2012 21:22:49 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 4725B19CA3A; Wed, 12 Sep 2012 09:37:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id gl2UONg6ebwH; Wed, 12 Sep 2012 09:37:04 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id C29B919CA35; Wed, 12 Sep 2012 09:37:03 +0200 (CEST) Message-ID: <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 21:22:47 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Freddie Cash References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 19:22:54 -0000 On 09/11/2012 11:34 PM, Freddie Cash wrote: > > On Sep 11, 2012 2:12 PM, "Giulio Ferro" > wrote: > > > > Well, there definitely seems to be a problem with igb and lagg. > > > > igb alone works as it should, but doesn't seem to work properly in lagg. > > > > To be sure I started from scratch from a 9.0 release with nothing but: > > > > /etc/rc.conf > > --------------------------------------------------- > > ifconfig_igb0="inet ..." > > > > ifconfig_igb1="up" > > ifconfig_igb2="up" > > ifconfig_igb3="up" > > > > cloned_interfaces="lagg0" > > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > igb3 192.168.x.x/24" > > > > sshd_enable="YES" > > --------------------------------------------------- > > > > This doesn't even manage to start sshd, it just hangs there at boot. > > > > Disabling lagg configuration everything works correctly. > > > > Just curious: does it work if you split the lagg configuration from the > IP config: > > ifconfig_lagg0="laggproto ..." > ifconfig_lagg0_alias0="inet 192..." > > I've had problems in the past with cloned interfaces not working right > if you do everything in one ifconfig line. Never spent much time > debugging it, though, as the split config always worked. > Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 RELEASE) I still think the problem is with lagg and / or igb. Someone should look into it. From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 19:40:49 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC7B1065670; Wed, 12 Sep 2012 19:40:49 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 703B28FC16; Wed, 12 Sep 2012 19:40:47 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1743429lbb.13 for ; Wed, 12 Sep 2012 12:40:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MCU/TdbCD0k8aHp6hnjm73CrPAunzIOHeoIaeSbkBb0=; b=f9pf20OiPoJSPxTSjt8ilSVbZ+0ojA2KP6uVOYtX+CnydaXLUFru31Z/AtHeZaCA5B GBD/njej1NIhdvnCcbMwm39wt0OAgU4UGRS0//mIP/4XclFIIBKx/lOkC06SrUU7A0C+ RTbnijDlXxc4mdJaTQrE60LKuSUNMNfj7/WMBuPBbFD9MkDHecgOrm2H2N0UujuQn9GS 8f2ah1M2W/IqURMzoux+f5/B8O3i8o1+1RTFEBrjqDZadMxvYgnVuTYhN2PUt8GL7YmT xfAfVYYFR0UXuM+HVw1ejCFqOjGViwMgU8rEyixFL1mwydjW+X7zf7fdr0YSBvgFeAD9 ZFIg== MIME-Version: 1.0 Received: by 10.112.26.38 with SMTP id i6mr51135lbg.76.1347478846941; Wed, 12 Sep 2012 12:40:46 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 12 Sep 2012 12:40:46 -0700 (PDT) In-Reply-To: <5050E107.6090403@zirakzigil.org> References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 12:40:46 -0700 Message-ID: From: Freddie Cash To: Giulio Ferro Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 19:40:49 -0000 On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro wrote: > On 09/11/2012 11:34 PM, Freddie Cash wrote: >> >> On Sep 11, 2012 2:12 PM, "Giulio Ferro" > > wrote: >> > >> > Well, there definitely seems to be a problem with igb and lagg. >> > >> > igb alone works as it should, but doesn't seem to work properly in >> lagg. >> > >> > To be sure I started from scratch from a 9.0 release with nothing but: >> > >> > /etc/rc.conf >> > --------------------------------------------------- >> > ifconfig_igb0="inet ..." >> > >> > ifconfig_igb1="up" >> > ifconfig_igb2="up" >> > ifconfig_igb3="up" >> > >> > cloned_interfaces="lagg0" >> > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport >> igb3 192.168.x.x/24" >> > >> > sshd_enable="YES" >> > --------------------------------------------------- >> > >> > This doesn't even manage to start sshd, it just hangs there at boot. >> > >> > Disabling lagg configuration everything works correctly. >> > >> >> Just curious: does it work if you split the lagg configuration from the >> IP config: >> >> ifconfig_lagg0="laggproto ..." >> ifconfig_lagg0_alias0="inet 192..." >> >> I've had problems in the past with cloned interfaces not working right >> if you do everything in one ifconfig line. Never spent much time >> debugging it, though, as the split config always worked. >> > > Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 > RELEASE) > > I still think the problem is with lagg and / or igb. > Someone should look into it. Thanks for checking. I've used lagg(4) with igb, just not on 9.x. You're right, it seems to be pointing to the igb(4) driver in 9.x compared to < 9.0. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 20:48:02 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 361081065688; Wed, 12 Sep 2012 20:48:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BD0EA8FC0A; Wed, 12 Sep 2012 20:48:01 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3390453vbm.13 for ; Wed, 12 Sep 2012 13:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QWfBuoN5GFFDS4W+f1pX1rw61Bd1ik/uM/Y1yeVdamA=; b=HbdchFnKGOlFptRx274d1YTtQCyaPEZMjIREqCBXqVbIEIkt2dkygFi+Leg4+H7rg6 zaFIWoFuDyEB7k5GFccfBOCZ9rhhQF8X6HJsVIrOqZMDENM27AQlmhtcNI+zXKIhVfjD B3lD971pv4elt33ezBfuFO93bs7SHWwHZ3qC1HawVruvhNC/GduuD+rss3N5Io708qys zVz9GcAuksaFDu0mp24dLm+u7zdJtRkwyuUjKHiD+qGveNOvIrqjsX0WbbOLjZmpAy2C C+JmmSm4buc4dYsB8vxQbRxcHrrVRezBjnAMvKENus3ldIppDRSJMLo17hnZq1C7Tw/T qyZA== MIME-Version: 1.0 Received: by 10.52.240.171 with SMTP id wb11mr23701811vdc.86.1347482880727; Wed, 12 Sep 2012 13:48:00 -0700 (PDT) Received: by 10.58.68.8 with HTTP; Wed, 12 Sep 2012 13:48:00 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:48:00 -0700 Message-ID: From: Jack Vogel To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 20:48:02 -0000 On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro > wrote: > > On 09/11/2012 11:34 PM, Freddie Cash wrote: > >> > >> On Sep 11, 2012 2:12 PM, "Giulio Ferro" >> > wrote: > >> > > >> > Well, there definitely seems to be a problem with igb and lagg. > >> > > >> > igb alone works as it should, but doesn't seem to work properly in > >> lagg. > >> > > >> > To be sure I started from scratch from a 9.0 release with nothing > but: > >> > > >> > /etc/rc.conf > >> > --------------------------------------------------- > >> > ifconfig_igb0="inet ..." > >> > > >> > ifconfig_igb1="up" > >> > ifconfig_igb2="up" > >> > ifconfig_igb3="up" > >> > > >> > cloned_interfaces="lagg0" > >> > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > >> igb3 192.168.x.x/24" > >> > > >> > sshd_enable="YES" > >> > --------------------------------------------------- > >> > > >> > This doesn't even manage to start sshd, it just hangs there at boot. > >> > > >> > Disabling lagg configuration everything works correctly. > >> > > >> > >> Just curious: does it work if you split the lagg configuration from the > >> IP config: > >> > >> ifconfig_lagg0="laggproto ..." > >> ifconfig_lagg0_alias0="inet 192..." > >> > >> I've had problems in the past with cloned interfaces not working right > >> if you do everything in one ifconfig line. Never spent much time > >> debugging it, though, as the split config always worked. > >> > > > > Nope, doesn't work. It always hangs at boot and cannot be killed > (freebsd 9 > > RELEASE) > > > > I still think the problem is with lagg and / or igb. > > Someone should look into it. > > Thanks for checking. I've used lagg(4) with igb, just not on 9.x. > > You're right, it seems to be pointing to the igb(4) driver in 9.x > compared to < 9.0. > > How do you determine that since it doesn't happen without lagg? I've no reports of igb hanging otherwise and its being used extensively. Jack > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 20:51:53 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 552B91065676; Wed, 12 Sep 2012 20:51:53 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 941958FC16; Wed, 12 Sep 2012 20:51:51 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1803414lbb.13 for ; Wed, 12 Sep 2012 13:51:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wU0OcIooFPH78oJ1J2rmrS2zFfBH7vD1pI/uMxGf99E=; b=VRxrrkENfW1MLknD8Qxb1/aKCmhkikGKzGErVIjlu16A2fPd+/bAVROCncO6/EoeGX WdN2fzTnTqUpY4497Xer8/WA7ufbOO8mcFrf6x0LjLwf+QKw29JB9CsLofqJu8LNNaWD s4R4pOhMAT+oPNgO91GoslmGdygfH68JwNgl00TYrJCZ2IWl540s0e4bGGiNTYFY93Ma OygvdvOOj46y3kpzO9u2KJ34A5y2EChX2hmy/jFIySNmKw5EgOg+dyTjEy3SgelUaBF1 mMmJdOAt+Y+1TWXQye+BbVzA0WEEH8rBnj8vnZYszdLwp541uMyzQgQUSJTr+ahWWFe8 uUuA== MIME-Version: 1.0 Received: by 10.152.103.146 with SMTP id fw18mr20159796lab.30.1347483110583; Wed, 12 Sep 2012 13:51:50 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 12 Sep 2012 13:51:50 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:51:50 -0700 Message-ID: From: Freddie Cash To: Jack Vogel Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 20:51:53 -0000 On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: > On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: >> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. >> >> You're right, it seems to be pointing to the igb(4) driver in 9.x >> compared to < 9.0. >> > How do you determine that since it doesn't happen without lagg? I've no > reports of igb hanging otherwise and its being used extensively. Well, I did say "seems to". :) igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 and 9-STABLE on those three boxes. igb+lagg doesn't work for him on 9.0. Although, I don't recall if non-LACP options were tried earlier in this thread, or if it's just the LACP mode that's failing. If one mode works (say failover) and LACP mode doesn't, that "seems to" point to lagg. I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to test this with as well. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 20:56:09 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38509106570E; Wed, 12 Sep 2012 20:56:09 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C1A298FC12; Wed, 12 Sep 2012 20:56:08 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3401847vbm.13 for ; Wed, 12 Sep 2012 13:56:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4LOrDZJlXQPYd6JhyriS2t6Km3HNwBcZqqYlu+84agQ=; b=Do814Nz6fkDQKa6kmyS7oM8r6wltyW/fEbJgxOzBmsethLVb3nSp26/0dZv5utYeRu vYnQpbhl+PNJCZ4TLkckev9I73VJth0OEPDY9kaGjaUerCBnj/Lwe67LJmTsnKK2qZu3 UT607aA5ZotgNikgcZx8aWr62wYhFaZ4l5Amap//vcILtG5ZSkjdUavdlJg/yo0xss6K Lc4+xDqHutMqMt8+gtvfz/Ahxg3YuADApTFkZ0odv1+xBjZXnX0blIXeeqAkzR+deUtO 0rD+jpyp/pbOVsIiXZ8v1qAYevmUDRcfdr+M3WSv4wQHwaWqyfA1N5j5NGxLYStH8TUo REgQ== MIME-Version: 1.0 Received: by 10.220.225.194 with SMTP id it2mr29861852vcb.32.1347483367823; Wed, 12 Sep 2012 13:56:07 -0700 (PDT) Received: by 10.58.68.8 with HTTP; Wed, 12 Sep 2012 13:56:07 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:56:07 -0700 Message-ID: From: Jack Vogel To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 20:56:09 -0000 On Wed, Sep 12, 2012 at 1:51 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: > > On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash > wrote: > >> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. > >> > >> You're right, it seems to be pointing to the igb(4) driver in 9.x > >> compared to < 9.0. > >> > > How do you determine that since it doesn't happen without lagg? I've no > > reports of igb hanging otherwise and its being used extensively. > > Well, I did say "seems to". :) > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > and 9-STABLE on those three boxes. > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > non-LACP options were tried earlier in this thread, or if it's just > the LACP mode that's failing. If one mode works (say failover) and > LACP mode doesn't, that "seems to" point to lagg. > > I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to > test this with as well. > > I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, if you see the issue there I can see about getting some time to look into it here. Jack From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 20:57:54 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B97410656D9; Wed, 12 Sep 2012 20:57:54 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id BB0918FC21; Wed, 12 Sep 2012 20:57:53 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 820A27300B; Wed, 12 Sep 2012 23:17:26 +0200 (CEST) Date: Wed, 12 Sep 2012 23:17:26 +0200 From: Luigi Rizzo To: Gleb Smirnoff Message-ID: <20120912211726.GB10974@onelab2.iet.unipi.it> References: <20120912123457.GC85604@glebius.int.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120912123457.GC85604@glebius.int.ru> User-Agent: Mutt/1.4.2.3i Cc: luigi@FreeBSD.org, "Bjoern A. Zeeb" , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 20:57:54 -0000 On Wed, Sep 12, 2012 at 04:34:57PM +0400, Gleb Smirnoff wrote: > Hi, > > we (me and Bjoern) would like to establish a single place > for all kinds of pfil(9) consumers, for current ones and > for future as well. > > The place chosen is sys/netpfil. > > On first round we'd like to move there our Tier-1 firewalls: > ipfw and pf. This also includes moving pf out of contrib. > > The plan of movement is the following: > > sys/contrib/pf/net/*.c -> sys/netpfil/pf/ > sys/contrib/pf/net/*.h -> sys/net/ [1] > contrib/pf/pfctl/*.c -> sbin/pfctl > contrib/pf/pfctl/*.h -> sbin/pfctl > contrib/pf/pfctl/pfctl.8 -> sbin/pfctl > contrib/pf/pfctl/*.4 -> share/man/man4 > contrib/pf/pfctl/*.5 -> share/man/man5 > > sys/netinet/ipfw -> sys/netpfil/ipfw I have two concerns against moving ipfw/ - what do we gain by moving ipfw/ further away from its user header files (whose location in netinet/ is pretty much part of the API so difficult to change) ? - pfil is just one of the APIs that the ipfw code uses to send/receive packets (pfil, netmap for FreeBSD, and then netfilter and ndispacket for the other OS). The pfil dependencies amount to probably 1% of the code. So if we really want to relocate ipfw/ i'd rather move to a more generic place (but as far as i know we do not have one for subsystems -- dev/ is used for drivers, other stuff has generally accumulated under sys/ ,see geom, ofed, netgraph). > That's all. > > [1] This line is arguable, however the future plan is to: > - split pfvar.h into pf.h and pf_var.h > - kill if_pfsync.h and if_pflog.h as soon as they stop being ifnets this i am curious about - are you planning to remove bpf support for pflog, or just implement it in a different way ? cheers luigi From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 23:21:08 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BF3D1065742; Wed, 12 Sep 2012 23:21:08 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from plsvl-mailgw-02.bluecoat.com (plsvl-mailgw-02.bluecoat.com [199.91.133.12]) by mx1.freebsd.org (Postfix) with ESMTP id 5438A8FC08; Wed, 12 Sep 2012 23:21:08 +0000 (UTC) Received: from PWSVL-EXCHTS-01.internal.cacheflow.com (unknown [10.2.2.122]) by plsvl-mailgw-02.bluecoat.com (Postfix) with ESMTP id BBB19200E8; Wed, 12 Sep 2012 16:12:49 -0700 (PDT) Received: from PWSVL-EXCMBX-03.internal.cacheflow.com ([fe80::f1c6:61a6:35aa:6971]) by PWSVL-EXCHTS-01.internal.cacheflow.com ([fe80::5c50:e2ba:8115:4223%20]) with mapi id 14.01.0289.001; Wed, 12 Sep 2012 16:12:49 -0700 From: "Li, Qing" To: Dominic Blais , Gleb Smirnoff , Vijay Singh Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QV9hNg6yz3+vBTKid2eQK9MzOqAAeR3oQABqzt/A= Date: Wed, 12 Sep 2012 23:12:48 +0000 Message-ID: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDC6@WIN2008.Domnt.abi.ca> In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDC6@WIN2008.Domnt.abi.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.2.2.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Adrian Chadd Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 23:21:08 -0000 >=20 > got message of size 184 on Wed Sep 12 00:15:49 2012 > RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > default default default ### <- This looks normal, I > usually see it when customers connect to > ### pppoe from MPD. >=20 The "default" value for the gateway refers to 0.0.0.0. You typically see such bogus route operations during DHCP initialization. I don't really see anything suspicious in the rest of the logs. --Qing From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 23:28:23 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7CCE1065670; Wed, 12 Sep 2012 23:28:23 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from plsvl-mailgw-01.bluecoat.com (plsvl-mailgw-01.bluecoat.com [199.91.133.11]) by mx1.freebsd.org (Postfix) with ESMTP id 7FCF48FC15; Wed, 12 Sep 2012 23:28:23 +0000 (UTC) Received: from pwsvl-exchts-03.internal.cacheflow.com (esxprd02.bluecoat.com [10.2.2.160]) by plsvl-mailgw-01.bluecoat.com (Postfix) with ESMTP id 0BCD281A07D; Wed, 12 Sep 2012 16:22:21 -0800 (AKDT) Received: from PWSVL-EXCMBX-03.internal.cacheflow.com ([fe80::f1c6:61a6:35aa:6971]) by pwsvl-exchts-03.internal.cacheflow.com ([fe80::a508:17dc:1550:e9f6%12]) with mapi id 14.01.0355.002; Wed, 12 Sep 2012 16:19:11 -0700 From: "Li, Qing" To: Vijay Singh , Gleb Smirnoff Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: AQHNkFisJV8pNMhWm0u79Z6TxdCrpZeHV5/w Date: Wed, 12 Sep 2012 23:19:10 +0000 Message-ID: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.2.2.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Adrian Chadd , Dominic Blais Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 23:28:23 -0000 >=20 > > V> > > V> Could this be > http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=3D226120&r2=3D226= 22 > 4&pathrev=3D226331 > > > > Why do you suspect this one? >=20 > I was hitting a similar issue in 8.2. After down/up on the interface > to the default gateway, I saw this message and arpresolve would never > complete. I was able to step through gdb to see that the RTF_GATEWAY > check was causing the problem. >=20 Do you have more specific information, e.g., the IP address that ARP was trying to resolve, and the route entry key the validation was performed against ? It's not clear from the above why the check would fail. As far as I can tell this commit should not break the interface route check for L2 operations. If anything I'd be suspecting=20 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D222143 However, I need more information to get a better understanding on what failed in your case. --Qing From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 23:42:26 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2DD3106566B; Wed, 12 Sep 2012 23:42:26 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7E23A8FC12; Wed, 12 Sep 2012 23:42:26 +0000 (UTC) Received: from [IPv6:::1] (proxy6.corp.yahoo.com [216.145.48.19]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q8CNg5vb021463; Wed, 12 Sep 2012 16:42:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1347493326; bh=jMQqoB2Eyx+2YVUG/ech8D7Hsi+V2/44j0XxJL9qNwQ=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=NGTmf+Q7e6ASgtHTKKXfsvpcyw1asNudf+z3axoqrox/uEUtsNsxRC49MgbMWmLrT EIqr+7tyMWiJcn6MizaTxRx1fvcPBIi4jrnwj0D1SDS9NP6Sp30km8CRK+W+ymnBnH cr/zbjfB4Pb80kunOIIqEww0usatlGnm86X9xe7U= From: Sean Bruno To: Jack Vogel In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 12 Sep 2012 16:42:05 -0700 Message-ID: <1347493325.4686.7.camel@powernoodle> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 493325003 Cc: "freebsd-net@freebsd.org" , Giulio Ferro , Freddie Cash , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2012 23:42:26 -0000 > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > > and 9-STABLE on those three boxes. > > > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > > non-LACP options were tried earlier in this thread, or if it's just > > the LACP mode that's failing. If one mode works (say failover) and > > LACP mode doesn't, that "seems to" point to lagg. > > > > I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to > > test this with as well. > > > > > > I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, > if you see the issue there I can see about getting some time to look into > it here. > > Jack We're running igb + lagg on two interfaces here at Yahoo without issues like this. We're using LACP exclusively with Cisco switches. If you're seeing failover issues, I wonder if its the switch you're using as opposed to the host and ethernet card? Just a shot in the dark here. Sean From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 00:12:42 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3F69106566B for ; Thu, 13 Sep 2012 00:12:42 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 96C9E8FC0C for ; Thu, 13 Sep 2012 00:12:42 +0000 (UTC) Received: by oagm1 with SMTP id m1so1785876oag.13 for ; Wed, 12 Sep 2012 17:12:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=pGqDlSUiNotkjGngE2wilDC+VXeosUDP4qhHPms6TgM=; b=wrONfAHcKa3fFrmuvVIa4AcNvn0if3+pbJx9JL0cJB8jZ4pIqexEKxtOqyIHrGcPmM 2LO2qn6Kdn5qqbKmIjod9JUqV5YvqzXGiMWccsdv5fXSELs7rPswLqy0gghBXDSdrqq2 SRyT7JBHelMiAQKuKS2xVRXLdwQ72e5+B+amPfw7Vli8Cz1sIG9H2OxC2f/3FkStA34Y PoHc/+X35u6Xvg+MfotH2gsX2WJqmPvfeJ3CzNKJlyRiuGgW7C0q60v7KO/XCAu7/NZp wDJtGn5oJaugTrHYHQelEQ3okrFiYW6yyvR53p3KHZs/Gk0DaoHJfi+Wc8pT9k6PrmVt Z68g== MIME-Version: 1.0 Received: by 10.60.2.134 with SMTP id 6mr173101oeu.62.1347495156658; Wed, 12 Sep 2012 17:12:36 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Wed, 12 Sep 2012 17:12:36 -0700 (PDT) Date: Wed, 12 Sep 2012 17:12:36 -0700 Message-ID: From: Garrett Cooper To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Restarting interfaces and routing table stickiness X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 00:12:42 -0000 Hi -net! I've been doing some IPv6 testing lately, and one of the issues that I've run into in the past (since at least 7.0-CURRENT) is that if I do `service netif restart `, e.g. `service netif restart` multiple times, and have addresses statically configured in rc.conf, more often than not the routing table doesn't properly get flushed and my addresses become unreachable (even after I call `service routing restart`). Recently, I ran into an issue with 9.1-RC1 where had to kill ntpd before it would allow me to reach one of the addresses I had assigned on a test server (server has a total of 4 physical NICs and 1 vlan'ed interface). The only surefire method to get things back to a sane state is to reboot the box (of course, please keep in mind that I'm using the netif rc script and not using other commands like route flush, route delete, etc). This behavior can be simply triggered like so on 8.x and below like so: /etc/rc.d/network_ipv6 restart /etc/rc.d/network_ipv6 restart The second restart typically results in the following messages from route(8): route: writing to routing socket: File exists add net fe80::: gateway ::1: route already in table route: writing to routing socket: File exists add net ff02::: gateway ::1: route already in table Similar methods should exist on all FreeBSD versions by doing `/etc/rc.d/netif restart` or `service netif restart`. Furthermore, this issue is exacerbated by using `service netif restart cxgb0` as the rc script might not be doing the right thing when clearing the routing tables. Thanks! -Garrett PS I'm wondering if this is a known issue and if there's anything I can do to reproduce/isolate this issue further. From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 00:24:40 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58241106564A for ; Thu, 13 Sep 2012 00:24:40 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3408FC17 for ; Thu, 13 Sep 2012 00:24:39 +0000 (UTC) Received: from alph.allbsd.org (p3048-ipbf1204funabasi.chiba.ocn.ne.jp [123.218.144.48]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id q8D0OMkR001748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Sep 2012 09:24:32 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.allbsd.org (8.14.5/8.14.5) with ESMTP id q8D0OK9W052317; Thu, 13 Sep 2012 09:24:21 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Thu, 13 Sep 2012 09:21:32 +0900 (JST) Message-Id: <20120913.092132.1572055980229833778.hrs@allbsd.org> To: yanegomi@gmail.com From: Hiroki Sato In-Reply-To: References: X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_Sep_13_09_21_32_2012_633)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Thu, 13 Sep 2012 09:24:32 +0900 (JST) X-Spam-Status: No, score=-96.3 required=13.0 tests=CONTENT_TYPE_PRESENT, FAKEDWORD_BACKQUOTE,ONLY1HOPDIRECT,RCVD_IN_RP_RNBL,SAMEHELOBY2HOP, USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-net@FreeBSD.org Subject: Re: Restarting interfaces and routing table stickiness X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 00:24:40 -0000 ----Security_Multipart(Thu_Sep_13_09_21_32_2012_633)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Garrett Cooper wrote in : ya> Hi -net! ya> I've been doing some IPv6 testing lately, and one of the issues ya> that I've run into in the past (since at least 7.0-CURRENT) is that if ya> I do `service netif restart `, e.g. `service netif restart` ya> multiple times, and have addresses statically configured in rc.conf, ya> more often than not the routing table doesn't properly get flushed and ya> my addresses become unreachable (even after I call `service routing ya> restart`). Recently, I ran into an issue with 9.1-RC1 where had to ya> kill ntpd before it would allow me to reach one of the addresses I had ya> assigned on a test server (server has a total of 4 physical NICs and 1 ya> vlan'ed interface). The only surefire method to get things back to a ya> sane state is to reboot the box (of course, please keep in mind that ya> I'm using the netif rc script and not using other commands like route ya> flush, route delete, etc). ya> This behavior can be simply triggered like so on 8.x and below like so: ya> ya> /etc/rc.d/network_ipv6 restart ya> /etc/rc.d/network_ipv6 restart Do you have a procedure which can reproduce the problem on 9.x and/or output with rc_debug="YES"? I guess the cause was that initialization of the routing table and interface configuration are separated, and it ended up being some incomplete configuration when restarting. -- Hiroki ----Security_Multipart(Thu_Sep_13_09_21_32_2012_633)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAlBRJwwACgkQTyzT2CeTzy0CTgCg2sndjXOqtGE+sgqEyt8DVTk2 GsYAoMLQh4kcFx52IgFHw1b+IaYwqhFu =qG1m -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Sep_13_09_21_32_2012_633)---- From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 01:49:29 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A57EE106564A for ; Thu, 13 Sep 2012 01:49:29 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7636B8FC08 for ; Thu, 13 Sep 2012 01:49:29 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8D1TCFa059955 for ; Wed, 12 Sep 2012 18:29:12 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <505136E8.6010708@rawbw.com> Date: Wed, 12 Sep 2012 18:29:12 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 01:49:29 -0000 I have the ndis based driver preloaded during boot. It creates ndis0 interface. /etc/rc.conf has the following lines: wlans_ndis0="wlan0" ifconfig_wlan0="WPA DHCP" However, wlan0 device isn't being created during system boot or during '/etc/rc.d/netif start'. '/etc/rc.d/wpa_supplicant start' also silently doesn't do anything. Only commands typed manually: > ifconfig wlan create wlandev ndis0 > wpa_supplicant -D ndis -i wlan0 -c /etc/wpa_supplicant.conf > dhclient wlan0 start wireless network. On another machine with ath0 wireless interface similar configuration works fine. How can I understand why wireless doesn't start during boot? Yuri From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 01:59:12 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28CC71065670; Thu, 13 Sep 2012 01:59:12 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id EA3DB8FC0A; Thu, 13 Sep 2012 01:59:11 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 501E423F6D9; Wed, 12 Sep 2012 21:59:08 -0400 (EDT) Date: Wed, 12 Sep 2012 21:59:04 -0400 From: Glen Barber To: Yuri Message-ID: <20120913015904.GC1341@glenbarber.us> References: <505136E8.6010708@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE" Content-Disposition: inline In-Reply-To: <505136E8.6010708@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 01:59:12 -0000 --nmemrqcdn5VTmUEE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 06:29:12PM -0700, Yuri wrote: > I have the ndis based driver preloaded during boot. It creates ndis0=20 > interface. > /etc/rc.conf has the following lines: > wlans_ndis0=3D"wlan0" > ifconfig_wlan0=3D"WPA DHCP" >=20 > However, wlan0 device isn't being created during system boot or during=20 > '/etc/rc.d/netif start'. > '/etc/rc.d/wpa_supplicant start' also silently doesn't do anything. >=20 > Only commands typed manually: > > ifconfig wlan create wlandev ndis0 > > wpa_supplicant -D ndis -i wlan0 -c /etc/wpa_supplicant.conf > > dhclient wlan0 > start wireless network. >=20 > On another machine with ath0 wireless interface similar configuration=20 > works fine. >=20 > How can I understand why wireless doesn't start during boot? >=20 What is 'uname -a'? I'm surprised you can have ndis(4) load during boot. Recent machines I tried to do that have panic'd during boot. Can you try creating a crontab entry to load ndis(4) post-boot? # start ndis(4) post-boot @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 Something similar to that worked for me to get the device to work close to boot time, without panic. Once loaded, wpa_supplicant(8) worked fine. Please also see: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/165630 which I would would be MFC'd already... Glen --nmemrqcdn5VTmUEE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUT3oAAoJEFJPDDeguUaj6XUH/RGJJcOZ/6sgHtUh98MulS02 UQpsAdEpafkC833jWXfcFg/0fz0sdPRuoRbeVeuZLyZ/98dBQ1bBCBk3d1Q10bnp pVACFzuL9Lqg8seF/VsRuPgcY/9IxkNJG40vAPEPsEvZ0OQKf2P4tm5w+1UXEOrA T5DgPVkeuvUVxlqbsgSBM0hzICZ+Msq0gt/4civkkN0C0X+M5jrxC8Fb8OiHSpi1 VzYArOCwMMeE5qbJuSUN81edJka5MVBW7vYM9eUFgorAGfKW2MpCtHVXQw9KVwgg 01KqUHiT6V9ev5tbvAHSbH/mWckmkzoHB+sUGBm6zVC5jsLnTcspgN7H2UFYUfA= =yr0H -----END PGP SIGNATURE----- --nmemrqcdn5VTmUEE-- From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 02:58:22 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BDBD106564A; Thu, 13 Sep 2012 02:58:22 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 540C48FC08; Thu, 13 Sep 2012 02:58:21 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8D2wLF3071461; Wed, 12 Sep 2012 19:58:21 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <50514BCC.3010607@rawbw.com> Date: Wed, 12 Sep 2012 19:58:20 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Glen Barber References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> In-Reply-To: <20120913015904.GC1341@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 02:58:22 -0000 On 09/12/2012 18:59, Glen Barber wrote: > What is 'uname -a'? FreeBSD xxx.xxx.org 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Jul 9 19:29:05 PDT 2012 xxx@xxx.org:/usr/obj/usr/src/sys/GENERIC i386 > > I'm surprised you can have ndis(4) load during boot. Recent machines I > tried to do that have panic'd during boot. I have these lines in /boot/loader.conf and if_ndis and ndis(4) based driver load fine: ndis_load="YES" if_ndis_load="YES" bcmwl5_sys_load="YES" > > Can you try creating a crontab entry to load ndis(4) post-boot? > > # start ndis(4) post-boot > @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 > > Something similar to that worked for me to get the device to work close > to boot time, without panic. Once loaded, wpa_supplicant(8) worked > fine. > > Please also see: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165630 > > which I would would be MFC'd already... What you are suggesting is for the case when loading if_ndis causes panic during boot. In my case it loads fine during boot, but it's not clear why '/etc/rc.d/netif' doesn't activate it. network works fine once all commands are run manually. Yuri From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 03:01:58 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 116AD106564A; Thu, 13 Sep 2012 03:01:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id DF49A8FC1B; Thu, 13 Sep 2012 03:01:57 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id B023823F6D9; Wed, 12 Sep 2012 23:01:56 -0400 (EDT) Date: Wed, 12 Sep 2012 23:01:53 -0400 From: Glen Barber To: Yuri Message-ID: <20120913030153.GH1341@glenbarber.us> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bygAmIonOAIqBxQB" Content-Disposition: inline In-Reply-To: <50514BCC.3010607@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 03:01:58 -0000 --bygAmIonOAIqBxQB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 07:58:20PM -0700, Yuri wrote: > > I'm surprised you can have ndis(4) load during boot. Recent machines I > > tried to do that have panic'd during boot. >=20 > I have these lines in /boot/loader.conf and if_ndis and ndis(4) based=20 > driver load fine: I understand that. > What you are suggesting is for the case when loading if_ndis causes=20 > panic during boot. > In my case it loads fine during boot, but it's not clear why=20 > '/etc/rc.d/netif' doesn't activate it. > network works fine once all commands are run manually. ndis(4) is buggy on SMP-enabled kernels. It would be helpful if you would at least try my cron(8) suggestion. Glen --bygAmIonOAIqBxQB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUUyhAAoJEFJPDDeguUajPOwH/iGk1R5ZCYfRVnOAobusHoPS GpfsjqpXdzsxf4DYU29o8HJ98wtd/P5muipZKQl0RdYVjYgGsZTLomi6wVn++ztw Y/2gcdSc0q+m3iWXwT9jb0HTJSn2zs9EVXzFicknKyjPHQ0r/JsAu+RYRc4Q/uIN FQ5Z+aAiZiIjC6Pai/JjksUnqP9dEONctAhlyhYnCHGIOeYPjVuUwX+e637ld6Wh 7LTgiT0LAynZ5jePc8fq+ClnVlHQymzNLxVnHAPCa2PUAdAehRW77d0LH/4CaxRP XBwtYqTigXhgCADsaGtczUFjpFw69CdwGt8DwQ0XHiE0cG/jVtF27y9ILSOEnN8= =V+5K -----END PGP SIGNATURE----- --bygAmIonOAIqBxQB-- From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 10:04:33 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F2BE106566B for ; Thu, 13 Sep 2012 10:04:33 +0000 (UTC) (envelope-from tretuliy2@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 396398FC17 for ; Thu, 13 Sep 2012 10:04:33 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so4022124pbb.13 for ; Thu, 13 Sep 2012 03:04:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=oFGZjttgPjx8SweG+tff1UQGdolkgAxJEgIKryy1Ops=; b=ZNRBY5LBHVgG6vo65wgZrKS+db4Ah241JV6WfGDQNiwm9CfCk4teoSd7eFAHKBjDAo nfAiDn+Rc2bfSRamEEaYO982dlopg1fHqZBbasiAIpV2X+cxff4w1fP23cfrY6xQaZIy nfJkTr6cB9zJq2WGl1Mbk9Kmrk2qxeGop9LfpFsehxoNS4IMnCg6NsxDE03a7I3D3fKq 56x+xHAbwbG8m3tV8d8w315ikShTnY8YzsQb1UaIdJHI3NS+SK/siaGhjRn8x8dgusSr OWxUSdo2JbyJ3KGtsNPLt9DdDFyt91pY9M7/9fic1tTAZ0GnHoRMv36HXqsJIHdQTc7k a4mA== MIME-Version: 1.0 Received: by 10.66.74.74 with SMTP id r10mr2721132pav.57.1347530672870; Thu, 13 Sep 2012 03:04:32 -0700 (PDT) Received: by 10.66.156.170 with HTTP; Thu, 13 Sep 2012 03:04:32 -0700 (PDT) Received: by 10.66.156.170 with HTTP; Thu, 13 Sep 2012 03:04:32 -0700 (PDT) In-Reply-To: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> Date: Thu, 13 Sep 2012 13:04:32 +0300 Message-ID: From: =?KOI8-R?B?98HEyc0g9dLB2sHF1w==?= To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 10:04:33 -0000 I have the same issue (default gateway unexpectedly changes on some random address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a wild guess that it is related to libalias compilled into kernel (troubles start showing itself when I started to use ipfw nat functionality ). From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 13:10:20 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D375D1065670; Thu, 13 Sep 2012 13:10:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A5CB48FC12; Thu, 13 Sep 2012 13:10:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8DDAJkU085660; Thu, 13 Sep 2012 13:10:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8DDAJMf085644; Thu, 13 Sep 2012 13:10:19 GMT (envelope-from linimon) Date: Thu, 13 Sep 2012 13:10:19 GMT Message-Id: <201209131310.q8DDAJMf085644@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/171532: [ndis] ndis(4) driver includes 'pccard'-specific code, even if 'device pccard' absent from config X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 13:10:20 -0000 Old Synopsis: ndis(4) driver includes 'pccard'-specific code, even if 'device pccard' absent from config New Synopsis: [ndis] ndis(4) driver includes 'pccard'-specific code, even if 'device pccard' absent from config Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Sep 13 13:10:02 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171532 From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 14:27:58 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7AAC1065705 for ; Thu, 13 Sep 2012 14:27:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3DC928FC1A for ; Thu, 13 Sep 2012 14:27:58 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 872A2B993; Thu, 13 Sep 2012 10:27:57 -0400 (EDT) From: John Baldwin To: freebsd-net@freebsd.org, Sean Bruno Date: Thu, 13 Sep 2012 10:24:09 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <201209112000.q8BK0LCk057201@freefall.freebsd.org> In-Reply-To: <201209112000.q8BK0LCk057201@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201209131024.09964.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 13 Sep 2012 10:27:57 -0400 (EDT) Cc: Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 14:27:58 -0000 On Tuesday, September 11, 2012 4:00:21 pm Sean Bruno wrote: > The following reply was made to PR kern/171524; it has been noted by GNATS. > > From: Sean Bruno > To: bug-followup@FreeBSD.org, dhojnik@brainbits.net > Cc: > Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or > shutdown > Date: Tue, 11 Sep 2012 12:56:16 -0700 > > It looks like the fix is not in releng_91 for release. > http://svnweb.freebsd.org/base/stable/9/sys/dev/ipmi/ipmi.c?revision=239920&view=markup > > You can either patch the system by hand by applying this change to your > local tree or update to stable/9 to fix this. > > http://www.wonkity.com/~wblock/docs/html/stable.html This has nothing to do with freebsd-net@ either, but it should probably be closed since it is fixed in HEAD. -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 15:34:42 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38661106564A; Thu, 13 Sep 2012 15:34:42 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 1FF4C8FC08; Thu, 13 Sep 2012 15:34:41 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8DFYfYv011864; Thu, 13 Sep 2012 08:34:41 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5051FD10.8040204@rawbw.com> Date: Thu, 13 Sep 2012 08:34:40 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Glen Barber References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> In-Reply-To: <20120913030153.GH1341@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 15:34:42 -0000 On 09/12/2012 20:01, Glen Barber wrote: > It would be helpful if you would at least try my cron(8) suggestion. So I tried adding the lines into crontab: @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 @reboot root /sbin/kldload /boot/modules/bcmwl5_sys.ko >/dev/null 2>&1 Firstly, for some reason, this method fails to load bcmwl5_sys.ko with the error message: KLD bcmwl5_sys.ko: depends on ndis - not available or version mismatch However, command 'kldload /boot/modules/bcmwl5_sys.ko' typed manually after boot succeeds without any messages. This is a mystery to me, why one way to run it produces this message and another one doesn't. And '/etc/rc.d/netif start' still doesn't start wifi even though all kernel modules were loaded after kernel boot. Yuri From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 16:36:17 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49A61106564A; Thu, 13 Sep 2012 16:36:17 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id C24158FC0C; Thu, 13 Sep 2012 16:36:16 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 8A79425D389C; Thu, 13 Sep 2012 16:36:14 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id A24D2BE858D; Thu, 13 Sep 2012 16:36:13 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id EVDo1JgO58UH; Thu, 13 Sep 2012 16:36:11 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id F1843BE858B; Thu, 13 Sep 2012 16:36:10 +0000 (UTC) Date: Thu, 13 Sep 2012 16:36:10 +0000 (UTC) From: "Bjoern A. Zeeb" To: luigi@FreeBSD.org In-Reply-To: <20120912211726.GB10974@onelab2.iet.unipi.it> Message-ID: References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Gleb Smirnoff , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 16:36:17 -0000 On Wed, 12 Sep 2012, Luigi Rizzo wrote: > On Wed, Sep 12, 2012 at 04:34:57PM +0400, Gleb Smirnoff wrote: >> Hi, >> >> we (me and Bjoern) would like to establish a single place >> for all kinds of pfil(9) consumers, for current ones and >> for future as well. >> >> The place chosen is sys/netpfil. >> >> On first round we'd like to move there our Tier-1 firewalls: >> ipfw and pf. This also includes moving pf out of contrib. >> >> The plan of movement is the following: >> >> sys/contrib/pf/net/*.c -> sys/netpfil/pf/ >> sys/contrib/pf/net/*.h -> sys/net/ [1] >> contrib/pf/pfctl/*.c -> sbin/pfctl >> contrib/pf/pfctl/*.h -> sbin/pfctl >> contrib/pf/pfctl/pfctl.8 -> sbin/pfctl >> contrib/pf/pfctl/*.4 -> share/man/man4 >> contrib/pf/pfctl/*.5 -> share/man/man5 >> >> sys/netinet/ipfw -> sys/netpfil/ipfw > > I have two concerns against moving ipfw/ > > - what do we gain by moving ipfw/ further > away from its user header files (whose location in netinet/ > is pretty much part of the API so difficult to change) ? What do we gain by having 3 firewalls ... in three different places ... in the tree? The result is that ipfw unconditionally depends on a pf header file .. oops .. that actually is an ALTQ thing *bummer*. > - pfil is just one of the APIs that the ipfw code > uses to send/receive packets (pfil, netmap for FreeBSD, > and then netfilter and ndispacket for the other OS). The other two really don't count for us. > The pfil dependencies amount to probably 1% of the code. > So if we really want to relocate ipfw/ i'd rather move to > a more generic place (but as far as i know we do not have > one for subsystems -- dev/ is used for drivers, other stuff > has generally accumulated under sys/ ,see geom, ofed, netgraph). You may remember we talked about this in the FreeBSD 8.0-CURRENT(?) times when ipfw moved the last time. So suggestions as saying no and not coming up with anything better is not helpful otherwise I'll tell to glebius "sorry for holding you up for 3 days" go head with his initial proposal to also put pf into netinet/pf if you'd prefer that? /bz -- Bjoern A. Zeeb You have to have visions! Sometimes you wonder why people are so reluctant to cleaning things up and finding a good soultion for the next decade. It's no fun probably? From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 16:51:16 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61CE71065673; Thu, 13 Sep 2012 16:51:16 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 2D8338FC0C; Thu, 13 Sep 2012 16:51:16 +0000 (UTC) Received: from glenbarber.us (75-146-225-65-Philadelphia.hfc.comcastbusiness.net [75.146.225.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id AB97123F6D9; Thu, 13 Sep 2012 12:51:13 -0400 (EDT) Date: Thu, 13 Sep 2012 12:51:12 -0400 From: Glen Barber To: Yuri Message-ID: <20120913165111.GA2436@glenbarber.us> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <5051FD10.8040204@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 16:51:16 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2012 at 08:34:40AM -0700, Yuri wrote: > On 09/12/2012 20:01, Glen Barber wrote: > > It would be helpful if you would at least try my cron(8) suggestion. >=20 > So I tried adding the lines into crontab: > @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 > @reboot root /sbin/kldload /boot/modules/bcmwl5_sys.ko >/dev/null 2>&1 >=20 > Firstly, for some reason, this method fails to load bcmwl5_sys.ko with=20 > the error message: > KLD bcmwl5_sys.ko: depends on ndis - not available or version mismatch >=20 Hmm. This should also be loading ndis.ko. If not, add that to the cron line as well. If that is the problem, sorry, that was my mistake. Also, are your kernel and userland in sync? And is this module built on the kernel you are currently running? Glen > However, command 'kldload /boot/modules/bcmwl5_sys.ko' typed manually=20 > after boot succeeds without any messages. This is a mystery to me, why=20 > one way to run it produces this message and another one doesn't. >=20 > And '/etc/rc.d/netif start' still doesn't start wifi even though all=20 > kernel modules were loaded after kernel boot. >=20 --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUg7/AAoJEFJPDDeguUajpg8H/223JVHiDZWEUufXbC2Vogif z0aDQzjU4VDZ0DwakFDeVYVPdBLqbFKMGgGMcBtk9g2/M93efw2YyZESq6doWVqz u+zsX2rjYpfqtla+rK3d7TmijlyAUwEggt+fPtF5Hcpf6XFvvh3TES1cmunhWqiQ Zy42LvcDLnOkJ0Yve0UgWmXV5+gR1jbjZch4Mhryb7K9mMnmBuSOaMn2wEBpC24W 0u7W+D6rEIe+2WHb4WaxMAGuD4+FE/JT2eBvDLnbFOVIYj3sgdvQqgnNmH7kawLo f4p0plhvU37AUCARzgYiiX1O9uj42Nc7017ur15HI0vYZBcX8pakIX01mWqInY8= =xToo -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 17:04:13 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5014106566B for ; Thu, 13 Sep 2012 17:04:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id AD3B28FC16 for ; Thu, 13 Sep 2012 17:04:13 +0000 (UTC) Received: by dadr6 with SMTP id r6so2024083dad.13 for ; Thu, 13 Sep 2012 10:04:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aIjP3xOOg960czs7AdDJlTznd/kAiCD1AdXJQ9Yee5I=; b=xcnl9o7MzPcw6qjV1+WBiF1eRHxSvq7fe+Hf4nxhETdRkR0xpy6UsMxWYeK3yiu4pk SUbNuuhZdMAEmTUTMUfHEwEtELwU5uaihnUOeWBjbYAXho9sK9q+/ZDidANw1uuDTjI1 mFRCBQPEZc+wKQj0EQM+TpE7X1OFo0n/mx6FJ9QV7asOnSN2ddZu9ly5NLzbBInuS0V7 IDx4NByTdBz7pq2SATB69ljayodxG7f9RqsuPExP0jY0khHZeLKdiAEDardrpA/9SFcF RAt5qGnRoKlgTn2xQTUpzo9QqXDVeBTW64w/EpXCuq62l52lmyLAmIRzjNBcpYOKxolw 8ROQ== MIME-Version: 1.0 Received: by 10.68.136.40 with SMTP id px8mr289451pbb.153.1347555853189; Thu, 13 Sep 2012 10:04:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Thu, 13 Sep 2012 10:04:13 -0700 (PDT) In-Reply-To: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> Date: Thu, 13 Sep 2012 10:04:13 -0700 X-Google-Sender-Auth: NqUV9MNEJnLgtLNBKHfmbZvpPHw Message-ID: From: Adrian Chadd To: =?UTF-8?B?0JLQsNC00LjQvCDQo9GA0LDQt9Cw0LXQsg==?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 17:04:14 -0000 On 13 September 2012 03:04, =D0=92=D0=B0=D0=B4=D0=B8=D0=BC =D0=A3=D1=80=D0= =B0=D0=B7=D0=B0=D0=B5=D0=B2 wrote: > I have the same issue (default gateway unexpectedly changes on some rando= m > address) on FreeBSD 9.0 Box with lot of traffic going through it, I have = a > wild guess that it is related to libalias compilled into kernel (trouble= s > start showing itself when I started to use ipfw nat functionality ). OOO. Wait. Is ipfw nat the common thread with all the people demonstrating this issue? Adrian From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 17:17:38 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFA41106564A; Thu, 13 Sep 2012 17:17:38 +0000 (UTC) (envelope-from krzysiek@airnet.opole.pl) Received: from base.airnet.opole.pl (ns2.airmax.pl [176.111.128.3]) by mx1.freebsd.org (Postfix) with ESMTP id 58B7E8FC08; Thu, 13 Sep 2012 17:17:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by base.airnet.opole.pl (Postfix) with ESMTP id 79FC67FF02F; Thu, 13 Sep 2012 19:17:31 +0200 (CEST) Received: from base.airnet.opole.pl ([127.0.0.1]) by localhost (mail.airnet.opole.pl [127.0.0.1]) (maiad, port 10024) with ESMTP id 51292-03; Thu, 13 Sep 2012 19:17:31 +0200 (CEST) Received: from [10.10.11.223] (unknown [176.111.138.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: krzysiek@airnet.opole.pl) by base.airnet.opole.pl (Postfix) with ESMTPSA id 4EC1D7FF020; Thu, 13 Sep 2012 19:17:31 +0200 (CEST) Message-ID: <50521527.1090507@airnet.opole.pl> Date: Thu, 13 Sep 2012 19:17:27 +0200 From: Krzysztof Barcikowski User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 17:17:38 -0000 W dniu 2012-09-13 19:04, Adrian Chadd pisze: > On 13 September 2012 03:04, Вадим Уразаев wrote: >> I have the same issue (default gateway unexpectedly changes on some random >> address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a >> wild guess that it is related to libalias compilled into kernel (troubles >> start showing itself when I started to use ipfw nat functionality ). > OOO. > > Wait. Is ipfw nat the common thread with all the people demonstrating > this issue? > > > > > Adrian > Hi! I don't use ipfw nat, but I do use ipfw+dummynet and PF for nat/filtering - together. Krzysiek From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 17:21:26 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5CA6106564A; Thu, 13 Sep 2012 17:21:26 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 4C8E08FC08; Thu, 13 Sep 2012 17:21:25 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 5CBE57300B; Thu, 13 Sep 2012 19:41:05 +0200 (CEST) Date: Thu, 13 Sep 2012 19:41:05 +0200 From: Luigi Rizzo To: "Bjoern A. Zeeb" Message-ID: <20120913174105.GA22571@onelab2.iet.unipi.it> References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: luigi@FreeBSD.org, Gleb Smirnoff , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 17:21:26 -0000 On Thu, Sep 13, 2012 at 04:36:10PM +0000, Bjoern A. Zeeb wrote: > On Wed, 12 Sep 2012, Luigi Rizzo wrote: > > >On Wed, Sep 12, 2012 at 04:34:57PM +0400, Gleb Smirnoff wrote: > >> Hi, > >> > >> we (me and Bjoern) would like to establish a single place > >>for all kinds of pfil(9) consumers, for current ones and > >>for future as well. > >> > >> The place chosen is sys/netpfil. > >> > >> On first round we'd like to move there our Tier-1 firewalls: > >>ipfw and pf. This also includes moving pf out of contrib. > >> > >> The plan of movement is the following: > >> > >>sys/contrib/pf/net/*.c -> sys/netpfil/pf/ > >>sys/contrib/pf/net/*.h -> sys/net/ [1] > >>contrib/pf/pfctl/*.c -> sbin/pfctl > >>contrib/pf/pfctl/*.h -> sbin/pfctl > >>contrib/pf/pfctl/pfctl.8 -> sbin/pfctl > >>contrib/pf/pfctl/*.4 -> share/man/man4 > >>contrib/pf/pfctl/*.5 -> share/man/man5 > >> > >>sys/netinet/ipfw -> sys/netpfil/ipfw > > > >I have two concerns against moving ipfw/ > > > >- what do we gain by moving ipfw/ further > > away from its user header files (whose location in netinet/ > > is pretty much part of the API so difficult to change) ? > > What do we gain by having 3 firewalls ... in three different places > ... in the tree? The point of my question was that if you do some work you expect some return, in the short or in the long term, otherwise you are wasting time. If you leave things as they are at least you break even. (i don't know what is the third firewall you mention, but it is irrelevent). Specifically, for ipfw i think the move is a mistake for the reason i am explaining below. > The result is that ipfw unconditionally depends on a pf header file > .. oops .. that actually is an ALTQ thing *bummer*. > > > >- pfil is just one of the APIs that the ipfw code > > uses to send/receive packets (pfil, netmap for FreeBSD, > > and then netfilter and ndispacket for the other OS). > > The other two really don't count for us. > > > > The pfil dependencies amount to probably 1% of the code. > > So if we really want to relocate ipfw/ i'd rather move to > > a more generic place (but as far as i know we do not have > > one for subsystems -- dev/ is used for drivers, other stuff > > has generally accumulated under sys/ ,see geom, ofed, netgraph). > > You may remember we talked about this in the FreeBSD 8.0-CURRENT(?) > times when ipfw moved the last time. > > So suggestions as saying no and not coming up with anything better > is not helpful otherwise I'll tell to glebius "sorry for holding you > up for 3 days" go head with his initial proposal to also put pf into > netinet/pf if you'd prefer that? First of all: the relocation of pf/ is unrelated to the relocation of other subsystems. If Gleb or you or both feel that pf goes under netpfil/pf/ i am perfectly fine with it and i never said anything that blocks this move. Second: What i contest is the fact that you classify ipfw as a "pfil client", when pfil is just a tiny adaptation layer to access ipfw. I mentioned the three alternative APIs (netmap, netfilter, ndis) to witness the fact that pfil is irrelevant to ipfw's operation. Third: any code relocation comes with some pain -- specifically, netinet/ is hardwired in many #include paths in the ipfw sources > grep netinet/ipfw sys/netinet/ipfw/* | grep include | wc 35 70 1791 so having it relocated (and in different places between HEAD and STABLE/9, and other platforms that may not count for you but do count for the maintainer, aka me) causes some extra maintainance work which I am willing to take if there are good reasons, but i do not see now. So for pf do whatever you see fit, i never objected. For ipfw, i think that netinet/ is more appropriate than netpfil/ (i'd be ok with something like net-subsystems/ but we do not have one such a thing and i do not have the time and energy to discuss and create one). > /bz > > -- > Bjoern A. Zeeb You have to have visions! > Sometimes you wonder why people are so reluctant to cleaning things up > and finding a good soultion for the next decade. It's no fun probably? Is this coming from a new targeted .sig service ? :) Cleaning up/refactoring is actually quite fun and gives you the feeling that you get things done even though it is mostly mechanical work. It is the "finding a good solution" part that is much harder. cheers luigi From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 17:26:56 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A28E106568C; Thu, 13 Sep 2012 17:26:56 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3ED8FC08; Thu, 13 Sep 2012 17:26:55 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id C49E4508A1; Thu, 13 Sep 2012 13:26:54 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id 6BA9450858; Thu, 13 Sep 2012 13:26:54 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Thu, 13 Sep 2012 13:26:54 -0400 From: Dominic Blais To: Adrian Chadd , =?utf-8?B?0JLQsNC00LjQvCDQo9GA0LDQt9Cw0LXQsg==?= Date: Thu, 13 Sep 2012 13:26:46 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2R0dqpTK77F/1dQkC8RKLzNjftzAAAwHig Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> In-Reply-To: Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 17:26:56 -0000 SGksDQoNCkFsdG91Z2ggSSdtIHVzaW5nIGlwZncgZm9yIHRyYWZmaWMgc2hhcGluZywgSSdtIG5v dCB1c2luZyBpdCBmb3IgTkFULiBJJ20gdXNpbmcgUEYgZm9yIE5BVC4NCg0KDQotLQ0KDQoNCg0K LS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQpEZcKgOiBvd25lci1mcmVlYnNkLW5ldEBmcmVl YnNkLm9yZyBbbWFpbHRvOm93bmVyLWZyZWVic2QtbmV0QGZyZWVic2Qub3JnXSBEZSBsYSBwYXJ0 IGRlIEFkcmlhbiBDaGFkZA0KRW52b3nDqcKgOiAxMyBzZXB0ZW1icmUgMjAxMiAxMzowNA0Kw4DC oDog0JLQsNC00LjQvCDQo9GA0LDQt9Cw0LXQsg0KQ2PCoDogZnJlZWJzZC1uZXRAZnJlZWJzZC5v cmcNCk9iamV0wqA6IFJlOiBrZXJuZWw6IGFycHJlc29sdmU6IGNhbid0IGFsbG9jYXRlIGxsaW5m byBmb3IgNjUuNTkuMjMzLjEwMg0KDQpPbiAxMyBTZXB0ZW1iZXIgMjAxMiAwMzowNCwg0JLQsNC0 0LjQvCDQo9GA0LDQt9Cw0LXQsiA8dHJldHVsaXkyQGdtYWlsLmNvbT4gd3JvdGU6DQo+IEkgaGF2 ZSB0aGUgc2FtZSBpc3N1ZSAoZGVmYXVsdCBnYXRld2F5IHVuZXhwZWN0ZWRseSBjaGFuZ2VzIG9u IHNvbWUgDQo+IHJhbmRvbQ0KPiBhZGRyZXNzKSBvbiBGcmVlQlNEIDkuMCBCb3ggd2l0aCBsb3Qg b2YgdHJhZmZpYyBnb2luZyB0aHJvdWdoIGl0LCBJIA0KPiBoYXZlIGEgd2lsZCBndWVzcyB0aGF0 IGl0IGlzIHJlbGF0ZWQgdG8gIGxpYmFsaWFzIGNvbXBpbGxlZCBpbnRvIA0KPiBrZXJuZWwgKHRy b3VibGVzIHN0YXJ0IHNob3dpbmcgaXRzZWxmIHdoZW4gSSBzdGFydGVkIHRvIHVzZSAgaXBmdyBu YXQgZnVuY3Rpb25hbGl0eSApLg0KDQpPT08uDQoNCldhaXQuIElzIGlwZncgbmF0IHRoZSBjb21t b24gdGhyZWFkIHdpdGggYWxsIHRoZSBwZW9wbGUgZGVtb25zdHJhdGluZyB0aGlzIGlzc3VlPw0K DQoNCg0KDQpBZHJpYW4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fDQpmcmVlYnNkLW5ldEBmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QNCmh0dHA6Ly9saXN0 cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtbmV0DQpUbyB1bnN1YnNjcmli ZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1uZXQtdW5zdWJzY3JpYmVAZnJlZWJzZC5vcmci DQo= From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 18:53:24 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95EE9106566B for ; Thu, 13 Sep 2012 18:53:24 +0000 (UTC) (envelope-from tretuliy2@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1208FC08 for ; Thu, 13 Sep 2012 18:53:23 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so4818408pbb.13 for ; Thu, 13 Sep 2012 11:53:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=dpmPg+CYM6+A9EIvCNWqIBRzQkD2X+H4O+hGNkWI8XY=; b=PzWkphe9OjAQT6Rd3YPiruWxftw0CzOWPMFcEQRZxmTEnejhn/wyNICHGRXf7be2mq LxBKVEssRZBTsGfhVt80/3J/z8qRFn158uahRuctwibLknIY3kzMWeyOCLg0K2RNMMBZ qFPNOcxnJOy6IY3M+b3j6uwXCEMZewsS9IP0fbuFAWX4wsPKjHg2jeDMsgWLR7TXyrZN PAtkHXzvbjVl6EAZqxUCPCGd+xOUv+B+YclzA7UnA+URGcUUJX4/JTg64GATNTacOCQs b6UBdVJVuWt12SpZ7nSjr/BJPj3epNe+XxYcIF3gRohNjsk7vYYDrwi6MTcT2qemIu9a 53Sg== MIME-Version: 1.0 Received: by 10.68.130.201 with SMTP id og9mr874580pbb.12.1347562403802; Thu, 13 Sep 2012 11:53:23 -0700 (PDT) Received: by 10.66.156.170 with HTTP; Thu, 13 Sep 2012 11:53:23 -0700 (PDT) In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> Date: Thu, 13 Sep 2012 21:53:23 +0300 Message-ID: From: =?KOI8-R?B?98HEyc0g9dLB2sHF1w==?= To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 18:53:24 -0000 Then my guess is wrong. I found the message, where similiar problem was described in ipfw mailling list http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with no answer. Maybe it will be usefull for somebody. From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 19:31:33 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72CEF106566B; Thu, 13 Sep 2012 19:31:33 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id E557C8FC08; Thu, 13 Sep 2012 19:31:32 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8DJVPin097971; Thu, 13 Sep 2012 23:31:25 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8DJVPJN097970; Thu, 13 Sep 2012 23:31:25 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 13 Sep 2012 23:31:25 +0400 From: Gleb Smirnoff To: Luigi Rizzo Message-ID: <20120913193125.GO85604@glebius.int.ru> References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> <20120913174105.GA22571@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20120913174105.GA22571@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: luigi@FreeBSD.org, "Bjoern A. Zeeb" , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 19:31:33 -0000 On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote: L> Second: L> What i contest is the fact that you classify ipfw as a "pfil client", L> when pfil is just a tiny adaptation layer to access ipfw. L> I mentioned the three alternative APIs (netmap, netfilter, ndis) L> to witness the fact that pfil is irrelevant to ipfw's operation. In FreeBSD ipfw is a pfil client. Dot. In Linux it is netfilter client, and if they want to they may or may not put it under netfilter/ipfw. We don't care. Same for Windows and ndis. ipfw isn't netinet specific, it also supports netinet6 and also supports layer2 pfil hooks. Putting all pfil clients into one place puts things in order. It simplifies kernel overview for newcomer, it makes things easier for those who want to hack on the pfil itself. L> Third: L> any code relocation comes with some pain -- specifically, netinet/ L> is hardwired in many #include paths in the ipfw sources L> L> > grep netinet/ipfw sys/netinet/ipfw/* | grep include | wc L> 35 70 1791 Numbers from your grep are impressive, but they are absolutely irrelevant. Actual diff for movement isn't that big. For example: - sys/net has zero diff, no files modified - sys/netinet/* has zero diff, just ipfw directory removed, no files modified - sbin/ipfw has zero diff This is actual diff that is already universe-tested. L> so having it relocated (and in different places between HEAD and L> STABLE/9, and other platforms that may not count for you but do L> count for the maintainer, aka me) causes some extra maintainance L> work which I am willing to take if there are good reasons, L> but i do not see now. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 19:47:27 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69151106566C; Thu, 13 Sep 2012 19:47:27 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 0913D8FC08; Thu, 13 Sep 2012 19:47:26 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 72A7578FC3; Thu, 13 Sep 2012 21:47:19 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id 57UnpgRruTVU; Thu, 13 Sep 2012 21:47:17 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id A7F2578FB5; Thu, 13 Sep 2012 21:47:17 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 9911219C41A; Thu, 13 Sep 2012 10:01:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id iyHe2vMaTfg5; Thu, 13 Sep 2012 10:01:31 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id ADADF19C416; Thu, 13 Sep 2012 10:01:30 +0200 (CEST) Message-ID: <50523843.8040006@zirakzigil.org> Date: Thu, 13 Sep 2012 21:47:15 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 19:47:27 -0000 On 09/12/2012 10:51 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: >> On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: >>> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. >>> >>> You're right, it seems to be pointing to the igb(4) driver in 9.x >>> compared to < 9.0. >>> >> How do you determine that since it doesn't happen without lagg? I've no >> reports of igb hanging otherwise and its being used extensively. > > Well, I did say "seems to". :) > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > and 9-STABLE on those three boxes. > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > non-LACP options were tried earlier in this thread, or if it's just > the LACP mode that's failing. If one mode works (say failover) and > LACP mode doesn't, that "seems to" point to lagg. Sorry, forgot to mention it. I tried both failover and lacp: neither worked. The switch is a Dell powerconnect 6248 with ports configured for aggragation. I first tried on a 9.1 prerelease, then on a 9.0 release to have everything clean. In both ssh, both as server and as client, become unresponsive and unkillable. The problem might also lie within ssh/d, but I somehow doubt it. I haven't tried other network services. From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 20:37:43 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9E5106564A; Thu, 13 Sep 2012 20:37:43 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id BD4468FC0C; Thu, 13 Sep 2012 20:37:42 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 03E237300A; Thu, 13 Sep 2012 22:57:22 +0200 (CEST) Date: Thu, 13 Sep 2012 22:57:21 +0200 From: Luigi Rizzo To: Gleb Smirnoff Message-ID: <20120913205721.GA24570@onelab2.iet.unipi.it> References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> <20120913174105.GA22571@onelab2.iet.unipi.it> <20120913193125.GO85604@glebius.int.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120913193125.GO85604@glebius.int.ru> User-Agent: Mutt/1.4.2.3i Cc: luigi@FreeBSD.org, "Bjoern A. Zeeb" , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2012 20:37:43 -0000 On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote: > On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote: > L> Second: > L> What i contest is the fact that you classify ipfw as a "pfil client", > L> when pfil is just a tiny adaptation layer to access ipfw. > L> I mentioned the three alternative APIs (netmap, netfilter, ndis) > L> to witness the fact that pfil is irrelevant to ipfw's operation. > > In FreeBSD ipfw is a pfil client. Dot. > > In Linux it is netfilter client, and if they want to they may or may not > put it under netfilter/ipfw. We don't care. Same for Windows and ndis. This is the second time a "we don't care" statement appears in this discussion and I find them extremely non constructive. I do not know who you consider as "we", but as one who maintains the code under multiple platforms i do have an interest in avoiding gratuitous changes that introduce differences between the various versions. > ipfw isn't netinet specific, it also supports netinet6 and also supports > layer2 pfil hooks. > > Putting all pfil clients into one place puts things in order. It simplifies > kernel overview for newcomer, it makes things easier for those who want > to hack on the pfil itself. > > L> Third: > L> any code relocation comes with some pain -- specifically, netinet/ > L> is hardwired in many #include paths in the ipfw sources > L> > L> > grep netinet/ipfw sys/netinet/ipfw/* | grep include | wc > L> 35 70 1791 > > Numbers from your grep are impressive, but they are absolutely irrelevant. > Actual diff for movement isn't that big. For example: > > - sys/net has zero diff, no files modified > - sys/netinet/* has zero diff, just ipfw directory removed, no files modified > - sbin/ipfw has zero diff please remain in context. We were talking about the files in netinet/ipfw, which have #include in them, so when moved to the new location these 35 lines need to be changed to #include Which is completely trivial, but introduces a difference between the files in HEAD and those in stable/9 (and in the other versions "we don't care" about) . Now if your plan involves removing the netinet/ prefix and adding ... compile-with "${NORMAL_C} -I$S/netpfil" to the lines in HEAD:sys/conf/files, and ... compile-with "${NORMAL_C} -I$S/netinet" for those in stable/9, i can lift this objection. I still think that a subsystem should not be classified by looking at one of the APIs it uses, but rather based on overall functionality. Hence in my opinion ipfw does not belong under netpfil/ more than it belongs under netinet/ , and lacking a better place i consider the relocation a gratuitous one. > This is actual diff that is already universe-tested. (attachment probably stripped by the mailing list ?) cheers luigi From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 00:45:31 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE807106567F; Fri, 14 Sep 2012 00:45:31 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 84D418FC21; Fri, 14 Sep 2012 00:45:31 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q8E0jURS025407; Thu, 13 Sep 2012 18:45:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q8E0jT3U025404; Thu, 13 Sep 2012 18:45:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 13 Sep 2012 18:45:29 -0600 (MDT) From: Warren Block To: Glen Barber In-Reply-To: <20120913165111.GA2436@glenbarber.us> Message-ID: References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 13 Sep 2012 18:45:30 -0600 (MDT) Cc: Yuri , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 00:45:31 -0000 On Thu, 13 Sep 2012, Glen Barber wrote: > On Thu, Sep 13, 2012 at 08:34:40AM -0700, Yuri wrote: >> On 09/12/2012 20:01, Glen Barber wrote: >>> It would be helpful if you would at least try my cron(8) suggestion. >> >> So I tried adding the lines into crontab: >> @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 >> @reboot root /sbin/kldload /boot/modules/bcmwl5_sys.ko >/dev/null 2>&1 >> >> Firstly, for some reason, this method fails to load bcmwl5_sys.ko with >> the error message: >> KLD bcmwl5_sys.ko: depends on ndis - not available or version mismatch >> > > Hmm. This should also be loading ndis.ko. If not, add that to the cron > line as well. If that is the problem, sorry, that was my mistake. On a fast machine, there could be a race there. Best to load them in order in a single command: @reboot root /sbin/kldload if_ndis.ko && /sbin/kldload bcmwl5_sys.ko From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 04:44:25 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 048E4106564A for ; Fri, 14 Sep 2012 04:44:25 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 65A558FC0C for ; Fri, 14 Sep 2012 04:44:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id q8E4iLlD025445; Fri, 14 Sep 2012 14:44:22 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 14 Sep 2012 14:44:21 +1000 (EST) From: Ian Smith To: =?KOI8-R?B?98HEyc0g9dLB2sHF1w==?= In-Reply-To: Message-ID: <20120914143050.C51539@sola.nimnet.asn.au> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 04:44:25 -0000 On Thu, 13 Sep 2012 21:53:23 +0300, ????? ??????? wrote: > Then my guess is wrong. I found the message, where similiar problem was > described in ipfw mailling list > http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with > no answer. > Maybe it will be usefull for somebody. For that problem at least, and another that's just emerged in ipfw@ - also using ipfw kernel nat - all interfaces shown have TSO enabled. % man ipfw | tail | head -4 Due to the architecture of libalias(3), ipfw nat is not compatible with the TCP segmentation offloading (TSO). Thus, to reliably nat your net- work traffic, please disable TSO on your NICs using ifconfig(8). I couldn't find an ifconfig shown in this thread, so I'm left wondering whether TSO is configured on the OP's or any of the problem boxes here? cheers, Ian From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 04:52:00 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C049106564A; Fri, 14 Sep 2012 04:52:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 11AE38FC0A; Fri, 14 Sep 2012 04:51:59 +0000 (UTC) Received: by dadr6 with SMTP id r6so2383848dad.13 for ; Thu, 13 Sep 2012 21:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=EFUh68nDeINLdt0jkrIJ3x/VajfHUMoXFfCseVUg100=; b=PyupF+hxOwNinqgPPjpdGydmt7jSYAei6+l1TiT5w8qHm36q+HMQP887fJhHmyAOxh aHLFlVKqJx5wB4ttFMYp3+tlZrzmruh3+Bl7OUA4iR0oyeYyduCPcAwlh71Oy/gLtsTU G8qDoxHTa7pTCG5CymiZzbaCWNKIXvQr6wY0b8qcKQKkw/pPUfwPx0y011+9LYQbgWBQ q87gEf+WujWkrNhj1oZ2/O3R6EO1JiP7uz8d6K3CD/Io7EhB3agLaJcACgKgiMYvMT34 L6FtYnVjTQKXME6hfXgB5HX1WUz1CN1lMW9uQIIpi31Klcng/BrYNGYDmiBJ/BGK7USY vbhA== Received: by 10.66.90.36 with SMTP id bt4mr2552362pab.54.1347598319547; Thu, 13 Sep 2012 21:51:59 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id vf8sm408700pbc.27.2012.09.13.21.51.56 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Sep 2012 21:51:58 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 14 Sep 2012 13:51:45 -0700 From: YongHyeon PYUN Date: Fri, 14 Sep 2012 13:51:45 -0700 To: Jeremiah Lott Message-ID: <20120914205145.GA7612@michelle.cdnetworks.com> References: <201204270607.q3R67TiO026862@freefall.freebsd.org> <8339513D-6727-4343-A86E-4F5BB1F9827D@averesystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8339513D-6727-4343-A86E-4F5BB1F9827D@averesystems.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/167325: [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 04:52:00 -0000 On Fri, Sep 07, 2012 at 05:44:48PM -0400, Jeremiah Lott wrote: > On Apr 27, 2012, at 2:07 AM, linimon@FreeBSD.org wrote: > > > Old Synopsis: sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC > > New Synopsis: [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=167325 > > I did an analysis of this pr a while back and I figured I'd share. Definitely looks like a real problem here, but at least in 8.2 it is difficult to hit it. First off, vlan tagging is not required to hit this. The code is question does not account for any amount of link-local header, so you can reproduce the bug even without vlans. > > In order to trigger it, the tcp stack must choose to send a tso "packet" with a total size (including tcp+ip header and options, but not link-local header) between 65522 and 65535 bytes (because adding 14 byte link-local header will then exceed 64K limit). In 8.1, the tcp stack only chooses to send tso bursts that will result in full mtu-size on-wire packets. To achieve this, it will truncate the tso packet size to be a multiple of mss, not including header and tcp options. The check has been relaxed a little in head, but the same basic check is still there. None of the "normal" mtus have multiples falling in this range. To reproduce it I used an mtu of 1445. When timestamps are in use, every packet has a 40 bytes tcp/ip header + 10 bytes for the timestamp option + 2 bytes pad. You can get a packet length 65523 as follows: > > 65523 - (40 + 10 + 2) = 65471 (size of tso packet data) > 65471 / 47 = 1393 (size of data per on-wire packet) > 1393 + (40 + 10 + 2) = 1445 (mtu is data + header + options + pad) > > Once you set your mtu to 1445, you need a program that can get the stack to send a maximum sized packet. With the congestion window that can be more difficult than it seems. I used some python that sends enough data to open the window, sleeps long enough to drain all outstanding data, but not long enough for the congestion window to go stale and close again, then sends a bunch more data. It also helps to turn off delayed acks on the receiver. Sometimes you will not drain the entire send buffer because an ack for the final chunk is still delayed when you start the second transmit. When the problem described in the pr hits, the EINVAL from bus_dmamap_load_mbuf_sg bubbles right up to userspace. > > At first I thought this was a driver bug rather than stack bug. The code in question does what it is commented to do (limit the tso packet so that ip->ip_len does not overflow). However, it also seems reasonable that the driver limit its dma tag at 64K (do we really want it allocating another whole page just for the 14 byte link-local header). Perhaps the tcp stack should ensure that the tso packet + max_linkhdr is < 64K. Comments? Hmm, I think it's a driver bug. Upper stack may not know whether L2 includes VLAN. Almost all drivers in tree includes L2 header size in DMA tag. If ethernet hardwares can handle this oversized frames(64KB + L2 header) with TSOv4/TSOv6 I think there is no reason not to support it. > > As an aside, the patch attached to the pr is also slightly wrong. Taking the max_linkhdr into account when rounding the packet to be a multiple of mss does not make sense, it should only take it into account when calculating the max tso length. > > Jeremiah Lott > Avere Systems From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 06:29:46 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22E1D106564A for ; Fri, 14 Sep 2012 06:29:46 +0000 (UTC) (envelope-from tretuliy2@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id DD27F8FC08 for ; Fri, 14 Sep 2012 06:29:45 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so5587788pbb.13 for ; Thu, 13 Sep 2012 23:29:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gJMRLABrpfE0NuclFKBXm2hC/D0hw2VFd0+sbOxzMUg=; b=X4cTKNeM4nBGtkvVwlabHD9MVt87UW0CTG7xVS6YQRlEdiC/EKwb4FL6Zq1WCNWYPp efpq21kBkbUFzMbvZJTpRKbUObAIYR+skqksTGQfQvOKbzM+7d+ezEMWiyhmapSgTXax K5Cx5wBWTUGKyQ0V6UR8bMYdNeDQdm0kU42M0nM7A5Fz5/c/+o7dbhJgbxQ3uG2faQ8N UoI7iHb1ZQCFYW1xz+fVmKDMV9EsqNzSKNnDL2FkAE7ABmqedeGR/50LIzSG/YOO0FGt 8iD3frRXj+mZJS0GvUF0RuqOco+E44PdGBXf3wwjbXEM9WJ3yg85UIGQe1iY3ktbED5U vnsg== MIME-Version: 1.0 Received: by 10.66.75.168 with SMTP id d8mr2936043paw.63.1347604185266; Thu, 13 Sep 2012 23:29:45 -0700 (PDT) Received: by 10.66.156.170 with HTTP; Thu, 13 Sep 2012 23:29:45 -0700 (PDT) In-Reply-To: <20120914143050.C51539@sola.nimnet.asn.au> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> <20120914143050.C51539@sola.nimnet.asn.au> Date: Fri, 14 Sep 2012 09:29:45 +0300 Message-ID: From: =?KOI8-R?B?98HEyc0g9dLB2sHF1w==?= To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 06:29:46 -0000 I am using two lagg interfaces : lagg0: flags=8843 metric 0 mtu 1500 options=400b8 ether 00:1b:21:55:a7:c4 nd6 options=9 media: Ethernet autoselect status: active laggproto lacp laggport: igb1 flags=1c laggport: igb0 flags=1c lagg1: flags=8843 metric 0 mtu 1500 options=400b8 ether 00:1b:21:63:59:c8 nd6 options=9 media: Ethernet autoselect status: active laggproto lacp laggport: igb3 flags=1c laggport: igb2 flags=1c I am not using ipfw nat for a while, and problem still occur. uname -a FreeBSD bras-2 9.0-RELEASE FreeBSD 9.0-RELEASE #1: Tue Feb 28 10:50:04 EET 2012 root@bras:/usr/obj/usr/src/sys/BRAS amd64 Xeon X3440/RAM - 4G, two network cards Intel Pro 1000 ET Dual Port. It has 400 Mbit/s traffic at peak going through. my ipfw rules are: 00100 allow ip from any to any via lo0 00200 deny ip from 127.0.0.0/8 to any 00300 deny ip from any to 127.0.0.0/8 00400 netgraph 1 udp from 10.0.0.0/8 to any dst-port 53 in via vlan* // Filter MX recods requests from RFC Net 00500 deny ip from table(2) to not x.x.x.x dst-port 25 01000 allow udp from any 68 to any dst-port 67 in via vlan* 01100 deny log icmp from any to any icmptypes 5,9,10 07000 allow ip from any to table(80) dst-port 53 // DNS ALLOW 07100 allow ip from table(80) 53 to any // DNS Reverse Allow 07200 allow ip from any to x.x.x.x // Billing Allow 07300 allow ip from x.x.x.x to any // Billing Reverse Allow 08000 fwd 127.0.0.1,83 ip from table(3) to not x.x.x.x dst-port 80,443,8080 in recv vlan* // New-Computers 08100 fwd 127.0.0.1,82 ip from not table(20) to not x.x.x.x dst-port 80,443,8080 in recv vlan* // Debotors 09000 allow ip from any to 255.255.255.255 dst-port 67 in via vlan* 10000 allow ip from table(20) to table(10) in recv vlan* // UA-IX Without shapers 10100 allow ip from table(10) to table(20) out xmit vlan* 10200 allow ip from table(20,0) to any in recv vlan* 10300 allow ip from any to table(20,0) out xmit vlan* 40000 pipe tablearg ip from any to table(20) out xmit vlan* 40100 pipe tablearg ip from table(21) to any in recv vlan* 40800 allow ip from table(20) to any out xmit ext_if 40900 allow ip from any to table(20) in recv ext_if 50000 allow ip from me to any 50005 allow tcp from any to me established 50010 allow tcp from any to me dst-port 125,53,83,84 setup 50020 allow udp from any to me dst-port 53,161 50030 allow icmp from any to me icmptypes 0,8 50040 allow tcp from x.x.x.x to me dst-port 72 setup 50050 deny tcp from any to me dst-port 72 setup 50100 allow ip from any to me 50300 allow ip from any to any out via vlan* 65500 deny log ip from any to any 65535 allow ip from any to any route monitor didn`t show event that changes default router. I use a script in crontab to restore proper gateway, for now. I am wandering: is it dummynet issue, because we all using it. My statistics of changing default gateway is follows August 5 August 14 August 18 September 2 September 6 I will appriciate any suggestion in debugging that problem. > > > I couldn't find an ifconfig shown in this thread, so I'm left wondering > whether TSO is configured on the OP's or any of the problem boxes here? > > cheers, Ian > From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 06:34:31 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA4D9106566B for ; Fri, 14 Sep 2012 06:34:31 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9B7A78FC16 for ; Fri, 14 Sep 2012 06:34:31 +0000 (UTC) Received: by oagm1 with SMTP id m1so3201439oag.13 for ; Thu, 13 Sep 2012 23:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=bybQewMBix4ZoVR1SxsZPJ82HuSGHcBXPzv49RmCwO4=; b=O0iPCnITUKw5RJJoY0WRI7ySZcOne4eGBxpOtWlgfF/HU8Wy1Tl6bWAOPUYH3p6cgT lsLdOitJfycIaSgkCh7slWr6TCBKFFcaTfE8EL2nzA04g1CKE8CiBZhtu7aX392QFq5D ZNJfYOBW6N6CUGWdJNDliNM7cCRR1tQHECeUHAt7Kg0sF2m40yet9kTg2fXu1oS0HRBt S86Ih06R6i5Yy+U7vnIKyINd3JX/0V1f2oSE7PwDxuk3l4KBfAlhjgLMSiMjpBQU2wRL 7Bx8BnTWVmuZVlaANk4poRq5AWqpZ2W0847cZhje/EDuIsuVlq2llMxGpm4zkZAhhE7i v1/Q== MIME-Version: 1.0 Received: by 10.182.222.39 with SMTP id qj7mr1721416obc.16.1347604471036; Thu, 13 Sep 2012 23:34:31 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Thu, 13 Sep 2012 23:34:30 -0700 (PDT) In-Reply-To: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> <20120914143050.C51539@sola.nimnet.asn.au> Date: Thu, 13 Sep 2012 23:34:30 -0700 Message-ID: From: Garrett Cooper To: =?UTF-8?B?0JLQsNC00LjQvCDQo9GA0LDQt9Cw0LXQsg==?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 06:34:32 -0000 On Thu, Sep 13, 2012 at 11:29 PM, =D0=92=D0=B0=D0=B4=D0=B8=D0=BC =D0=A3=D1= =80=D0=B0=D0=B7=D0=B0=D0=B5=D0=B2 wrote: > I am using two lagg interfaces : > lagg0: flags=3D8843 metric 0 mtu = 1500 > options=3D400b8 > ether 00:1b:21:55:a7:c4 > nd6 options=3D9 > media: Ethernet autoselect > status: active > laggproto lacp > laggport: igb1 flags=3D1c > laggport: igb0 flags=3D1c > > lagg1: flags=3D8843 metric 0 mtu = 1500 > options=3D400b8 > ether 00:1b:21:63:59:c8 > nd6 options=3D9 > media: Ethernet autoselect > status: active > laggproto lacp > laggport: igb3 flags=3D1c > laggport: igb2 flags=3D1c > > I am not using ipfw nat for a while, and problem still occur. > > uname -a > FreeBSD bras-2 9.0-RELEASE FreeBSD 9.0-RELEASE #1: Tue Feb 28 10:50:04 EE= T > 2012 root@bras:/usr/obj/usr/src/sys/BRAS amd64 > Xeon X3440/RAM - 4G, two network cards Intel Pro 1000 ET Dual Port. > It has 400 Mbit/s traffic at peak going through. > > > my ipfw rules are: > > 00100 allow ip from any to any via lo0 > 00200 deny ip from 127.0.0.0/8 to any > 00300 deny ip from any to 127.0.0.0/8 > 00400 netgraph 1 udp from 10.0.0.0/8 to any dst-port 53 in via vlan* // > Filter MX recods requests from RFC Net > 00500 deny ip from table(2) to not x.x.x.x dst-port 25 > 01000 allow udp from any 68 to any dst-port 67 in via vlan* > 01100 deny log icmp from any to any icmptypes 5,9,10 > 07000 allow ip from any to table(80) dst-port 53 // DNS ALLOW > 07100 allow ip from table(80) 53 to any // DNS Reverse Allow > 07200 allow ip from any to x.x.x.x // Billing Allow > 07300 allow ip from x.x.x.x to any // Billing Reverse Allow > 08000 fwd 127.0.0.1,83 ip from table(3) to not x.x.x.x dst-port 80,443,80= 80 > in recv vlan* // New-Computers > 08100 fwd 127.0.0.1,82 ip from not table(20) to not x.x.x.x dst-port > 80,443,8080 in recv vlan* // Debotors > 09000 allow ip from any to 255.255.255.255 dst-port 67 in via vlan* > 10000 allow ip from table(20) to table(10) in recv vlan* // UA-IX Withou= t > shapers > 10100 allow ip from table(10) to table(20) out xmit vlan* > 10200 allow ip from table(20,0) to any in recv vlan* > 10300 allow ip from any to table(20,0) out xmit vlan* > 40000 pipe tablearg ip from any to table(20) out xmit vlan* > 40100 pipe tablearg ip from table(21) to any in recv vlan* > 40800 allow ip from table(20) to any out xmit ext_if > 40900 allow ip from any to table(20) in recv ext_if > 50000 allow ip from me to any > 50005 allow tcp from any to me established > 50010 allow tcp from any to me dst-port 125,53,83,84 setup > 50020 allow udp from any to me dst-port 53,161 > 50030 allow icmp from any to me icmptypes 0,8 > 50040 allow tcp from x.x.x.x to me dst-port 72 setup > 50050 deny tcp from any to me dst-port 72 setup > 50100 allow ip from any to me > 50300 allow ip from any to any out via vlan* > 65500 deny log ip from any to any > 65535 allow ip from any to any > > route monitor didn`t show event that changes default router. > I use a script in crontab to restore proper gateway, for now. > I am wandering: is it dummynet issue, because we all using it. > My statistics of changing default gateway is follows > August 5 > August 14 > August 18 > September 2 > September 6 > > I will appriciate any suggestion in debugging that problem. Try disabling tso at the global level in the kernel. Under some circumstances with some drives VLAN_HWTSO -> TSO. -Garrett From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 07:09:41 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A073D106566C; Fri, 14 Sep 2012 07:09:41 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7F9CB8FC14; Fri, 14 Sep 2012 07:09:41 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8E79YaX002637; Fri, 14 Sep 2012 00:09:35 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5052D82E.4050005@rawbw.com> Date: Fri, 14 Sep 2012 00:09:34 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Warren Block References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Glen Barber , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 07:09:41 -0000 On 09/13/2012 17:45, Warren Block wrote: > > On a fast machine, there could be a race there. Best to load them in > order in a single command: > > @reboot root /sbin/kldload if_ndis.ko && /sbin/kldload > bcmwl5_sys.ko It was some mismatch between kernel/userland/ndis driver. After I fixed the mismatch, wifi still doesn't get initialized during boot and 'netif start' ran by hand also doesn't start it. Yuri From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 08:14:07 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 740461065673; Fri, 14 Sep 2012 08:14:07 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id EFE3A8FC18; Fri, 14 Sep 2012 08:14:05 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 69ADE7300A; Fri, 14 Sep 2012 10:33:40 +0200 (CEST) Date: Fri, 14 Sep 2012 10:33:40 +0200 From: Luigi Rizzo To: Gleb Smirnoff Message-ID: <20120914083340.GA31420@onelab2.iet.unipi.it> References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> <20120913174105.GA22571@onelab2.iet.unipi.it> <20120913193125.GO85604@glebius.int.ru> <20120913205721.GA24570@onelab2.iet.unipi.it> <20120914072350.GQ85604@glebius.int.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120914072350.GQ85604@glebius.int.ru> User-Agent: Mutt/1.4.2.3i Cc: luigi@FreeBSD.org, "Bjoern A. Zeeb" , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 08:14:07 -0000 On Fri, Sep 14, 2012 at 11:23:50AM +0400, Gleb Smirnoff wrote: > On Thu, Sep 13, 2012 at 10:57:21PM +0200, Luigi Rizzo wrote: > L> On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote: > L> > On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote: > L> > L> Second: > L> > L> What i contest is the fact that you classify ipfw as a "pfil client", > L> > L> when pfil is just a tiny adaptation layer to access ipfw. > L> > L> I mentioned the three alternative APIs (netmap, netfilter, ndis) > L> > L> to witness the fact that pfil is irrelevant to ipfw's operation. > L> > > L> > In FreeBSD ipfw is a pfil client. Dot. > L> > > L> > In Linux it is netfilter client, and if they want to they may or may not > L> > put it under netfilter/ipfw. We don't care. Same for Windows and ndis. > L> > L> This is the second time a "we don't care" statement appears in > L> this discussion and I find them extremely non constructive. > > Don't take "we don't care" out of context! We don't care where ipfw > resides in Linux or Windows. I don't see why we should to. We do care > where pfil consumers reside in FreeBSD. i am not taking it out of context, i am saying that deliberately ignoring that this (or other) code is used elsewhere is not a sensible thing to do -- it makes maintainance harder, reduces the chance of getting bugfixes from the outside, etc. Not long ago there was a thread on using wrappers to access ifnet fields so that third parties have an easier time in using our code, and this is the approach that we should follow. So rather than "we don't care" i'd like to read "let's see if we can find a solution that satisfies all". I take your offer to move the code also in stable/9 as a step in this direction. So, to somehow close the issue (as it seems a made decision) > L> I do not know who you consider as "we", but as one who maintains > L> the code under multiple platforms i do have an interest in avoiding > L> gratuitous changes that introduce differences between the various > L> versions. > > The movement is mergeable since userland doesn't depend on it. If you'd > like I could merge movement to stable/9, so you won't have any differencies > between maintained versions. deal. > L> please remain in context. > L> We were talking about the files in netinet/ipfw, which have > L> #include > L> in them, so when moved to the new location these 35 lines > L> need to be changed to > L> #include > L> Which is completely trivial, but introduces a difference between > L> the files in HEAD and those in stable/9 (and in the other versions > L> "we don't care" about) . > > Does ipfw resides in netinet/ipfw on other platforms: Linux, Windows? right now yes (it's an external module, so the only real concern is the hardwired netinet/ in the #includes). I dont mind relocating it there too, as long as it is done everywhere. > L> Now if your plan involves removing the netinet/ prefix and adding > L> ... compile-with "${NORMAL_C} -I$S/netpfil" > L> to the lines in HEAD:sys/conf/files, and > L> ... compile-with "${NORMAL_C} -I$S/netinet" > L> for those in stable/9, i can lift this objection. > > Don't see reason for -I. It compiles okay w/o it. See diff attached. It compiles because you have all these tiny changes: Index: sys/netpfil/ipfw/dn_heap.c =================================================================== --- sys/netpfil/ipfw/dn_heap.c (working copy) +++ sys/netpfil/ipfw/dn_heap.c (working copy) @@ -37,7 +37,7 @@ #include #include #include -#include +#include #ifndef log #define log(x, arg...) #endif and not just a plain 'svn mv'. > L> I still think that a subsystem should not be classified by looking > L> at one of the APIs it uses, but rather based on overall functionality. > L> Hence in my opinion ipfw does not belong under netpfil/ more than > L> it belongs under netinet/ , and lacking a better place i consider > L> the relocation a gratuitous one. > > Ipfw overall functionality is packet filtering. Since packet filtering > can happen at different layers and protocols, none of the following > directories suit perfectly: net, netinet, netinet6. Thus, we (me + Bjoern) > decided to make a separate directory for packet filters. Since all > packet filters attach to kernel via pfil(9) we decided to name > the directory netpfil. Up until now you were only talking about "pfil consumers", and this is what i was disagreeing about. Now you say netpfil/ is the home for "packet filters", which is a different story, and one that makes sense to me (but it also means that it can be used as the home for other packet filters even if they do not use the pfil api). So, it seems we have reached a compromise: netpfil is the home for "packet filters", and ipfw goes there also in stable/9 (or, if it is simpler, we remove the netinet/ prefix from the #include and compile with -I ...). ok ? cheers luigi From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 08:17:41 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2E121065672; Fri, 14 Sep 2012 08:17:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id EC23A8FC16; Fri, 14 Sep 2012 08:17:40 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8E8HdEl002359; Fri, 14 Sep 2012 12:17:39 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8E8HdSx002358; Fri, 14 Sep 2012 12:17:39 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 14 Sep 2012 12:17:39 +0400 From: Gleb Smirnoff To: Luigi Rizzo Message-ID: <20120914081739.GV85604@glebius.int.ru> References: <20120912123457.GC85604@glebius.int.ru> <20120912211726.GB10974@onelab2.iet.unipi.it> <20120913174105.GA22571@onelab2.iet.unipi.it> <20120913193125.GO85604@glebius.int.ru> <20120913205721.GA24570@onelab2.iet.unipi.it> <20120914072350.GQ85604@glebius.int.ru> <20120914083340.GA31420@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20120914083340.GA31420@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: luigi@FreeBSD.org, "Bjoern A. Zeeb" , net@FreeBSD.org Subject: Re: moving pfil consumers to sys/netpfil X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 08:17:41 -0000 On Fri, Sep 14, 2012 at 10:33:40AM +0200, Luigi Rizzo wrote: L> On Fri, Sep 14, 2012 at 11:23:50AM +0400, Gleb Smirnoff wrote: L> > On Thu, Sep 13, 2012 at 10:57:21PM +0200, Luigi Rizzo wrote: L> > L> On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote: L> > L> > On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote: L> > L> > L> Second: L> > L> > L> What i contest is the fact that you classify ipfw as a "pfil client", L> > L> > L> when pfil is just a tiny adaptation layer to access ipfw. L> > L> > L> I mentioned the three alternative APIs (netmap, netfilter, ndis) L> > L> > L> to witness the fact that pfil is irrelevant to ipfw's operation. L> > L> > L> > L> > In FreeBSD ipfw is a pfil client. Dot. L> > L> > L> > L> > In Linux it is netfilter client, and if they want to they may or may not L> > L> > put it under netfilter/ipfw. We don't care. Same for Windows and ndis. L> > L> L> > L> This is the second time a "we don't care" statement appears in L> > L> this discussion and I find them extremely non constructive. L> > L> > Don't take "we don't care" out of context! We don't care where ipfw L> > resides in Linux or Windows. I don't see why we should to. We do care L> > where pfil consumers reside in FreeBSD. L> L> i am not taking it out of context, i am saying that deliberately L> ignoring that this (or other) code is used elsewhere is not a sensible L> thing to do -- it makes maintainance harder, reduces the chance of L> getting bugfixes from the outside, etc. Not long ago there was a L> thread on using wrappers to access ifnet fields so that third L> parties have an easier time in using our code, and this is the L> approach that we should follow. L> L> So rather than "we don't care" i'd like to read "let's see if we can L> find a solution that satisfies all". I take your offer to move the L> code also in stable/9 as a step in this direction. L> L> So, to somehow close the issue (as it seems a made decision) L> L> > L> I do not know who you consider as "we", but as one who maintains L> > L> the code under multiple platforms i do have an interest in avoiding L> > L> gratuitous changes that introduce differences between the various L> > L> versions. L> > L> > The movement is mergeable since userland doesn't depend on it. If you'd L> > like I could merge movement to stable/9, so you won't have any differencies L> > between maintained versions. L> L> deal. L> L> > L> please remain in context. L> > L> We were talking about the files in netinet/ipfw, which have L> > L> #include L> > L> in them, so when moved to the new location these 35 lines L> > L> need to be changed to L> > L> #include L> > L> Which is completely trivial, but introduces a difference between L> > L> the files in HEAD and those in stable/9 (and in the other versions L> > L> "we don't care" about) . L> > L> > Does ipfw resides in netinet/ipfw on other platforms: Linux, Windows? L> L> right now yes (it's an external module, so the only real concern is L> the hardwired netinet/ in the #includes). L> I dont mind relocating it there too, as long as it is done everywhere. L> L> > L> Now if your plan involves removing the netinet/ prefix and adding L> > L> ... compile-with "${NORMAL_C} -I$S/netpfil" L> > L> to the lines in HEAD:sys/conf/files, and L> > L> ... compile-with "${NORMAL_C} -I$S/netinet" L> > L> for those in stable/9, i can lift this objection. L> > L> > Don't see reason for -I. It compiles okay w/o it. See diff attached. L> L> It compiles because you have all these tiny changes: L> L> Index: sys/netpfil/ipfw/dn_heap.c L> =================================================================== L> --- sys/netpfil/ipfw/dn_heap.c (working copy) L> +++ sys/netpfil/ipfw/dn_heap.c (working copy) L> @@ -37,7 +37,7 @@ L> #include L> #include L> #include L> -#include L> +#include L> #ifndef log L> #define log(x, arg...) L> #endif L> L> and not just a plain 'svn mv'. L> L> > L> I still think that a subsystem should not be classified by looking L> > L> at one of the APIs it uses, but rather based on overall functionality. L> > L> Hence in my opinion ipfw does not belong under netpfil/ more than L> > L> it belongs under netinet/ , and lacking a better place i consider L> > L> the relocation a gratuitous one. L> > L> > Ipfw overall functionality is packet filtering. Since packet filtering L> > can happen at different layers and protocols, none of the following L> > directories suit perfectly: net, netinet, netinet6. Thus, we (me + Bjoern) L> > decided to make a separate directory for packet filters. Since all L> > packet filters attach to kernel via pfil(9) we decided to name L> > the directory netpfil. L> L> Up until now you were only talking about "pfil consumers", L> and this is what i was disagreeing about. L> L> Now you say netpfil/ is the home for "packet filters", which is a L> different story, and one that makes sense to me (but it also means L> that it can be used as the home for other packet filters even if L> they do not use the pfil api). L> L> So, it seems we have reached a compromise: L> L> netpfil is the home for "packet filters", and ipfw goes there also L> in stable/9 (or, if it is simpler, we remove the netinet/ prefix L> from the #include and compile with -I ...). L> L> ok ? Thanks! I'm fine with this. Then I just need ack from Bjoern that the move is mergeable. IMO, it is mergeable, but I may miss something. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 08:21:44 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 146A51065670 for ; Fri, 14 Sep 2012 08:21:44 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id BECBC8FC16 for ; Fri, 14 Sep 2012 08:21:43 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id B5C4E5C946; Fri, 14 Sep 2012 10:21:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id WuCa_dOifEkc; Fri, 14 Sep 2012 10:21:42 +0200 (CEST) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 0AAC55C945; Fri, 14 Sep 2012 10:21:42 +0200 (CEST) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.incore (Postfix) with ESMTP id 04A134508A; Fri, 14 Sep 2012 10:21:42 +0200 (CEST) Message-ID: <5052E915.8050408@incore.de> Date: Fri, 14 Sep 2012 10:21:41 +0200 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky , freebsd-net@freebsd.org References: <504E1B19.3020901@incore.de> <201209102033.54948.hselasky@c2i.net> <504F4383.2080503@incore.de> <201209111652.17974.hselasky@c2i.net> In-Reply-To: <201209111652.17974.hselasky@c2i.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Cc: Subject: Re: ISDN4BSD (HPS version) is going into ports X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 08:21:44 -0000 Hi, >>>> Problem 2: I tried to get more information for problem 1 with the >>>> analyze mode of isdndecode using the custom cable as decribed in >>>> cable.txt. I connected my ISDN phone to an "ISDN Basisanschluß" with my >>>> cable box between them (receiving side unit 8, sending side unit 9), >>>> but after the commands >>>> >>>> cat /dev/ihfc8.X > /dev/null 2>&1 & (X=0,1,2) >>>> cat /dev/ihfc9.X > /dev/null 2>&1 & >>>> isdndecode -a -b -R 8 -T 9 -i -x >>>> > You need to run something like this first: > isdndebug -u 9 -b 0 -p P_HDLC -b 1 P_HDLC -b 2 P_TRANSPARENT > If it doesn't work, I will check later. A bit busy right now. Thanks for this. The D-channel trace works correct with your isdndebug command, but no luck with B-cahnnels. I also tried isdndebug -u 9 -b 0 -p P_HDLC -b 1 -p P_TRANS -b 2 -p P_TRANS and isdndebug -u 9 -b 0 -p P_HDLC -b 1 -p P_TRANS_RING -b 2 -p P_TRANS_RING with the same result: D-channel ok, B-channels give only X'FF'. I am not sure, if I had ever traced B-channel data in analyze mode successful before. -- Andreas Longwitz From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 10:37:24 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB52A106564A for ; Fri, 14 Sep 2012 10:37:24 +0000 (UTC) (envelope-from tretuliy2@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 902FE8FC08 for ; Fri, 14 Sep 2012 10:37:24 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so5901191pbb.13 for ; Fri, 14 Sep 2012 03:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CfLGyhXrl528aWfCSO+gzAGvo8s0botzKGE7+9sZUsA=; b=vjHq5isfmZ8AhHiKftuLCbrLA1v634sWyOuwL11VJfyL2sfCNXj4CkNW6Sjo18XnOf QmwAsDeYUxE4GhQfbys/0U28oUOHYgaQDCbo8HtGW1FQSsNFlUs05bS9nFTYINZSsDrN PeCbC9V9b9ZmA5WuCbHTKQe1vWkW0PclIBWElB2jl4CTE1SmmLv3ck6jYa3FaB2f/2x6 cwGqbMWvvQwbbUgIGc9gFx3JZQd+OPL52xUxvuFzb73mYezYmT9/+Pq/p+V8ySewi8G6 nY6s7R0dv+85wOPEFHVQ+4xArCe0xBDhnd+LbHJ+qcaYj0iLShLBgZ368DLs4+MUyo9F YIYA== MIME-Version: 1.0 Received: by 10.66.74.74 with SMTP id r10mr3677079pav.57.1347619043900; Fri, 14 Sep 2012 03:37:23 -0700 (PDT) Received: by 10.66.156.170 with HTTP; Fri, 14 Sep 2012 03:37:23 -0700 (PDT) In-Reply-To: References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca> <20120914143050.C51539@sola.nimnet.asn.au> Date: Fri, 14 Sep 2012 13:37:23 +0300 Message-ID: From: =?KOI8-R?B?98HEyc0g9dLB2sHF1w==?= To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 10:37:24 -0000 Ok, I will disable vlan_hwtso using ifconfig -vlanhwtso. Thanks. > Try disabling tso at the global level in the kernel. Under some > circumstances with some drives VLAN_HWTSO -> TSO. > -Garrett > From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 17:47:40 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4384D1065672; Fri, 14 Sep 2012 17:47:40 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8EA8FC0C; Fri, 14 Sep 2012 17:47:39 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8EHldVb056301; Fri, 14 Sep 2012 10:47:39 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <50536DBA.9000000@rawbw.com> Date: Fri, 14 Sep 2012 10:47:38 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> In-Reply-To: <5052D82E.4050005@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Warren Block , Glen Barber , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 17:47:40 -0000 On 09/14/2012 00:09, Yuri wrote: > > It was some mismatch between kernel/userland/ndis driver. After I > fixed the mismatch, wifi still doesn't get initialized during boot and > 'netif start' ran by hand also doesn't start it. Never mind, it was an issue of /etc out of sync with the world. Yuri From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 17:54:06 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 084BA106566C; Fri, 14 Sep 2012 17:54:06 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id C49B38FC1A; Fri, 14 Sep 2012 17:54:05 +0000 (UTC) Received: from glenbarber.us (75-146-225-65-Philadelphia.hfc.comcastbusiness.net [75.146.225.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id CBE7F23F6D9; Fri, 14 Sep 2012 13:54:04 -0400 (EDT) Date: Fri, 14 Sep 2012 13:54:03 -0400 From: Glen Barber To: Yuri Message-ID: <20120914175402.GC1323@glenbarber.us> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline In-Reply-To: <50536DBA.9000000@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Warren Block , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 17:54:06 -0000 --ZwgA9U+XZDXt4+m+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 14, 2012 at 10:47:38AM -0700, Yuri wrote: > On 09/14/2012 00:09, Yuri wrote: > > > > It was some mismatch between kernel/userland/ndis driver. After I=20 > > fixed the mismatch, wifi still doesn't get initialized during boot and= =20 > > 'netif start' ran by hand also doesn't start it. >=20 > Never mind, it was an issue of /etc out of sync with the world. >=20 Ok. Thanks for letting us know. Glen --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQU286AAoJEFJPDDeguUajNlgH/3JZNYDS7egyiKfVbZ/4xN1H J0aomgWwVX8QEwe6cdPiy73EcOAQW83yVxY+F1POaXKHe/pIc8tLfjiKPvANuPSM 26qUbbaQ5YZ6PAmO0aKKJVG+1B4/TpbpCAMycusNIGweBs/l1R7q1o7H5Fh8oY7W Jix0DFGKz1zF5mA2NqRpi2+k5ZG/2N2kgqoFm7SpHFbUETtiykwSc3CILoiZG/+F IZHhuV5mh7rZmSqLXWYccJvSNCV55ZXbxXJlndOkM8vxYDyX1fS5jr8Gdyiw+DwB Mx3wEDWgRM30Idpf/ZZqbBpWRupxtChJh1JS56snNGUcJDPFbZim3wnIPVoWd2M= =ClIl -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 18:32:32 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43B5010656A8; Fri, 14 Sep 2012 18:32:32 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 27D738FC14; Fri, 14 Sep 2012 18:32:31 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8EIWVJi071200; Fri, 14 Sep 2012 11:32:31 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5053783E.3080504@rawbw.com> Date: Fri, 14 Sep 2012 11:32:30 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Glen Barber References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> <20120914175402.GC1323@glenbarber.us> In-Reply-To: <20120914175402.GC1323@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 18:32:32 -0000 On 09/14/2012 10:54, Glen Barber wrote: > Ok. Thanks for letting us know. Now wpa_supplicant starts and is operational, however '/etc/rc.d/netif start' always issues this warning: Starting wpa_supplicant /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting Network: lo0 ndis0 re0. Also (as a result) dhclient isn't started, but succeeds when started manually. wpa_supplicant started by hand doesn't print any errors. I can't find any option in wpa_supplicant.conf making it to write a log what is wrong. On linux it seems to be -f option for the log file. Any way to make netif more verbose? Yuri From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 18:49:52 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9427D106566C; Fri, 14 Sep 2012 18:49:52 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E49DF8FC19; Fri, 14 Sep 2012 18:49:51 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1357240bkc.13 for ; Fri, 14 Sep 2012 11:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xBqbLslT8b1e1uSWndD/ulHzPfOLKGs/uC/as/ijzYo=; b=quFVRXGzzwl9QrMRmRjy5GRJp9/OywPnQSuBXO/ffMn9haGdM/B82c3VSOafoZ2s+3 kWGTH2I0BDgs5NvITmrbjZZofcACrDLptmKs/vwZ78guT5QOX3TnLlVRNba2AulRyKEa /0LzgDsmklg+VP+wGnBrxk5C0vPnbLaKyl9MNUZFZIv7C7E1aDb95U/j9vDmmDNgm0Cn CCiDlOc5icuWG2zJQKPxxhJUez3i5Gozx9Kmu6b16OTewmmCKWCx2dQpZJJweh6bvHDZ 6p5Qkx3NaqdkaetOc769JwqoE5J+7w4/fcmGSpYvY19upCP7xdukGlvGj3E6UCUQiLSC GjMA== MIME-Version: 1.0 Received: by 10.204.152.13 with SMTP id e13mr1844871bkw.10.1347648590509; Fri, 14 Sep 2012 11:49:50 -0700 (PDT) Received: by 10.204.163.206 with HTTP; Fri, 14 Sep 2012 11:49:50 -0700 (PDT) In-Reply-To: <5053783E.3080504@rawbw.com> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> <20120914175402.GC1323@glenbarber.us> <5053783E.3080504@rawbw.com> Date: Fri, 14 Sep 2012 11:49:50 -0700 Message-ID: From: hiren panchasara To: Yuri Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Glen Barber , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 18:49:52 -0000 On Fri, Sep 14, 2012 at 11:32 AM, Yuri wrote: > On 09/14/2012 10:54, Glen Barber wrote: > >> Ok. Thanks for letting us know. >> > > Now wpa_supplicant starts and is operational, however '/etc/rc.d/netif > start' always issues this warning: > Starting wpa_supplicant > /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant > Starting Network: lo0 ndis0 re0. > > Also (as a result) dhclient isn't started, but succeeds when started > manually. > wpa_supplicant started by hand doesn't print any errors. > > I can't find any option in wpa_supplicant.conf making it to write a log > what is wrong. On linux it seems to be -f option for the log file. > Any way to make netif more verbose? Not sure if you looked at - man wpa_supplicant, which has -d for debugging -s for pumping messages to syslog Thanks, Hiren From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 22:39:10 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 138FE10656F7; Fri, 14 Sep 2012 22:39:10 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id E88758FC1E; Fri, 14 Sep 2012 22:39:09 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8EMd71f037530; Fri, 14 Sep 2012 15:39:08 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5053B20B.7080205@rawbw.com> Date: Fri, 14 Sep 2012 15:39:07 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: hiren panchasara References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> <20120914175402.GC1323@glenbarber.us> <5053783E.3080504@rawbw.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Glen Barber , freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2012 22:39:10 -0000 On 09/14/2012 11:49, hiren panchasara wrote: > Not sure if you looked at - man wpa_supplicant, which has > -d for debugging > -s for pumping messages to syslog wpa_supplicant ran with -d -d doesn't print any error messages and runs fine. 'netif start' is the one issuing a warning and preventing dhclient from start. I am asking how to increase the verbosity and determine why netif thinks wpa_supplicant fails. Yuri From owner-freebsd-net@FreeBSD.ORG Sat Sep 15 18:27:03 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC4AB106564A for ; Sat, 15 Sep 2012 18:27:03 +0000 (UTC) (envelope-from mcmarc44@googlemail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 480148FC18 for ; Sat, 15 Sep 2012 18:27:03 +0000 (UTC) Received: by weyx56 with SMTP id x56so3625042wey.13 for ; Sat, 15 Sep 2012 11:27:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:from:to:subject:date:mime-version:content-type :content-transfer-encoding:x-priority; bh=uYMwZFNq+5VsrH+DIyhtFmHjCWuCSek7oJd/jAumE4k=; b=Js6erV3hcCpNk4zFEIFVWfs3VPvnBDlSUi67RmHWGl5lAB2J7llGNY2XxcHyD9XRO4 aNCLXLLnrEExhhl6NO0xhn3+Z4fNNc5EQJSHiIR2op2zOWWSxv1o5k4bNBjBcL1vOzXm QfLbKEKWL3tdCVYIU5ubVWvv+SvDcfL09iKDwDdRsAGUDLHtTw5AW4chdUi6aI4m8J4k CJ5NJjeHH3t0aSCK6ShqAe9JhRalsj6G/Czupv8JM1Vwmj/KUf0a4+BUu59d7BsdfvY5 8awIaJ5vWxqpC/qXlRX/XhoaDcbJ2mnuW3uSTMDp45o/FV6Yydgg9AQMxzZ+uo9W2Mjw MsbQ== Received: by 10.180.98.200 with SMTP id ek8mr6087080wib.0.1347733622229; Sat, 15 Sep 2012 11:27:02 -0700 (PDT) Received: from comet-PC (host-92-2-27-235.as43234.net. [92.2.27.235]) by mx.google.com with ESMTPS id cu1sm6634023wib.6.2012.09.15.11.26.59 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Sep 2012 11:27:00 -0700 (PDT) Message-ID: <02a0f26d-41167-03cd8103389699@comet-pc> From: "marc mccusker" To: freebsd-net@freebsd.org Date: Sat, 15 Sep 2012 19:25:56 +0100 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Priority: 3 Subject: WINTRILLIONS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2012 18:27:03 -0000 Quite simply, WinTrillions is the most significant lottery website on the planet - with more prizes, far more lotteries and bigger jackpots on provide than wherever else. As witnessed on Television set, WinTrillions.co.uk gives you the opportunity to engage in the world's richest official lotteries as element of syndicates, with above £300 Million in prizes offered to be won each and every simple week! Smart gamers decide on WinTrillions.co.united kingdom to increase their chances of successful the lottery. You never ever shed a ticket. You in no way skip a attract. And you are guaranteed to obtain your reveal of prizes when you acquire. WinTrillions.co.united kingdom is accredited and regulated in the United kingdom. Play from as small as £5 for every week and be part of their 191,835 lottery winners now. WinTrillions.co.uk (the trading name of Jackpot Messenger Services Ltd) is one of the world's greatest and most respected on the web lottery brokers. Since it released in 2005, Win Trillions has presented lottery game titles to over 250,000 customers about the world. Trillonario holds passions in firms in 4 various countries (the Uk, Spain, Cyprus and Uruguay) and has administrative workplaces and staff located about the planet. Lottery Games you can play: Spain El Gordo Lotto U.S.A New York Lotto Australia Powerball Australia Italy SuperEnalotto U.S.A Megamillions Lotto Australia Oz Lotto U.S.A California Lotto U.S.A Hoosier Lotto Canada Lotto United Kingdom National Lottery United Kingdom Thunderball Germany Lotto Spain La Primitiva France France Loto Brazil Mega Sena Lotto U.S.A Florida Lotto Ireland Irish Lotto U.S.A Hot Lotto Europe EuroJackpot Europe Euromillions Lotto Another great thing about this site is there are amazing discount packages so you can play upto 140 lines per week for a very good price. Now it is proven that 1/3 of jackpot winners have used websites like wintrillions. I dont know about use but i think increasing my odds in winning would be a big advantage. How many times have you went out buying a lottery ticket and going home and watched the draw and getting really excited? Lets face it everyone has and has had that feeling that your ticket is the golden ticket (wait thats willy wonka and the chocolate factory but you get the idea). Here are the great lotto syndicates that you can chose from: Power Combo Syndicate 140 lines each week EuroMillions Mini Syndicate 25 tickets each day EuroMillions Max Syndicate 50 tickets each draw Euro Combo Syndicate 70 lines each week SuperEnalotto Syndicate 20 tickets each day MegaMillions Syndicate 30 tickets each day Oz Lotto Syndicate 9 tickets each draw Spanish Primitiva Syndicate 40 tickets each draw Florida Syndicate 50 tickets each day Irish Lotto Syndicate 20 tickets each draw EuroJackpot Syndicate 20 tickets each draw SIGN-UP TODAY AND RECIEVE YOUR BONUS