All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Rick Jones <rick.jones2@hp.com>, Martin Schiller <mschiller@tdt.de>
Cc: Caitlin Bestler <caitlin.bestler@gmail.com>, netdev@vger.kernel.org
Subject: Re: Suppress / delay SYN-ACK
Date: Fri, 13 Oct 2006 22:13:45 +0200	[thread overview]
Message-ID: <452FF379.2080600@cosmosbay.com> (raw)
In-Reply-To: <452FC15D.7030902@hp.com>

Rick Jones a écrit :
> Eric Dumazet wrote:
>> Rick Jones a écrit :
>>
>>>> More to the point, on what basis would the application be rejecting a
>>>> connection request based solely on the SYN?
>>>
>>>
>>> True, it isn't like there would suddenly be any call user data as in 
>>> XTI/TLI.
>>
>>
>> DATA payload could be included in the SYN packet. TCP specs allow this 
>> AFAIK.
> 
> Yes, but it isn't supposed to be delivered until the 3-way handshake is 
> complete right?

Are you speaking of 20 years old BSD API ? :)

Martin, I played with libnetfilter_queue 
(http://www.netfilter.org/projects/libnetfilter_queue/index.html)

With this single iptables rules, I was able to do what you want : transmit the 
SYN message to a user application, that may DROP this packet or let it pass 
normal TCP stack.

iptables -A INPUT -p tcp --dport 333 --syn -j QUEUE

Then hack nfqnl_test.c to meet your needs (see nfq_set_verdict(), 
nfq_get_payload())

Be prepared to receive the 'same SYN' several time if your X.25 call attempt 
is too long.

(You have to be root unfortunatly)

Eric


  reply	other threads:[~2006-10-13 20:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  8:08 Suppress / delay SYN-ACK Martin Schiller
2006-10-12  8:38 ` Eric Dumazet
2006-10-12 10:13   ` Martin Schiller
2006-10-12 10:31     ` Evgeniy Polyakov
2006-10-12 10:39       ` Eric Dumazet
2006-10-12 10:53         ` Evgeniy Polyakov
2006-10-12 10:36     ` Eric Dumazet
2006-10-12 16:13 ` Rick Jones
2006-10-12 21:58   ` Caitlin Bestler
2006-10-12 22:12     ` jamal
2006-10-12 22:54     ` Rick Jones
2006-10-13  0:57       ` Stephen Hemminger
2006-10-13  4:11       ` Eric Dumazet
2006-10-13 16:39         ` Rick Jones
2006-10-13 20:13           ` Eric Dumazet [this message]
2006-10-13 21:50             ` Rick Jones
2006-10-16  6:52             ` Martin Schiller
2006-10-13  5:41     ` Stephen J. Bevan
2006-10-13  6:28       ` Martin Schiller
2006-10-16  7:02 ` Lennert Buytenhek
2006-10-17 12:04   ` Martin Schiller
2006-10-17 12:54     ` Eric Dumazet
2006-10-18  6:23       ` Martin Schiller

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=452FF379.2080600@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=caitlin.bestler@gmail.com \
    --cc=mschiller@tdt.de \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.