From: Christian Riechmann <riechmann@fgan.de>
To: netfilter@lists.netfilter.org
Subject: Re: Need some clarification or help
Date: Tue, 20 Apr 2004 22:51:44 +0200 [thread overview]
Message-ID: <20040420205144.GC2997@rie.rie.priv> (raw)
In-Reply-To: <200404201947.39774.Antony@Soft-Solutions.co.uk>
Antony,
first thanks for your reply and your hint concerning vtun.
I have some remarks to your reply and put them inside your message.
On 2004-04-20 19:47:39 +0100, Antony Stone wrote:
> On Tuesday 20 April 2004 7:22 pm, Christian Riechmann wrote:
>
> > Hello,
> >
> > is it possible to read - via ipq_read/ipq_get_packet - a UDP packetr
> > and after some changes to accept - via ipq_set_verdict with NF_ACCEPT and
> > shorter length - it as a TCP packet?
>
> My immediate response to this is "no, of course not, because UDP and TCP
> packet headers are completely different".
>
> I mean, UDP packets just get sent - who knows whether the receiver gets them
> or not? TCP involves a three-way handshake to set up a connection, and then
> sequence & acknowledgement numbers to maintain the reliability. Creating
> that out of nowhere would be difficult.
Maybe I am a little bit lazy when describing my method as "tunnelling".
Therefore I will go a little bit deeper.
I know that UDP and TCP protocols are completely different, especially
the 3-way handshake. But all its steps are TCP packets. Therefore my idea
is to encapsulate on each side each TCP packet into a UDP packet, send
this one to the other side, decapsulate the original TCP paket from the UDP
packet and inject the TCP packet to the kernel. This way the total TCP
dialog shall be exchanged as payload of separate UDP packets. UDP
is necessary, because only UDP can use broadcast addresses.
(I use this type of address to emulate LAN-broadcast within a mobile
adhoc network. Therefore I doubt that vtun would help me.)
>
> > Here is what I wish to do:
> > For the transmission of IP packets (UDP, ICMP, TCP) between two hosts
> > I want to send these packets through a UDP tunnel.
>
> Tunnelling is a very different matter from converting UDP packets into TCP
> packets, and should be eminently feasible.
As I tried to explain, I do NOT want to convert UDP to TCP, I only want to
transport TCP packets as UDP payload.
I would be glad if you can comment the method described above.
Regards
Christian
--
Christian Riechmann E-Mail: riechmann@fgan.de
c/o FGAN/FKIE Tel: (+49) 228/9435 345,378
Neuenahrer Strasse 20 Fax: (+49) 228/9435 685
D-53343 Wachtberg, Germany
next prev parent reply other threads:[~2004-04-20 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 18:22 Need some clarification or help Christian Riechmann
2004-04-20 18:47 ` Antony Stone
2004-04-20 20:51 ` Christian Riechmann [this message]
2004-04-20 21:07 ` Antony Stone
2004-04-21 11:45 ` Christian Riechmann
2004-04-20 21:32 ` Jee J.Z.
2004-04-21 11:14 ` Christian Riechmann
2004-04-21 15:41 ` Jee J.Z.
2004-04-21 19:51 ` Christian Riechmann
2004-04-21 22:17 ` Jee J.Z.
2004-04-22 20:41 ` root
2004-04-22 21:34 ` Jee J.Z.
2004-04-23 10:17 ` Christian Riechmann
2004-04-22 0:38 ` Henrik Nordstrom
2004-04-22 21:32 ` Christian Riechmann
2004-04-23 7:02 ` Henrik Nordstrom
2004-04-23 10:22 ` Christian Riechmann
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=20040420205144.GC2997@rie.rie.priv \
--to=riechmann@fgan.de \
--cc=netfilter@lists.netfilter.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