Date: Mon, 19 Jan 2015 04:38:01 +0000 From: Emma Turing <emma@robotbase.org> To: <freebsd-net@freebsd.org> Subject: Kickstarter Invitation Message-ID: <30485748.20150119043801.54bc8a29158b18.76859008@mail134-16.atl141.mandrillapp.com>
next in thread | raw e-mail | index | archive | help
Hi, I'd like to invite you to back our Kickstarter project - The World's First Personal Robot <https://www.kickstarter.com/projects/403524037/personal-robot>. We're already 210% funded and the #1 Robot Project on Kickstarter now. PERSONAL ROBOT IS THE WHOLE PACKAGE: - The world's first personal assistant robot that can see, hear, smell, move, and feel - The smartest home automation system (supports both Z-Wave and Zigbee) - A photographer, storyteller, companion, security guard, and more - Powered by Artificial Intelligence algorithms - Open APIs We're been featured by TechCrunch, Mashable, and VentureBeat. Thanks, Emma *If you're not interested, please simply reply "don't email" and we'll stop emailing you immediately.* From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 05:12:24 2015 Return-Path: <owner-freebsd-net@FreeBSD.ORG> Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECCD7A84 for <net@freebsd.org>; Mon, 19 Jan 2015 05:12:24 +0000 (UTC) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BDF2204 for <net@freebsd.org>; Mon, 19 Jan 2015 05:12:24 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id ge10so5854937lab.10 for <net@freebsd.org>; Sun, 18 Jan 2015 21:12:21 -0800 (PST) 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=S1U5keuvIUqW6N3GnLLCd2UC5kWy+mD99Songh+i87Y=; b=kmyMc1nFADszdBmCuV5GLbpDL7AqaN431r/um699icRL0BaKoFUn6I21r4VIM1uZ7e MtcRT7gwuzOHb1cMvH9TFrryk3q1DcbJlNZ/X4iOWPRqMeURzWbi5VBB871s+9o6YpNp GNp/G9XhxbXJXiMB4tUq5eeVtlip/kQ+Po9byxF43qFH9fYFlctY+OfsZELr5WIk2auq CltzTF08jHYZfWUo3mHGTxIsEe47NDGS5caP2JcbkJkO474KucWHelASRqtNFzhiCIrh c4rUfmbKSZ3FhYMuY10r5NfbF9Q+kVBPvzch7bxVQKyOnI+JUJWzPzIoRorFVDrO81i+ N/8A== MIME-Version: 1.0 X-Received: by 10.112.167.136 with SMTP id zo8mr25712214lbb.17.1421644341828; Sun, 18 Jan 2015 21:12:21 -0800 (PST) Received: by 10.112.160.68 with HTTP; Sun, 18 Jan 2015 21:12:21 -0800 (PST) In-Reply-To: <20141117193354.T31139@sola.nimnet.asn.au> References: <CAD3kpuU8jQjMdfEiGNwYLToJDSZWGbJgQTzGeAFEw1UBLY4M3Q@mail.gmail.com> <20141117193354.T31139@sola.nimnet.asn.au> Date: Mon, 19 Jan 2015 13:12:21 +0800 Message-ID: <CAD3kpuWvoQWYUgjoHMUVArqdf49vBLDjArdb_N868LU3yEUQmg@mail.gmail.com> Subject: Re: dragonflybsd's ipfw From: Sato Kentney <satokentney@gmail.com> To: Ian Smith <smithi@nimnet.asn.au> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net <net@freebsd.org> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>; List-Post: <mailto:freebsd-net@freebsd.org> List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 19 Jan 2015 05:12:25 -0000 Hi, I get below from another email this morning, the ipfw can add dynamic rules according to below email. *You can manually insert a state as below and the state will be maintain by ipfw itself.* *ipfw state add rulenum 100 udp 192.168.1.1:0 <http://192.168.1.1:0/>; 8.8.8.8:53 <http://8.8.8.8:53/>; expiry +600* *so you dont need to implement the logic to maintain the IP addresses or configure any crontab to remove..* *different state can have different expiry or "life time"* =E3=81=82=E3=82=8A=E3=81=8C=E3=81=A8=E3=81=86 =E4=BD=90=E8=97=A4=E6=9F=AF=E5=BE=B7 2014-11-17 17:07 GMT+08:00 Ian Smith <smithi@nimnet.asn.au>: > On Mon, 17 Nov 2014 15:48:13 +0800, Sato Kentney wrote: > > > I saw a email in dragonflybsd email list, someone is doing this! > > http://www.dragonflybsd.org/docs/ipfw2/ > > We've had 'ipfw2' for a very long while. I couldn't help wondering why > DF wouldn't just import our many years of development and experience > rather than using bycn82's 'rewrite'? .. but DF already has ipfw2: > > http://leaf.dragonflybsd.org/cgi/web-man?command=3Dipfw§ion=3DANY > > man page dated October 2008. Before tables, in-kernel NAT, later > dummynet updates and no doubt more. So why not start from there? > > cheers, Ian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30485748.20150119043801.54bc8a29158b18.76859008>