imported>OCDoc Import: Imported from legacy OpenComputers documentation at ocdoc.cil.li

2026-08-24T08:08:27Z

Imported from legacy OpenComputers documentation at ocdoc.cil.li

New page

= Component: Tunnel =

This component is provided by the [[Item/linked card|linked card]].

This card is similar to the [[Component/modem|network card's component]], but as it is only point-to-point, no ports can be configured, and the connection is always open.

Component name: `tunnel`. Callbacks:

* `send(data...)`

<pre>Sends the specified data to the card this one is linked to.
</pre>
* `maxPacketSize():number`

<pre>Gets the maximum packet size (config setting).
</pre>
* `getChannel():string`

<pre>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.
</pre>
* `getWakeMessage():string`

<pre>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.
</pre>
* `setWakeMessage(message: string, [fuzzy: boolean]):string`

<pre>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.
</pre>
== This card generates `modem_message` signals of the same format network cards do. ==

{{:Component/contents}}

Component/tunnel - Revision history

imported>OCDoc Import: Imported from legacy OpenComputers documentation at ocdoc.cil.li