Re: Dynamic routing table - dropping service

Jonathan Hui

unread,

Apr 6, 2022, 2:13:33 PM4/6/22

to Michał Poterek, openthread-users

Thread Border Routers will send ICMPv6 Router Advertisement messages with a Route Information Option (RIO) that advertises a route to the Thread network (in your case fd27:fb0c:165:18df::/64). This allows hosts on the Wi-Fi network to know how to route packets to the Thread network.

Assuming that both the eero and your BeagleBone are operating in the same Thread network, it should not matter which border router the ICMPv6 Echo Request goes through.

Are you able to ping your Thread device(s) through the eero router when your BeagleBone is disabled?

--

Jonathan Hui

On Tue, Apr 5, 2022 at 5:17 PM Michał Poterek <superv...@gmail.com> wrote:

With below commands I found out that fe80::58ce:25df:5c8d:6341 is belonging to ETH interface of EERO wifi router which providing as well Thread network ant its connected to the same switch which BeagleBone is.
Any idea how to avoid situation where route fd27:fb0c:165:18df::/64 fe80::58ce:25df:5c8d:6341 UG 100 2 eth0 is created automatically?

root@beaglebone:/home/c# nmap -6 fe80::58ce:25df:5c8d:6341
Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-06 00:05 UTC
Nmap scan report for fe80::58ce:25df:5c8d:6341
Host is up (0.00042s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
53/tcp open domain
3001/tcp open nessus
10001/tcp open scp-config
MAC Address: 80:B9:7A:D8:F6:F2 (Unknown)

EERO router (192.168.1.100) at 80:b9:7a:d8:f6:f2 [ether] on eth0

środa, 6 kwietnia 2022 o 01:58:04 UTC+2 Michał Poterek napisał(a):
I dont know to which interface this address belong to fe80::58ce:25df:5c8d:6341
root@beaglebone:/home/c# ping fe80::58ce:25df:5c8d:6341
PING fe80::58ce:25df:5c8d:6341(fe80::58ce:25df:5c8d:6341) 56 data bytes
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=1 ttl=64 time=0.621 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=2 ttl=64 time=0.462 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=3 ttl=64 time=0.487 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=4 ttl=64 time=0.481 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=5 ttl=64 time=0.492 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=6 ttl=64 time=0.502 ms
64 bytes from fe80::58ce:25df:5c8d:6341%eth0: icmp_seq=7 ttl=64 time=0.482 ms

root@beaglebone:/home/c# ip -6 add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 fd36:fef4:77fd:0:3cf2:c4cf:f3ee:c419/64 scope global dynamic noprefixroute
valid_lft 1761sec preferred_lft 1761sec
inet6 fe80::f61d:8bfd:d972:618a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: nat64: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 state UP qlen 500
inet6 fdaa:bb:1::2/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::f083:9f0c:ce2a:3db2/64 scope link stable-privacy
valid_lft forever preferred_lft forever
7: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 state UNKNOWN qlen 500
inet6 fdde:ad11:11de::ff:fe00:fc11/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdde:ad11:11de::ff:fe00:fc38/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdde:ad11:11de::ff:fe00:fc10/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdde:ad11:11de::ff:fe00:7800/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fd27:fb0c:165:18df:f1b1:ed78:f110:70/64 scope global nodad
valid_lft forever preferred_lft forever
inet6 fdde:ad11:11de:0:87c6:20d1:deb1:4977/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fe80::d0b0:5f8e:f635:342f/64 scope link nodad
valid_lft forever preferred_lft forever

ot-ctl
> ipaddr
fdde:ad11:11de:0:0:ff:fe00:fc11
fdde:ad11:11de:0:0:ff:fe00:fc38
fdde:ad11:11de:0:0:ff:fe00:fc10
fdde:ad11:11de:0:0:ff:fe00:7800

fd27:fb0c:165:18df:f1b1:ed78:f110:70
fdde:ad11:11de:0:87c6:20d1:deb1:4977
fe80:0:0:0:d0b0:5f8e:f635:342f
Done

środa, 6 kwietnia 2022 o 01:36:54 UTC+2 Michał Poterek napisał(a):
thats might be helpful for analysis

root@beaglebone:/home/c# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.243 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fd36:fef4:77fd:0:3cf2:c4cf:f3ee:c419 prefixlen 64 scopeid 0x0<global>
inet6 fe80::f61d:8bfd:d972:618a prefixlen 64 scopeid 0x20<link>
ether 40:2e:71:d9:1a:04 txqueuelen 1000 (Ethernet)
RX packets 22926 bytes 3541201 (3.3 MiB)
RX errors 0 dropped 601 overruns 0 frame 0
TX packets 13466 bytes 7867903 (7.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 54

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 91 bytes 12940 (12.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 91 bytes 12940 (12.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

nat64: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 192.168.255.1 netmask 255.255.255.255 destination 192.168.255.1
inet6 fe80::f083:9f0c:ce2a:3db2 prefixlen 64 scopeid 0x20<link>
inet6 fdaa:bb:1::2 prefixlen 128 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 20 bytes 1880 (1.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 24 bytes 2184 (2.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wpan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1280
inet6 fdde:ad11:11de::ff:fe00:7800 prefixlen 64 scopeid 0x0<global>
inet6 fd27:fb0c:165:18df:f1b1:ed78:f110:70 prefixlen 64 scopeid 0x0<global>
inet6 fdde:ad11:11de::ff:fe00:fc38 prefixlen 64 scopeid 0x0<global>
inet6 fdde:ad11:11de::ff:fe00:fc11 prefixlen 64 scopeid 0x0<global>
inet6 fdde:ad11:11de:0:87c6:20d1:deb1:4977 prefixlen 64 scopeid 0x0<global>
inet6 fe80::d0b0:5f8e:f635:342f prefixlen 64 scopeid 0x20<link>
inet6 fdde:ad11:11de::ff:fe00:fc10 prefixlen 64 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 146 bytes 15293 (14.9 KiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 195 bytes 22305 (21.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

środa, 6 kwietnia 2022 o 01:14:44 UTC+2 Michał Poterek napisał(a):
I'm built BeagleBone Border Router based on the latest OpenThread working with RCP CC1352 (recently I received compiled firmware for RCP from TI to tests).

I'm using Node-Red COAP communication to end devices. Recently I installed Cacti to monitor ICMP responses from EndDevices and I notice that sometimes I loosing communication for something like 30 seconds.

I found that it's related to the route -6 table.
When I ping -I wpan 0 fd27:fb0c:165:18df:e225:5320:b718:24e6 I haven't dropouts at all.
When I ping fd27:fb0c:165:18df:e225:5320:b718:24e6 I have dropouts from time to time even like 30 second.

Below you can find route -6 tables. Something adding red line automatically and when this route is added then I loosing communication if I use ping fd27:fb0c:165:18df:e225:5320:b718:24e6 but ping -I wpan 0 fd27:fb0c:165:18df:e225:5320:b718:24e6 can still run at that time.

I will be appreciated for ideas how to solve this issue.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/404e3103-ae7b-43b0-8799-f4e837de4bd5n%40googlegroups.com.

Michał Poterek

unread,

Apr 6, 2022, 7:04:05 PM4/6/22

to openthread-users

Hi, I'm able to ping End Device from windows PC when BeagleBone is off.

ping fd27:fb0c:165:18df:e225:5320:b718:24e6 -t
Pinging fd27:fb0c:165:18df:e225:5320:b718:24e6 with 32 bytes of data:
Reply from fd27:fb0c:165:18df:e225:5320:b718:24e6: time=69ms
Reply from fd27:fb0c:165:18df:e225:5320:b718:24e6: time=46ms
Reply from fd27:fb0c:165:18df:e225:5320:b718:24e6: time=44ms

Below is my routing table on windows machine

C:\Users\micha>route PRINt -6
===========================================================================
Interface List
3...d8 bb c1 72 b0 bd ......Killer E3100G 2.5 Gigabit Ethernet Controller
12...00 e0 4c 68 02 66 ......Realtek USB GbE Family Controller #2
45...00 15 5d 6f 67 1a ......Hyper-V Virtual Ethernet Adapter
24...2c 8d b1 d9 77 be ......Microsoft Wi-Fi Direct Virtual Adapter #3
23...2e 8d b1 d9 77 bd ......Microsoft Wi-Fi Direct Virtual Adapter #4
10...2c 8d b1 d9 77 bd ......Killer(R) Wi-Fi 6E AX1675x 160MHz Wireless Network Adapter (210NGW) #2
13...2c 8d b1 d9 77 c1 ......Bluetooth Device (Personal Area Network) #2
1...........................Software Loopback Interface 1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
10 291 ::/0 fe80::58ce:25df:5c8d:6341
10 291 ::/0 fe80::b88b:10a9:e798:c8d5
1 331 ::1/128 On-link
10 291 fd27:fb0c:165:18df::/64 fe80::f61d:8bfd:d972:618a
10 291 fd27:fb0c:165:18df::/64 fe80::e841:480e:883f:72e9
10 291 fd27:fb0c:165:18df::/64 fe80::b88b:10a9:e798:c8d5
10 291 fd27:fb0c:165:18df::/64 fe80::58ce:25df:5c8d:6341
10 291 fd69:438e:c4b6:1::/64 On-link
10 291 fd69:438e:c4b6:1:7d18:dae0:1b59:bfc4/128
On-link
10 291 fd69:438e:c4b6:1:ec4d:fac4:6a05:be50/128
On-link
10 291 fdfc:5753:8911::/64 On-link
10 291 fe80::/64 On-link
45 271 fe80::/64 On-link
10 291 fe80::7d18:dae0:1b59:bfc4/128
On-link
45 271 fe80::d1af:13f3:639c:f348/128
On-link
1 331 ff00::/8 On-link
10 291 ff00::/8 On-link
45 271 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

Jonathan Hui

unread,

Apr 7, 2022, 1:47:33 PM4/7/22

to Michał Poterek, openthread-users

When sending an ICMPv6 Echo Request from the BeagleBone when there is a route to eero, what is the IPv6 Source Address? Is it possible for you to provide a pcap file?

--

Jonathan Hui

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/cfcd17ff-cacf-45ff-99d2-45a31a4e04e8n%40googlegroups.com.

Reply all

Reply to author

Forward