From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 3.7.5-2 released
Date: Sun, 3 Feb 2013 20:45:46 -0500 [thread overview]
Message-ID: <1E7D86FF-8DEC-4D6E-8808-546DA608AF97@gmail.com> (raw)
In-Reply-To: <CAA93jw4Mt_HZwkHjZi=DzR=1PWGJjX_7uNRajdkfDAwcLeii4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
Dave,
Congratulations on this new version. It's looking good. I ran my "configuring all the standard stuff" script and the IPv6 configuration script, and both worked as expected. They're "config.sh" and "tunnelbroker.sh", respectively, on the wiki's "Files" tab - http://www.bufferbloat.net/projects/cerowrt/files. You can use these scripts to make the following configuration changes easily and repeatably after flashing a new version of the firmware. (You can comment out sections to match your own preferences.)
- Update the root password
- Set the time zone
- Enable SNMP for traffic monitoring and measurements
- Enable NetFlow export for traffic analysis
- Enable mDNS/ZeroConf on the ge00 (WAN) interface
- Change default IP addresses and subnets for interfaces
- Change default DNS names
- Change default wireless SSID names
- Change the QoS settings (may not be necessary, but this how to do it)
- Change the wireless security credentials
- Set up an IPv6 tunnel and give each of the local interfaces its own /64 subnet
One continuing problem with CeroWrt (and probably the underlying OpenWrt base) is that the IPv6 tunnel does not automatically re-establish itself if there's a problem. For example, if my DSL at home gets a new IP address, the tunnel to Hurricane Electric goes down. I have to use an HTTPS query (listed in the tunnelbroker.sh script) to re-establish the tunnel.
Does anyone on this list know how to force the reconnect when the 6in4 tunnel goes down? If not, what's the right list to get this question? Thanks.
Rich Brown
Hanover, NH USA
On Feb 3, 2013, at 11:45 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> + sources tagged and pushed to cerowrt-next and cerofiles-next on github
> + Kernel 3.7.5
> + resync with openwrt
> (this has more gui support for the new ipv6 stuff, also seems to have better ipv6 lifetime support)
> + dnsmasq 2.66test13
> + nut actually works with the cyberpower ups this time
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 3078 bytes --]
next prev parent reply other threads:[~2013-02-04 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 16:45 Dave Taht
2013-02-04 1:45 ` Rich Brown [this message]
2013-02-04 3:39 ` dpreed
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=1E7D86FF-8DEC-4D6E-8808-546DA608AF97@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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