Rich - Thanks for the scripts.

 

I'm sorry you need to tunnel at all.  Most competitive access providers seem to be supporting IPv6 using anycast and 6to4 natively these days(it's the datacenters and corporate Intranets that use 10.*.*.* who seem to never want to change, since F5 and others make all that Intranet middlebox stuff that security "mavens" seem to think actually protect all their unpatched Windows machines).

 

But here is what I used to use, documented:

 

https://www.tunnelbroker.net/forums/index.php?topic=1994.0

 

gives you tools to detect your IPv4 address and update the tunnelbroker to know it.  You can used these tools with curl or wget to  periodically query your own IPv4 address as it shows, and when changed, do an update to it.

 

Maybe you already knew that - but maybe you just knew about theupdate.

 

 

 

 

-----Original Message-----
From: "Rich Brown" <richb.hanover@gmail.com>
Sent: Sunday, February 3, 2013 8:45pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 3.7.5-2 released

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