k.rennerandClaude Opus 4.7
85b8d2acb1
Default kernel `accept_ra_rt_info_max_plen=0` drops every RA route-info entry. OTBR advertises the Thread OMR prefix (fd5f:…/64) to v30iot as an RIO, so matter-server's net1 silently rejected it and had no route to Thread devices — CASE sessions hit UDP retransmission timeouts despite mDNS discovery succeeding. Add an initContainer with NET_ADMIN that bumps the limit to 64 on net1/all/default before the main container starts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>