I didn't say anything about their tech support, which is "lacking".
Agreed. But then again, the same could be said for anyone who truly needs to talk to Linksys tech support.
While we're talking about Linksys and lacking, what friggin language is the linksys online documentation written in? Engrish? I swear one of these days I'm going to click on "help" and see "HOW ARE YOU GENTLEMAN. ALL YOUR ROUTER ARE BELONG TO US."
And of course, anecdotal evidence in which you compare an aironet sans antennae to a D-Link is clearly irrefutable.
Web administration is great, but it ain't exactly secure. Do a search on vulnerabilities for both cisco and linksys products and you'll find that web administration is not the way to go. If you read the DoD's recommendations for securing routers and switches, they suggest that web administration be disabled right off the bat. I personally wouldn't expect members of the slashdot crowd to get intimidated by a console cable and a command line, but I guess that's a sign of the times.
256 WEP: w00t. WEP is insecure no matter how long the key is. If you send enough data over the airwaves, it will get crax0red, no way around it. Look into LEAP if you're serious about secure wireless networking. Care to guess which company developed it? But don't worry, Cisco is working on standardizing it, so one day maybe D-Link will support it too.
So your customer is running in a multi-homed environment, and they don't implement MEDs to tell their BGP routers to prefer their primary ISP. Yup, it's definitely Qwest's fault that their routing tables are b0rked.
Slashdot Mirror
While we're talking about Linksys and lacking, what friggin language is the linksys online documentation written in? Engrish? I swear one of these days I'm going to click on "help" and see "HOW ARE YOU GENTLEMAN. ALL YOUR ROUTER ARE BELONG TO US."
Web administration is great, but it ain't exactly secure. Do a search on vulnerabilities for both cisco and linksys products and you'll find that web administration is not the way to go. If you read the DoD's recommendations for securing routers and switches, they suggest that web administration be disabled right off the bat. I personally wouldn't expect members of the slashdot crowd to get intimidated by a console cable and a command line, but I guess that's a sign of the times.
256 WEP: w00t. WEP is insecure no matter how long the key is. If you send enough data over the airwaves, it will get crax0red, no way around it. Look into LEAP if you're serious about secure wireless networking. Care to guess which company developed it? But don't worry, Cisco is working on standardizing it, so one day maybe D-Link will support it too.
Oh yah, and the patch would introduce two more security flaws.
And crash the box.
So your customer is running in a multi-homed environment, and they don't implement MEDs to tell their BGP routers to prefer their primary ISP. Yup, it's definitely Qwest's fault that their routing tables are b0rked.
Check here for BGP operation and here for BGP authentication.
They already do that. They're called Autonomous Systems.