-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multicast forwarding (TZ-410) #42
Comments
Could you please set this command to BR and to see the BBR is enabled or not?
|
after enabling bbr, the multicast forwarding works now. thanks |
Could you please enlarge the configuration to (Top) → Component config → mDNS → (16) Maximum actions pending to the server |
Also you need to set the |
I guess you want to try the multicast forwarding feature of the ESP BR, so you need to try like the previous comment. But if you just want to let the BR join the multicast listenning group on the WiFi netif and ping the BR from host, you can just use the lwip address adding command like this |
Yes, for the linux host, I think you can have try with set the
Tips: As for the interface name you can obtain it using the command |
thanks a lot, with the ttl setting everything finalling works. Thanks |
Great! Actually, in our docs, we have already recommend to set the ttl |
Hi, during testing the basic_thread_boarder_router exsample, i was stucked doing the multicast forwarding codelab,
after using mcast commond, my esp32boarder router and other 2 esp32h2 FTD all joined ff04::123 multicast group
but when try to ping ff04::123 address from outside windows machine it doesn't response (the windwos route table seems alright, and ping each FTD with there ULA address works)
can i ask am i missing any config steps to make this work? Should i add some code to register the netif: en interface to the multicast group as well? (i guess my esp32 boarder router didn't receive the ff04::123 address multicast data because it didn't register it in the outside network?)
The text was updated successfully, but these errors were encountered: