Sphirewall 0.9.9.4 Finally Released

The Sphirewall Team is damn excited to announce another release today. Sphirewall 0.9.9.4 packs punches in a few areas with the introduction of many features and enhancements that were requested by our users.

Users will notice right from the word go the changes to the look and feel of the web management interface. It has had a makeover of sorts, with new graphs, and controls offering a more streamlined administration experience. Top that off with new Openvpn Client support, more flexible and streamlined Event Management, Port Range support for acls, Dynamic Dns, performance enhancements, bugfixes and the list just goes on and on.

Here is a sneak peek at the reworked wmi

Screen Shot 2013-06-06 at 2.08.07 PM Screen Shot 2013-06-06 at 2.07.47 PM

 

For the full list of new features, check out the release notes http://sphirewall.net/release-notes

Join us on the forums to get involved, we would love to hear your feedback,

Sphirewall 0.9.9.3 Released Today

Today Sphirewall version 0.9.9.3 has been released. This release is packed with bugfixes, enhancements to existing functionality and some love for the Web Management Interface. Most effort for this release was spent on stability and runtime optimisations. Users will notice a more responsive and stable system.

You can download the latest version here and view the release notes here

Sphirewall 0.9.9.2 Released Early – Bugfixes

Today we released several bugfixes for issues that arose in the last release. 0.9.9.2 is now available from the aptitude repository and through the debian distribution.

These bugfixes include, but are not limited to:

  • An issue with graphing in Firefox and Safari
  • An issue with init scripts
  • An issue with tab rendering in Firefox and Safari

For the full release notes, check here

We urge users to update to this version as soon as possible.

Getting an insight into your network with Sphirewall Analytics

After running the latest release of Sphirewall for 3 days, I thought it would be cool to take a peek at what statistics are available on my home network. Sphirewall is driven to provide more information on your network which coupled with active events and a more user driven approach can prove to be very valuable. But enough with the blatant plugging and lets take a look.

The visibility starts right from the dashboard, where you are presented with a graph showing total connections active on your network.

Screen Shot 2013-03-05 at 10.37.14 PM

This can give you some indication as to how much traffic is currently running through your network, and what the general load is like. Somewhat boring, unless your just wanting to check if things are running ok.

So we dive straight into the reporting tab. On opening, you are presented with a screen looking something like below.

Screen Shot 2013-03-05 at 10.39.30 PM

Here you see a summary of total transfer over a time frame, extending and reducing the filter timeframe will dictate whether you see data on a day breakdown, or hourly breakdown. But this is not so interesting at the moment, what I really want to see is what my annoying flat mates have been doing through my internet connection. So we flick to the address breakdown, I am not using user authentication on my home network.

Screen Shot 2013-03-05 at 10.45.17 PM

This report shows me very quickly, that the top host on my network is 192.168.2.100. Just as I suspected, but I want more information. Clicking on the ip address “192.168.2.100″ directs me to more details

Screen Shot 2013-03-05 at 10.47.36 PM

This report, apart from the funny looking graphs, shows us that on the 4th of May, there was a large increase in traffic transfer. The other days are almost irrelevant. We can filter down to that particular date by just clicking on it.

Screen Shot 2013-03-05 at 10.51.44 PM

This screen gives you a hour by hour breakdown of transfer from this host, followed by a breakdown by port. We can very quickly see here that this user has been surfing the web on port 80, the standart http port. Clicking on this port, will bring you to the web application reporting, which provides a nice breakdown of website urls.

Screen Shot 2013-03-05 at 10.55.30 PM

Here you can see a breakdown of websites the users on 192.168.2.100 have seen. Its quite interesting, and you can extend it further by clicking on the urls. We can very quickly see that he or she has been streaming music via Digitally Imported Radio (a very cool service by the way).

This reporting does not stop here, you can start analysing at many different starting points, and are always able to drill down and filter on specific dates, hosts, ports and what not. The information gathered here can also be used, for things such as quotas, accounting and dynamic rules. It can get pretty cool. We collect and aggregate statistics on a hourly basis, lower aggregations are possible, however normally they are not required. There is another side to the reporting system that may be less obvious, we also record system metrics. There is alot happening inside Sphirewall, and for debugging purposes its sometimes useful to take a look at these numbers. Take a look at the Performance and Metrics tab under Status.

If you have questions, or ideas, drop is a line on our forums, or email the development team via support@sphirewalllabs.co.nz

 

Sphirewall 0.9.9.1 Released Today

The Sphirewall team is very excited to announce another great release. 0.9.9.1 brings to the table a whole new level of network management with a greatly improved web management interface and a couple of killer new features.

The main new features with this release include, openvpn support, enhanced address pools/aliases with support for remote lists, maxmind geoip and the first iteration in a application level filtering system starting with a http web filter. We have also invested a large amount of time in tuning several aspects of the web management interface. Setting configuration options, adding rules and almost all aspects of the WMI are easier to use and more intuitive for advanced and novice users alike.

Screen Shot 2013-03-04 at 9.54.57 PM

The full release notes can be found here.

Over the coming months we will be working hard on the application layer filtering and alias/pooling subsystem. If you would like to see something in Sphirewall, we would love to hear from you. Jump to our forums, or send an email direct to the team support@sphirewalllabs.co.nz

 

Sphirewall 0.9.9.0 Released Today!!

The Sphirewall Team is very happy to announce the December/January installment of Sphirewall.

Sphirewall 0.9.9.0 brings with it dramatic performance and stability improvements in the core, layer 7 http packet inspection for web reporting and many more features that push Sphirewall to fit your needs. This release was mostly about optimising Sphirewall for high load networks, and in this respect we succeeded.

  • Reporting on website level
  • Increased support for the command line
  • Automatic user creation
  • Increased support for managing network interfaces and the isc-dhcp-server daemon
  • Increased configurability for high load networks
  • Support for gigabit networks
  • Security and user input validation in the web client
  • Several critical bugfixes

The next release will be in 2 months, and will be coupled with more layer 7 control for your network.

Visit our website for more information, and downloads http://sphirewall.net

Sphirewall 0.9.8.9 Released Today

The Sphirewall team once again is happy to release another version of Sphirewall. This release has seen a major change to the Kernel –> Userspace communication, both the command line and web based management interfaces have seen improvements in handling user input and presentation, and we have made loads of small improvements and bug fixes.

For the full release notes, visit http://sphirewall.net/release-notes and to download sphirewall visit http://sphirewall.net/downloads.html

You can also checkout our roadmap for the following releases and vote on stories at http://sphirewall.net/roadmap.html

Thanks,

Why I created another linux firewall project, and why its unmatched by any other product

The story starts in a student flat in Christchurch, New Zealand. At this time I have two flatmates who were “hardcore” gamers and when they weren’t gaming they were downloading or streaming media from various sites. At this time, being the network nerd in the house I had setup a nice Iptables firewall, hand coded rules on a old compaq laptop that shipped with windows 95 20 years ago. It ran perfectly, and naturally I was rather proud of it.

However the day came when we got the first internet bill, $700 dollars for 200G transfer. For 3 students, this is alot of cash. But alas, we survived. Then the next bill came, and the next, and well you get the story. So I started searching for a better firewall setup, that could tell me who was using the bandwidth, and how much they were using. Then we could split the bill evenly and I would get a new toy to play with. So I searched, and I found nothing. Only a few forums with other people having the same problem, and the only solution being either buy a very expensive firewall system from cisco or manually script something with iptables counters (which by the way is not at all flexible). To even authenticate a user was a problem unless you were running a proxy server, and of course with a network where there is more than just http traffic a proxy server was not the solution. This situation magnifies in a corporate or school environment, then its vital to see what is going on in your network.

At this point, I was surprised and frustrated, how could it be possible that no one had made this type of system. So I created it. I spent perhaps 6 months on the initial version, and ran into loads of problems. First started with iptables, but it was to restrictive to get the user authentication right, then I experimented with pf, and encountered the same problem. So I built it all from scratch, and thus Sphirewall was born.
Over the last 3 years, development has been on and off, and the entire codebase has been rewritten. But as it stands now, Sphirewall 0.9.8.8 is almost ready for release, and what you can do with it is getting cool. With detailed analytics and user management, the possibilities opened up for some really cool features like role based QOS, capture portal, quotas, event driven management.

At the moment we support:

  • User accounts and roles
  • Detailed analytics, you can see what user/host has been doing on the network
  • QOS
  • Quotas
  • Nat/Pat
  • Filtering

All firewall rules can be based on user roles, or normal criteria. Sphirewall actually hooks into the kernel packet stream itself, so its really stands alone in comparison to other firewalls that are just rule generators for Iptables or pf.

Sphirewall is managed via a JSON api, and built on top of this is our php web management interface

Sure there are bugs, and lots of things that could be improved, but I am looking for some feedback, and some support from the community. So take a look at the project and tell us what you think.

 

Sphirewall 0.9.8.7 Released

The sphirewall team once again has a release to announce. The latest version 0.9.8.7 is now available through our mirrors and in more forms than ever before.

With this release comes many usability features, the biggest being the introduction of a debian based linux distribution. We now packages as an ISO. This means you can get up and running with sphirewall in a matter of minutes without any dependencies or linux knowledge.

Other improvements with this release include but are not limited to,

  • Rework the analytics front end to display more information and in a nicer fashion
  • Fix all major bugs
  • Total transfer statistics
  • Group, mac address and other criteria to scli firewall rules
  • Native ldap and pam support
  • Removed dependency on google graphs, and rework graphs in web interface

Check it out now, and help steer to project by getting involved