Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: William Katsak <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Upper routing throughput limit
Date: Fri, 11 Jul 2014 11:33:36 +0200	[thread overview]
Message-ID: <87pphc8cjz.fsf@toke.dk> (raw)
In-Reply-To: <53BEAF05.8000601@gmail.com> (William Katsak's message of "Thu, 10 Jul 2014 11:19:33 -0400")

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

William Katsak <wkatsak@gmail.com> writes:

> I was considering the possibility of using PfSense on an x86 box as my
> main router/firewall for better throughput, and hanging Cero off of
> that for wifi. Anyone doing something similar? If so, how do you
> organize the subnets?

I have a similar setup with a dual-ethernet x86 box acting as router
for my 100/100 Mbps connection. The plan was originally to stick a
minipci wifi card in there to also act as access point, but for now I've
settled on using a cerowrt box as a relatively dumb wifi box. The setup
is something like this

+------------+           +----------+           +------------+
|            |           |          |           |            |
|  Internet  +-----------+  Router  +-----------+  WNDR3800  |
|            |           |          |           |            |
+------------+           +----------+           +------------+

The router downstream ethernet port is plugged into the wan port on the
WNDR3800 and I've configured three 802.1Q VLANs on the link between the
router and the cerowrt box, which are bridged to the LAN switch, the
private wifi interfaces and the guest wifi interfaces respectively. This
allows me to run dnsmasq etc on the router, and have the cerowrt box
simply provide wifi connectivity, but without bridging the wifi directly
to the ethernet LAN. I got lazy and only did one VLAN for each type of
wifi, rather than having one per frequency as in stock cerowrt, but see
no reason why adding additional VLANs for each frequency should pose any
problems.

The only daemons running on the cerowrt box are dropbear, radsecproxy
(for 802.11i authentication on the private wifi), ntpd, netifd and
hostapd. The router box runs a stock Arch Linux installation, with
dnsmasq serving up a /27 and a /64 (from he.net) on each of the virtual
vlan interfaces, most of the network setup managed through
systemd-networkd, and a couple of scripts to set up the he.net tunnel
and an SQM-derived shaper, as well as a manual firewall setup. The
router box also runs BIND as a local resolver, a TOR node, minidlna and
various other daemons.

The VLAN setup on the cerowrt box took a couple of attempts to get
right, but now that it is running it seems to work well. I'll be happy
to share the config if you're interested. :)

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2014-07-11  9:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:49 William Katsak
2014-07-10 15:01 ` Aaron Wood
2014-07-10 15:19   ` William Katsak
2014-07-11  9:33     ` Toke Høiland-Jørgensen [this message]
     [not found]       ` <3FF07025-9AE2-4A6F-9E7B-A0AC5CAFD290@gmail.com>
2014-08-09 18:52         ` Toke Høiland-Jørgensen
2014-08-06 19:35   ` William Katsak
2014-08-06 23:06     ` David Lang
2014-08-06 23:10       ` Dave Taht

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=87pphc8cjz.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=wkatsak@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