Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen.hemminger@gmail.com>
Cc: jow@openwrt.org, Cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] OpenVPN?
Date: Tue, 9 Apr 2013 22:55:53 -0700	[thread overview]
Message-ID: <CAA93jw65=rKK2wt+37cJ6Wr3VHjDgARzC9gMgaJBrxCUY2uhaQ@mail.gmail.com> (raw)
In-Reply-To: <CAJjQ54XtL3mRu=Y0it7dhr7fM7md93EAY5dr5R1RbR879yXqbA@mail.gmail.com>

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

I used to include openvpn as part of the default build of cero. It broke
entirely in the the 3.7.5 release so it was removed. It is fixed in the
3.8.6-2 release but it appears the luci gui is currently marked as broken
in openwrt head.

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.6-2/

You can get the openvpn-openssl and openvpn-easyrsa packages via

opkg update
opkg install openvpn-openssl

I note I'm not huge on generating rsa keys on devices with minimal entropy.

I also note that either vtun or openvpn could use some debloating and love,
in that when I last pounded a lot of data through it, it had interesting
drop characteristics, and that it appears useful to attach fq_codel to a
vtun interface in some cases.

On Tue, Apr 9, 2013 at 10:22 PM, Stephen Hemminger <
stephen.hemminger@gmail.com> wrote:

> Any Cerowrt instructions to enable openvpn. Or is it the same as Openwrt?
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>


-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

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

  reply	other threads:[~2013-04-10  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  5:22 Stephen Hemminger
2013-04-10  5:55 ` Dave Taht [this message]
2013-04-10 18:25 ` Chris Lawrence

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='CAA93jw65=rKK2wt+37cJ6Wr3VHjDgARzC9gMgaJBrxCUY2uhaQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Cerowrt-devel@lists.bufferbloat.net \
    --cc=jow@openwrt.org \
    --cc=stephen.hemminger@gmail.com \
    /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