Re: unbound binaries execution issue
Hello Paul, Can i know if I can specify the particular interface as a default gw for sending query in the code without explicitly configuring that interface as a gw. I checked in my system and it fails. In my system I do not have any default gw configured. So the packets generated within my system are not going outside until I configure a default gw. Rgds simon On Mon, Mar 5, 2018 at 5:24 PM, Paul Wouters wrote: > On Mon, 5 Mar 2018, SIMON BABY via Unbound-users wrote: > > I get the below error while trying to launch unbound-host or >> unbound-anchor or any unbound executable in my build env. Can someone help >> to solve this issue? >> >> sbaby@ubuntu:~/workspace/wqar/tmp/work/mips-mv-linux/libunbo >> und-1.6.8-r0/libunbound/unbound-1.6.8$ ./unbound-host >> > > is "sbaby" a mips machines too? It looks like you are perhaps > cross-compiling, so in that case the binary cannot be tested > on the build host. > > Or maybe your "mips-mv-linux" is a cross compile using a different > set of libraries (like a different c library) ? > > Paul >
unbound sending query with out default GW
Hi, Can i know if I can specify the particular interface as a default gw for sending query in the code without explicitly configuring that interface as a gw. I checked in my system and it fails. Rgds Simon
Re: unbound doesn't remove pidfile
Shawn Zhou via Unbound-users wrote: > I am running unbound 1.5.8 on ubuntu xenial. unbound doesn't run remove the > pid file after it's stopped. I believe the unbound packaging on Ubuntu xenial is old enough that it still uses the sysv generator to create the service unit. You will probably want to add this fix to your unbound init script, which I don't think was ever backported to xenial (it was originally added in 1.5.9-1): https://salsa.debian.org/dns-team/unbound/commit/1c139abaa0fe58f8d97b64c96da6c3332b1b9e49 -- Robert Edmonds edmo...@debian.org
Re: Unbound 1.7.0rc1 pre-release
Hi Andreas, Thanks for the patches, and real fast too! I have applied them, all three. For fastrpz, I removed the trailing whitespace, both from the source and from the patch file. The patch already applied for me, before your fix. With the fix it applies without offsets. The fix uses -p1, not -p0. Also, I don't agree that the spelling is improved by lintian. But to remove the warning, the patch is applied. Best regards, Wouter On 06/03/18 23:32, A. Schulze via Unbound-users wrote: > > > Am 06.03.2018 um 11:02 schrieb W.C.A. Wijngaards via Unbound-users: >> Unbound 1.7.0rc1 maintainers prerelease is available > Hello Wouter, > > the feature list sounds promising! > 3 points: > > > 1. > contrib/fastrpz.patch apply but not without additional help from patch > I have a "fixed" version that apply without warnings. -> attached > > also I received 2 warnings from quilt, the tool to manage patch stacks in > Debian, > while preparing this fastrpz.patch > Warning: trailing whitespace in line 1390 of daemon/worker.c > Warning: trailing whitespace in line 879 of services/cache/dns.c > > 2. > since some months I use a patch that log keytag queries generated by unbound > to support trustanchor signaling. > It's a simple change but it helped us a lot to identify hosts not using the > new KSK-2017 > -> log_trust-anchor-signaling.patch > > (I wish, NSD could log such queries, too) > > 3. > Debian lintian warn about "allow to" should be written as "allow one to" > -> spelling-error-in-manpage.patch > > > That's only from packaging, tommorow I'll /install/ the new version... > > Andreas > signature.asc Description: OpenPGP digital signature
