Slashdot Mirror
Time To Cut the Ethernet Cable?
coondoggie writes in with a Network World piece that begins "A range of companies with wireless LANs are discovering that 50% to 90% or more of Ethernet ports now go unused, because Wi-Fi has become so prevalent. They look at racks of unused switches, ports, Ethernet wall jacks, the cabling that connects them all, the yearly maintenance charges for unused switches, electrical charges, and cooling costs. So why not formally drop what many end users have already discarded — the Ethernet cable? 'There's definitely a right-sizing going on,' says Michael King, research director, mobile and wireless, for Gartner. 'By 2011, 70% of all net new ports will be wireless. People are saying, "we don't need to be spending so much on a wired infrastructure if no one is using it."' ... There is debate over whether WLANs, including the high-throughput 802.11n networks, will be able to deliver enough bandwidth." Cisco, which makes both wireless and wired gear, has a spokesman quoted calling this idea of right-sizing a "shortsighted message from a wireless-only provider. It's penny-wise and pound-foolish."
And while you can have hundreds of parallel Gbit/sec cables running through the same building, each running at maximum speed, you can not have hundreds of parallel 802.11n-accesspoint each reaching maximum throughput at the same time.
Not only half duplex, but as you say in your post title (not the text), the resources are shared between all users within a physical area. Aggregate throughput drops quickly as the number of users on a WLAN increases.
If we replaced our copper connections with WLAN at my company, the network would become effectively useless. Too many users.
Another way to think of it is: For a typical user, even a 100Base-T wire to a switch will match even the latest and greatest MIMO high speed implementations (advertised 270-300, but in reality you'll be lucky to see 100 Mbps real world in a single direction).
Once you go above 2-3 users, the switch connections win hands-down.
Add gigabit into the mix (cheap nowadays) and wired wins by an even greater margin.
retrorocket.o not found, launch anyway?
Steps to break a wireless network:
#1 - Pull up to parking lot. ...
#2 - Sniff advertised name of network
#3 - Put up your AP, set name to clone network's name
#4 - Record authentication attempts
#5
#6 - Profit!
If you can get access to a wired network; then you can plug in a WAP with your own encryption. Most companies don't question who is roaming around.
It is a question of series vs. parallel. Any sort of wireless connection is going to be shared by multiple people using it in a serial fashion. This means that Ann can't send while Fred is sending. Period.
OK, if you have Ethernet cables running to both Ann and Fred then they can, absolutely both send at the same time. With switches linked by fiber and where everyone isn't banging on the same server you often acheive parallel communications all the way through the system.
If you are posting on Slashdot or reading email it may not make a big deal. Moving large files around, interacting with some remote graphic intensive application or just doing "office work" with lots of transactions can make this seems like a really silly idea.
Sure, wired connections are expensive to run and they shouldn't be run except for productivity or security. In my company, both of these are considerations and it would be unthinkable to rely on wireless.
1. Apparently you don't know why the pairs are twisted.
2. The very little incidental radiation from the signal cannot be reliably read as far away as a Wifi signal can.
Learn a thing or two or stfu.
Assuming we're talking a modern encrypted network, #5 is going to be hard to work out. The handshake algorithm is no longer vulnerable to replay attacks, so I'm not sure what you plan on doing with your recorded authentication attempts.
The enemies of Democracy are
This is false.
Wireless does not require authentication. It only has authentication if you configure it with WPA/WPA2 and RADIUS. This is called 802.1x or EAP. In fact, you can configure your wired switches with 802.1x and RADIUS and get the same result, no connection without authentication. Just because many places do not use 802.1x on their wired LAN doesn't mean it isn't there.
Also, if the encryption is broken with wireless, I believe you can "listen" to the traffic from the other wireless clients and use that to steal information(I am almost certain this is the case with pre-shared keys, but I am not so sure with WPA/WPA2 RADIUS). With wired, even unencrypted, you can only listen to network traffic that is broadcast or directed to your MAC address. There are attacks where you can convince other computers that you are the router or you can DoS the switch into hub mode, but those attacks can be tricky to pull off and may depend on the network equipment used.
Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
You've just made a serious breech of Slashdot protocol. You shouldn't post AC, when your comment would be modded funny..
Last time I checked, Funny gave no karma, and Overrated took away karma. So if moderators go into a Funny/Overrated mod war over a comment, the poster loses karma rapidly. Such mod wars have brought users from Excellent (posting at 2) down to Terrible (posting at -1) in one day.
On the wireless Internets, there are no tubes, so there are no tubes to get clogged.
The tube from the antenna to the AP that gets clogged more easily than the tubes on a wired switch. But residential Internet service is even easier to clog than the antenna tube.