net: setKeepAlive options ignored before connect #31663

Activity

1. targos

   added

   netIssues and PRs related to the net subsystem.Issues and PRs related to the net subsystem.

   on Dec 26, 2020
2. pmarrapese commented on Jan 28, 2021

   

   pmarrapese

   on Jan 28, 2021

   More actions

   • Version: v14.15.4
   • Platform: Windows [Version 10.0.17763.1637]

   Confirmed this still behaves this way. In this example, Wireshark shows the first keepalive packet going out 60 seconds after the connection is established.

   const net = require('net');
   
   let socket = net.createConnection({
    host: 'localhost',
    port: 31337
   });
   socket.setKeepAlive(true, 1000);
   socket.on('connect', () => {
    console.log('socket is connected');
   });

   Moving the setKeepAlive call into the connect handler causes them to go out every 1s, as intended. If there is no intention to modify this behavior, this should at least be noted in the documentation.
3. oyyd commented on Jun 30, 2022

   

   oyyd

   on Jun 30, 2022

   Contributor

   More actions

   Looks like this has been solved in #41310.
4. github-actions commented on Jun 27, 2026

   

   github-actionsbot

   on Jun 27, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been marked as stale due to 210 days of inactivity.
   It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
5. github-actions

   added

   staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

   on Jun 27, 2026
6. github-actions commented on Jul 28, 2026

   

   github-actionsbot

   on Jul 28, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
   If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
7. github-actions

   closed this as not plannedon Jul 28, 2026