[LARTC] re: keeping up with file sharing programs
On Thu, 2002-10-10 at 02:02, Don Cohen wrote: > I have a different proposal. > I think you should use ESFQ, always based on the internal IP address, > i.e., in the outbound direction base it on source, inbound use dest. I do like that ESFQ supports flows based on IP. However, Alex says in http://mailman.ds9a.nl/pipermail/lartc/2002q2/003963.html that it's poorly tested and to expect b00ms. My environment is production, so I'm a bit tentative to install something like this. Can anyone here tell me what their experiences with ESFQ have been like? Cheers, Jason. -- Jason Tackaberry :: [EMAIL PROTECTED] :: 705-949-2301 x330 Academic Computing Support Specialist Information Technology Services Algoma University College :: www.auc.ca ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
[LARTC] re: keeping up with file sharing programs
I have a different proposal. I think you should use ESFQ, always based on the internal IP address, i.e., in the outbound direction base it on source, inbound use dest. (This is to separately share upload and download bandwidth.) That means that someone trying to use small bandwidth will get it right away while those trying to use a lot will have to share it equally with others. I'm not optimistic about the other schemes that have been suggested: - identify good ports Then people will start using those ports for the bad stuff. - identify bad ip addresses Then people will go around borrowing each others computers - even a separate class for the residence halls Then people will go to the academic buildings to use the computers there. At a college I'd even expect that faculty members would let students borrow their computers, so there's not even much point to giving faculty a separate class. It's true that this might cause trouble for people trying to do large downloads of important stuff. But are you supposed to know which stuff is important? When people claim that what they're doing is important you can put them in the important class and tell all in that class who the others are and that they're competing with each other - so complain to each other before they complain to you. In fact, I'd try to monitor the usage of such people and distribute the results to them all, so they know who to blame. When people complain about others whose stuff they think is not really important you can let some higher academic authority make the call. ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
