Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: [homenet] Routing protocol comparison document
Date: Mon, 2 Mar 2015 12:32:26 -0800	[thread overview]
Message-ID: <CALQXh-PmGP9q+DumXE_vLTW9t-g+NAbJw8C7cSc3RVmyBa01fQ@mail.gmail.com> (raw)
In-Reply-To: <874mq3w3gq.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

I would definitely be interested in being involved with how to secure and
firewall, but still provide access to, internal IPv6 hosts.  Ie, the
internet the way it's supposed to work (peer to peer), but with the
security that we've inadvertently picked up along the way by using NAT
everywhere for the last ~10-20 years worth of home routers.

Basically, the question is:  How do I access my home remotely, without
exposing it to the world.

The IPSec portions of IPv6 seem like most, but not all, of the building
blocks.

-Aaron

On Mon, Mar 2, 2015 at 12:26 PM, Toke Høiland-Jørgensen <toke@toke.dk>
wrote:

> Dave Taht <dave.taht@gmail.com> writes:
>
> > Any objections here?
>
> Yes! I certainly wouldn't want to run that.
>
> > Suggestions for how to make one of the ipv6 translation techniques
> > work right?
>
> Turn them off? ;)
>
> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 1770 bytes --]

  reply	other threads:[~2015-03-02 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54EE258E.8060302@gmail.com>
     [not found] ` <201502272200.t1RM0Aru020484@maildrop31.somerville.occnc.com>
     [not found]   ` <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail.com>
     [not found]     ` <7ia8zvjkdq.wl-jch@pps.univ-paris-diderot.fr>
     [not found]       ` <CAA93jw6d+Fz3B24O9HWbgzKSX_z2KihkCSXkibbM+Zp0U8oxcQ@mail.gmail.com>
2015-03-02 19:45         ` Dave Taht
2015-03-02 20:26           ` Toke Høiland-Jørgensen
2015-03-02 20:32             ` Aaron Wood [this message]
2015-03-02 20:45             ` Dave Taht
2015-03-03 14:36           ` [Cerowrt-devel] " JF Tremblay

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALQXh-PmGP9q+DumXE_vLTW9t-g+NAbJw8C7cSc3RVmyBa01fQ@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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