From: tobin@apporbit.com (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux Networking Internals Question
Date: Tue, 26 Jun 2018 08:51:07 +1000 [thread overview]
Message-ID: <20180625225107.GN3006@eros> (raw)
In-Reply-To: <CA+CftcHBNpOm5BJhx4iG8uPNdoC4vK4b+GtRTrqtr=wMGVmbUw@mail.gmail.com>
On Sat, Jun 16, 2018 at 11:17:01PM +0530, V.Ravikumar wrote:
> Understood Rami Rosen. Thank you.
>
> Regards
> Ravi
>
> On Sat, Jun 16, 2018 at 11:10 PM, Rami Rosen <roszenrami@gmail.com> wrote:
>
> > Hi Ravi,
> > The path that a packet goes through, from being received by the
> > network driver and up to kernel Layer 3 (IPV4/IPV6) and from
> > there to kernel Layer 4 (UDP/TCP/SCTP/other sockets) and from there to
> > userspace sockets is quite complex. The logic is heavy, on that path
> > there are lookups in routing tables, netfilter hooks, sanity checks,
> > interaction with other subsystems, and more.
> >
> > In order to try to simplify things, and not go into deep technical
> > details, we can say that generally the 5 tuple of the packet (SRC
> > address, DST address, SRC port, DST port and protocol) is what
> > determines to which socket it will go.
> >
> > Regards,
> > Rami Rosen
> > http://ramirose.wixsite.com/ramirosen
> >
> >
> >
> >
> > On 16 June 2018 at 20:16, V.Ravikumar <ravikumar.vallabhu@gmail.com>
> > wrote:
> > > Hi All,
> > >
> > > I wanted to know how a packet received will be handovered to a correct
> > user
> > > process.
> > > Basically I want to understand what are the various header parameters in
> > > packet which will help to find the open socket descriptor of respective
> > > user process. I'm not able to find the exact answers in the web.
Or you could read Rami's book, you will learn a whole bunch :)
Tobin
prev parent reply other threads:[~2018-06-25 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 17:16 Linux Networking Internals Question V.Ravikumar
2018-06-16 17:40 ` Rami Rosen
2018-06-16 17:47 ` V.Ravikumar
2018-06-25 22:51 ` Tobin C. Harding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180625225107.GN3006@eros \
--to=tobin@apporbit.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).