If the network cable is unpluged, openthread clean thread network route/SRP information. Should it be OK from design?

[wallaceL]

If the network cable is unpluged, openthread clean thread network route/SRP information. Should it be OK from the design?

[jwhui]

The OpenThread routing manager will handle state changes on the infrastructure interface:

openthread/src/core/border_router/infra_if.cpp

Line 114 in dd631b2

Error InfraIf::HandleStateChanged(uint32_t aIfIndex, bool aIsRunning)

However, OpenThread does not currently clear the SRP server state when the border router role is disabled. This is intentional, since the device may choose to offer an SRP server even when there is no infrastructure link. This allows supporting DNS-SD in isolated Thread networks.

However, I could see some benefit to offering a mode that automatically disables SRP server when BR role is disabled.

[wallaceL]

understand, border routing manager is stopped. If I want to communicate with the device in thread mesh in this case, what should I do?

[jwhui]

Thread devices in the same mesh network can continue to communicate using mesh-local addresses.

[wallaceL]

mesh local address of the devices is not in SRP, and how do I get the mesh local address of device?

[jwhui]

SRP Client configuration allows specifying a list of IPv6 addresses or automatically picking the most appropriate address - see src/cli/README_SRP_CLIENT.md for more details.

[abtink]

However, I could see some benefit to offering a mode that automatically disables SRP server when BR role is disabled.

I agree. I think this would be useful in some situations.
I can later add a mechanism (new API or config) to auto enable/disable SRP server along BR (RoutingManager) functionality