Packages wishlist?
-
How about Nagios? Im looking forward to have it on my pfsense box.
-
First, I would think it would be best to get the core elements 100% stable. Then get add-on packages like Squid Proxy, SquidGuard, IDS… working as stable as possible.
I would definitely like to help out schools that can't afford a lot for technology on pfSense But problems with SquidGuard puts a serious damper on that. See Google SafeSearch bug in the forum. Simple problems liek this can seriously limit utilization of pfSense.
I have two schools right now that need something like pfSense. I have to corporate donated hardware, just can't get the software that works.
Charlie
-
1 - Peerguardian style package. Something to block out those bad ip's ;) Needs to have peerguardian style auto update blocklists. To me this is a big priority as there is not much for 64 bit windows support for this style of program. Having this feature at the router makes the most sense anyways.
2 - email. it actually would be nice to have an email appliance with webmail. I'm looking at clarkconnect, but only for the email functionality, as the rest is defiantly lacking compared to pfsense.
It's hard to really ask for much more.
-
I have not read thru all 14 pages of the wishlist so I'm not sure if this has been suggested or not.
One of the unique features that is available in Windows SBS servers is Remote Web Workspace (RWW). That feature is not available with any other version of windows or as standalone because it replaces the functionality of a terminal server to some extent. And Terminal Server CALs bring MS a lot of that green stuff.
For those that do not know what RWW is, please do a google search. A video or two of it in action is on the net. Also this: http://www.sbsfaq.com/Lists/FAQs/Attachments/135/Remote%20Web%20Workplace%20-%20Part%201.pdf is a good article on how RWW works behind the scenes.
Now back to the idea of a package: the way I see it, all the functionality that is needs to make an RWW alike package (I'll call it RDP Portal) is already available in pfSense.
Here is how I think the package should work:
The package:
1. Maintains a list of all machines on the private side (interfaces and network ranges configurable/selectable) that can be RDP-ied to. This list can either be manually generated, imported, or generated by doing a scan of the network(s) for machines that listen on TCP:3389 (port selectable in config.) Use DNS to resolve the names (that was understood, why did I even mention it.)
2. Presents a web page on the public side (again interface and IP selectable) that acts as the portal for the RDP Proxy. Once the users log in (authentication based on Kerberos or Radius), they are presented with a list of machines they can RDP into. Some form of access control list can probably be introduced through LDAP or other means here to restrict which machines the user get to see in that list. Also a TCPPing can probably be done to only list machines that are active. May have to be a background scheduled TCPPing so that the network is not jammed by these when the list need to be displayed to the portal client.
3. When a user selects a machine to connect to, a port forwarding rule is created on the fly that maps a dynamic high port (would be nice if a usable port range can be defined and a port from it is randomly selected) on the selected IP on the WAN side, mapping it to port 3389 of the target machine. At the same time a firewall rule is created between the IP that the client contacted the portal with and the RDP machine he chose to connect to. This is where this solution would differ from the MS RDP Proxy they implement in SBS. They proxy the connections and we will be doing this using port forwarding.
4. The RDP portal web page then redirect the user to a page with the ActiveX embedded RDP client to open an RDP connection for the client to the desired machine.
5. Does some sort of states monitoring to see when the connection ends or dies at which point both the port forwarding rule and the access rule can be removed (possibly with a delay since I think the RDP client does try to reestablish the session if for some reason it is lost.)
That is pretty much all I can think of to include in a package like that. I'm sure others can probably add some nifty features to it.
Now there may be security related ramifications of such a package because it would essentially be a scripted mechanism with root access.
I may have some time starting third week of February to possibly start developing a package like this. But I'm not going to be able to do it on my own. Will need help. Probably lots of it.
Thanks,
Shahid
-
i want and need really bad for reporting system such as lightsquid for firewall rules in pfsense.
-
How about a x64 version and a VMWare package?? Seriously, what better to run on a firewall then a VM?? You could install a Host OS on a protected OS.
-
How about a x64 version and a VMWare package?? Seriously, what better to run on a firewall then a VM?? You could install a Host OS on a protected OS.
Until VMWare actually runs on FreeBSD, there's zero chance of it becoming a package. An amd64 port is in the works, but for fairly obvious reasons also won't be a package :)
–Bill
-
wanted:
OSSEC HIDS package for pfSense !
-
Re: the question about docs -
If you can provide some better docs and how-to for the XML/GUI portion of the packaging, I will probably be able to provide a dnscache package. I want it, and there seem to be other people who want it; IMHO a fast caching resolver is a big win for a network with slower upstream connectivity, and it goes great with squid too. (It would be nice to implement it with an option for forward-only vs. full caching recursive resolver.)
I've done a lot of FreeBSD work, including building a near-appliance system of packages for a spam filtering system. I have a home FreeBSD system to develop on (at 6.4 currently) and the dnscache binary package should be easy; I've built lots of packages before, and that might even be available for 7.1 from the FreeBSD package repository.
It's just understanding what's involved in hooking it in that's an issue for me - how to map setting up the configuration, forwarders/root servers, etc. into the pfSense menus, and whether there's actual PHP code to write or not.
-
It's just understanding what's involved in hooking it in that's an issue for me - how to map setting up the configuration, forwarders/root servers, etc. into the pfSense menus, and whether there's actual PHP code to write or not.
This might help you:
http://devwiki.pfsense.org/PfSenseDevHome
–> http://devwiki.pfsense.org/PackageInfo -
This might help you:
http://devwiki.pfsense.org/PfSenseDevHome
–> http://devwiki.pfsense.org/PackageInfoThank you! I had looked at the wiki previously, but hadn't found that overview page.
-
PF SENSE as a Dynamic DNS server
can something like this be implemented
http://code.blitzaffe.com/pages/phpscripts/files/ddns_server_54-35 -
What about Dans Guardian???
-
Hi
A preprocessor for Snort that block the packets that matches the rules before they ever reach the target, and make the Snort implementation a true IPS would be nice. -
DenyHosts. I was able to install it with the pkg_add command, so it shouldn't be that hard right.
I would love to help if someone can tell me what I need to do to get this package made, maybe and example. -
A USER TRACE MODULE!!
Kind of simple, i think : a module which when activated, logs everything regarding a certain authenticated user, from captive portal for instance. You go on the GUI, then type in the name of the user and here it goes, it displays you all the websites the user went to, and when he logged in etc…
Doing the same with pfsense requieres to log systems to a syslog, and to transfert squid logs files to a server, and you have to check each file to find what you're looking for. This module could be really usefull, and totally push to garbage products like zyxel G4100 or Ucopia boxes...
-
snort is already there use pfSense 1.2.3 RC1 and then look under packages.
-
TOS/DSCP set and reset (or TOS/DSCP remarking)
-
I would like to see a package that analyzes all traffic and organizes it in the same way that lightsquid does it. NTOP is the only package that comes close, but I found it unstable and the information is scattered.
For example each day you get a list of all your host ip addresses and underneath it will have all the sorted protocols used by that ip address and the ip addresses that it connected to.
192.168.1.28
HTTP
1 v7.cache5.c.youtube.com 1 24.9 M 24.9 M 18.1%
FTP
Sent
1 ftp.ftp.com 1 24.9 M 24.9 M 18.1%
Recieved
1 ftp.ftp.com 1 14.7 M 14.7 M X% -
How about the R-U-ON server monitoring agent (http://www.r-u-on.com)?
