The Link SAP specifies an abstract media dependent interface between the MIHF and lower layers media-specific protocol stacks of technologies such as IEEE 802.3, IEEE 802.11, IEEE 802.16, 3GPP and 3GPP2.
The provided ICMP Link SAP implementation is very simple and it can only detect the attachment of a new node using the ICMP protocol.
MIH Link SAP Configuration: --help Display configuration options --conf.file arg (=link_sap.conf) Configuration file --conf.recv_buff_len arg (=4096) Receive buffer length --link.id arg (=link) Link SAP ID --link.port arg (=1235) Listening Port --link.tec arg Technology type --link.link_addr arg Interface address --link.event_list arg List of supported events --link.command_list arg List of supported commands --mihf.ip arg (=127.0.0.1) Local MIHF IP --mihf.id arg (=local-mihf) Local MIHF ID --mihf.local_port arg (=1025) Local MIHF communication port
Note | |
---|---|
All configurable parameters are self-explained and, therefore, we will only mention those that are more complex to configure. Technology type: Network interface card technology. Supported values: GSM, GPRS, EDGE, 802.3, Other, 802_11, CDMA2000, UMTS, CDMA2000-HRPD, 802_16, 802_20, 802_22. Usage: tec = <NIC technology> Interface Address: Network interface card address. Usage: link_addr = <interface address> List of supported events: Comma separated list of the Link SAP's supported events. Usage: event_list = <link event 1>, <link event 2>, (...), <link event N> List of supported events: Comma separated list of the Link SAP's supported commands. Usage: command_list = <link command 1>, <link command 2>, (...), <link command N> |
The Link SAP can be configured based on a set of parameters, which can be configured either using an configuration file or passing them directly in the command line.
Before running the Link SAP, the local MIHF should already be running. Otherwise, the Link SAP will try to register with a non-exitent MIHF.
Now you can trigger some events by attaching another node to the device.