From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84200C433ED for ; Sun, 16 May 2021 23:20:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 54DAA61073 for ; Sun, 16 May 2021 23:20:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234612AbhEPXWH (ORCPT ); Sun, 16 May 2021 19:22:07 -0400 Received: from mail-40135.protonmail.ch ([185.70.40.135]:20809 "EHLO mail-40135.protonmail.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233677AbhEPXWF (ORCPT ); Sun, 16 May 2021 19:22:05 -0400 Date: Sun, 16 May 2021 23:20:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1621207248; bh=o9NUnpWwWPmYQ+iKKyofsmuL+q/XvnMFtWtsza/uW30=; h=Date:From:Cc:Reply-To:Subject:From; b=bQpi9TG4ZMfr03jIujOUYkipkR4H2JvI/JsWnnbiLa2bmPy20REdDsKhlTjysb1ht l6PpZKe113wjw+n/om0YriBP3U083wQH9u2PITchSDW57K4a7LNaL61Y4eYYA6yp+N Wb4eZJlhKARyhfWWTREv2kQpkMU+mHl+uMNn5byw= From: louisrossberg Cc: "linux-kernel@vger.kernel.org" Reply-To: louisrossberg Subject: Listening on a TCP socket from a Kernel Module Message-ID: <5J_z4QNPMBAk4y0rGshI7mBykT1tivh3037CbQRYXTu_Ra6zuojEcI0RB04ghXQxgdtDbt3YFv6sA882mrFyTdzQePwHwvLoECnqFTnYNZI=@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, can somebody point me in the right direction for what I would use to= listen on a TCP socket from the kernel? I am working on a kernel module an= d have spent the past day looking through include/net and include/linux for= something that would allow me to do so. I know TCP listening is typically = done in userspace, but it should be possible at the kernel level right? tcp= _diag looks promising, but it seems like that is mainly for monitoring sock= ets, and I'm not sure if I would be able to provide responses from it. Louis Rossberg, Warped Technologies