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.
Presumably people need to know version number. I think one of the big problems with the original wrt54g is network throughput. With cable services regularly hitting 50Mbps+ mine can't really cope - even on the wired connections.
So, a question for those of you running openWRT or similar, which not too expensive router would you recommend to replace my decade old wrt54G?
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.
TP-Link routers are cheap and well supported by OpenWRT. At the low end, the TL-WR841N can easily route 50Mbps WAN to LAN and costs just $20.
Mine is a TPLINK WDR3600. Simultaneous dual-band, gigabit everything, 2 USB ports, and even a real power button (!). It's been running "ATTITUDE ADJUSTMENT (12.09, r36088) " for a little more than a year and it's great.
I've been very satisfied with my Netgear WNDR3700 (gigabit, dual band, USB, etc.) to the point where I'll almost certainly get a Netgear when I replace next year (to move to AC). I have been running various svn checkouts of OpenWRT over the last 3+ years and haven't had many problems (and those I did encounter would have been avoided if I stuck to the formal releases).
Sadly, PS/2 was yet another victim of USB, which doesn't care what you plug into it, the electrical slut.
Personally I wish its death would be fast and painful. that way i don't have to deal with it as long.
---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
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?
OpenWRT has had support for native IPv6 for as long as anyone can remember. However, the support wasn't native, in the sense that it required some knowledge to configure properly.
With the current trunk (and this snapshot), you can configure things like DHCPv6 prefix delegation, DHCPv6 relaying, proxy-ND and so on over the web interface -- and it just works. (Famous last words.)
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?