Slashdot Mirror
OpenWRT 14.07 RC1 Supports Native IPv6, Procd Init System
An anonymous reader writes Release Candidate One of OpenWRT 14.07 "Barrier Breaker" is released. Big for this tiny embedded Linux distribution for routers in 14.07 is native IPv6 support and the procd init system integration. The native IPv6 support is with the RA and DHCPv6+PD client and server support plus other changes. Procd is OpenWRT's new preinit, init, hotplug, and event system.
Perhaps not too exciting is support for upgrading on devices with NAND, and file system snapshot/restore so you can experiment without fear of leaving your network broken. There's also experimental support for the musl standard C library.
I just tried it but something is not working.
# ping6 www.slashdot.org
unknown host
Something is horribly broken here.
That's a feature, not a bug.
Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
Are there tunnel brokers which don't require a WhoIs entry for the tunnel endpoint?
What? No systemd integration?
I just picked it up at a garage sale!
Perhaps not too exciting is support for upgrading on devices with NAND, and file system snapshot/restore so you can experiment without fear of leaving your network broken.
That must be a great thank you to the coder(s) who spent hours and hours implementing those features. :P
It's all modern and D-Bussy and neckbeardy. Why not use systemd since init is old school?
I want to delete my account but Slashdot doesn't allow it.
possible sane systemd replacement in debian and others.
Or perhaps desktop linux keeps bloating up, and we see OpenWRT desktop that replaces Debian/Ubuntu/Fedora.
Maybe here: http://downloads.openwrt.org/barrier_breaker/14.07-rc1/brcm47xx/legacy/
because systemd is not and init system. It's and everything system.
Look at the comparison with procd in the openwrt to get an idea of the unbounded nature of systemd.
systemd is not suitable for and embedded system because it's too fat.
systemd is not suitable for an non-embedded system, because the performance gains over the lighter alternatives are insignificant on a desktop system.
The big question... is there any remotely-mainstream 802.11ac router for which OpenWRT actually has non-broken 5GHz, beamforming, or any other advanced wi-fi feature? Or are we basically still stuck having to buy two routers... an open one running OpenWRT for routing (and other embedded-level networking tasks), and a proprietary one running stock firmware for non-dysfunctional 802.11ac? I want to use OpenWRT. Really, I do. But every time I'm in a mood to try it, I look at the litany of horrors in the "known bugs" list (or complaints on various forums that usually have "minor" bugs like "5GHz doesn't work" or "wifi randomly quits working after a day or two".
I have been running native ipv6 and whatever other modern stuff on my ASUS RT-N16 via TomatoUSB for many years.
So uh... What took you dorks so long?
complaints on various forums that usually have "minor" bugs like "5GHz doesn't work" or "wifi randomly quits working after a day or two"
Just to prevent people from getting the wrong idea -- OpenWRT is fully functional and rock solid on a lot of 802.11n hardware (including 40MHz support). I haven't played with 802.11ac yet.
I've been eying this myself, since I would like to upgrade my card to 802.11ac at some point as well. There are two pieces to the puzzle, user space support, and kernel driver support. AFAIK, both are supported but you need fairly new software. The ath10k driver supposedly supports 802.11ac and was included in linux 3.11. I believe newer versions of hostapd support 802.11ac but can't find any specifics about what version it was included in, but the newer the version, the better (so, preferably 2.2). And of course you will need to find a wireless card that uses the ath10k driver. I run my router off a normal PC and have a distro with recent software so this is easy to do, but I have no idea what versions OpenWRT supports.
According to this everything should work: http://wireless.kernel.org/en/...
But according to this there are mixed results: https://forum.openwrt.org/view...
Because most ISPs still haven't gotten their act together with IPv6, and many of the ones that have would rather outsource the tunnel function rather than run it themselves. And one of the biggest hurdles toward doing IPv6 (besides getting decent performance out of the bigger network equipment) is replacing all the cable modems / DSL routers / etc. that don't support it adequately.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
I pushed my router to dd-wrt a while ago. At the time, I liked the UI on dd-wrt better than openWRT. I also noticed some issues on my specific hardware for OpenWRT. How do they stack up?
Unfortunately, some common routers contain a buggy early revision of the QCA9880 802.11ac chip that's not supported by ath10k and never will be.
I have had a TP-Link WDR3600 for about 7 months. About 4 months ago I decided I wanted to start doing ipv6 and the TP-Link software didn't work with Comcast for ipv6. I found a pre-release of Barrier Breaker loaded it up, rebooted and it all worked. I guess it is time to upgrade to the release candidate. There were some issues with the second radio and supporting 802.11an but a few minutes searching on line and I had fix for that too.
Beamforming? 4x4 MIMO? 802.11n hand-offs from AP to AP as you walk down the stairs & your downstairs AP router comes into view with a stronger signal? OK, I'll admit, the last one is a feature that I'd bet 97% of the people reading this didn't even know has *existed* since 802.11n came out... and fewer still have ever gotten to actually work with *any* firmware, stock, open, hacked, or otherwise. But it's a feature I care about, because I have too many adjacent neighbors to use 2.4GHz (downstairs, I have 6-8 SSIDs in view... upstairs, I have about 14), and 5GHz has utterly SHIT propagation between my upstairs and downstairs (mostly, because my first floor's ceiling/second-floor's floor is a suspended concrete slab cast in place on steel pan decking that acts like a big Faraday cage).
How does the native support look on the official IPv6 compliance tests at TAHI?
Not everyone wants DHCP at home, when router advertisements and automatic addressing are as good or better. How does this look?
Does the router support Mobile IP?
Are there any disabled kernel options relating to the protocol?
How does it fare on IPv6 NAT?
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
I think it's also worth mentioning that this release supports DNSSEC validation. That's a bigger deal than the IPv6 support in my book, especially since it already supported IPv6 it just required knowledge to configure.
The Information Revolution will be fought on the command line.
Someone? Anyone? Bueller?