Border agent port conflicts with application port #11280
Unanswered
sarveshkumarv3
asked this question in
Q&A
Replies: 1 comment
-
@sarveshkumarv3 , it would be very helpful if you could provide both logs and pcaps. Are you able to reproduce this in any way? The Border Router should only receive packets with an IPv6 Destination Address that is assigned to one of its network interfaces. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug A clear and concise description of what the bug is.
When border agent port collides with the application port (used by Matter stack on another device), the packets are not routed to the intended destination. Can BA port be a standard IANA assigned port similar to MLE port?
Scenario
Device1 (matter stack, source of packet) -> Device 2 (Border Agent) -> Device 3 (matter stack, destination)
When device 1 picks the source port which collides with the BA port, the response from device 3 is not routed back to device 1 .
To Reproduce Information to reproduce the behavior, including:
Git commit id
IEEE 802.15.4 hardware platform
Build steps
Network topology
Expected behavior A clear and concise description of what you expected to happen.
Expected the packets to be routed to the Device 1 matter stack and not the Device 2 Border Agent
Console/log output If applicable, add console/log output to help explain your problem.
Unfortunately I couldn't get logs for this scenario
Additional context Add any other context about the problem here.
NA
Beta Was this translation helpful? Give feedback.
All reactions