How would the program communicate the changes?  Would it be encrypted?  If yes how?  Are you talking about an executible that the user would have to run on there PC..ie download locally?

It is rather ambiguous, that could just mean you can't put something up there that says "donate $X so I can fund my business" or something like that, where what we would use it for would be specific development projects which normally appear to be fine by their policies. But since it's going towards payroll, people work on whatever we get paid to work on, I don't know. If you hear back from them, let us know.

http://curlftpfs.sourceforge.net/

–Bill

@mhab12:

If you want to turn off disk caching for embedded, search the package forum for null disk mode or something similar.  I can't quite recall the correct terminology, but it has been done before.

This is in the squid gui settings now. Just pick "null" for the cache type.

If the bar to entry is too high for you, at least consider buying the book.  I suspect the $30USD outlay would have saved you several days' effort.

I don't really need this but I think it's an interesting feature and would help sponsor it if it moves forward (and can be restricted to certain interfaces & block certain MAC addresses).  Truth of the matter is though, unless there is some preexisting code for FreeBSD, this is a multi-thousand dollar project and you're either going to need to dig deeper or find a lot more people willing to contribute.

Thank you ! I will work with cmb and try to get this to work.

CJ

There was some passionate discussion about this very topic (Snort v. Suricata) on Slashdot the other day…
http://it.slashdot.org/story/10/07/21/1221209/Is-Open-Source-SNORT-Dead?art_pos=1

2.0's dyndns supports registering any interface, but will never change which interface is registered based on WAN status.

I think the easiest solution for this is to run the updater on a client PC on the LAN, then when WAN status changes the registration will come from a different IP.

You're looking at several hundred hours of development time, minimum for something like that.  Probably close to a thousand hours to develop something that doesn't suck with the ferocity that Untangle's UI does.

Thanks for the replies. Further examination of the documentation of the underlying software revealed that MLPPP links MUST use the same username and password. :)

I'm displaying the "Description" field if it is not blank and the "Link Interfaces/Ports" if the Description is left blank.

Almost ready for testing . . .

GB

Then withdraw bounty -)

@xbipin:

the traffic shaper in 2.0 is the bounty one or we need to pay some amount and get it for 2.0 platform?

It's the bounty one, so no need to pay unless you want to support pfSense in general.

Im interested, wrote me at leoalfa09 in gmail dot com

@cmb:

Is auth-user-pass the only thing preventing you from using the GUI? That will be implemented in 2.0, so it will be something you can accommodate in the GUI.

Ok, I seem to have it working now by choosing 'SSL/TLS' as server mode. auth-user-pass was not the problem as I had saved my credentials on a file. I had problems because I wanted to load the ca certificate from the additional options instead of importing it in the certificate manager. Now the tunnel is working, I can ping through the interface, although I'm having a hard time pushing traffic through the tun interface. I'll post a thread for that in the relative section.

@tommyboy180:

Can this be does with pptp? If so let me know I may add to the bounty.

I don't know about your setup, but I might still be interested in paying for a specific configuration page for VPN gateways to the internet.

That's definitely doable, but you're asking for somewhere around 100 hours of work for less than what a developer with that skill set gets paid in a day.

If your budget increases to around $5000 USD, we'd be glad to do that for you. Contact me via email, cmb at pfsense dot org, if that's feasible.

this @rokio:

yes, we did work with the static port setting enabled, and I tried the siproxd package too.
thanks for the tip of the states… should have known that earlier!

r

Update march 9, 2010, it has been fixed! no need to respond anymore

rr

never mind (bounty closed)…..i`ve almost done it myself and as soon as it will 100% completed i will post the solution here.

or you can grab the update your self and install it yourself through the shell, not sure about simlinks and the integration, but I had this group problem when testing  smoothwall until smoothwall offered an upgrade to the program.. for free non-the-less.

squid2.7 was compiled for freebsd7.0 with delaypool disabled.