Slashdot Mirror

This isn't about quality of the video at all. It's about QOS for video.

This report is what Comcast uses to determine just how much to throttle Netflix to get the most people to come running back to cable but not run afoul of the FCC.

Not sure what you can do with a computer webcam, there's webcam feeds like...

http://www.ciscopress.com/articles/article.asp?p=465446

Or if your one of "those" people

http://en.wikipedia.org/wiki/Lifelog

There's a ton of projects along those lines, webcams don't do much otherwise besides serve their initial purpose.

Donations are another option, so is the trash.

Try the boys and girls club or something along the lines of charity, I've gone this path before for getting rid of old IT equipment.

Routing TCP/IP Volume I (ISBN-13: 978-1587052026) also falls into the "classics" category of Cisco Press.

That's not research, suggest you buy and read this: http://www.ciscopress.com/bookstore/product.asp?isbn=158705115X

Here's an extract, because I'm not lending you my copy, to get you started: http://www.ciscopress.com/articles/article.asp?p=174313&seqNum=4

Also, if you're configuring Cisco kit, as I do, consider adapting Rob's access-list, found here: http://www.cymru.com/Documents/icmp-messages.html

Now refund my cluepon please.

That's not research, suggest you buy and read this: http://www.ciscopress.com/bookstore/product.asp?isbn=158705115X

Here's an extract, because I'm not lending you my copy, to get you started: http://www.ciscopress.com/articles/article.asp?p=174313&seqNum=4

Also, if you're configuring Cisco kit, as I do, consider adapting Rob's access-list, found here: http://www.cymru.com/Documents/icmp-messages.html

Now refund my cluepon please.

I have a lot of respect for Larry Roberts. The idea of only discarding a single packet per flow on a congested interface in order to slow things down is a good one.

If WRED didn't exist on every production-grade router made in the last 10+ years then there would certainly be a need for this technology. However, I'm not really sure how much benefit the "multi-flow fairness" concept would provide vs. just configuring WRED to discard only payload packets & not TCP control traffic. The tradeoff is the added complexity of the congestion avoidance mechanism having to be flow-aware, which increases cost, time to market, heat & power consumption, etc.

Such a technique combined with microflow policing would come closer to what he describes. In fact one could probably refer to the congestion avoidance technique described in the article as "adaptive microflow policing".

A pretty standard config used with OpenBSD's PF firewall is to prioritize ACKs in both directions so that a line congested in one direction is still useful in the other.

BTW, TCP has already been re-engineered; it's called SCTP. If you've got a custom high-bandwidth point-to-point application where you have complete control over both ends (mostly research stuff at this point), check it out.

A different approach to bandwidth management that is being developed by the major router vendors is the application-aware network. Imagine if the router was smart enough to read a field in an XML stream that indicates that this particular flow requires 64kbps or it should be dropped, it should have 256kbps to work well, and giving it more than 1mbps is not useful and you start to get the idea. That's just the tip of the iceberg.

Anyway, congestion control is useful & necessary, but "quality of service is no substitute for quantity of service"...

1000 milliseconds = eons for network traffic.

From http://www.ciscopress.com/articles/article.asp?p=357102

"One-way latency (mouth to ear) should be no more than 150 ms."
"Average one-way jitter should be targeted at less than 30 ms."

"Read Cisco's "Building MPLS-Based Broadband VPNs" if you want a clue on just how bad DOCSIS and DSL are."

Can I borrow $60.00 from you? Or at the very least use your personal information to save to "my account".

WPA IS TOTALLY SECURE AND CAN NOT BE BROKEN WITH

You're fucking retarded. Either ditch the router and use wires, or simply do MAC filtering and watch your logs.

> As I understand it, preshared-key WPA is little or no more secure than WEP. It may depend upon your key.

WEP keys can be discovered by packet collection (one must collect a lot of packets, but once that's done there are tools that make the key discovery trivial) regardless of the complexity of the key.

WPA keys can be discovered with four collected packets and a brute force dictionary tool, if a weak passphrase is used.

WPA-PSK with a strong passphrase greater than 20 characters in length would be a difficult target for which to solve with currently available tools.

Here is a good short read on the topic.

This announcment make make my request pointless but here goes:

I have been thinking about starting up a DSL based ISP and obviously need to have a thorough knowledge of the technology and how to implement it. Finding books\papers that really dig into the topic is darn near impossible. I found this book. Does that book cover the topic sufficiently to let you really implement it or do you know of any better/complimentary books?

Personally, I've found that the 'x for dummies' / 'x for complete idiots' are about as useful as a rudimentary Google search.

I like O'Reilly's "Missing Manual" series, so I'd suggest O'Reilly's Home Networking: The Missing Manual (coming in july 2005).

If you don't want to wait until this comes in print, I'd recommend Cisco's "Home Networking Simplified", which was reviewed on Slashdot a few days ago. From the review:

This is an almost perfect book on home networking for the person who has a Windows computer or two (and nothing else) and knows nothing. It pains me to admit that I have a number of friends who fall into this category and I would have no hesitation in lending them a copy of this book. Given the cost, I'm not sure I'd recommend this book to everyone, but I do feel that it is the perfect volume for the local library; borrowing it for two weeks while setting up the home net would be the ideal solution for people like my mate Tim, who (while a pediatric specialist) has trouble hooking up a router, or the neighbours downstairs who can't properly secure a wireless network.

Table of Contents:

Part II Simple Home Networks
Chapter 5 Creating a Basic Home Network
Planning a Network
Designing Your Network
Building Your Network

How to Build It: Connecting Two Computers
Decide on the Type of NICs
Physically Install the NIC
Internal NIC in a Desktop Computer
Internal PCMCIA NIC in a Laptop Computer
External NIC for a Desktop or Laptop Computer
Configure Windows to "Talk To" the NIC
Build a Network Between the Two Computers
Back-to-Back
Using a Hub, Switch, or Router
Set Up the Network in Windows
Troubleshooting Tips: Building a Network

Chapter 6 Sharing Network Resources
File Sharing
Printer Sharing
Practicing Safe Share
Sharing Guidelines
Network Design Guidelines
How to Build It: File and Printer Sharing
Enable File and Printer Sharing
Share a File Over the Network
Map a Shared File Folder as a Disk Drive
Share a Printer Over the Network
Map a Shared Printer
Add Security Precautions to File and Printer Sharing ...

Chapter 9 - security