From: Vijay Subramanian <subramanian.vijay@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, shemminger@vyatta.com,
eric.dumazet@gmail.com, alexander.h.duyck@intel.com
Subject: Re: [PATCH net-next] udp: Add socket early demux support
Date: Tue, 26 Jun 2012 17:06:29 -0700 [thread overview]
Message-ID: <CAGK4HS-bh2_hwiQAM+-4UaD8Ts5NAVEh19nBbAT8fQn1GookSw@mail.gmail.com> (raw)
In-Reply-To: <20120626.143401.445148198931339546.davem@davemloft.net>
Thanks for the reviews and feedback, Dave and Eric. They were very helpful.
On 26 June 2012 14:34, David Miller <davem@davemloft.net> wrote:
>
> You can't do this.
>
> If the UDP socket has wildcards, that means the source address of the
> route will not be validated. This means we will start accepting
> spoofed packets. It also means the route you are caching is going
> to be the wrong route since the keys are variable.
Thanks for this explanation.
I see why Eric wanted me to test with DNS server bound to wildcard
address. I guess the same issue exists with multicast too which I had
not even considered.
>
> You can only do an early demux where all the keys are fully specified
> and there are no wildcards. That why for TCP we only early demux for
> established sockets.
I guess for UDP, early demux will work only if server binds to a
specific address and port instead of wildcard. But I believe
a lot of UDP servers use wildcard addresses, so use of early demux for
UDP may be limited.
Thanks,
Vijay
next prev parent reply other threads:[~2012-06-27 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 19:43 [PATCH net-next] udp: Add socket early demux support Vijay Subramanian
2012-06-26 20:49 ` Eric Dumazet
2012-06-26 21:34 ` David Miller
2012-06-27 0:06 ` Vijay Subramanian [this message]
2012-06-27 2:29 ` Changli Gao
2012-06-27 3:59 ` David Miller
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=CAGK4HS-bh2_hwiQAM+-4UaD8Ts5NAVEh19nBbAT8fQn1GookSw@mail.gmail.com \
--to=subramanian.vijay@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).