Inliniac » Vuurmuur http://www.inliniac.net/blog Everything inline. Thu, 29 Jul 2010 19:38:06 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Vuurmuur rpms http://www.inliniac.net/blog/2009/11/03/vuurmuur-rpms.html http://www.inliniac.net/blog/2009/11/03/vuurmuur-rpms.html#comments Tue, 03 Nov 2009 15:44:49 +0000 Victor Julien http://www.inliniac.net/blog/?p=301 Daniele Sluijters has spend quite an effort at creating Vuurmuur rpms for Fedora 11 and CentOS 5, both 32 bit and 64 bit. The packages are available at the Vuurmuur ftp-server here: ftp://ftp.vuurmuur.org/releases/0.7/contrib/ Currently we have packages for 0.7, hopefully 0.8beta2 will follow later. Thanks Daniele!

]]> http://www.inliniac.net/blog/2009/11/03/vuurmuur-rpms.html/feed 0 Vuurmuur development http://www.inliniac.net/blog/2009/11/01/vuurmuur-development.html http://www.inliniac.net/blog/2009/11/01/vuurmuur-development.html#comments Sun, 01 Nov 2009 17:46:07 +0000 Victor Julien http://www.inliniac.net/blog/?p=298 Ever since I’ve been working on the OISF engine I’ve been unable to spend much time on my Vuurmuur project. Luckily it seems development is picking up some speed again because there are some (new) people working on some improvements. Two development branches have been started in svn. The first is “nflog” which is meant for the development of support for libnetfilter_log to replace the current syslog based vuurmuur_log.

The second is called “ipv6″ and is meant for adding IPv6 support to Vuurmuur as a frontend to ip6tables. This is going to be quite an effort, but I’m excited that it got started!

Anyone interested in joining the development effort is welcome to do so. Join us at #vuurmuur on freenode.

On a side note, last week I released Vuurmuur 0.8 beta 2, exactly 6 months after beta 1. I’ll try to do the next release a little sooner!

]]> http://www.inliniac.net/blog/2009/11/01/vuurmuur-development.html/feed 0 Vuurmuur 0.7 is out http://www.inliniac.net/blog/2009/04/04/vuurmuur-07-is-out.html http://www.inliniac.net/blog/2009/04/04/vuurmuur-07-is-out.html#comments Sat, 04 Apr 2009 08:04:25 +0000 Victor Julien http://www.inliniac.net/blog/?p=249 A new version of Vuurmuur is out: 0.7. This release mainly fixes bugs and build issues. Translations are generated and installed again, lots of traffic shaping fixes were made.

Support for pmtu MSS clamping was added, as was support for NAT source port randomization.

See http://www.vuurmuur.org/trac/wiki/Changelog for all changes.

Debs for Debian and Ubuntu are available, see
http://www.vuurmuur.org/trac/wiki/InstallationDebian

The source installer and Autopackage are on the ftp server:
ftp://ftp.vuurmuur.org/releases/0.7/

Looking forward, I’m planning on improving the services handling in 0.8. Especially supporting all protocols from /etc/protocols, instead of just a small list of hardcodes ones. Check http://www.vuurmuur.org/trac/milestone/0.8 to monitor the plans and progress on the 0.8 release. Suggestions & help are welcome!

Update November 3rd: RPMS are available as well: ftp://ftp.vuurmuur.org/releases/0.7/contrib/

]]> http://www.inliniac.net/blog/2009/04/04/vuurmuur-07-is-out.html/feed 3 Vuurmuur 0.7 getting close http://www.inliniac.net/blog/2009/03/31/vuurmuur-07-getting-close.html http://www.inliniac.net/blog/2009/03/31/vuurmuur-07-getting-close.html#comments Tue, 31 Mar 2009 15:42:35 +0000 Victor Julien http://www.inliniac.net/blog/?p=245 The next stable version of Vuurmuur, 0.7, is getting close. Last week I released release candidate 3. If you’re a Vuurmuur user, please try 0.7rc3 and report back to me on how it works! For a list of changes, please see the closed tickets. Thanks!

]]> http://www.inliniac.net/blog/2009/03/31/vuurmuur-07-getting-close.html/feed 0 Checking out SourceForge’s Marketplace http://www.inliniac.net/blog/2009/01/06/checking-out-sourceforges-marketplace.html http://www.inliniac.net/blog/2009/01/06/checking-out-sourceforges-marketplace.html#comments Tue, 06 Jan 2009 14:26:31 +0000 Victor Julien http://www.inliniac.net/blog/?p=203 I’ve registered myself as a seller of services on SourceForge’s Open Source Marketplace. I’ve done so offering software development services for the Snort, Snort_inline and Vuurmuur projects. I was wondering if anyone has any experience (good or bad) with the Marketplace system, either as a buyer or seller of services. Let me know!

]]> http://www.inliniac.net/blog/2009/01/06/checking-out-sourceforges-marketplace.html/feed 0 Vuurmuur makes it into Debian (Sid) http://www.inliniac.net/blog/2008/12/09/vuurmuur-makes-it-into-debian-sid.html http://www.inliniac.net/blog/2008/12/09/vuurmuur-makes-it-into-debian-sid.html#comments Tue, 09 Dec 2008 14:08:57 +0000 Victor Julien http://www.inliniac.net/blog/?p=184 Thanks to the hard work of Debian’s Daniel Baumann Vuurmuur has been included in Debian unstable/Sid. This hopefully means that Vuurmuur will be getting a lot more users. Eventually it should get into testing and even stable, although the next release “lenny” will come too soon for that. The “lenny” feature freeze was already in place before Vuurmuur got included in Sid. Anyway, for me this is big news!

See here for the packages:
http://packages.debian.org/sid/libvuurmuur0
http://packages.debian.org/sid/vuurmuur
http://packages.debian.org/sid/vuurmuur-conf

Big thanks to Daniel Bauman!

]]> http://www.inliniac.net/blog/2008/12/09/vuurmuur-makes-it-into-debian-sid.html/feed 2 New Vuurmuur version numbering scheme http://www.inliniac.net/blog/2008/09/22/new-vuurmuur-version-numbering-scheme.html http://www.inliniac.net/blog/2008/09/22/new-vuurmuur-version-numbering-scheme.html#comments Mon, 22 Sep 2008 15:15:12 +0000 Victor Julien http://www.inliniac.net/blog/?p=166 Today I’ve changed the versioning scheme for Vuurmuur. I was unhappy with the scheme for quite some time already. Versions like 0.5.73 are not making much sense in my view. Originally, my intention was to have a scheme like the linux kernel at the time had. Even versions for stable releases, odd versions for unstable/development releases. The idea was that the 0.5.x development series would some day become a 0.6 stable, after which the 0.7 development series would begin. Of course, that never happened. Instead, I added the alpha releases that became the real development releases and the 0.5.x effectively became the stable releases. So we ended up with releases like 0.5.74 alpha 6. In my opinion quite confusing.

The new scheme is a lot simpler. There will be a two digit version number with optionally a suffix for development releases. The next stable release will be 0.6. In the path to it, there will be 0.6betaX releases and 0.6rcX releases. After the 0.6 release the next will be 0.7 and so on. After 0.9 the next is 1.0, so no more .74 releases ;-)

I’ve released 0.6rc1 today, and expect 0.6 stable to be out shortly.

]]> http://www.inliniac.net/blog/2008/09/22/new-vuurmuur-version-numbering-scheme.html/feed 0 Support for source port randomization in Vuurmuur http://www.inliniac.net/blog/2008/07/25/support-for-source-port-randomization-in-vuurmuur.html http://www.inliniac.net/blog/2008/07/25/support-for-source-port-randomization-in-vuurmuur.html#comments Fri, 25 Jul 2008 21:50:59 +0000 Victor Julien http://www.inliniac.net/blog/?p=142 One of the workarounds for the current DNS problems is that servers introduce source port randomization.  So it’s time for you to patch your DNS server so it uses random source ports. If for some reason you are unable to do that, iptables can help. Michael Rash has a good write up of how that works here.

In Vuurmuur there is now a per rule option, that can be enabled for the SNAT, MASQ, PORTFW, DNAT and BOUNCE actions, called ‘random’. This passes the ‘–random’ option to the iptables rules Vuurmuur creates. Note that you need a recent distro for this. Debian Etch is too old, Ubuntu Hardy is fine. The new functionality is just released in Vuurmuur 0.5.74 alpha 6. Check it out!

*UPDATE 29/07/08* it turns out iptables/netfilter does not undo existing randomization so removed the text suggesting that.

]]> http://www.inliniac.net/blog/2008/07/25/support-for-source-port-randomization-in-vuurmuur.html/feed 0 Multiple Snort_inline processes with Vuurmuur http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html#comments Mon, 12 Nov 2007 21:29:58 +0000 Victor Julien http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html One of the cool things of the Snort_inline project is the support for NFQUEUE. NFQUEUE is the new queuing mechanism to push packets from the kernel to userspace so a userspace program can issue a verdict on it. What makes NFQUEUE cooler than it’s predecessor ip_queue is that it supports multiple queue’s. This means that there can be more than one Snort_inline process inspecting and judging traffic. The challenge is to make sure that each Snort_inline instance sees all traffic belonging to a certain connection so Snort_inline can do stateful inspection on it. Luckily, Vuurmuur makes it very easy.

Normally an ‘accept’ rule in Vuurmuur looks like this:

accept service http from local.lan to world.inet options log

The NFQUEUE equivalent of this rule is:

nfqueue service http from local.lan to world.inet options log,nfqueuenum=”1″

To have ftp handled by another Snort_inline instance, just add a new rule:

nfqueue service ftp from local.lan to world.inet options log,nfqueuenum=”2″

Easy, no? :) Vuurmuur creates the iptables rules that are required. It uses some advanced connmark-fu for it, so the right Snort_inline process receives all packets from a connection. It uses the helper match to make sure related connections are handled by the right queue, such as the ftp data channel. Of course you also need Snort_inline to be ready for it. See this post for more info on that.

The Snort_inline configuration part takes some work. You have to setup your init scripts to start all instances, setup different configs, logging to different locations. You will need multiple Barnyard’s and if using Sguil multiple snort_agent.tcl instances. When updating the rules you need to take care of the multiple processes as well. As said, it takes some work, but it’s rewarding. You can for example setup an extra Snort_inline instance for testing purposes only. Send all traffic from a certain IP to it to try out new rules, config changes, etc. I have set it up to have separate processes monitor my dmz and my lan.

What is possible as well, but not with Vuurmuur so far, is to have a form of poor man’s load balancing by sending new connections to one of multiple processes. This could be done by making use of the ‘ipt_statistics’ iptables module (fmr ipt_random). This allows a rule to be activated only some percent of the time. By using some more connmark-fu it’s possible to have multiple Snort_inline instances to handle different connections of the same type of traffic. I’ll add support for that to a future Vuurmuur release.

]]> http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html/feed 1 GUI part of Vuurmuur traffic shaping done http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html#comments Thu, 01 Nov 2007 23:03:18 +0000 Victor Julien http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html The GUI part of Vuurmuur’s traffic shaping is done. That means it’s in a usable state. It’s probably rough around the edges, but anyone is invited to give it a try. Below two screens.

Vuurmuur shape rule settings.

The per rule shaping settings.

Vuurmuur shape interface settings.

The per interface settings for the shaping.

Expect an alpha release soon! :)

]]> http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html/feed 1