- Add a new entry called "Super tunnel daemon". [1]
- Update one of the sysinstall entries with some new information. [2] - Update the ktrace(1)/kdump(1) entry with some new information. [2] Submitted by: phk [1] Submitted by: netchild [2]
This commit is contained in:
parent
bd023dfda0
commit
f33ae3f04c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27602
1 changed files with 45 additions and 2 deletions
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.34 2006/04/18 17:41:58 joel Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.35 2006/04/18 17:44:07 joel Exp $">
|
||||
<!ENTITY title "FreeBSD list of projects and ideas for volunteers">
|
||||
<!ENTITY % navincludes SYSTEM "../../includes.navdevelopers.sgml"> %navincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -107,6 +107,7 @@
|
|||
|
||||
<h3>Networking</h3>
|
||||
<ul>
|
||||
<li><a href="#p-suptundaemon">Super tunnel daemon</a></li>
|
||||
<li><a href="#p-csup">Implement missing csup features</a></li>
|
||||
<li><a href="#p-zeroconf">Add zeroconf (Rendezvous/Bonjour) support to
|
||||
FreeBSD</a></li>
|
||||
|
|
@ -756,6 +757,8 @@
|
|||
"pieces" (e.g. syscall's) to the ktrace output and to extend the output
|
||||
with "decoded" (translating hex/dec values into human readable
|
||||
information, e.g. O_RDONLY in the case of open(2)) information.</p>
|
||||
<p><a href="mailto:dpk@dpk.net">David Kirchner</a> is currently working on
|
||||
this and the results will (most likely) be committed soon.</p>
|
||||
<p><strong>Requirements</strong>:</p>
|
||||
<ul>
|
||||
<li>Knowledge of C.</li>
|
||||
|
|
@ -862,6 +865,44 @@
|
|||
|
||||
<hr>
|
||||
|
||||
<a name="p-suptundaemon"></a>
|
||||
<h2>Super tunnel daemon</h2>
|
||||
<p><strong>Technical contact</strong>: <a
|
||||
href="mailto:phk@FreeBSD.org">&a.phk;</a></p>
|
||||
<p>IP can be tunneled over IP, UDP, TCP, SSH, DNS, HTTP and many other
|
||||
protocols, and this means that it is often possible to get a
|
||||
connection out through a firewall, but each of these encapsulations
|
||||
require prior setup of a specific program for each encapsulation, and
|
||||
the user must experiment to decide which one to use at any one time.
|
||||
The super tunnel daemon should implement pluggable encapsulations and
|
||||
make it automatically select the most efficient encapsulation that
|
||||
works at any one time. The user should not notice transitions from one
|
||||
encapsulation to another, apart from maybe a small delay.</p>
|
||||
<p>Wanted features (not sorted or prioritized):</p>
|
||||
<ul>
|
||||
<li>Autodetection of the environment (DHCP, DNS, routing, ...) in a
|
||||
non-offensive way (no global portscans allowed; asking via DHCP,
|
||||
zeroconf or similar technologies is ok) as far as possible.</li>
|
||||
<li>Plugin architecture for easy addition of further encapsulations.</li>
|
||||
<li>Failover from one encapsulation to another.</li>
|
||||
<li>Distinct configuration files for encapsulations which need to be
|
||||
configured (e.g. proxy, authentication, ...).</li>
|
||||
<li>Possibility to disable installed encapsulations.</li>
|
||||
<li>Print/log hints for protocols which require some configuration,
|
||||
e.g. telling the user to use keys and perhaps the ssh-agent for ssh.</li>
|
||||
<li>Configurable additional plugin directories (for plugins installed
|
||||
via the ports collection).</li>
|
||||
<li>Log how it is able to tunnel the traffic (this also makes it useful
|
||||
for finding unwanted holes in the configuration of a firewall).</li>
|
||||
</ul>
|
||||
<p><strong>Requirements</strong>:</p>
|
||||
<ul>
|
||||
<li>Good knowledge of C.</li>
|
||||
<li>Good knowledge about networks.</li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<a name="p-csup"></a>
|
||||
<h2>Implement missing csup features</h2>
|
||||
<p><strong>Technical contact</strong>: <a
|
||||
|
|
@ -1125,7 +1166,9 @@
|
|||
to remove sysinstall when the new installer enters the tree without loosing
|
||||
nice functionality. Additionally novice users cannot shoot themselves in the
|
||||
foot by accidentally triggering the wrong actions in unrelated parts of
|
||||
sysinstall. &a.netchild; has some working code.</p>
|
||||
sysinstall. &a.netchild; has some working code which will (most likely) be
|
||||
committed after 6.1 is released. The code is nearly finished, so no more help
|
||||
is needed at the moment.</p>
|
||||
<p><strong>Requirements</strong>:</p>
|
||||
<ul>
|
||||
<li>Knowledge of C.</li>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue