# Dynamically drop TCP/IP connection between 2 nodes

**URL:** https://discourse.nodered.org/t/dynamically-drop-tcp-ip-connection-between-2-nodes/92400
**Category:** General
**Created:** [15 October 2024 08:47 UTC](https://discourse.nodered.org/t/dynamically-drop-tcp-ip-connection-between-2-nodes/92400 "2024-10-15T08:47:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [15 October 2024 09:38 UTC](https://discourse.nodered.org/t/dynamically-drop-tcp-ip-connection-between-2-nodes/92400/2 "2024-10-15T09:38:53Z")

</div>

As I [understand](https://discourse.nodered.org/t/dynamically-disable-individual-nodes/92396/30) you really just want to be able to deactivate the tcp _listener_ not the tcp out. So being able to _dynamically_ disable the tcp in node would be what you're looking for.

The [msg.reset](https://github.com/node-red/node-red/blob/2854351909dee9f92597faba3f37239134294eec/packages/node_modules/%40node-red/nodes/core/network/31-tcpin.js#L414-L416) is a feature of the tcp out node to _dynamically_ close a _connected_ tcp client.

What I understand you need is to prevent tcp clients from connecting to the tcp in node which means dynamically turning off the tcp in node, i.e., the underlying tcp listener.

That is not possible because the tcp in node does not take any input messages that control its behaviour, therefore there is no way to send it a message to the tcp in node to stop listening for new connections.

---

_[View the full topic](https://discourse.nodered.org/t/dynamically-drop-tcp-ip-connection-between-2-nodes/92400)._