Simon Lin

I think we can fix it by one these solutions: 1. Parse the IP6 header in `processTransmit` of `posix/platform/netif.cpp` and skip such messages 2. Ip6::SendRaw drop multicast packets with link...

@librasungirl @jwhui I think option 1 should be the simplest way to go. Configuring it to be like 10 seconds should be more suitable for most home networks. For option...

@IHIDCHAOS Thanks for the info. I think we need to support reset no matter `otbr-agent` is using `ubus` or `dbus` or none. Per my understanding, otbr-agent tries to avoid **real**...

One hint is that the DUA prefix `fd00:7d03:7d03:7d03::/64` should not be added as routes. Instead, `fd00:7d03:7d03:7d03::/64` should be advertised as a on-link prefix, usually by [radvd](https://radvd.litech.org/). For example, we are...

> Our OTBR container is configured with a custom virtual bridge otbr0. We don't pass --net=host for our containers. We are using the same architecture for Backbone Router tests in...

> @simonlingoogle Thanks for the information. I have a couple more questions about your configuration if you don't mind. > > > > 1. When you are setting up your...

I suspect that the issue is due to a wrong docker image. The `otbr:latest` image does not have complete Thread 1.2 features because it's basically for testing Thread 1.3 features....

> My OTBR container is using a docker bridge network otbr0 (created in step 2 above). So I have to perform step 5 (route add) to inform my host that...

`BORDER_ROUTING` feature creates an ICMPv6 socket to receive and process RS/RA messages. However, it does not receive or process NS/NA packets. And the Host should not be running `BORDER_ROUTING`, anyway....

should we create another ticket for the new ping issue? for this host issue, we may still need to fix some thci scripts.