From owner-freebsd-ipfw@freebsd.org Mon Sep 19 08:11:06 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 E130FBE0097 for ; Mon, 19 Sep 2016 08:11:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D041A1BD9 for ; Mon, 19 Sep 2016 08:11:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8J8B6FW054744 for ; Mon, 19 Sep 2016 08:11:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ipfw@FreeBSD.org Subject: [Bug 212649] ipfw(8): Referencing a table in the ruleset causes ipfw list/show to crash with SIGSEGV. Date: Mon, 19 Sep 2016 08:11:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: crest@bultmann.eu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ipfw@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 08:11:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212649 --- Comment #6 from Jan Bramkamp --- I applied the patch from #212649 to 11.0-RC2 and it fixed the problem. Is t= here any chance for the patch to be included in 11.0-RELEASE? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ipfw@freebsd.org Tue Sep 20 06:30:39 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 A7F77BE178B for ; Tue, 20 Sep 2016 06:30:39 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 747B47C8 for ; Tue, 20 Sep 2016 06:30:39 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id 186so9984005itf.0 for ; Mon, 19 Sep 2016 23:30:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=nNu1tb75O8vqMzZI6pciQhZzp8bdhK6fuHLE+J1RAcc=; b=DbMpKar5ClQ8SqbTovoVFoM9lFjGn9sBtbYP8yWE+0tAtH5W7P1Cr6z15CWi5cfibi HnOv8qXWY3l/ucZbwuOYI3RX7XqTwp8B9gOXydMLlyd/hGKzxftuql55miffypNutJ0n gZJ/hs2IpwWv3AXQgX9HV/7DkB9fMnqxOvvX3oDKYDfXf+wEJpimQPHopaUb8pRBJgyP BLTsb6Fu17641wmgF1TGfKclDy6t4ao1ECukV2ny/zV6Vv/GCUIT71du/xcXPEmK1yRg VEl6cR5b39wqiZfq0xCvbM4aQl77qe+cEQ0KIVusQ6k7bjDjaCLTE3Dgte1kMrzPNJLq GQKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=nNu1tb75O8vqMzZI6pciQhZzp8bdhK6fuHLE+J1RAcc=; b=CLY5HYKGmTiP3jD6M9zR9m1+QGXwREPu+McfD0xt0bmrhnIUg+prXMTxuC0hFFOBXU wcxQXOPdjhwq/VPb6Nrg8LA7V7k6YMWskDvHjFWJDkrlpdMmkCod2qsJJc2Ahq+bcMG7 f8c3+wtI9t8nziWn7NunLFDytR/Kez2enJfB4eJLUDuDg5e39P/lrulTaEGRK5Y7Pthy Jno5u/NzCbl0rG7BsuwdJTVxOcITedTyN1vph9MN/hQ7q0vANx8jN8kNaFJi7tsNnQJi 3UHaTQuao5tNoNoO61VLXpP2Dm/JlTuLSCrFMOgCtNxS154aPRO/AcCWHZ8V+T9v79KY exEg== X-Gm-Message-State: AE9vXwPPUwlmY340PsKAdtlfYDETfekviKWNTS9V9PEJ+zTVGuYCpRIGs8sXXNun4TwOUzTYcR99lBA0DKxYAg== X-Received: by 10.36.163.193 with SMTP id p184mr2084105ite.102.1474353038567; Mon, 19 Sep 2016 23:30:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.104.207 with HTTP; Mon, 19 Sep 2016 23:30:38 -0700 (PDT) From: Kulamani Sethi Date: Tue, 20 Sep 2016 12:00:38 +0530 Message-ID: Subject: IPFW compatibility on windows 10 To: freebsd-ipfw@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 06:30:39 -0000 Hello All, I am in the phase of developing one application using ipfw3 but now my concern is about ipfw compatibility, is ipfw works fine with windows 10 ? because I am planning to upgrade machines with windows 10 soon. Please help me. *With best Regards,* Kulamani Sethi, Bangalore, India From owner-freebsd-ipfw@freebsd.org Tue Sep 20 16:16:02 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 5D1D5BE1A6E for ; Tue, 20 Sep 2016 16:16:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BB1033A for ; Tue, 20 Sep 2016 16:16:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u8KGFx7L072512 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 20 Sep 2016 09:16:00 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: ipfw table expiry.. how to do it..? To: "freebsd-ipfw@freebsd.org" References: From: Julian Elischer Message-ID: <73e735d6-04cb-3e88-594c-b4e63b2971d7@freebsd.org> Date: Tue, 20 Sep 2016 09:15:54 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 16:16:02 -0000 On 11/09/2016 8:03 PM, Julian Elischer wrote: > > Unfortunately we don't have any timers on table entries, so it's not > possible to see how long an entry has been in use, or idle. > > > If I were to ha ve a captive portal, which placed the address of > 'allowed' hosts into a table, we would have no way to time them out > when they go idle. The omly thing you can do is throw away all the > entries at some time, and force them to all log in again. > > Does anyone have any patches to add "access time" to table entries? > > > I'm guessing the way it would need to be done now would be to use > dynamic rules and having the syn packet of every session sent to > no takers? From owner-freebsd-ipfw@freebsd.org Tue Sep 20 16:34:22 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 CD5B8BE22FB for ; Tue, 20 Sep 2016 16:34:22 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B18F81099 for ; Tue, 20 Sep 2016 16:34:22 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u8KGYD0d072604 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 20 Sep 2016 09:34:14 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: ipfw table expiry.. how to do it..? To: bycn82@dragonflybsd.org, Ian Smith References: <0f1acc7f-2c85-dc4d-a272-5631c1e749cd@elischer.org> <20160912135241.J91459@sola.nimnet.asn.au> Cc: Julian Elischer , "freebsd-ipfw@freebsd.org" From: Julian Elischer Message-ID: Date: Tue, 20 Sep 2016 09:34:08 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 16:34:22 -0000 Hi Bill, On 15/09/2016 9:48 PM, Bill Yuan wrote: > In Ipfw3, each table entry has its own counter and last hit > timestamp for both directions. I suspect you are confusing tables and dynamic rules? (your comment about 'direction') if not, can you give examples? > > On 12 September 2016 at 12:12, Ian Smith > wrote: > > On Mon, 12 Sep 2016 11:04:26 +0800, Julian Elischer wrote: > > > Unfortunately we don't have any timers on table entries, so > it's not possible > > to see how long an entry has been in use, or idle. > > > > > > If I were to ha ve a captive portal, which placed the address > of 'allowed' > > hosts into a table, we would have no way to time them out > when they go idle. > > The omly thing you can do is throw away all the entries at > some time, and > > force them to all log in again. > > > > Does anyone have any patches to add "access time" to table > entries? > > > > > > I'm guessing the way it would need to be done now would be to > use dynamic > > rules and having the syn packet of every tcp session sent to > the portal for > > approval, before being passed back to create the dynamic rule. > > Well nothing like patches, and surely not what you want, but > I've been > using the below since '08 to add timestamps to entries, and a > couple of > related scripts to list entries for particular tables in date > order etc. > I never finished adding the 'purge before somedate' script .. > > Nowadays with multiple table values you could maybe have useful > tablearg > values like skipto targets as well. > > cheers, Ian > > #!/bin/sh > # addr_to_table 24/11/8 smithi > # add ipaddr[/masklen|32] and value (seconds from epoch) to table N > # 31/12/9 CIDR matching for updates, (ab)using table 0 for calc > # 4/4/11 prefer direct ipaddr/masklen format, add numeric check > usage() { > [ "$1" ] && echo $1 > echo "usage: `basename $0` table address[/masklen | [ > masklen]]" > exit 1 > } > validint() { # value min max > [ "`echo $1 | tr -d 0-9`" ] && return 1 # not all numeric > [ $1 -ge $2 -a $1 -le $3 ] && return 0 || return 1 > } > [ "$2" ] || usage > table=$1 ; addr=$2 > `validint $table 1 127` || usage "table '$table' not 1..127" > [ "$3" ] && mlen=$3 || mlen=32 # allow old but prefer CIDR format > [ "${addr%/*}" != "$addr" ] && mlen=${addr#*/} && addr=${addr%/*} > `validint $mlen 8 32` || usage "masklen '$mlen' not 8..32" > > addr=$addr/$mlen > if [ $mlen -lt 32 ]; then # calc CIDR netblock addr using > table 0 > ipfw -q table 0 flush ; ipfw -q table 0 add $addr > addr=`ipfw table 0 list | awk '{print $1}'` > fi # only needed if looking up > addr/mask > > ipfw -q table $table add $addr `date "+%s"` 2>/dev/null > [ $? -eq 0 ] || echo "table $table add $addr `date +%s` failed: > dupe?" > exit 0 > _______________________________________________ > freebsd-ipfw@freebsd.org > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > > To unsubscribe, send any mail to > "freebsd-ipfw-unsubscribe@freebsd.org > " > > From owner-freebsd-ipfw@freebsd.org Tue Sep 20 23:01:45 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 B324DBE3001 for ; Tue, 20 Sep 2016 23:01:45 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 885B51583 for ; Tue, 20 Sep 2016 23:01:45 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id m186so35659024ioa.2 for ; Tue, 20 Sep 2016 16:01: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:from:date:message-id:subject:to :cc; bh=6Q9Xy+MU2/lxPsk7Aj+Mf1a/jsgq989ttqTaN8jNtno=; b=jNuE/XOm7ToO4wD7eGvvhnLhpPI0JC08tPJI6KzX+ymMmUla0ZcR+l75FZgGbZYAOV mavwRgaFDq/QdSuOBNjpuhNShKpl4IOl30NSwYKlvUeRJkNzdYGkzfUOIu23dN9SZ1z5 oNjJ4AK/E7UefMmCE+M9UF0YRcaBL2yQ+ZVIpMQcwzsS1+an+5IDZe5pVB35POsMmByh 8kHdDqCUfAmShygpaFa+1ATnmKWkm7KCjDK1uPo7zveiqGaG9oSQqjNv29GBuMGpFkDS oD5UeQfdeF6CSQY703g6j5VXhjkQf7bLB42+g7deo4uabjoJqWwB7dqikFdxZCuxy6oi j8XA== 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:from:date :message-id:subject:to:cc; bh=6Q9Xy+MU2/lxPsk7Aj+Mf1a/jsgq989ttqTaN8jNtno=; b=XD/qoJmElzM/8btRLEHHSdRNRjYANTkueObMxGe6Bf/+DDbDUMdfsgtSUEyaJpuRza Z2Q0MpNNLCRhCc3ozVByOhHgkBV4awy2LYV2c7oHQnOSJddkPQHE3ota52N7v9L1og2I HPifLssibM+GervsIBRMtYBy8wJ7K/zXJwwfFZqpFabxHujV5IyNeeGMw/R4BaZaTbcp Z2aFGigLMpI5HkkCmQKyGxCorGHy9hBDKOAXIemjjZ1xsHiYCfCU/ZTWX22K5h3oCvW5 OFjeWGnjJUu56iNb4NDPC0dn+OGddXc3t6+gXeMYU4HfPYu4RlI9SR1srbXIJqAhUI9+ lfYg== X-Gm-Message-State: AE9vXwN2dsnMfvhi7hJwTDtN+53f+vFK3r2LkiKshD11fhmfBohPRDfojrb+2Ip2960pnJ1phCc7cgpJ7o4tyQ== X-Received: by 10.107.36.213 with SMTP id k204mr47689076iok.129.1474412504831; Tue, 20 Sep 2016 16:01:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.26.3 with HTTP; Tue, 20 Sep 2016 16:01:44 -0700 (PDT) In-Reply-To: References: From: Ben Woods Date: Wed, 21 Sep 2016 07:01:44 +0800 Message-ID: Subject: Re: IPFW compatibility on windows 10 To: Kulamani Sethi Cc: "freebsd-ipfw@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 23:01:45 -0000 On Tuesday, 20 September 2016, Kulamani Sethi wrote: > Hello All, > > I am in the phase of developing one application using ipfw3 but now my > concern is about ipfw compatibility, is ipfw works fine with windows 10 ? > because I am planning to upgrade machines with windows 10 soon. > > Please help me. > > > > *With best Regards,* > > Kulamani Sethi, > Bangalore, India > Hi Kulamani, It does appear that someone has made a version of IPFW that works with Windows: http://wipfw.sourceforge.net/ Any questions regarding how it works or for help would probably be best directed to the forums on that website, as people on this mailing list (including myself) are unlikely to be familiar with the Windows version. That said, if you have general questions about how the FreeBSD version of IPFW works, assuming that they will apply to the Windows version, you could post them here. Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-ipfw@freebsd.org Wed Sep 21 00:39:00 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 3D903BE07A8 for ; Wed, 21 Sep 2016 00:39:00 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 C7C2A355 for ; Wed, 21 Sep 2016 00:38:59 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id a25so15852814wmi.1 for ; Tue, 20 Sep 2016 17:38:59 -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:from:date:message-id :subject:to:cc; bh=ijUAenkYRfrA4TiL6CzFW4kHkLM3XOZB31nB1tcL3vg=; b=Ml3t+0WziO9xvJfrxOXAkf/TvNvJuw+F3D3+IlEhOsHlex0Ko4+iAJxeAPhZrFLl0/ olls5ioDiab5XhK1cCipd3moBv+visXvBMdy3UlMNPWs684L6+KAZ42WBzqwKRrk3pMG SfXhXZTEjfbug5ho6T29sW6YATnBp7RoZwsmO1zsCDuoHAjzMqlnSkMdkDBjSWIreArG NVnmz8SOpwwbXt0RpCxUgEQr8tDO3RTbMy/SOZ+QxPnykYhbFPFQyCEkE3iOoDwL577Z fq0CjkNFrom2cAPcxUAfdZfwXFKE8oac0ncwiRqs1O2Sxs4RYxrHaNMgNrJ8kStJTZsT pMMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ijUAenkYRfrA4TiL6CzFW4kHkLM3XOZB31nB1tcL3vg=; b=W9PJgz6+racKhSafqCZUyphTBpbBp+bHRq1ApEP5ur4R3BAurSkb3H/PntOND819If gnzmWf4w3k7Ch1asx0B/AmnqboR0wqiIM42yIsfKunjBucfW3CIPbk3CbX/XvX1xfbha Uxg6quQpyVhMYh0D0mjCsFX9/NW9zfzDD7ltT7EO9Ku53up7U2sCbwpujGLub3XQnLG9 mbty82dRFwGQgr2AlXop0jyun+LB3BLjCwFt5CT99RXmrLQb4zn+6/0qOie2q/p0+x4X ZM/Q2MF55eYKORAFWk6yHTsUWxCxrDKEPhD41DK7YkWPrK8jgJ3ZFQsJCKrZkOi4vHRq m1vQ== X-Gm-Message-State: AE9vXwNL5S4VjwaJfmq1hHy6eLFxRrntQPpcKroWh4asPKcCPGhFcGBPv507dDG5yZIAsKhXlLHPPURry313BQ== X-Received: by 10.28.26.13 with SMTP id a13mr498488wma.8.1474418338025; Tue, 20 Sep 2016 17:38:58 -0700 (PDT) MIME-Version: 1.0 Sender: rizzo.unipi@gmail.com Received: by 10.28.113.206 with HTTP; Tue, 20 Sep 2016 17:38:57 -0700 (PDT) In-Reply-To: References: From: Luigi Rizzo Date: Wed, 21 Sep 2016 02:38:57 +0200 X-Google-Sender-Auth: NQ3lFxLTZh4KXi7rmzeJyYWGXJA Message-ID: Subject: Re: IPFW compatibility on windows 10 To: Ben Woods Cc: Kulamani Sethi , "freebsd-ipfw@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 00:39:00 -0000 On Wed, Sep 21, 2016 at 1:01 AM, Ben Woods wrote: > On Tuesday, 20 September 2016, Kulamani Sethi > wrote: > >> Hello All, >> >> I am in the phase of developing one application using ipfw3 but now my >> concern is about ipfw compatibility, is ipfw works fine with windows 10 ? >> because I am planning to upgrade machines with windows 10 soon. >> >> Please help me. >> >> >> >> *With best Regards,* >> >> Kulamani Sethi, >> Bangalore, India >> > > Hi Kulamani, > > It does appear that someone has made a version of IPFW that works with > Windows: > http://wipfw.sourceforge.net/ I think he refers to a more recent version of the code https://github.com/luigirizzo/dummynet which we ported to Windows7 a few years ago and last updated around 2013-2014. I have not tested it on Windows10, the usual difficulty people have is that the kernel module is not signed so you need to run the OS disabling driver signing. cheers luigi > Any questions regarding how it works or for help would probably be best > directed to the forums on that website, as people on this mailing list > (including myself) are unlikely to be familiar with the Windows version. > > That said, if you have general questions about how the FreeBSD version of > IPFW works, assuming that they will apply to the Windows version, you could > post them here. > > Regards, > Ben > > > -- > > -- > From: Benjamin Woods > woodsb02@gmail.com > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" -- -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2217533 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-ipfw@freebsd.org Wed Sep 21 15:39:26 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 6E3C2BE4D0E for ; Wed, 21 Sep 2016 15:39:26 +0000 (UTC) (envelope-from "") Received: from smtp.eli.org (smtp.eli.org [209.136.219.131]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26F093B7 for ; Wed, 21 Sep 2016 15:39:25 +0000 (UTC) (envelope-from "") Received: from ELISRV1.elidomain ([20.0.1.4]) by ELISRV1 ([20.0.1.4]) with mapi; Wed, 21 Sep 2016 11:38:13 -0400 From: Jay Pendergrass To: "freebsd-ipfw@freebsd.org" Date: Wed, 21 Sep 2016 11:38:12 -0400 Subject: Out of Office: 8658 pendergrass Thread-Topic: 8658 pendergrass Thread-Index: AdIUHilExjIVZveYRbKsRSGGPfC6tAAAAAYp Message-ID: <17BF9D6FF5EC604891E2B84441657AB301240D795559@ELISRV1> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 15:39:26 -0000 SSBhbSBvdXQgb2YgdGhlIG9mZmljZSB1bnRpbCBTZXB0ZW1iZXIgMjIuIEkgd2lsbCBiZSByZWNl aXZpbmcgZW1haWxzIGludGVybWl0dGVudGx5LiBJIHdpbGwgcmV0dXJuIHlvdXIgbWVzc2FnZSBh cyBzb29uIGFzIEkgYW0gYWJsZS4gSW4gdGhlIGludGVyaW0sIHBsZWFzZSBjb250YWN0IEppbSBN Y0VsZmlzaCBhdCBtY2VsZmlzaEBlbGkub3JnLg0K From owner-freebsd-ipfw@freebsd.org Wed Sep 21 20:48:12 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 178B2BE3CBB for ; Wed, 21 Sep 2016 20:48:12 +0000 (UTC) (envelope-from info@midsommar.online) Received: from smtp208.server19.mailrelay-i.com (smtp208.server19.mailrelay-i.com [93.159.208.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6AE9B7A for ; Wed, 21 Sep 2016 20:48:11 +0000 (UTC) (envelope-from info@midsommar.online) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=dkim; d=midsommar.online; h=Reply-To:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; i=info@midsommar.online; bh=8kyeF9mlbgURj4Q0c1UFcZ8zRNI=; b=gOV+/QdkcOOW7t/FbbbboAT9fcERJAYmpBLjktLZZaOlHC6BRdRo+d2fY9YnImvm7q0abD0Unj55 yd423agazAbIfXOAi3C26MZG3lOt+d3NDeB6RJ5YTnQGBGBOHXg60ALGv+9Xe17eiYTKtMhg93yK 8nRLubyQL+V4V3SyhpU= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=dkim; d=midsommar.online; b=kjzHnwHE8Srr1eNFbPOOCbqV7ouQbZZna9+o3aTLv9uKtbtAj6uwCaNEX1yI9YJMUVk2ZkeNbRDM LLQO48d+0J/JGfZYqUpSV9LfSqS+85WM54HVVcakKfo5XrqRAw2+Fft8I88/tU0t5Bw8O3imEBQf u7IcJQwO+7iqldDRkC0=; Received: by smtp208.server19.mailrelay-i.com id hsbp0k16r3g4 for ; Wed, 21 Sep 2016 22:32:49 +0200 (envelope-from ) X-SmtpId: VTJGc2RHVmtYMStYWHlQRmt0OGNlUThnZ1pRL1M1QTZYbzd0RTlZSTFrR2VibXNtVkNXTGh3UFBXZGpKClBTbHBJdkJaU21BemZKYk1mdzN2dEkwZ2x3PT0K Organization: Midsommar Festival Reply-To: info@midsommar.online Message-ID: From: "YouTube" To: Subject: =?windows-1252?Q?Raffaella_sent_you_a_video:_"MIDSOMMAR_FESTIVAL_2016"?= Date: Wed, 21 Sep 2016 22:32:24 +0200 X-Priority: 1 X-Mailer: SMTP Component MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 20:48:12 -0000 Raffaella has shared a video with you on YouTube: = https://www.youtube.com/watch?v=3DVtV83ls5JpE From owner-freebsd-ipfw@freebsd.org Thu Sep 22 06:44:53 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 3769EBE5FC5 for ; Thu, 22 Sep 2016 06:44:53 +0000 (UTC) (envelope-from srikanthkumar.net@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (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 E79E838A for ; Thu, 22 Sep 2016 06:44:52 +0000 (UTC) (envelope-from srikanthkumar.net@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id u196so11389795vkd.1 for ; Wed, 21 Sep 2016 23:44:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=LVhJRGgzzgTUjrNPBqPQvHthreY0R2dn3wYmHEFpNyA=; b=XiWIPPFHiPJylol0T2RQ7XMDuu7iCO9wsnHDHu2sn0hoTqy69ygcrOhV0B4gQMouRb KtAjLVmVcM11wTk0y1UKPCb4e1rYAH2Ol95YuCVKfBvMha65JjQFPklb8zIRsgH8IgCA hPZ6EYQ1OxrCGUZ+ckg5Bv+cRdXok8092A9yP0CLx9qQ81nBMXG6aarWmQJLlWSbukfZ E9qINOm6DuFOtxwT2ct0pIqH0ACIoAXW21OkNckAcRbfLOLHx+qSkVUJeVnJUTZp7WZf 4vAzeL0czFhjzbNqXguSbiZeSrZXODYOkCLLHbHqq3o5psJdVVPjL26FpodKntNRPMCJ gS5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=LVhJRGgzzgTUjrNPBqPQvHthreY0R2dn3wYmHEFpNyA=; b=Sel06pWa2mtDivsqERUlD5lHVTvTpCJK46MBJ2cOvGIml5MxTGr573iHCs8UnoqtEs 2fa3ZkYQqVrb1RDmG15vonVKiMc3kV5Wgg+ulqfpbgXjjg/VSDoI0tcyF0Rqmjjq9Cqh 8g62e8irch+y8wXqrHOFDklCLcij/32r7Fnv3hsqEXF6hCo7BZv8/Ph2RlunxUWNWt34 iNEJIr8d4wchbA5L9EyRsff70WnJZQniTEMfZPzlpsroVrrfBRGOALs9/gckoEeuHwOt iFAV8nmSFE1pAU/0bmVwT4rwXAybu+BD1yoqIL/ydIoD4NsjptPghSpZyEV0hmJE5V6y oq+w== X-Gm-Message-State: AE9vXwM9URaoOQDhjWalCB0JgQYL0rbokFlUgOJE6rok/vRIS5A344s92iy17OkCpTIHtAK4oIXJo7TyqVq7Hw== X-Received: by 10.31.164.214 with SMTP id n205mr198513vke.103.1474526692159; Wed, 21 Sep 2016 23:44:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.86.76 with HTTP; Wed, 21 Sep 2016 23:44:31 -0700 (PDT) From: Srikanth Reddy Date: Thu, 22 Sep 2016 12:14:31 +0530 Message-ID: Subject: IPFW+ Dummynet on Windows 10 To: freebsd-ipfw@freebsd.org Cc: kulamani.sethi@gmail.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 06:44:53 -0000 Hi, we are lucky to find your contact information. we are developing a small application using IPFW+Dummynet network adapter,but when we try to test that in Windows 10 OS we are unable to add the Service in Network Settings. Please help us in fixing the issue. Thanks & Regards, Srikanth. From owner-freebsd-ipfw@freebsd.org Fri Sep 23 22:48:26 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 7DD77BE8AE3 for ; Fri, 23 Sep 2016 22:48:26 +0000 (UTC) (envelope-from bounce-id=D268=U587731.start.ovh.net=1474668651.58-D705B@110-prod.mail-out.ovh.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 60D7ABB2 for ; Fri, 23 Sep 2016 22:48:26 +0000 (UTC) (envelope-from bounce-id=D268=U587731.start.ovh.net=1474668651.58-D705B@110-prod.mail-out.ovh.net) Received: by mailman.ysv.freebsd.org (Postfix) id 5C831BE8AE2; Fri, 23 Sep 2016 22:48:26 +0000 (UTC) Delivered-To: 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 5C23CBE8AE1 for ; Fri, 23 Sep 2016 22:48:26 +0000 (UTC) (envelope-from bounce-id=D268=U587731.start.ovh.net=1474668651.58-D705B@110-prod.mail-out.ovh.net) Received: from 2.mo169.mail-out.ovh.net (2.mo169.mail-out.ovh.net [178.33.251.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 213ABBB1 for ; Fri, 23 Sep 2016 22:48:25 +0000 (UTC) (envelope-from bounce-id=D268=U587731.start.ovh.net=1474668651.58-D705B@110-prod.mail-out.ovh.net) Received: from 110.mail-out.ovh.net (unknown [10.108.2.8]) by mo169.mail-out.ovh.net (Postfix) with ESMTP id D053DB006 for ; Sat, 24 Sep 2016 00:10:52 +0200 (CEST) Received: from 110.mail-out.ovh.net (localhost [127.0.0.1]) by 110.mail-out.ovh.net (Postfix) with ESMTP id B3BE620394 for ; Sat, 24 Sep 2016 00:10:52 +0200 (CEST) Received: from start.ovh.net (gw-cluster014.ovh.net [213.251.182.114]) by 110.mail-out.ovh.net (Postfix) with ESMTP id 40B6A209CF for ; Sat, 24 Sep 2016 00:10:50 +0200 (CEST) Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id 3E5453A36E for ; Sat, 24 Sep 2016 00:10:50 +0200 (CEST) Received: by start.ovh.net (Postfix, from userid 587731) id 31A673A368; Sat, 24 Sep 2016 00:10:50 +0200 (CEST) To: ipfw@freebsd.org Subject: Unable to deliver your item, #00000544006 Date: Sat, 24 Sep 2016 00:10:50 +0200 From: "FedEx Ground" Reply-To: "FedEx Ground" Message-ID: X-Priority: 3 MIME-Version: 1.0 X-Ovh-Tracer-Id: 12135512148480296743 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeelvddrtdelgddtvdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecu Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 22:48:26 -0000 Dear Customer, Courier was unable to deliver the parcel to you. Shipment Label is attached to this email. Kind regards, Frederick Durham, Station Agent.