From owner-freebsd-ipfw@freebsd.org Thu Mar 17 10:46:41 2016 Return-Path: Delivered-To: freebsd-ipfw@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19278AD31DC for ; Thu, 17 Mar 2016 10:46:41 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D06F71A9E; Thu, 17 Mar 2016 10:46:40 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: by mail-ob0-x236.google.com with SMTP id m7so79162491obh.3; Thu, 17 Mar 2016 03:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=qniOoew4a3QOp5rR9Y1PLs0+Zzy2yO/l9DztrH9y3fc=; b=vJyQjjxRTGFOdCcRN0nuvqeU8vBtA8Zi3IzEhntGFGBhskjQcbX4cp2Qz+TnZI8D87 HIL2Q9aLAQ7tUCJhf2WBtM3YoudJTdGImDt55Bl/3IXS2M4qPUEO05hgBt5HOIYTtieF D1Xp3md8n9mkWszPMa5csPHmmXiuMgshlyge3/7bQ3P8KomsM1TRI9RdD97XfkRtYiXy 4eHunxzfVKspd184GNqVMCPZfxj9cvPIMCeBtKXSawckRrpzGrbtfWD7zdloth6oyj9j 4KCsQcNt1gBwDGgIuUJS09k0R+qF815kHWoUkqZtNcNrs7TSUf95O8qh89ygW894UVrT Njqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=qniOoew4a3QOp5rR9Y1PLs0+Zzy2yO/l9DztrH9y3fc=; b=OrUPvOWxlLpZ1ozjkuyvB6xKfYndAMWM0bcaSYsNyA9DxTcSbQi16TVhJwYItiHv+2 Cn1j1k5H29VYg2UZ3tXC3ng0hl/ZHpXDyAODmZDkJ9iiEle5mbafTIfaIYUny/JbVsMo 6rUch2pwTYYH8VjAFT021fMzm4tG/Wttp+FroWjtvHQ251XMrVrRwckUEwoz2UmTZVMZ 9BnEWbTCJTcOCKOQTdJ1KyqRQTHryYDz0lodIz5jBQwjokfK3fm8WxSj/PHV0c/bwI2n C3ZMRI5XM/uGcSt3SN9X2Rn4WeauW26Trc29slHnOZL+OJBkRONoTmUXpgv5mZ30llvN FmDQ== X-Gm-Message-State: AD7BkJJL1ymGlkAYbk+y/9cBXxLVsoLYOxgBtHcMb/pG1YV069S/4NkXT70ty+9771N+E40WtqpzH55rUayYHw== MIME-Version: 1.0 X-Received: by 10.60.246.164 with SMTP id xx4mr5791685oec.1.1458211600022; Thu, 17 Mar 2016 03:46:40 -0700 (PDT) Received: by 10.157.9.10 with HTTP; Thu, 17 Mar 2016 03:46:39 -0700 (PDT) In-Reply-To: <20160316015635.A61428@sola.nimnet.asn.au> References: <56E5F9CD.7080200@freebsd.org> <56E5FA38.20305@freebsd.org> <20160314145020.G61428@sola.nimnet.asn.au> <20160316015635.A61428@sola.nimnet.asn.au> Date: Thu, 17 Mar 2016 16:16:39 +0530 Message-ID: Subject: Re: Network goes down when installing ipfw From: Kulamani Sethi To: Ian Smith Cc: bycn82@dragonflybsd.org, Julian Elischer , "freebsd-ipfw@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 10:46:41 -0000 Yes Lan, you absolutely right...! I talked about ipfw+dummynet (i.c: ipfw3) for windows machine only. Today i able to fix my problem regarding "*network goes down after installing ipfw+dummynet".* Problem was,* ipfw.sys* (windows driver file) file didn't signed properly by Microsoft code signing tool *signTool.exe*. Thanks to all to be part of our overall discussion to fix it. This is the way how we learn new things. On Tue, Mar 15, 2016 at 9:16 PM, Ian Smith wrote: > On Mon, 14 Mar 2016 19:24:21 +0800, Bill Yuan wrote: > > On Monday, March 14, 2016, Ian Smith wrote: > > > > > On Mon, 14 Mar 2016 07:39:36 +0800, Julian Elischer wrote: > > > > On 14/03/2016 7:37 AM, Julian Elischer wrote: > > > > > On 11/03/2016 8:46 PM, Kulamani Sethi wrote: > > > > > > Dear all, > > > > > > > > > > > > I am using ipfw3. When i am installing ipfw driver in > > > windows-7 > > > > > > machine the network goes down. If uninstall that driver again > then > > > > > > network > > > > > > comes automatically. That means ipfw driver does not support. > > > > > > > > > > > > I have also digitally signed by Microsoft kernel > mode > > > > > > signing > > > > > > process for authenticate the publisher. > > > > > > > > > > > > > > > > > > Process of installing: Local Area Connection-> properties -> > > > Install -> > > > > > > service -> Add ->OK (I can also see there message by system > "Driver > > > > > > digitally signed") > > > > > > > > > > this is amusing.. Ipfw on windows? I never knew of this.. > > > > > > > > > > can you send us all the links to this project? > > > > never mind: > > > > > > > > google to the rescue: > > > > > > > > http://wipfw.sourceforge.net/ > > > > > > What's amazing is that we - you and I, anyway - have never heard of > it. > > > > > > And that it goes back to 2005, and apart from fwd, seems to follow > ipfw > > > semantics, up to 2011 anyway. Kudos to the porters, fitting it into= a > > > Wimdows kernel environment. A gui even, pretty standard 'man ipfw' > > > docs, properly attributed authorship .. > > > > > > "IPFW ported to Windows=C2=AE by Ruslan Staritsin and Vladislav Gonc= harov." > > > > > > As for Kulamani's problem, I wonder if it needs some technique rough= ly > > > equivalent to that needed when loading ipfw over a remote connection= : > > > > > > # kldload ipfw && ipfw add 65000 allow ip from any to any > > > > > > but I really shouldn't try second-guessing ANYTHING to do with > Windows, > > > which always seems to hate me even more than the reverse :) > > > > > > > > > Could anyone please help me for this issue. Thanks in advance= . > > > > > > From the Contacts page on SF: "If you have any questions about this > > > project, please email at iptables@mail.ru " > > > Oh please lah. it is not ipfw3 > > Well Bill, it's gotten harder to tell what is meant by 'ipfw3'. I spent > - hopefully not wasted - several hours digging around today, trying to > ease my own confusion, and I've kept half an eye on this for years. > > Luigi and colleagues first released versions if ipfw+dummynet under the > name ipfw3 in early 2010 as near as I can tell. The naming is explained > in the README at https://github.com/luigirizzo/dummynet which includes > versions for Linux (2.4 and 2.6 at that time), OpenWRT and yes, Windows. > > Several other releases are at http://info.iet.unipi.it/~marta/dummynet/ > all using the ipfw3 moniker. > > So perhaps that is the ipfw3 Kulamani is talking about, not wipfw? > > Further, https://github.com/luigirizzo/dummynet/blob/master/NOTES > acknowledges that the windows port was originally begun from wipfw. > > If you google "ipfw3" (including quotes) you'll find references to your > ipfw3 for dragonflyBSD, and plenty of references to *ipfw3.* archives of > ipfw + dummynet sources and binaries as used with various Linux distros, > questions about mostly the latter on lots of forums and lists .. > > This one is a good browse starting point, moving down or up the tree: > https://www.cct.lsu.edu/~xuelin/dummynet/20100319-ipfw3/ipfw3/ for an > early version. > > So I have to wonder whether you did much research before choosing a name > for a different implementation? I guess that's too late to fix now, but > let's try to be clear about differentiating two quite different things. > > cheers, Ian >