Hi everyone,
I’m trying to run my ConBee 2 as an OpenThread Border Router via Docker, but I’m running into issues. After flashing with GCFFlasher, the otbr-agent fails to start properly.
What I did:
- Flashed ConBee 2:
GCFFlasher_internal -d /dev/ttyACM0 -t 60 -f ot-rcp-cb2_0x01010700.GCF
- Configured
otbr-env.list:
# Adjust otbr-env.list
OT_RCP_DEVICE=spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
# IMPORTANT: Use wlp1s0 instead of wlan0/eth0
OT_INFRA_IF=wlp1s0 # Your Wi-Fi interface
OT_THREAD_IF=wpan0
# Log level
OT_LOG_LEVEL=7
# Optional WLAN optimizations
OT_BACKBONE_ROUTER=1
OT_NAT64=1
- Started Docker:
docker run --name=otbr --detach --network=host --cap-add=NET_ADMIN \
--device=/dev/ttyACM0 --device=/dev/net/tun \
--volume=/var/lib/otbr:/data --env-file=otbr-env.list \
--restart=always openthread/border-router
Problem:
When checking the logs (docker logs otbr -f), I repeatedly get errors like:
iptables v1.8.10 (nf_tables): interface name `wlp1s0 # Dein WLAN-Interface' must be shorter than IFNAMSIZ (15)
...
P-Trel--------: Failed to bind socket to the interface wlp1s0 # De
Platform------: PrepareSocket() at trel.cpp:215: No such device
otbr-agent exited with code 5 (by signal 0)
Additionally, it seems communication with the co-processor is failing:
P-SpinelDrive-: Waiting response: key=1
P-SpinelDrive-: Wait for response timeout
Platform------: Init() at spinel_driver.cpp:87: Failure
otbr-agent exited with code 1 (by signal 0)
Questions:
- Could the issue be my Wi-Fi interface (
OT_INFRA_IF)? I left it as in the example, including the comment. - Is the co-processor reset / Spinel timeout normal after flashing, or did I flash something incorrectly?
- Are there known Docker settings on Linux that make
otbr-agentrun stable?
Any tips or guidance to get my ConBee 2 working again would be much appreciated.
Thanks in advance!