There's a lot of multipath-related work being done right now, at the IETF, within OpenWRT, and independently.
We've been working on providing multiple routes automatically (disclaimer -- I'm a co-author). As to actually making use of the multiple routes, the solution that currently works best is MP-TCP, a set of kernel patches that allows TCP to use multiple routes simultaneously, with no modification to applications. Other solutions are SHIM6, which works below the transport layer, and Multipath Mosh, which works at the application layer.
I'm pretty confident we'll be able to have most of this stuff enabled by default in mainstream Linux distributions by the end of the year.
I got yelled at for recommending to my students to buy the course text online vs. going through the bookstore ($40-$60 bucks vs $250 at the bookstore for the same text).
Getting yelled at by stupid or corrupt administrators is part of the job.
College isn't about learning anymore, it's all about making money.
College is what the lecturers and the students make it. If you've got tenure, then you're pretty much untouchable, precisely so that you can take a stand without fear of the repercussions. (Of course, if you haven't got tenure yet, then tread carefully.)
Yeah, what I'm saying is we have been able to do exactly that (web configuration) with the various TomatoUSB modded firmwares for years along with a bunch of other stuff (VPN, etc).
Proxy-ND? Stateful DHCPv6? Somehow I doubt it.
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?
They're very different beasts.
DD-WRT is a single, monolithic image, similar to a vendor firmware but with more features. What is available tends to be well integrated into the GUI, but if a feature is not available, you're pretty much out of luck (unless you're willing to install software by hand).
OpenWRT, on the other hand, is a package based system: there's a base system and an extensive set of optional packages that you may install. It used to be the case that the OpenWRT GUI was not very good, but it has improved a lot in recent years, and I now find it fairly usable. Of course, not all packages are well integrated with the GUI.
I'd recommend going with OpenWRT. The base system should be reasonably easy to understand, and you'll be able to easily install extra software when you find that you have unusual needs.
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.)
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.
Maybe it's just because I'm unfamiliar with MathML, but this seems like a *very* verbose way of writing equations.
Yeah, it's pretty horrible. The only way to write (presentation) MathML is to generate it automatically from a sane input format, either a GUI or something like LaTeX.
We'd still deal with the inconvenience if it were universally supported by browsers -- but 15 years after MathML was conceived, it still isn't.
We've been waiting for math rendering support in HTML for slightly over 15 years (MathML came out in 1998, and there was HTML 3 math before that).
We've given up. Both the scientific and the higher education communities are using PDF almost exclusively, and our respective userbases (fellow scientists and students) have accepted PDF as the format of choice. At the same time, PDF support in browsers and on tablets has become good enough to make that a reasonable proposition.
But yeah, let's write blog postings about why MathML is not dead, it only smells funny.
This is an individual submission, not an IETF working group draft, and does not appear to either be proposed for an IETF wg draft or to be in the RFC Editor's queue. In short, it has nothing to do with the IETF.
only members of parliament can be ministers of Her Majesty's government.
Nonsense. The prime minister (who doesn't necessarily have to be an MP either) chooses his cabinet.
Wikipedia has been known to be wrong before, but it appears to confirm what I've always been told:
The Government Ministers are all members of Parliament, and are accountable to it.
For most senior Ministers this is usually the elected House of Commons rather than the House of Lords. There have been some recent exceptions to this [...]
I'd love to hear otherwise from a reliable source.