From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: William Katsak <wkatsak@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Upper routing throughput limit
Date: Sat, 09 Aug 2014 20:52:23 +0200 [thread overview]
Message-ID: <87ha1l8pi0.fsf@toke.dk> (raw)
In-Reply-To: <3FF07025-9AE2-4A6F-9E7B-A0AC5CAFD290@gmail.com> (William Katsak's message of "Wed, 6 Aug 2014 22:14:10 -0400")
[-- Attachment #1: Type: text/plain, Size: 2443 bytes --]
William Katsak <wkatsak@gmail.com> writes:
> Somehow I didn’t see this email the last time I posted about this. I
> was wondering too about how to nicely do the VLANs for the wifi. I
> wouldn’t mind checking out your config (this will be relevant on the
> Cero wide no matter what I do for the main router).
Right, well I just re-did the setup from a vanilla cerowrt image, so
here goes:
For the secondary access point, I use the wan port as an 'uplink' port
that trunks the vlans for each of the wireless networks (and one for the
wired as well). Thus, vlan1 is the wired lan, vlan2 is the first
'internal' network (sw00), vlan3 is sw10, vlan4 is gw00 and vlan5 is
gw10. For a vanilla cerowrt box, I shut off all daemons apart from
dropbear (for ssh access) and the network config. This includes dnsmasq
(DHCP is assumed to be on the upstream server). Going through init
scripts to `/etc/init.d/foo stop && /etc/init.d/foo disable` until
everything is shut off should do it.
After that, it's really only a few modifications to /etc/config/network
that is needed to achieve this:
1. Get rid of the config for the wan interface completely (the 'config
interface ge00' block and the ipv6 equivalent).
2. For the se00 interface, make sure these lines are present:
option 'ifname' 'se00 ge00.1'
option 'type' 'bridge'
replacing any lines with the same option names. The openwrt network
setup automatically configures VLANs from the .N syntax.
3. Similarly, for the wireless interfaces change 'type' from 'none' to
'bridge' and add an 'option ifname ge00.N' line, with N being the
vlan number as listed above.
4. Configure the IP addresses of each interface to correspond to the
upstream router setup. I just add 1 to each IP and configure the DHCP
server to start at (GW ip)+2 rather than (GW ip)+1.
5. Plug in the cerowrt lan port to the upstream router, and make sure
that has the appropriate 5 VLANs configured with a DHCP server
running on each, etc.
I've used this setup for replacing the WNDR box with a beefier device
for high-speed routing, as well as for adding a second WNDR for extended
wifi range (doing that this way rather than meshing allows clients to
roam while keeping their IP and DHCP lease, and gets me a single DNS
namespace since there's only one dnsmasq instance).
Hope this explanation makes sense. :)
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2014-08-09 18:52 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
[not found] ` <3FF07025-9AE2-4A6F-9E7B-A0AC5CAFD290@gmail.com>
2014-08-09 18:52 ` Toke Høiland-Jørgensen [this message]
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=87ha1l8pi0.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