Thinking about seeing how our firmware compiles on the new release!
-------- Original Message --------
From: Dave Taht <dave.taht(a)bufferbloat.net>
Sent: October 6, 2014 9:35:17 AM PDT
To: Steven Barth <cyrus(a)openwrt.org>
Cc: openwrt-devel(a)lists.openwrt.org
Subject: Re: [OpenWrt-Devel] Barrier Breaker 14.07 Final
Congrats everyone!
Here's to a faster, bufferbloat-free and ipv6 enabled
Internet!
On Thu, Oct 02, 2014 at 02:59:08PM +0200, Steven Barth wrote:
> The OpenWrt developers are proud to announce the final release
> of OpenWrt Barrier Breaker.
>
> _______ ________ __
> | |.-----.-----.-----.| | | |.----.| |_
> | - || _ | -__| || | | || _|| _|
> |_______|| __|_____|__|__||________||__| |____|
> |__| W I R E L E S S F R E E D O M
> -----------------------------------------------------
> BARRIER BREAKER (14.07)
> -----------------------------------------------------
> * 1/2 oz Galliano Pour all ingredients into
> * 4 oz cold Coffee an irish coffee mug filled
> * 1 1/2 oz Dark Rum with crushed ice. Stir.
> * 2 tsp. Creme de Cacao
> -----------------------------------------------------
>
> http://downloads.openwrt.org/barrier_breaker/14.07/
>
> Important changes since RC3
> * various ath9k related fixes
> * a few board related fixes
> * fixes for packages depdending on curl
> * per feed download folders
>
> Important changes since RC2
> * NAT & firewall throughput improvements
> * Security updates for OpenSSL & PolarSSL
> * Minor fixes in DHCP & DHCPv6 handling
> * Configuration support for GRE tunnels
> * Various other fixes
>
> Important changes since RC1
> * fix a long standing ath9k deadlock bug
> * all feeds are now built
> * image builder now works and RC2 contains all board specific images
> * various board/stability fixes
>
> ** Highlights since Attitude Adjustment **
> Default configuration and images
>
> * Linux kernel updated to version 3.10
> * Procd: new preinit, init, hotplug and event system written in C
> * Native IPv6-support
> - RA & DHCPv6+PD client and server
> - Local prefix allocation & source-restricted routes
> (multihoming)
> * Filesystem improvements
> - Added support for sysupgrade on NAND-flash
> - Added support for filesystem snapshot and rollback
> - Rewritten mounting system in C for rootfs and block devices
> * UCI configuration improvements
> - Support for testing configuration and rollback to working
> last working state
> - Unified change trigger system to restart services on-demand
> - Added a data validation layer
> * Networking improvements
> - Netifd now handles setup and configuration reload of
> wireless interfaces
> - Added reworked event support to allow obsoleting network
> hotplug-scripts
> - Added support for dynamic firewall rules and zones
> - Added support for transparent multicast to unicast
> translation for bridges
> - Various other fixes and improvements
>
> Additional highlights selectable in the package feeds or SDK
> * Extended IPv6-support
> - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support
> - Experimental support for Lightweight 4over6, MAP-E and MAP-T
> - Draft-support for self-managing home networks (HNCP)
> * rpcd: new JSONRPC over HTTP-frontend for remote access to ubus
> * mdns: new lightweight mdns daemon (work in progress)
> * Initial support for the musl C standard library
> * Support for QMI-based 3g/4g modems
> * Support for DNSSEC validation
> * Added architecture for package signing and SHA256 hashing
> * ... and many more cool things
>
> Package feed reorganization
> For quite a while already we are not very satisfied with the quality
> of the packages-feed. To address this, we decided to do a fresh start
> on GitHub. The new feed https://github.com/openwrt/packages should be
> used from now on and package maintainers are asked to move their
> packages there. For the final release we will still build the old
> packages feed but it will be necessary to enable it manually in the
> opkg package list to be usable.
> Additionally we would like to give a big thank you to all of our
> package
> maintainers working on our various feeds.
>
> New build servers
> We would like to express our gratitude to Imagination Technology for
> funding the 2 build servers that we used for the release.
>
> Whats next ?
> We aim at releasing Chaos Calmer (CC) before the end of the year. The
> CC release will use 3.14 or a newer LTS kernel as baseline.
>
>
> Have fun!
> The OpenWrt developer team
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel(a)lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel(a)lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
I am running iOS 5.0.1 on my iphone. It's connected to peoplesopen.net from
sudo room and has
IP: 10.1.1.192
Gateway and DNS: 10.42.0.99
I'm not getting any connectivity, web or otherwise.
However, my laptop is also connected to peoplesopen.net from sudoroom and
has the same gateway and dns and has IP 10.1.1.246 and works perfectly.
I can even ping 10.1.1.192 from my laptop and I can connect to the iphone
via ssh and I can even connect out to the internet from my iphone from the
command line using ssh and DNS resolve works!
But when I try to do anything from the phone's GUI, web browser, or even
IRC, it just sits there loading, trying to connect.
Could this be something to do with the captive portal?
Hrummm. Max if you want to borrow my phone to test you totes can.
--
marc/juul
So the nodes that aren't on the wired network have unusually high
loadavg/cpu usage. Checked the logs and it seems tunneldigger
is doing lots of DNS lookups. (60/sec)
I have changed beta (10.1.2.1) to use an IP address and the load
average is low again (around 0.1).
Since it is very convenient to use DNS for the exit node, we should hack the
tunneldigger client to slow down.
tunneldigger also seems to use more memory than it should (it uses 5MB).
Alex
After our discussion about uptime over SNMP I poked around a bit.
sysUpTime is indeed in the System MIB (required by all SNMP
implementations), but
mini-snmpd has a bug.
Witness:
root@monitor1:~# snmpwalk -v1 -c public 10.1.1.1 1.3.6.1.2.1.1
iso.3.6.1.2.1.1.1.0 = ""
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1
iso.3.6.1.2.1.1.3.0 = Timeticks: (936051) 2:36:00.51
iso.3.6.1.2.1.1.4.0 = STRING: "info(a)sudomesh.org"
iso.3.6.1.2.1.1.5.0 = STRING: "my.node"
iso.3.6.1.2.1.1.6.0 = STRING: "Omni"
Note the terminating zeros on the OIDs; they shouldn't be there.
1.3.6.1.2.1.1.3 is the correct OID for sysUpTime.
I'll look into fixing it. It looks like memory stats are similarly affected.
Alex
Hey Team,
I set up a "production" exit server on a digital ocean server.
It's accessible at droplet1.sudomesh.org
I think that for the next few weeks when we're setting up test beds, we can
use it for our exit.
Alex, Juul and I have root access. I didn't bother setting up users - if I
do then I'll let folks know.
Max