From: Dave Taht <dave.taht@gmail.com>
To: James Cloos <cloos@jhcloos.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] switching to cero
Date: Sat, 15 Nov 2014 12:15:29 -0800 [thread overview]
Message-ID: <CAA93jw68iZg+xjO8QzrRwKsnKbv6p=fTdG7yiH_2rbpjbq+H3g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7GB=T7-_MhQHytqxZbriioeCNKhR07R0=UZtZNkcj3iw@mail.gmail.com>
These instructions assume a box running babels on the other side. As
you are using static routing on the main box, you can use static
routing on the cerowrt box also and not disable via the "defaultroute
0" line.
On the other hand, I like routing protocols, so if you want you can
merely add babels (the source specific version) to the main gateway
and configure it to export it's routes.
http://www.ietf.org/mail-archive/web/homenet/current/msg02814.html
On Sat, Nov 15, 2014 at 12:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
> http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_an_interior_gateway_router
>
> On Sat, Nov 15, 2014 at 11:45 AM, James Cloos <cloos@jhcloos.com> wrote:
>> I bought a 3800 many months ago, but ran openwrt on it because I didn't
>> want to renumber my wired net.
>>
>> I finally was able to aquire a box to use as my edge router, and
>> switched the 3800 to cero for the wireless clients. Everything on
>> the edge box is compiled locally.
>>
>> I have a route on the edge pointing 172.16.0.0/12 to the 3800, and plan
>> on the it doing all of the NAT. The 3800 will just need to push packets.
>>
>> Does anyone have any suggestions on how best to optimize the edge
>> routing in such a scenerio?
>>
>> -JimC
>> --
>> James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next prev parent reply other threads:[~2014-11-15 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 19:45 James Cloos
2014-11-15 20:09 ` Dave Taht
2014-11-15 20:15 ` Dave Taht [this message]
2014-11-17 21:41 ` William Katsak
2014-11-18 15:38 ` James Cloos
2014-11-18 16:07 ` William Katsak
2014-11-18 16:37 ` James Cloos
2014-11-18 16:45 ` Dave Taht
2014-11-18 18:04 ` James Cloos
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='CAA93jw68iZg+xjO8QzrRwKsnKbv6p=fTdG7yiH_2rbpjbq+H3g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cloos@jhcloos.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