I just sent an email to the reporter from NewsPressNow who posted a typical net neutrality story. A flaw in this kind of reporting is the tacit acceptance of an ISP’s blandishments that the Internet was fine before the 2015 FCC rules, and that “… And I don’t know if you’d find anyone who said
Update – November 2017: Added descriptions for the other tools I had investigated. Now that LEDE Project has an official release, I hungered for a way to see what kinds of traffic is going through my network. I wanted to answer the question, “who’s hogging the bandwidth?” To do that, I needed a Netflow Collector.
The Battle for the Net site https://www.battleforthenet.com/ no longer seems to have the telephone form(!) But… Boing Boing does. Go to https://boingboing.net/. You’ll see a popup window with a place to enter your phone number. Click OK, and they pop up a script on-screen. They call you, you answer, then you supply your zip code.
Although I usually agree with him, one of my favorite bloggers, Dave Winer, recently said this: One of the ideas circulating is that your ISP has a monopoly, owns the only way for you to get to the Internet, but that’s an old idea, it’s no longer true. Where I live the wireless vendors are
Hat tip to Ro Khanna (@RoKhanna on Twitter) for this… A Portugal ISP (with no net neutrality constraints) appears to be charging 4.99€ (about US$5.86) per month for access to social media. And another 4.99€ for streaming video (Youtube, Netflix, etc). Oh, and another 4.99€ for streaming music. And additional charges for other kinds of
DRY – Don’t Repeat Yourself – is it relevant for documentation? I recently saw this comment on a forum… I’m not sure how useful it is to remove duplication [from the documentation pages]. It’s not code… IMHO, duplication in documentation is a couple orders of magnitude worse than duplication in code (and duplication in code
[Part of the series of blog postings on Netflow] Netflow is a network protocol invented by Cisco that provides granular visibility on network utilization. Routers and switches send (“export”) Netflow datagrams that summarize traffic through them to a Netflow Collector program that displays the data. This gives visibility into “who’s using the network?” Virtually all
[Part of the series of blog postings on Netflow] A lightweight Netflow collector and web display based on NFSEN/NFDUMP in a Docker container. NFSEN and NFDUMP are documented and hosted at SourceForge.net This container listens on ports 2055, 4739, 6343, and 9666 for netflow, ipfix, and sFlow exports. It displays the collected data in a
[Part of the series of blog postings on Netflow] Webview Netflow Reporter is a lightweight Netflow collector and web display tool based on wvnetflow and flow-tools in a Docker container. Webview Netflow Reporter was created by Craig Weinhold firstname.lastname@example.org. The original wvnetflow site is hosted at SourceForge.net. The Dockerfile is available from Github. Pros Pretty