Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juergen Botz <jurgen@botz.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?
Date: Sat, 16 Nov 2013 08:42:29 -0300	[thread overview]
Message-ID: <52875A25.3060300@botz.org> (raw)
In-Reply-To: <CAA93jw6srNA+JhwuxyyjVcvZNDniuQu_eXi4BBjXu70d3Fb49w@mail.gmail.com>

On 11/15/2013 02:10 AM, Dave Taht wrote:
> Well, an alternative is to bridge or use WDS.

I tried WDS at one point about a year ago but never was able
to get it to work on cerowrt.  Anybody out there using WDS
with recent cerowrt?

WDS is kind of kludgey, but it is a fairly simple "just works"
approach for small multi-AP networks.

:j





  reply	other threads:[~2013-11-16 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15  5:03 Kelvin Edmison
2013-11-15  5:10 ` Dave Taht
2013-11-16 11:42   ` Juergen Botz [this message]
2013-11-16 16:55   ` Dave Taht
2013-11-17  1:56     ` Kelvin Edmison

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=52875A25.3060300@botz.org \
    --to=jurgen@botz.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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