E2guardian package for pfsense - $??
-
the /usr/local/etc messages may be related to pbi vs pkg isntall
the /tmp/.dguardianipc errors are related to previous dansguardians install and tmp files it creates.
-
What can I do to help get this into the repo? Testing?
-
Testing it out now on my production home system. So far no major problems. Will update this post later.
-
I see period "Exited with status 11" messages in system logs. No obvious malfunction while browsing internet though.
-
I am so very excited about this going into the repo that I am checking the web page every few hours.
I appreciate the work from those who have contributed.
-
I was hoping Renato would post here with an ETA. As I mentioned before, I PM'd him (before I knew he was on holiday), with a link to this thread, but I have seen no post here, and received no reply by PM either. He's either ignoring me (us), or not checking his messages. :'(
Based on the fact he is checking code for pfSense, I'm going to assume he is a pfSense staff member. If that is the case then I'm very disappointed at the lack of updates the company is providing their customers.
Does anyone have any direct contact with him? It would quite excellent if we could get an ETA posted here. :)
-
Better ask for a comunity repo IMHO.
-
FYI - installing 2.2.4 borked my entire internet access. E2Guardian won't start (linked file missing) but even when I disable it and turn off the NAT rule that should be forwarding all traffic to E2Guardian I am unable to make http connections out (https still works). May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
-
May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
Yes. After any firmware upgrade, you need to check freebsd packages you've installed. Sometimes will be a dependence some times just the pkg itself.
-
FYI - installing 2.2.4 borked my entire internet access. E2Guardian won't start (linked file missing) but even when I disable it and turn off the NAT rule that should be forwarding all traffic to E2Guardian I am unable to make http connections out (https still works). May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
Ok, I've tried the following upgrade procedure in a VM: Firstly, I've uninstalled e2guardian using pkg, then upgraded pfSense to 2.2.4, and then reinstalled e2guardian freeBSD packages. This seems to work (I haven't tested it fully yet though).
Here are the steps:- Before the upgrade:
pkg delete e2guardian pkg delete pcre-
Upgrade pfSense to 2.2.4
-
Reinstall e2guardian packages
pkg install e2guardian- Go to e2guardian config and save a page (this is to reapply configs)
I believe this might work even if you applied the upgrade without deinstalling e2guardian first (e.g. do steps 1,3 and 4 after the upgrade). However, I haven't tried it.
-
Is anything happening with this?
-
Is anything happening with this?
https://github.com/marcelloc/pfsense-packages/pull/2/files
https://github.com/marcelloc/pfsense-packages/pull/4/files -
Is anything happening with this?
I haven't seen any updates with regards to the pfSense e2guardian package, so I assume we are still just waiting for Renato (renatohtpc - https://forum.pfsense.org/index.php?action=profile;u=265729) to finish the code review.
He was apparently on holiday, and would be working on it when he got back, but that should have been over a week ago. I PM'd him a while back with a link to this thread with the hope he might let us know what is happening. I assume he either isn't checking his messages, or he doesn't want us to know what is happening. =(
Marcello suggests just installing the code, but I haven't had a chance to try that out. some others seem to have had some success though.
-
Watching the pull request daily, it looks extremely close…
-
Watching the pull request daily, it looks extremely close…
After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.
If you need the e2guardian package, I suggest testing the manual install.
-
After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.
If you need the e2guardian package, I suggest testing the manual install.
I was hoping to be able to wait it out, but i'm going to have to go ahead and do the install manually. Thanks for all your hard work on this. I agree with you that we need a community package list, something that can be turned on for those that don't mind an unofficial list… I think it would help get new and fixed packages out faster. All the code in the pull requests that has just been abandoned because of (undocumented) code format requirements etc... It's sad... A lot of the packages seem very out of date.
-
I think it would help get new and fixed packages out faster.
No panic. We are already cleaning up
:o :o :o ;D ;D ;D
-
No panic. We are already cleaning up
:o :o :o ;D ;D ;D
I do appreciate the work you have been doing to clean up the packages! You have been committing clean up and fixes like crazy and I really do appreciate it! I will revoke my previous opinion only if the packages continue to be well maintained after this blitz :) . To me the packages are one of the greatest strengths of PFSense!
-
Watching the pull request daily, it looks extremely close…
After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.
If you need the e2guardian package, I suggest testing the manual install.
I went ahead and installed manually. First off thank you Marcelloc for all your work on this and everyone else! Content filtering is such a HUGE option to have in my opinion. I did hit a couple of issues however… First the tabs, Users, and IPs, do not work. They both point to xml files but the only files that match are template files. I could see where the users template files (There are two) could be combined and be a working XML, but the IPs file is only half of the xml file. Second and it's not a break issue, the first tab doesn't load correctly until you click on it and have it reload. I can see that it's just how the original menu option loads the url is slightly off. Everything else seems to be working great and I was able to get it all up and running without much work! Love it!
Thanks again for all your hard work on this!!!!
-
I do appreciate the work you have been doing to clean up the packages! You have been committing clean up and fixes like crazy and I really do appreciate it! I will revoke my previous opinion only if the packages continue to be well maintained after this blitz :) . To me the packages are one of the greatest strengths of PFSense!
Hopefully packages will be much more self-maintaining and uptodate with 2.3. The PBI packaging format was one of the worst disasters that could happen here. Hopefully, someone would also
- provide documentation
- provide some VM image with pre-built package server set up ready for testing
The current state with exactly ZERO documentation had led to all this shit, certainly NOT the way to go on!
P.S. Don't count on me maintaining ~100 of packages. I'm ~ half way done with the cleanup, considerably tired, disgusted by the shitty code and annoyed by the absence of any docs. Even the very little we had (a howto on setting up a custom package repo) has vanished.
:( >:( >:(
