Closed ihidchaos closed 4 years ago
I don't know the details, but the key line seems to be TunnelIPv6Interface: Couldn't get tunnel name! errno=77, File descriptor in bad state
This is where the wpan
TUN interface is being created and system fails to get its name.
Quick things to check: Are you running as sudo
?
On OpenWrt, otbr-agent is managing the tun device. So I don't think you can run wpantund and otbr-agent together. Actually, we have two solutions: wpantund + NCP + otbr-agent(use the wpantund/master branch of ot-br-posix), and otbr-agent + RCP. The latter solution is now preferred and supported on OpenWrt, in which the CLI tool is ot-ctl.
On OpenWrt, otbr-agent is managing the tun device. So I don't think you can run wpantund and otbr-agent together. Actually, we have two solutions: wpantund + NCP + otbr-agent(use the wpantund/master branch of ot-br-posix), and otbr-agent + RCP. The latter solution is now preferred and supported on OpenWrt, in which the CLI tool is ot-ctl.
Yes, when I stop oybr-agent, wpantund can start normally and wpanctl can also be used. thank you!
Describe the bug I compiled openwrt on the Raspberry Pi, integrated ot-br-posix and wpantund. Now otbr-agent runs successfully, but wpantund cannot start. I want to know how to use wpantund on openwrt,thanks.
To Reproduce Information to reproduce the behavior, including:
Expected behavior A clear and concise description of what you expected to happen.
Console/log output
Additional context wpantund.conf use
Config:NCP:SocketPath "serial:/dev/ttyACM0,raw,b115200,crtscts=1"