From: Steven Brown <swbrown@variadic.org>
To: dccp@vger.kernel.org
Subject: Existing solutions for encapsulation?
Date: Wed, 05 Mar 2008 19:40:04 +0000 [thread overview]
Message-ID: <47CEF714.708@variadic.org> (raw)
I'm running into a need for encapsulation due to various providers
mangling (mandatory NATs on local EVDO service) or dropping (AT&T Yahoo
DSL residential service (but business service works it seems)) DCCP
traffic. I figure DCCP-NAT[1] support in the stack is exactly what I
need, but AFAIK it's not implemented yet (only in DCCP-TP I think).
Is there an existing solution at the moment to add the encoding, or near
term plan to implement it? If not, would it make sense to route the
traffic into a tun device that adds/removes the encoding? Is there a
better way to get the DCCP packet before it's sent than having an extra
service/interface like that? I'm not familiar enough with the kernel
layer to implement it there in reasonable time which is why I'm looking
at doing a quick hack in userland.
[1] http://www.phelan-4.com/dccp/draft-phelan-dccp-natencap-00.txt
next reply other threads:[~2008-03-05 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 19:40 Steven Brown [this message]
2008-03-08 4:59 ` Existing solutions for encapsulation? Ian McDonald
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=47CEF714.708@variadic.org \
--to=swbrown@variadic.org \
--cc=dccp@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 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.