From: "Jee J.Z." <jz105@york.ac.uk>
To: Christian Riechmann <riechmann@fgan.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Need some clarification or help
Date: Tue, 20 Apr 2004 22:32:36 +0100 [thread overview]
Message-ID: <003c01c4271e$ffbe9a00$68892090@grouse> (raw)
In-Reply-To: 20040420205144.GC2997@rie.rie.priv
Hi Christian,
> 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.)
This sounds to me like that you need two transport layers to do this at the
receivers. Otherwise the encapsulated TCP packets will be forwarded as the
payload of UDP packets to upper layers. The receivers even don't know they
were actually TCP packets, and upper layers will get confused what these
payloads mean. Am I missing something obvious?
Cheers,
Jee
> >
> > > 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 21:32 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
2004-04-20 21:07 ` Antony Stone
2004-04-21 11:45 ` Christian Riechmann
2004-04-20 21:32 ` Jee J.Z. [this message]
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='003c01c4271e$ffbe9a00$68892090@grouse' \
--to=jz105@york.ac.uk \
--cc=netfilter@lists.netfilter.org \
--cc=riechmann@fgan.de \
/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