This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
component:tunnel [2014/07/10 12:02] sangar created |
component:tunnel [2018/10/12 23:40] (current) payonel |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Component: Tunnel | ||
+ | ================ | ||
This component is provided by the [[item:linked_card|linked card]]. | This component is provided by the [[item:linked_card|linked card]]. | ||
Line 10: | Line 12: | ||
- `maxPacketSize():number` | - `maxPacketSize():number` | ||
Gets the maximum packet size (config setting). | Gets the maximum packet size (config setting). | ||
+ | - `getChannel():string` | ||
+ | Gets the tunnel address of the link card. This is also available in `linkChannel` using an inventory controller and getting the stack from an inventory slot. | ||
+ | - `getWakeMessage():string` | ||
+ | Gets the current wake-up message. When the network card detects the wake message (a string in the first argument of a network packet), on any port and the machine is off, the machine is started. This is the same functionality also provided by robots, cases, servers, drones, and tablets. | ||
+ | - `setWakeMessage(message: string, [fuzzy: boolean]):string` | ||
+ | Sets the wake-up message to the specified **string**. The message matching can be fuzzy (default is false). A fuzzy match ignores additional trailing arguments in the network packet. | ||
This card generates `modem_message` signals of the same format network cards do. | This card generates `modem_message` signals of the same format network cards do. |