Classification and shaping are separate functions, and as such Arno and I agree these should be separate plugins.
If Lonnie wants to combine them in Astlinux then that's his prerogative, but making this change upstream to my plugin without asking me is egregious and not consistent with ownership etiquette in Open Source projects. David's best chance of a solution is to RE-MARK the packets, so they are handled properly throughout the network, not just while transiting the Astlinux firewall. Also, the best place to MARK them is on the source host (based on the port #'s). It's trivial to do it there if that host is running linux and has iptables installed. Please back this out upstream. David: please contact the vendor and file an RFE (request for enhancement) that the application generating this traffic mark it properly (as per RFC-4594). If this problem is affecting you, it's probably affecting others that don't have the technical means to work around it. I've slowly been getting patches upstream to Apache, APR, Proftpd, Firefox, Thunderbird, Cyrus, Openssh, Sendmail, Wget, libcurl, etc. to get applications to use the correct settings. This is the end-game. In fact, if you send me the details off-list about the system and app, I might know of a proper fix for you. On 12/1/10 8:40 AM, Lonnie Abelbeck wrote: > Hi David, > > Good question. To be clear, the traffic shaper plugin only effects traffic > traversing the external interface, it has no effect on local to local traffic. > > Given that, you pose an interesting idea, such as adding a traffic shaper > config variable like SHAPER_P2P_LOCAL_HOSTS="", while doable it might offend > the purists, let me consider that. Note this would effect time sensitive > protocols like NTP and such for that IP address. > > As a test, give this a try... > > # remove t443 > SHAPER_BULKDATA_PORTS="t20 t21 t25 t80 t110 t137:139 u137:139 t143 t465 t515 > t993 t8080" > # add t443 > SHAPER_P2P_PORTS="t443" > > And describe any results (privately if you wish). > > Lonnie > > > On Dec 1, 2010, at 8:48 AM, David Kerr wrote: > >> I've been looking at the traffic shaper plugin hoping to improve performance >> of my WAN connection. I can see how to configure it to prioritize traffic >> by port number, but is there a way to have it prioritize by IP address? >> >> What I want to do is designate a particular device inside my LAN as having >> the lowest priority... any traffic to or from it will be prioritized lower >> than traffic to or from any other device on my network. >> >> The situation is that I have a nice shiny new ReadyNAS RAID storage box, and >> I have set it up to backup to an online backup service. There are gigabytes >> of data being uploaded, and while I can throttle the transfer rate in the >> backup s/w, I would like to tell it to use all available bandwidth. When I >> do this other computers on my network suffer noticeably... web sites are not >> as responsive. And things are particularly ugly if I try and connect into my >> LAN from outside. >> >> In the traffic shaper I can see how to manage bandwidth by port number... >> but unfortunately the backup s/w is connecting to port 443 at the offsite >> server, the same as any browser uses for https/ssl pages. So I can't >> prioritize it low without affecting everything else that uses https/ssl port >> 443. >> >> Any suggestions? >> >> Thanks, >> David ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
