Oakland's Sudo Mesh Looks to Counter the Digital Divide With a Mesh Network
techpresident.com
techpresident.com
They reference the RedHook (Brooklyn) project in the article which was an inspiring attempt - especially in how they got local help for installation and maintenance. I am not sure how that project is going as the blog does nto have a lot of recent updates http://rhicenter.org/
I volunteer for a meetup based project in my home town which is having a hard time getting roof access for the network. In my limited experience it seems the biggest obstacles are not tech problems but NIMBY.
Meshnet is a great idea - one of these days it will break through. It is exciting to see these projects
It's trivially easy to detect this kind of TOS abuse, even if the traffic is encrypted.
I'm all for the creation of bypass networks but suggesting that connecting those networks to a cable modem connection is just going to end badly.
It is? How? How could you possibly differentiate traffic coming from a single household with high bandwidth usage and a single person sharing their connection if it's all tunnelled over a VPN?
Like I said, trivial.
For the VPN, choose a fixed packet size, and maximum bandwidth in packets per second (evenly spaced "ticks"). Every tick, if there is a packet waiting to transmit, send it with padding to the max size. Otherwise, send a dummy packet that is discarded by the remote.
That's right telcos - we can reinvent circuit switching too!
Because people have known about padding for a while and yet we still have methods to de-anonymize TOR networks. When you use those techniques on a minor mesh network like this, it's an order of magnitude easier.
Keep in mind that the cable company or broadband provider doesn't have to have much in the way of proof, just a suspicion and your connection will be terminated.
> broadband provider doesn't have to have much in the way of proof
This pretty much goes for any software that doesn't just visit Facialbook et al. Barring any sort of public utility regulation, the only way to push back against that is to get software widely deployed.
Similarly, port number and usage can also be an easy tell when you see sockets opening on a pattern like this over time: [ ..., 15001, 15002, 15005, 9004, 9005, 15006, 9006, ...]
Often IPmasq/NAT doesn't help either, as it can exhibit its own distinct pattern of port/etc usage often due to how router maintains its statefulness.
[1] http://lcamtuf.coredump.cx/newtcp/ At least we're improving with more randomness - the old version this paper ( http://lcamtuf.coredump.cx/oldtcp/tcpseq.html ) shows how bad it used to be, with some vendors exhibiting very reliably non-random patterns.
Isn't Comcast currently loudly trumpeting the fact that they are -- as a condition of approval of a merger -- bound by the terms of the FCCs 2010 Open Internet Order (even though that Order was later struck down as generally-applicable regulation) which prohibits protects the right of consumers to send any lawful traffic without blocking or discrimination?
I hope the noisebridge reboot can bring them in to this territory of Getting Shit Done.
One side note, there is already 2 wireless ISPs in san francisco. The very-corporate WebPass and the super-hackery monkeybrains.
The latter folk are awesome, overworked but deliver exceptional ISP value!