Packages wishlist?
-
Oh, okay, that's cool, I didn't know that!! ::)
Thanks Leoandru!
-
Okay, I've tried this out on my own pfSense FW, I can install the packages no problem. I guess I need to make a custom kernel however, because there is now smbfs.ko to be loaded. I tried just copying one from my freebsd system, but that doesn't work. I've built a kernel before, but just with very basic changes. What would I have to do to build the pfSense kernel with only the addition of that one module? Where do I specify for it to build that module?
Thanks for your help…
-
Some form of packet capturing for use with Ethereal would be incredible!
-
This might be possible for a package?
Is there a way, (or possible) to have pfSense put IP addresses of people in a sort of temporary pool that will block all access from them, if they say lauch an attack against the router.
Multiple attempts to attack the router results in a 6 hour ban. Something of that sort.
-
This might be possible for a package?
Is there a way, (or possible) to have pfSense put IP addresses of people in a sort of temporary pool that will block all access from them, if they say lauch an attack against the router.
Multiple attempts to attack the router results in a 6 hour ban. Something of that sort.
That's possible with Snort. However, it's not always desirable to run an IDS in your firewall. Besides, if you have to use such a system, you should be confortable enough to implement it manually, without GUIs.
-
No they won't not unless your doing a clean install. I have Been running a jabber server on my pfSense box that survived several upgrades.
Likewise, I didnt want to get a separate box just to run a jabber server, so I just installed and configured it on my firewall.maybe you could publish the package for the community to use?
-
Anything custom that starts from /usr/local/etc/rc.d/ is not touched during upgrades.
This is basically the package area (/usr/local/).
You are pretty safe in adding you own startup files in /usr/local/etc/rc.d/*.sh … We do not touch them during upgrade.
-
I think it would be great to see a package for myNetWatchman (http://www.mynetwatchman.com) if possible. That and perhaps SFTP :-[
-
-
SFTP is already in, it's part of SSH.
This is true, but I'd like to know how to use an SFTP client when the menu is presented after every SSH login…
-
login true a sftp client
then you don't get that ssh menu -
I'm not sure if this can be done but some sort of log reporting package which would generate a couple web pages on the statistics….kinda like awstats with a builtin syslog thing....sorta hard to describe but would be cool.
-
login true a sftp client
then you don't get that ssh menuI've tried gftp, putty-tools, hsftp and the sftp binary all with the same result - what would you recommend for a linux sftp client?
-
login true a sftp client
then you don't get that ssh menuI've tried gftp, putty-tools, hsftp and the sftp binary all with the same result - what would you recommend for a linux sftp client?
gftp works. Double check your configuration.
-
One I always liked and it was a pain in the ass to configure and to setup Squid with Squid Guard.
Maybe there is a better content filter out there but SquidGuard seemed to work fairly well.
I know of a lot of buisnesses/clients that love to have either reality/pornographic/sports/etc/etc websites filtered. Although I havn't messed with SquidGuard in some time it had no Auto Blacklist to update. I did however right a script to grab one from my FTP server ever week when it was updated.
-
I'd like to see gkrellmd(the X11-less daemon only) and bfilter(an ad/script/img blocking proxy).
Atm I have a gkrellm(thanks to some very nice people from irc) installed but it's lacking an interface to configure it via the web configurator.
-
I've found www.ipp2p.org for iptables/netfilter.
Is there any packages can do blocking p2p filesharing traffic in FreeBSD/pfSense? -
Snort would be able to do this, also a layer7 filter of some sort would also be able to do this.
P2P is in general hard to filter out as it tends to use whatever port it can get it's hands on (like www port 80).
You need either a raw packet filter, or a layer7 filter.
At this point there is no way to effectively block P2P in pfsense. -
i like to see a complete packages (tftpd,nfs,etc…) to allow diskless/pxe client boot into something like thinstation or puppy or others...
like these ones:
thinstation.sf.net
http://forums.freesco.org/support/index.php?showtopic=13170&st=45&#entry74098 -
Nagios would be a good package