dnsmasq in border router error

[Edward]

I'm trying the example border router using 2 x nRF52840 boards one with CLI and the other with NCP connected to a PI. I can get ipv6 addresses and get them to ping each other but can't get a 2001 ip address (no internet connectivity). Looking at the system log for Openwrt I see the router fails to start the dnsmasq service with the error 'failed to create listening socket for port 53: Address in use'. So there is a conflict on port 53 between bind named which has already started and dnsmasq. How do I fix this?

[Edward]

I get this from dns resolve

dns resolve ipv4.google.com fd00:0064:0123:4567::1

DNS response for ipv4.google.com - Error 30: ResponseTimeout

and this from ifconfig on BR eth0 Link encap:Ethernet HWaddr B8:27:EB:5E:13:8E
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fe5e:138e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30075 errors:0 dropped:17728 overruns:0 frame:0 TX packets:669 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6333320 (6.0 MiB) TX bytes:89924 (87.8 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:17197 errors:0 dropped:0 overruns:0 frame:0 TX packets:17197 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:1374961 (1.3 MiB) TX bytes:1374961 (1.3 MiB)

tayga-nat64 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.64.1 P-t-P:192.168.64.1 Mask:255.255.255.255 inet6 addr: fd00:64:123:4567::1/128 Scope:Global inet6 addr: fd00:64:123::/64 Scope:Global inet6 addr: fd00:64:123::1/128 Scope:Global UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:76 (76.0 B)

wlan0 Link encap:Ethernet HWaddr B8:27:EB:0B:46:DB
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fe0b:46db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1400 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:986 (986.0 B)

From PI ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=45.5 ms

From CLI

ping fd00:0064:0123:4567::0808:0808

ipaddr

fdde:ad00:beef:0:0:ff:fe00:3400

fe80:0:0:0:10aa:3eb:55b3:7ab7

fdde:ad00:beef:0:af6e:c9d3:6ab5:d060

Done

You are correct the cable from the RPi to the NCP was faulty so now I can ping fd00:0064:0123:4567::0808:0808 from a node. But the RPi seems a bit flaky in starting wpantund.

Thank you Piotr

Maybe wpantund is a bit slow in starting, I'll see how it goes and again many thanks for resolving this.

[Piotr Szkotak]

I'm happy to see that it is working now. What do you mean by "flaky"? If you have some delay on mind it is expected as we need to have the OS fully booted, perform initial setup and then start the wpantund daemon itself.