From: Dale Mellor <dale@rdmp.org>
To: Leonardo Rodrigues <leolistas@solutti.com.br>
Cc: netfilter@vger.kernel.org
Subject: Re: How to stop kernel TCP responses on a port
Date: Fri, 05 Sep 2014 05:27:33 +0100 [thread overview]
Message-ID: <1409891253.15027.24.camel@l3> (raw)
In-Reply-To: <54089069.8010603@solutti.com.br>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
> On 04/09/14 12:17, Dale Mellor wrote:
> I want to do TCP with raw sockets. How can I filter away the kernel's
> RST/ACK/SYN response messages when I want to do this myself?
On Thu, 2014-09-04 at 13:16 -0300, Leonardo Rodrigues wrote:
you'll probably need to tweak the kernel itself for that. If you
wanna do all the 'dirty work', why not use UDP instead of TCP ??
I need to tunnel TCP (specifically telnet) through a space link to a
spacecraft in orbit (don't worry, security exists in the link layer).
But of course I need the SYN/ACKs to come from the spacecraft itself
(rather than the ground-station PC) so I know when I can send commands
up. I'm going to try to use the iptables' QUEUE target and a user-space
packet filter, thinking that if I reject the incoming SYN it will be
dropped without further ado, and then I can synthesize a response later
with a raw socket.
Any thoughts people may have on this would likely be useful.
Thanks,
Dale
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-09-05 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 15:17 How to stop kernel TCP responses on a port Dale Mellor
2014-09-04 16:16 ` Leonardo Rodrigues
2014-09-05 4:27 ` Dale Mellor [this message]
[not found] ` <CBD8736BE6044AE0B06076D69855AF85@gmail.com>
2014-09-05 5:41 ` Dale Mellor
2014-09-08 3:11 ` Brad Campbell
2014-09-09 13:49 ` Dale Mellor
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=1409891253.15027.24.camel@l3 \
--to=dale@rdmp.org \
--cc=leolistas@solutti.com.br \
--cc=netfilter@vger.kernel.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).