Page History

...

• Make sure we have wpan0 interface up
• brlan0 should be up and running
• who creates wpan0
  • otbr-agent
  • More technical explanation
    • Initial OTBR-agent startup:
      • OTBR-agent process starts
      • At this point, no wpan0 interface exists yet
      • No socket exists yet at /run/openthread-wpan0.sock
    • OTBR-agent creates socket:
      • Creates Unix domain socket at /run/openthread-wpan0.sock
      • This socket will be used for IPC/control operations
    • OTBR-agent creates network interface:
      • Creates the wpan0 network interface
      • Takes ownership of managing this interface
    • Runtime dependencies:
      • The wpan0 interface is ONLY available while OTBR-agent is running
      • If OTBR-agent stops, the wpan0 interface goes away
      • Other services/processes should not expect wpan0 to exist without OTBR-agent running
    • Communication flow:
      • Other processes can communicate with OTBR-agent through the socket at /run/openthread-wpan0.sock
      • Network traffic goes through the wpan0 interface managed by OTBR-agent
  • Can i assume that the above mentioned kernel config to be enabled,if so why
    • 1. CONFIG_TUN=y
         • Required since OTBR-agent creates the wpan0 network interface
         • The TUN/TAP driver support enables creation of virtual network interfaces
         • Without this, OTBR-agent wouldn't be able to create the wpan0 interface
      2. CONFIG_IEEE802154=y
         • Required as the base IEEE 802.15.4 protocol support
         • Provides the fundamental IEEE 802.15.4 networking stack
         • OTBR-agent uses this for Thread networking which runs on 802.15.4
      3. CONFIG_MAC802154=y
         • Required for MAC layer operations of IEEE 802.15.4
         • Handles MAC layer functionality like addressing and frame formatting
         • OTBR-agent relies on this for proper 802.15.4 packet handling

      Without these kernel configurations:

      • The wpan0 interface creation would fail
      • The IEEE 802.15.4 networking stack wouldn't be available
      • The MAC layer operations for Thread networking wouldn't work