Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Amahi Linux Home Server 4.2

Matthias Ettrich Receives German Federal Cross of Merit

Using Windows Is Like...

Installing Ubuntu 9.10

Hands-on: OpenMoko WikiReader is simple, appealing

Perl far from dead, more popular than you think

Microsoft Exchange alternatives

Kubuntu 9.10: A Mixed Bag

Could Microsoft switch to Linux?

Red Hat Virtualization Manager for Windows Only?




Systems Implementation Engineer II – Disk-Based Back-Up/Replication/RedHat Linux (PA)
Next Step Systems
US-PA-Philadelphia

Justtechjobs.com Post A Job | Post A Resume
:ImageStream: Who Needs to Read Encrypted Traffic?
ImageStream: Who Needs to Read Encrypted Traffic?
Nov 14, 2008, 20 :03 UTC (1 Talkback[s]) (3272 reads)

(Other stories by Alex Goldman)

"PUFQ depends on LinuxIMQ. "Linux IMQ is a virtual network device that can be used to queue packets" says Utter. "First, the PUFQ methodology classifies high-priority traffic using IP tables, and marks each packet so later stages will know how to properly prioritize each packet. Then the traffic is redirected to the PUFQ and non-PUFQ paths based on the rule set for IP blocks or other parameters."

""The PUFQ path splits the traffic into separate rate-limited queues for each user," says Utter. "Then the packets are forwarded through a high priority or low priority queues based on the priority mark. The packets return to the normal routing path until they are ready to be forwarded. Then on the exit path, PUFQ traffic is separated into high and low priority queues again. It is at this point where the high and low priority traffic can be rate limited on an aggregate basis if needed."

Complete Story

Related Stories:
Budget Fair Queuing IO Scheduler(Apr 17, 2008)
Linux on a Mikrotik 532a, Part 4 - Traffic Shaping, Firewall(Oct 13, 2008)
DNS Hijacking, ISP Packet Modification, Morals and Privacy(Oct 01, 2008)
Bandwidth Limiting HOWTO with Linux, tc and iproute2(Sep 24, 2008)


Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat  
  Talkback(s) Name  and Date
yep, The Owner Classes are hard at work  ...   Freedom   
Neo
Nov 14, 2008, 20:59:02
 
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Reprints, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs