2.1-BETA0 -> 2.1-BETA1 unbound won't install
-
Is the Unbound package fixed now so we can go in and try and install on 2.1 PfSense 64?
-
I haven't seen any commits to it, and the ticket hasn't been updated, so I'd say probably not.
-
It says 100% done.
Does this mean Unbound on 2.1 is fixed?
-
That was referring to moving it to a package (out of the GUI)
The package part still needs fixed. The maintainer knows, he'll get to it when he has time.
-
We have been using unbound for Quite some time. (pretty much the day
unbound support started to appear on pfsense)all of our production pfsense boxes with Beta1 (and beta0) on them work fine PROVIDED
your willing to use google and unbounds website to figure out the errors and
how to fix them UNTIL the maintainer can fix it.been doing it for quite some time now and know my way around unbound and pfsense.
(FreeBSD runs all of our Production Servers)i do the mods in the lab first and do my testing before rolling out changes to ALL of our
pfsense boxes and thats after 30 days of testing hard in the lab. -
Do you actually fix the unbound source code, or do you just move files around so that unbound can actually find them?
-
SunCatalyst
Can you share the instructions on how to fix Unbound to work on pfSense 2.1 Beta 64?
Is there a patched package you can upload somewhere?
-
i dont have any packages to share to fix things NOR would i want to step on the maintainers Toes. (wagonza)
im sure he will get to it Soon.things like the key missing or a file missing , you have to be able to poke around to see what the
fix is. sometimes its as simple as symbolic linking a file thats in the wrong place to the correct place
or grabbing unbound from FreeBSD's server itself and pull it apart to find the files you need.ive spent Numerous hours reading and figuring out unbound.
Good Luck.
-
On a i386 system the following seems to get unbound working after the package install:
At the console:
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound.conf /usr/local/etc/unbound/unbound.conf
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_server.key /usr/local/etc/unbound/unbound_server.key
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_server.pem /usr/local/etc/unbound/unbound_server.pem
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_control.key /usr/local/etc/unbound/unbound_control.key
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_control.pem /usr/local/etc/unbound/unbound_control.pem
Something similar should do for the x64 version. -
Hi guys,
I got unbound installed and it works great…...for about an hour.
This is the same thing it was doing the last time I tried it about a year ago.
-Will
-
Hi guys,
I got unbound installed and it works great…...for about an hour.
This is the same thing it was doing the last time I tried it about a year ago.
-Will
Could you be anymore vague about so that we couldn't help you at all?
But anyways, I'm running Unbound just fine on the 18.3 snapshot, x64 etc. Of course had to do the links by hand but otherwise works as it should.
-
Hi n1ko,
I'd be less vague if I could. About all I can tell you is that unbound seems to work just great for about an hour and then all my DNS resolution stops working. Disable unbound, re-enable the dns forwarder & I'm back in business.
I would expect that it's related to this:
http://forum.pfsense.org/index.php/topic,43044.msg234009.html#msg234009
as this is the exact same behavior I saw in January 2012.
-Will
-
Unbound package seems to be broken for the past couple months.
Is it abandoned by the developer?
Should it be deleted from the 2.1 pfSense Packages?
-
It's not abandoned, he's just been very busy lately.
-
Is there any real expectation that the unbound package will ever work in 2.1? This has been an open concern for about two months now.
-
In last week i installed unbound here and to work i copy the certs to /usr/local/etc folder (like jcyr posted) and installed the .tbz package (make package-recursive in freebsd 8.3). First installed by package manager in pfsense, secound install the .tbz. This is wrong way to do, but, it's working by 5 days now until the final solution (the pbi corrected with the new binaries).
Best Regards.
-
It will be fixed properly eventually. Either when the package maintainer gets time (he's really busy with work), or when someone else that's capable of fixing it steps up and submits some fixes for it.
-
Does unbound install and work correctly in 2.0.1? I'll gladly forgo IPV6 functionality for a working secure DNS.
-
jimp, have some howto to use the pbi build system just for pfsense ?.
I can update the package always.Best Regards.
-
The PBIs are fine, it's the package code that needs updated. Several other packages needed similar modifications (e.g. squid, snort, zabbix, nut, nrpe, avahi, bandwidthd, etc) it shouldn't be too hard to follow their lead in how things are fixed.
