@JustinHoMi:

Supposedly the pfsense developers were going to add the capability of using external blacklists to pfsense core, but I don't know what happened to that….

This functionality is slated for the 1.3 release.

There is an application level filering present in 1.3 builds it just is missing the GUI.

@pinoyboy:

Are you saying $300 or more dollars or 30x as in 30x200= $6000?

Pare, ermal has a point.  I know a similar project to this, and it costs the telco $x million…

i was just checking other ways and to make your work simpler, there is an open source project called openSBC along with it is open SIPstack and it uses a very basic form of encryption or lets say putting the data in the plain UDP packet and encryption is XOR and it bypasses the block.
actually i have a few ppl interested in using voip so i could give them the embedded PC with pfsense in it that would work as a standalone PC to encrypt voip or basically bypass the block.
Plz let me know how much u or some1 else would charge for such a thing as the code can be used from openSBC, the XOR encryption or something that sort and port it to pfsense as a plugin.
To my knowledge, porting the XOR method would be something like $50 or if u use the voipswitch way then $75 or $100.
im not sure what type of work is involved so u plz guide me how much should it be for.

Tried it and it looks like it works correctly.  Will monitor it and report back.

This feature is something I would really like as well.  Additionally, I was wondering if this configuration would also be possible with SSL VPN's using OpenVPN.

In the past month I have recently installed 2 untangle PC's and they only support SSL VPN using OpenVPN.  I would like to be able to setup a site to site VPN for monitoring and support purposes.  The clients will be connecting using either: Cisco PIX, Cisco ASA, or Untangle's OpenVPN solution.  I would consider adding to the bounty as well.  Does anyone know if this solution would also work with SSL VPN's?

The author of this bounty has withdrawn it.

Anybody willing to take this bounty? It's the actual logging in filter.log which needs to be modified.

Ok, at this point I am going to withdraw my request for this bounty. If anyone else wants to keep it going by all means but I will no longer require it.

1:1 Nat in Tomato will solve all my requirements and I will not be using Pfsense anymore.

Thanks everyone for the attempt.

I know this is already possible with Cisco devices and GRE tunnels with a routing protocol. 1.3 is supposed to have support for GRE tunnels so it will be possible to do in 1.3 with a routing protocol across those tunnels. I'm not sure of other methods to currently accomplish it.

You may be able to create a failover pool and use policy based routing to send the IPsec traffic from the datacenter to the remote sites using the pool. You would use the remote sites to host the IPsec and have the datacenter as a mobile client.

Sorry for the late reply, I was busy with other things…

Thanks for the offer, but what I'm after is really a GUI option to do that and it needs to be a solution that will be included in one of the next official releases.

If you can create a GUI option that will be included in the official pfsense downloads, then I'm willing to increase the bounty to $100.

Christian

Feel free to expire it anyway.

I think that would be a good Idea. One could even put a price on a resourse like that.

Solved it myself will post info soon.

@sullrich:

I have access now to a 3G sprint USB card.  I plan on taking this bounty.

Please if you have offered cash towards this please let me know that you are still interested.

Thanks!
PS: this will also add "dial up modem" support as well.

When you say dial-up modem support, does that include a dial-up server? As in, could it be used for people to dial in to the pfsense box to gain access to the network?

OK. I withdraw the $ 300 bounty here and I'll post it in the thread you suggested.

Thanks.

Mike

Sorry for the possible stupid question, but im assuming anyone can grab up a bounty? If thats the case, I may be interested in this project =]

I am currently working with pfsense in a test environment to try to replace our current setup at work.

Now as far as questions about the bounty, I'm assuming you would want this proxy to work with different back-end servers. i.e. :

192.168.1.10 www.site1.com
192.168.1.11 www.site2.com
192.168.1.12 www.site3.com

Use pfsense as central WAF (web appliance firewall) that would check content, and if ok pass on to appropriate site. Im assuming this would be configured through pfsense, i.e. point site1 to .10 ip, site2 .11 and site3 .12.

Let me know if that makes sense!

thanks,

kosta