Re: unbound binaries execution issue

2018-03-09 Thread SIMON BABY via Unbound-users 
Hi Pete,

Quad9 worked. Thank you for the help.

Rgds
Simon

On Fri, Mar 9, 2018 at 3:12 PM, Pete Wright  wrote:

>
>
> On 03/09/2018 15:04, SIMON BABY via Unbound-users wrote:
>
>> Hello Paul,
>>
>> Do we have any other public DNS validating servers other that 8.8.8.8
>> which support DNSSEC? I tried with 8.8.8.8 and the results are always
>> bogus. it looks like 8.8.8.8 is stripping off all the
>> DNSSEC related flags when it send back the reply to my client.
>>
>>
> I believe the "Quad9" (9.9.9.9) public resolver supports DNSSEC properlly:
> https://www.quad9.net/
>
> hope this helps,
> -pete
>
> --
> Pete Wright
> p...@nomadlogic.org
> @nomadlogicLA
>
>

Re: unbound binaries execution issue

2018-03-09 Thread Pete Wright via Unbound-users 



On 03/09/2018 15:04, SIMON BABY via Unbound-users wrote:

Hello Paul,

Do we have any other public DNS validating servers other that 8.8.8.8 
which support DNSSEC? I tried with 8.8.8.8 and the results are always 
bogus. it looks like 8.8.8.8 is stripping off all the

DNSSEC related flags when it send back the reply to my client.



I believe the "Quad9" (9.9.9.9) public resolver supports DNSSEC properlly:
https://www.quad9.net/

hope this helps,
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

Re: unbound binaries execution issue

2018-03-09 Thread SIMON BABY via Unbound-users 
Thank you so much Paul. I will try with QUAD9.

Rgds
Simon

On Fri, Mar 9, 2018 at 3:12 PM, Pete Wright  wrote:

>
>
> On 03/09/2018 15:04, SIMON BABY via Unbound-users wrote:
>
>> Hello Paul,
>>
>> Do we have any other public DNS validating servers other that 8.8.8.8
>> which support DNSSEC? I tried with 8.8.8.8 and the results are always
>> bogus. it looks like 8.8.8.8 is stripping off all the
>> DNSSEC related flags when it send back the reply to my client.
>>
>>
> I believe the "Quad9" (9.9.9.9) public resolver supports DNSSEC properlly:
> https://www.quad9.net/
>
> hope this helps,
> -pete
>
> --
> Pete Wright
> p...@nomadlogic.org
> @nomadlogicLA
>
>

Re: unbound binaries execution issue

2018-03-09 Thread SIMON BABY via Unbound-users 
Hello Paul,

Do we have any other public DNS validating servers other that 8.8.8.8 which
support DNSSEC? I tried with 8.8.8.8 and the results are always bogus. it
looks like 8.8.8.8 is stripping off all the
DNSSEC related flags when it send back the reply to my client.

Rgds
Simon

On Wed, Mar 7, 2018 at 1:31 PM, SIMON BABY  wrote:

> 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
>>
>
>

Re: unbound binaries execution issue

2018-03-07 Thread SIMON BABY via Unbound-users 
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
>

Re: unbound binaries execution issue

2018-03-06 Thread W.C.A. Wijngaards via Unbound-users 
Hi,

Yes the key files are platform independent.

Best regards, Wouter

On 06/03/18 06:54, SIMON BABY via Unbound-users wrote:
> Hello Paul,
> 
> Thank for looking into my issue. Yes, Am  cross compiling for the
> target. Below is my configuration logs.  I am implementing the client
> resolver application with the library. So if I cannot run the binary in
> my host machine, how can I generate the trust-anchor key and pass to the
> application. May be I can execute unbound-anchor on the target  and
> generate the key, and then put back to the application on the host machine?
> 
> 
> 
> +
> /home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/configure
> --build=i686-linux --host=mips64-mv-linux --target=mips64-mv-linux
> --prefix=/usr --exec_prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
> --libexecdir=/usr/libexec --datadir=/usr/share --sysconfdir=/etc
> --sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib32
> --includedir=/usr/include --oldincludedir=/usr/include
> --infodir=/usr/share/info --mandir=/usr/share/man --build=i686-linux
> --host=mips64-mv-linux --target=mips64-mv-linux
> checking for mips64-mv-linux-gcc... mips-montavista-linux-gnu-gcc
> -march=octeon  -msoft-float   -mabi=n32
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 accepts -g... yes
> checking for mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float 
>  -mabi=n32 option to accept ISO C89... none needed
> checking how to run the C preprocessor... mips-montavista-linux-gnu-gcc -E
> checking for grep that handles long lines and -e...
> /home/sbaby/workspace/wqar/tmp/staging/i686-linux/usr/bin/grep
> checking for egrep...
> /home/sbaby/workspace/wqar/tmp/staging/i686-linux/usr/bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking for an ANSI C-conforming const... yes
> checking for mips64-mv-linux-gcc... (cached)
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 accepts -g... (cached) yes
> checking for mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float 
>  -mabi=n32 option to accept ISO C89... (cached) none needed
> checking mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float 
>  -mabi=n32 dependency flag... -MM
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 supports -Werror... yes
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 supports -Wall... yes
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 supports -std=c99... yes
> checking whether mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32 supports -xc99... no
> checking for getopt.h... yes
> checking for time.h... yes
> checking whether we need -std=c99 -D__EXTENSIONS__ -D_BSD_SOURCE
> -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600
> -D_XOPEN_SOURCE_EXTENDED=1 -D_ALL_SOURCE as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
> checking whether we need -std=c99 -D__EXTENSIONS__ -D_BSD_SOURCE
> -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600
> -D_ALL_SOURCE as a flag for mips-montavista-linux-gnu-gcc -march=octeon 
> -msoft-float   -mabi=n32... no
> checking whether we need -std=c99 as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
> checking whether we need -D_BSD_SOURCE -D_DEFAULT_SOURCE as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
> checking whether we need -D_GNU_SOURCE as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... yes
> checking whether we need -D_GNU_SOURCE -D_FRSRESGID as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
> checking whether we need -D_POSIX_C_SOURCE=200112 as a flag for
> mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
> checking whether we need -D__EXTENSIONS__ as a flag for
>

Re: unbound binaries execution issue

2018-03-05 Thread SIMON BABY via Unbound-users 
Hello Paul,

Thank for looking into my issue. Yes, Am  cross compiling for the target.
Below is my configuration logs.  I am implementing the client resolver
application with the library. So if I cannot run the binary in my host
machine, how can I generate the trust-anchor key and pass to the
application. May be I can execute unbound-anchor on the target  and
generate the key, and then put back to the application on the host machine?



+
/home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/configure
--build=i686-linux --host=mips64-mv-linux --target=mips64-mv-linux
--prefix=/usr --exec_prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/libexec --datadir=/usr/share --sysconfdir=/etc
--sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib32
--includedir=/usr/include --oldincludedir=/usr/include
--infodir=/usr/share/info --mandir=/usr/share/man --build=i686-linux
--host=mips64-mv-linux --target=mips64-mv-linux
checking for mips64-mv-linux-gcc... mips-montavista-linux-gnu-gcc
-march=octeon  -msoft-float   -mabi=n32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 accepts -g... yes
checking for mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 option to accept ISO C89... none needed
checking how to run the C preprocessor... mips-montavista-linux-gnu-gcc -E
checking for grep that handles long lines and -e...
/home/sbaby/workspace/wqar/tmp/staging/i686-linux/usr/bin/grep
checking for egrep...
/home/sbaby/workspace/wqar/tmp/staging/i686-linux/usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for an ANSI C-conforming const... yes
checking for mips64-mv-linux-gcc... (cached) mips-montavista-linux-gnu-gcc
-march=octeon  -msoft-float   -mabi=n32
checking whether we are using the GNU C compiler... (cached) yes
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 accepts -g... (cached) yes
checking for mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 option to accept ISO C89... (cached) none needed
checking mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 dependency flag... -MM
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 supports -Werror... yes
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 supports -Wall... yes
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 supports -std=c99... yes
checking whether mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 supports -xc99... no
checking for getopt.h... yes
checking for time.h... yes
checking whether we need -std=c99 -D__EXTENSIONS__ -D_BSD_SOURCE
-D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600
-D_XOPEN_SOURCE_EXTENDED=1 -D_ALL_SOURCE as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking whether we need -std=c99 -D__EXTENSIONS__ -D_BSD_SOURCE
-D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600
-D_ALL_SOURCE as a flag for mips-montavista-linux-gnu-gcc -march=octeon
-msoft-float   -mabi=n32... no
checking whether we need -std=c99 as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking whether we need -D_BSD_SOURCE -D_DEFAULT_SOURCE as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking whether we need -D_GNU_SOURCE as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... yes
checking whether we need -D_GNU_SOURCE -D_FRSRESGID as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking whether we need -D_POSIX_C_SOURCE=200112 as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking whether we need -D__EXTENSIONS__ as a flag for
mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float   -mabi=n32... no
checking if mips-montavista-linux-gnu-gcc -march=octeon  -msoft-float
 -mabi=n32 supports -flto... no
checking for inline... inline
checking whether the C compiler (mips-montavista-linux-gnu-gcc
-march=octeon  -msoft-float   -mabi=n32) accepts the "format"

Re: unbound binaries execution issue

2018-03-05 Thread Paul Wouters via Unbound-users 

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/libunbound-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 binaries execution issue

2018-03-05 Thread SIMON BABY via Unbound-users 
Hi All,

 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/libunbound-1.6.8-r0/libunbound/unbound-1.6.8$
./unbound-host
./unbound-host: line 117:
/home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/.libs/lt-unbound-host:
cannot execute binary file
./unbound-host: line 117:
/home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/.libs/lt-unbound-host:
Success

sbaby@ubuntu:~/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8$
ls -ll unbound-anchor
-rwxr-xr-x 1 sbaby sbaby 9402 2018-03-05 15:25 unbound-anchor
sbaby@ubuntu:~/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8$
./unbound-anchor
./unbound-anchor: line 117:
/home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/.libs/lt-unbound-anchor:
cannot execute binary file
./unbound-anchor: line 117:
/home/sbaby/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8/.libs/lt-unbound-anchor:
Success
sbaby@ubuntu
:~/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8$




sbaby@ubuntu:~/workspace/wqar/tmp/work/mips-mv-linux/libunbound-1.6.8-r0/libunbound/unbound-1.6.8$
ls
acl_list.loautotrust.lo config.status  dnstree.lo
 iter_donotq.lolibunbound.lo  Makefile.innetevent.lo
 rbtree.o services timehist.o unbound-host
 val_nsec.lo
acl_list.o autotrust.o  config.sub dnstree.o
iter_donotq.o libunbound.o   malloc.lo  netevent.o
README   shm_main.lo  tube.lounbound-host.lo
val_nsec.o
aclocal.m4 ax_pthread.m4configure  doc
iter_fwd.lo   libworker.lo   malloc.o   net_help.lo
 reallocarray.lo  shm_main.o   tube.o unbound-host.o
 val_secalgo.lo
ac_pkg_swig.m4 cachedb  configure.ac   edns-subnet
iter_fwd.olibworker.omemcmp.lo  net_help.o
reallocarray.o   slabhash.lo  ub_event.lounbound.lo
 val_secalgo.o
acx_nlnetlabs.m4   cachedb.lo   context.lo explicit_bzero.lo
iter_hints.lo LICENSEmemcmp.o   outbound_list.lo
regional.lo  slabhash.o   ub_event.o unbound.o
val_sigcrypt.lo
acx_python.m4  cachedb.ocontext.o  explicit_bzero.o
 iter_hints.o  listen_dnsport.lo  mesh.looutbound_list.o
 regional.o   sldnsub_event_pluggable.lo  util
 val_sigcrypt.o
alloc.lo   cachedump.lo contribfptr_wlist.lo
iter_priv.lo  listen_dnsport.o   mesh.o outside_network.lo
remote.losmallapp ub_event_pluggable.o   val_anchor.lo
val_utils.lo
alloc.ocachedump.o  daemon fptr_wlist.o
 iter_priv.o   localzone.lo   mini_event.lo  outside_network.o
 remote.o stats.lo unboundval_anchor.o
 val_utils.o
arc4_lock.lo   compat   daemon.lo  getentropy_linux.lo
iter_resptype.lo  localzone.omini_event.o   packed_rrset.lo
 respip   stats.o  unbound-anchor validator
view.lo
arc4_lock.oconfig_file.lo   daemon.o   getentropy_linux.o
 iter_resptype.o   locks.lo   modstack.lopacked_rrset.o
respip.lostr2wire.lo  unbound-anchor.lo  validator.lo view.o
arc4random.lo  config_file.odname.lo   infra.lo
 iter_scrub.lo locks.omodstack.o parse.lo
respip.o str2wire.o   unbound-anchor.o   validator.o  winrc
arc4random.o   config.guess dname.oinfra.o
iter_scrub.o  log.lo module.lo  parse.o
 rrdef.lo strlcat.lo   unbound-checkconf  val_kcache.lo
winsock_event.lo
arc4random_uniform.lo  config.h dns64  install-sh
 iter_utils.lo log.o  module.o   parseutil.lo
rrdef.o  strlcat.ounbound-checkconf.lo   val_kcache.o
 winsock_event.o
arc4random_uniform.o   config.h.in  dns64.lo   ipsecmod
 iter_utils.o  lookup3.lo msgencode.lo   parseutil.o
 rrset.lo strlcpy.lo   unbound-checkconf.oval_kentry.lo
wire2str.lo
as112.lo   configlexer.lo   dns64.oiterator
 keyraw.lo lookup3.o  msgencode.opatches
 rrset.o  strlcpy.ounbound-controlval_kentry.o
 wire2str.o
as112.oconfiglexer.odnscrypt   iterator.lo
keyraw.o  lruhash.lo msgparse.lopythonmod
 rtt.lo   systemd.m4   unbound-control.lo val_neg.lo
 worker_cb.lo
authzone.loconfig.log   dns.lo iterator.o
 libtool   lruhash.o  msgparse.o random.lo
 rtt.otestcode