mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@bagpuss.swansea.linux.org.uk>
To: samudrala@us.ibm.com (Sridhar Samudrala)
Cc: hadi@cyberus.ca (jamal),
	diffserv-general@lists.sourceforge.net, kuznet@ms2.inr.ac.ru,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	linux-net@vger.kernel.org, rusty@rustcorp.com.au, thiemo@sics.se,
	samudrala@us.ibm.com (Sridhar Samudrala),
	tewarir@us.ibm.com (Renu Tewari),
	dmfreim@us.ibm.com
Subject: Re: [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism:
Date: Sun, 29 Jul 2001 17:27:50 -0400 (EDT)	[thread overview]
Message-ID: <200107292127.f6TLRpC01583@bagpuss.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0107301359350.23307-100000@w-sridhar2.des.sequent.com> from "Sridhar Samudrala" at Jul 30, 2001 03:08:34 PM

> Our patch can be used along with SYN policing to prioritize incoming
> connection requests on a socket. SYN policing can be used to limit 
> the rate of a particular class, but it cannot be used to prioritize a 

No. Because you cant prove the packets are not spoofed. An attacker 
becomes able to block classes


  reply	other threads:[~2001-08-02 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 17:36 [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept Queue Douglas M Freimuth
2001-07-30 19:26 ` jamal
2001-07-30 22:08   ` Sridhar Samudrala
2001-07-29 21:27     ` Alan Cox [this message]
2001-08-03 16:40       ` [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Sridhar Samudrala
2001-08-03 18:33       ` kuznet
2001-07-30 22:28     ` [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept Queue Justin Guyett
2001-07-31 10:24       ` Chris Wedgwood
2001-07-31  6:13   ` David S. 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=200107292127.f6TLRpC01583@bagpuss.swansea.linux.org.uk \
    --to=alan@bagpuss.swansea.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=diffserv-general@lists.sourceforge.net \
    --cc=dmfreim@us.ibm.com \
    --cc=hadi@cyberus.ca \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=samudrala@us.ibm.com \
    --cc=tewarir@us.ibm.com \
    --cc=thiemo@sics.se \
    /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
all inboxes | Powered by JetHome®