From owner-soc-status@freebsd.org Thu Aug 6 08:38:04 2015 Return-Path: Delivered-To: soc-status@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 31B989B4649 for ; Thu, 6 Aug 2015 08:38:04 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from smtp.hungerhost.com (smtp.hungerhost.com [216.38.53.177]) (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 06330D27 for ; Thu, 6 Aug 2015 08:38:03 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from global-1-30.nat.csx.cam.ac.uk ([131.111.184.30]:3063 helo=[172.17.217.49]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1ZNGgc-00066x-Or; Thu, 06 Aug 2015 04:38:02 -0400 From: "George Neville-Neil" To: "Daniel Peyrolon" Cc: soc-status@freebsd.org Subject: Re: Status reports for "JIT for firewalling" Date: Thu, 06 Aug 2015 09:38:02 +0100 Message-ID: In-Reply-To: References: <358A0094-61DE-4685-933F-EDED85A6A07C@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.2r5107) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - freebsd.org X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2015 08:38:04 -0000 Great, I'll go look at the update etc. Best, George On 5 Aug 2015, at 22:49, Daniel Peyrolon wrote: > Yes, all of that is commited at my repo. > > El mar., 4 ago. 2015 a las 14:13, George Neville-Neil () > escribió: > >> Sounds very promising. >> Have you committed an pushed the changes that made everything >> start to work? Even if that's just a set of notes, rather than code, >> that ought to be preserved. >> >> Best, >> George >> On 3 Aug 2015, at 9:15, Daniel Peyrolon wrote: >> >>> Hello, >>> >>> Finally we have the firewall working! >>> I get a kernel panic whenever I try to filter an unbounded number of >>> packets, but it doesn't when filtering a small amount of packets. >>> >>> The things to do now are: >>> - Test that the emission of all the new rules is working properly, and >>> test that rule. >>> - Avoid kernel panic. This will take a longer time, but we need this in >>> order to get the firewall working in real-world systems. >>> - Write flow modifying rules: Given that I've been out of the game for >>> so long, I haven't been able to get those rules written yet, but luckily >>> they are only two rules, and its implementation shouldn't be hard. >>> >>> El lun., 27 jul. 2015 a las 20:36, Daniel Peyrolon (>> ) >>> escribió: >>> >>>> Hi again, >>>> >>>> Unfortunately I haven't been able to make any further progress. >>>> I've been having a lot of problems to get the compiler working. I tested >>>> many different hypotheses about the bug with no success so far, and I've >>>> talked with David Chisnall to see if he could lend me a hand and he has >>>> given me some pointers. So, hopefully, I'll be past this stage this >> week. >>>> >>>> El lun., 20 jul. 2015 a las 15:43, George Neville-Neil (< >> gnn@freebsd.org>) >>>> escribió: >>>> >>>>> Seems like the next thing to do is build from source as David suggests. >>>>> >>>>> Best, >>>>> George >>>>> >>>>> >>>>> On 20 Jul 2015, at 4:47, Daniel Peyrolon wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> This has not been a productive week. I've been so far unable to get >>>>>> the >>>>>> compiler working, I contacted David Chinsall as I said, and I have >>>>>> been >>>>>> looking to make everything works. The initialization process of LLVM >>>>>> is not >>>>>> working as expected, which may be related to a bad install (we have >>>>>> already >>>>>> disarded that), a bad building process, or a bad LLVM initialization >>>>>> process. Given the fact that the LLVM API has changed a lot since the >>>>>> last >>>>>> time, that may be possible. >>>>>> >>>>>> El sáb., 11 jul. 2015 a las 12:24, Daniel Peyrolon >>>>>> () >>>>>> escribió: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> This last pair of weeks I've written the code needed to compile >>>>>>> almost all >>>>>>> the rules, except those that modify control flow: call and skipto. >>>>>>> For >>>>>>> those ones I will have to write them by hand on LLVM IR. >>>>>>> >>>>>>> I also started working on the testing code. I'm using conductor to >>>>>>> control the different hosts. I already have reserved a pair of hosts >>>>>>> from >>>>>>> the netperf cluster in order to get that running. >>>>>>> >>>>>>> So far I haven't been able to test anything because the compiler is >>>>>>> not >>>>>>> working yet, there has been a change in the API of LLVM since I last >>>>>>> worked >>>>>>> with it, I sent an email to my past mentor, David Chisnall asking for >>>>>>> advice. >>>>>>> -- >>>>>>> Daniel >>>>>>> >>>>>> -- >>>>>> Daniel >>>>> >>>> -- >>>> Daniel >>>> >>> -- >>> Daniel >> > -- > Daniel