GrandStream HT502 BEHIND router
-
Geez! doktornotor calm down !!! ;)
While I have shown signs of frustrations, my frustrations really were about the packages not the base platform. If any of you took 2 seconds to look at my other thread where I EXPLICITELY mentioned that on the base platform I had ZERO problems, but with HAVP, Squid and its crappy guardian, I had issues, you would have understood my POV.
I have repeatedly said that I was more than willing to give my time for FREE to help troubleshoot and analyze what the hell is going on with these packages because they're not working well. Is this not what Opensource projects needs in the end? Contributors and people helping for FREE?
It is not pfsense that frustrates me, it is NOT even the packages so much , its people attitude.
You post severe problems you have, you spend the necessary time to document it and write a meaningful thread about it, you explicitly ask developers and other "experts" to at least say a few words, and all you get is:
13 Replies
1139 ViewsWhich on the 13 replies, 11 are MINE.
Thats fine. I get the point. pfsense is meant to be alone to work properly, no packages added. Then I suggest pfsense devs add a big fat warning in the package manager:
Warning! Adding packages may (will) break your pfsense install
-
This is just funny. You need a rather flaky and sensitive VOIP stuff working behind firewall, and instead of setting things up so that it works and calling it a day, you go, overload your box with extremely intrusive, extremely resource intensive and rather horrible to maintain bloat and come back to vent your frustrations about how broken it is. Seriously. Just do not do that! You are causing this whole trouble to yourself!
Now - yeah, snort does NOT work out of the box, never has, never will. And quite frankly my point of view is that it is just pure evil for any home/SOHO environment, not to mention the effort constant babysitting required. (This thing has been dropped from multiple firewall distros for a damn good reason, your rants being a prime example. The mailing lists and forums basically flooded with complaints from people thinking that IDS/IPS/UTM is a musthave, point-and-click, plug and play stuff.) Getting similar intrusive and complicated setups working does not take hours nor days… Do not have time and patience for that? Well, see above, just don't install such things. And regardless, take as a fact that it may just as well never work properly with things like some buggy flaky VOIP device, depending on the device itself, the SIP provider, the ISP, etc. etc. etc.
Finally, these issues are nothing pfsense specific. Snort is exact same intrusive and disruptive everywhere else, HAVP (and the ClamAV thing behind it) does not magically become any better, nor does squid/squidguard when run on say Debian or Fedora instead of FreeBSD/pfSense.
-
I understand your frustrations. Me, being a relative newbie here get your point.
However, the reason the devs and others are not jumping through whoops to reply is because your issues have actually already been talked to death on the forums and they are really busy people. (I'd guess that anyway)If I were you, I'd run pfsense as vanilla as I could and only add what is needed.
I'd say the same for all distros. -
All right, I get the point. This is really eye opening and changed the way I see the pfsense project forever.
I still dream that some day, there are some REALLY SOLID packages for pfsense.
I kept tinkering with this because for a long while, I had success with the pfsense - havp - squid - snort - squidguard combination… Real success.
I still think all of this can be somewhow improved or fixed.
-
As suggested above - these are NOT pfsense-specific issues for the most part. You need to work with upstream to get those sorted out, improved, polished, more usable, less sucky, more shiny, more out-of-the box experience stuff. Those downstream pfSense guys just package the stuff together and ship it (in addition, providing some added value, such at the GUIs.) Unless the issue is one related to the packaging/customized configuration stuff… this won't get solved here.