Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Walter de Donato <walter.dedonato@unina.it>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] initial openvpn results on capetown
Date: Mon, 30 May 2011 16:43:35 -0600	[thread overview]
Message-ID: <BANLkTik7rqbupDD1+Jw48MQhMj=BKY5+xA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin5hkbSENYefWLEs7VW+-58b9rCaw@mail.gmail.com>

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

On Mon, May 30, 2011 at 2:02 PM, Walter de Donato
<walter.dedonato@unina.it>wrote:

> I really like all these analysis on scalability and flexibility.


And redundancy, and security, and robustness.

I'm glad to share what I'm working on.


> Anyway, I think we won't need to have many tunnels active at the same time.
>
>
The current scope of bismark is a goal 200 devices in the field, as I
understand it.

How do you plan to push out new packages?


> The goal of having these tunnels is to be able to occasionally talk to the
> devices,
> access to their console/web_interface.
>

SNMP is used heavily by large scale corporate monitoring tools such as
nagios, cacti, etc.


Do you have other goals in mind?
>
>
Bismark is leveraging one project of 'uberwrt' and bufferbloat.net. There
are five others at present. There will hopefully be more.

While I do not expect to get a one-size-fits all solution to the needs of
all the projects, it is worth it to do more than a cursory investigation on
something that may need to be supported (by others) for a decade in the
field.

There is a need for a vpn solution in all the sub-projects,
(it's my number #1 request)

not just for monitoring boxes currently invisible behind NAT,

but for corporate connectivity, which is what vpns are usually used for.

I also like the idea of 'home router management as a service', which is
embedded in the 'network-dashboard' idea.

Additionally to the vpn issue, getting port mirroring to work comes from a
request from MIT to be able to leverage their monitoring box, which is an
external box that can run at wire speeds.

It may sit on top of bismark one day to verify results.




> Walter
>
> 2011/5/30 Dave Taht <dave.taht@gmail.com>
>
>> On Mon, May 30, 2011 at 8:52 AM, Srikanth Sundaresan <srikanth@gatech.edu
>> > wrote:
>>
>>>
>>> On May 30, 2011, at 6:58 PM, Dave Taht wrote:
>>>
>>> > After running overnight, the openvpn server grew to about 8MB in size,
>>> and seems to have stabilized there.
>>>
>>> That's a lot, isn't it?
>>
>>
>> No. The server should run on a far more capable host than the router,
>> which would hardly notice.
>>
>> More important is that I'm not observing unbounded memory growth, which is
>> important for long running processes.
>>
>> The server size is also a function of the number of connected clients.
>> There are only two connected now.
>>
>> The client (after much less abuse than I put the server through last
>> night) weighs in at
>>
>> 12932     1 root     S     4548   7%   0% /usr/sbin/openvpn --syslog
>> openvpn(cu
>>
>> Note that using VSZ as per either of these measurements do is a bad idea
>> in that it inaccurately accounts for stack size and shared library usage.
>>
>> But as a rough measure, it's not bad, and we currently have over 32MB of
>> ram to spare, even after openvpn is  running. dnsmasq, after some usage,
>> will grow larger than it is at present.
>>
>> I'll put the client through some abuse in a bit.
>>
>> As a client, openvpn has the ability to take a list of addresses, and
>> ports, to try an outgoing connection on.
>>
>> As a server, multiple servers can listen also on multiple ports, on
>> multiple machines as well, so it is theoretically scalable to thousands of
>> users.
>>
>> My principal problem (long term) with openvpn, is as a user space daemon
>> it cannot take advantage of hardware acceleration on the client side, where
>> available (of the hardware projected to be in use for cerowrt, the only
>> thing that does hardware crypto is the dreamplug). I would also like to try
>> a heavier crypto algo than blowfish.
>>
>> That said, once I got through the 'generate a cert setup hassle', it's
>> nice to be able to get to port 81 through the vpn, as well as see snmp
>> stuff.
>>
>>
>> _______________________________________________
>> Bismark-devel mailing list
>> Bismark-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bismark-devel
>>
>>
>
>
> --
> Walter de Donato, PhD Student
> Dipartimento di Informatica e Sistemistica
> Università  degli Studi di Napoli "Federico II"
> Via Claudio 21 -- 80125 Napoli (Italy)
> Phone: +39 081 76 83821 - Fax: +39 081 76 83816
> Email: walter.dedonato@unina.it
> WWW: http://wpage.unina.it/walter.dedonato
>
>


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

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

  reply	other threads:[~2011-05-30 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 21:01 Dave Taht
2011-05-30 13:28 ` Dave Taht
2011-05-30 18:12   ` Dave Taht
2011-05-30 20:02     ` Walter de Donato
2011-05-30 22:43       ` Dave Taht [this message]
2011-05-30 23:06         ` Dave Taht
2011-05-31 14:52           ` Walter de Donato

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='BANLkTik7rqbupDD1+Jw48MQhMj=BKY5+xA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bismark-devel@lists.bufferbloat.net \
    --cc=walter.dedonato@unina.it \
    /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