From: Park Lee <parklee_sel@yahoo.com>
To: Neil Horman <nhorman@redhat.com>
Cc: jamal <hadi@cyberus.ca>, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Must every packet have a creating socket? (was Re: Does a forwarded packet has a local socket with it?)
Date: Wed, 20 Apr 2005 10:29:43 -0700 (PDT) [thread overview]
Message-ID: <20050420172944.69275.qmail@web51501.mail.yahoo.com> (raw)
On Tue, 19 Apr 2005 at 08:26, Neil Horman wrote:
> Not sure what your asking here. Asking "Does these
> two sockets belong to local socket?" is a pretty
> meaningless question, as the terminology is
> nonsensical. All sockets have a protocol associated
> with them (except raw sockets, but thats another
> topic). When you create a socket you associate it
> with a protocol family (AF_INET, AF_INET6,
> AF_NETLINK, AF_APPLETALK, etc),
> a connection type (SOCK_STREAM for connection
> oriented protocols, SOCK_DGRAM for connection-less
> protocols), and a protocol (IPPROTO_TCP,
> IPPROTO_UDP, etc). Depending on the family, type
> and protocol you select, you can talk to different
> systems/services.
>
> Does that answer your question?
Thanks a lot.
Can I think that every packet (e.g. IP packet) must
have a corresponding creating socket? (i.e. Must every
packet be created by a socket?)
Is there any other way to originate a packet?
Thank you.
Best Regards,
Park Lee
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
next reply other threads:[~2005-04-20 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 17:29 Park Lee [this message]
2005-04-21 1:20 ` Must every packet have a creating socket? (was Re: Does a forwarded packet has a local socket with it?) Rick Jones
2005-04-22 11:39 ` Must every packet have a creating socket? Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 13:05 Must every packet have a creating socket? (was Re: Does a forwarded packet has a local socket with it?) Park Lee
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=20050420172944.69275.qmail@web51501.mail.yahoo.com \
--to=parklee_sel@yahoo.com \
--cc=hadi@cyberus.ca \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nhorman@redhat.com \
/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).