Introducing 802.11s - Wireless Mesh Networking
ikewillis writes "Intel has introduced a new wireless networking standard called 802.11s. This standard utilizes a mesh topology, allowing for fully self-configuring networks where each node can relay messages on behalf of others, thus increasing the range and available bandwidth with the number of nodes active within the system, versus the point-to-point structure of existing WiFi networks. This will radically transform WiFi hotspots, allowing the geographical area and available bandwidth on the network to scale with the number of participants."
where do they get all these letters from? There seems to be 802.11b, 802.11a, 802.11g and now 802.11s, and I have no idea why the letters are what they are. Anyone care to explain?
once you get licenses in the picture, you disempower the smaller entities and empower the larger entities. And I think that most Americans are starting to see that whenever larger entities gain power over small entities and citizens, then things start to go sour...
eat shiat and bark at the moon
Set up enough of these, and you could do your own neighborhood network...
Could this jump-start the "freeweb" movement, particularly since the telcos are lobbying and pushing to kill the muni wireless attempts?
Let's get the entrepreneurs and the networking hippies on the same "frequency."
You can't talk about Wikipedia's flaws on Wikipedia
For example, no one has given a MAC protocol that solves the hidden/exposed sender/receiver problems simultaneously. Without such a MAC protocol, it is impossible to resolve the contention fairly. 802.11 DCF solves hidden and exposed sender, but not receiver.
Also, Gupta and Kumar showed that the per-node bandwidth in a wireless mesh with random node placement is O(1/sqrt(n)). This is especially bad news for the sort of nationwide wireless meshes people have been talking about here.
Finally, TCP is especially problematic over multiple wireless hops. It causes self-interference which creates massive packet loss due to contention. TCP is built on the assumption that all packet loss is from congestion, but this assumption is not met by wireless contention losses.
In my own simulations, TCP's overaggression causes routing packet losses, creating spurious route breakage and even more TCP timeouts.
Shockwave Flash movies are the greatest thing to happen to non-sequitur humor since Japan.