Doubts regarding using 2 Border Router in a Single Thread Network

[Rohith R]

1. When we use 2 Border Routers in a single Thread Network. What all are the things to be taken care  off?(Planning a Back up Border Router in Design)

2. When I tried to ping Border Router(RCP) from my laptop it was not happening. What could be the reason

3.Is it mandatory RCP to be leader (RCP connected to Border Router)for communicate a device in a Thread network from  External Network

Commit ID: 17cdb3bad795db87bfcd2c272366ab5a4f270ffc

[Jonathan Hui]

On Thu, Aug 12, 2021 at 6:36 AM Rohith R <rohith...@gmail.com> wrote:

1. When we use 2 Border Routers in a single Thread Network. What all are the things to be taken care  off?(Planning a Back up Border Router in Design)

You shouldn't need to do anything. The two border routers should coexist on the network.

2. When I tried to ping Border Router(RCP) from my laptop it was not happening. What could be the reason

Can you provide more details? What IPv6 address are you trying to ping?

3.Is it mandatory RCP to be leader (RCP connected to Border Router)for communicate a device in a Thread network from  External Network

No, the border router may operate as a child, router, or leader.

Note that the RCP only implements the 802.15.4 PHY and lower MAC layers. The higher layers are implemented on the host side separate from the RCP.

--

Jonathan Hui

[Rohith R]

    Can you provide more details? What IPv6 address are you trying to ping?

     I have used the Global Unicast Address of each thread device to ping from my laptop.(Laptop and Border router are in the same network). I have used the following Address in the Bold.

   Leader IP: 

   fdb8:5419:9d1b:13f5:39f5:1af5:1531:68ee

    fd50:886a:c6e6:8d1d:0:ff:fe00:fc00

   fd50:886a:c6e6:8d1d:0:ff:fe00:a800

   fd50:886a:c6e6:8d1d:ace9:6ee5:d1fb:74d7

   fe80:0:0:0:c839:8fca:5ee9:b745

Router IP:

  fd50:886a:c6e6:8d1d:0:ff:fe00:fc11

  fd50:886a:c6e6:8d1d:0:ff:fe00:fc38

  fdb8:5419:9d1b:13f5:bc20:9593:6b6e:e223

  fd50:886a:c6e6:8d1d:0:ff:fe00:fc10

  fd50:886a:c6e6:8d1d:0:ff:fe00:6800

  fd50:886a:c6e6:8d1d:f6c:5877:bb3e:9a38

  fe80:0:0:0:98c9:aeb5:90fd:6ce1

Child IP:

  fdb8:5419:9d1b:13f5:f5eb:c1b4:d4ec:80b6

  fd50:886a:c6e6:8d1d:0:ff:fe00:a802

  fd50:886a:c6e6:8d1d:1918:6237:7a40:f15f

  fe80:0:0:0:94cc:6c3a:2351:5409

One of my doubts are

1. Will  GUA  changes, when Leader Border Router changes? (In our case with two Border Routers as leader and Router, when we disconnected the leader border router GUA of Child changed.  )

2. If GUA changes, how can we communicate with a device in the Thread network from outside

3. Pinging  within the Thread Interfaces occurs sometimes and sometimes not. What will be the reason

   

[Jonathan Hui]

On Fri, Aug 13, 2021 at 3:31 AM Rohith R <rohith...@gmail.com> wrote:

One of my doubts are

1. Will  GUA  changes, when Leader Border Router changes? (In our case with two Border Routers as leader and Router, when we disconnected the leader border router GUA of Child changed.  )

Each border router locally generates its own Off Mesh Routable (OMR) prefix. If the border router currently advertising the OMR prefix goes away, the new border router will use a different OMR prefix.

 

2. If GUA changes, how can we communicate with a device in the Thread network from outside

You will need a mechanism to discover the new IPv6 address. DNS-based Service Discovery is one way to discover the current IPv6 address for a given service.

 

3. Pinging  within the Thread Interfaces occurs sometimes and sometimes not. What will be the reason

Without more visibility into your scenario, it is difficult to pinpoint a specific reason. For example, one possibility is the host does not have a route to the OMR prefix. Another possibility is the Border Router does not have a route to the given Thread device.

--

Jonathan Hui