can not ping from OTBR to MTD #8757
-
Describe the bug A clear and concise description of what the bug is.
check the route table
after remove the following rule and the system
Below is some log information about the OTBR process,
I don't know why this happened. I can't found the following rule in other test environment,
To Reproduce Information to reproduce the behavior, including:
Expected behavior A clear and concise description of what you expected to happen. Console/log output If applicable, add console/log output to help explain your problem. Additional context Add any other context about the problem here. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
Is it related to whether the router the OTBR connects to has access to the global IPv6 network? |
Beta Was this translation helpful? Give feedback.
-
The problem is that you have routes to Are you manually configuring the This could happen if you have another border router that is using the same |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
The problem is that you have routes to
fd11:22::/64
going out theeth0
interface, rather thanwpan0
interface. This can cause the error you see withping
command.Are you manually configuring the
fd11:22::/64
prefix anywhere? Typically, unique local addresses should have more randomness than that.This could happen if you have another border router that is using the same
fd11:22::/64
prefix, which it would advertise using ICMPv6 Router Advertisements and cause the route to be installed viaeth0
interface.