[squid-users] Can Traffic Management Settings be configured for other TCP protocols?

[J Green]

Re logging, does this eventually get logged by Squid, somewhere?

For this implementation, I was going to use pfSense.  Turns out that Sarg
is no longer included in the package list for pfSense (current version).



On Tue, May 10, 2016 at 2:43 PM, J Green <corpengineer at gmail.com> wrote:

> Very interesting, thank you both.
>
> On Tue, May 10, 2016 at 2:23 PM, Yuri Voinov <yvoinov at gmail.com> wrote:
>
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>>
>> 11.05.16 2:57, Eliezer Croitoru пишет:
>> >
>> > Hey,
>> >
>> >
>> >
>> > You can always use a TOS from squid to mark connections and\or users
>> and to somehow create some policy case on that.
>>
>> Sure, Eliezer. I've forgot about TOS. Good point.
>> >
>> > I have used more then once the Linux "tc" to "jail" a user which was
>> abusing his unbound bandwidth policy.
>> >
>> > I do not like the idea but I have asked couple networking experts about
>> the most used approach compared to the most efficient and it's seems pretty
>> reasonable from the business aspect of networking to slow(not hog) a user.
>> > Specifically there are places which defines the Internet as a WEB only
>> ie port 80 and 443 and for HTTP only traffic.
>> >
>> > For these purposes squid is great while there are other approaches to
>> the subject.
>> >
>> >
>> >
>> > Eliezer
>> >
>> >
>> >
>> > ----
>> >
>> > Eliezer Croitoru <http://ngtech.co.il/lmgtfy/>
>> <http://ngtech.co.il/lmgtfy/>
>> > Linux System Administrator
>> > Mobile: +972-5-28704261
>> > Email: eliezer at ngtech.co.il
>> >
>> >
>> >
>> > *From:*squid-users [mailto:squid-users-bounces at lists.squid-cache.org
>> <squid-users-bounces at lists.squid-cache.org>] *On Behalf Of *J Green
>> > *Sent:* Tuesday, May 10, 2016 8:42 PM
>> > *To:* Yuri Voinov
>> > *Cc:* squid-users at lists.squid-cache.org
>> > *Subject:* Re: [squid-users] Can Traffic Management Settings be
>> configured for other TCP protocols?
>> >
>> >
>> >
>> > That is fair, re intended use.  But yes, management want to know if
>> users are attempting to circumvent policy.  Re analyzing logs, I did not
>> see this logged anywhere.  Is there perhaps a debug mode which I need to
>> enable?
>> >
>> > Thank you.
>> >
>> >
>> >
>> > On Tue, May 10, 2016 at 10:29 AM, Yuri Voinov <yvoinov at gmail.com
>> <mailto:yvoinov at gmail.com> <yvoinov at gmail.com>> wrote:
>> >
>> >
>> > First, upload is PUT method usage. Most common HTTP/HTTPS is GET/HEAD
>> methods.
>> >
>> > Second, logging of all things is not my goal.
>> >
>> > For me, it is sufficient that the restrictions imposed by me in
>> accordance with the policy. The amount of downloads for my count analyzers
>> logs, if management is interesting to read the reports independently.
>> >
>> > 10.05.16 23:25, J Green пишет:
>> > > So back to the intended use cases for HTTP, HTTPS, & FTP , how can
>> you log violations of maximum download/upload size?  I see an error message
>> generated on the client system, but not w/in Squid.  Thank you.
>> >
>> > > On Mon, May 9, 2016 at 10:12 AM, Yuri Voinov <yvoinov at gmail.com
>> <mailto:yvoinov at gmail.com> <yvoinov at gmail.com> <mailto:yvoinov at gmail.com>
>> <yvoinov at gmail.com> <mailto:yvoinov at gmail.com> <yvoinov at gmail.com>>
>> wrote:
>> >
>> >
>> > > Squid is not a proxy server every imaginable the TCP-usage protocol.
>> >
>> > > AFAIK HTTP/HTTPS/FTP. That's all, folks.
>> >
>> >
>> > > 09.05.16 23:07, J Green пишет:
>> > > > Hello all:
>> >
>> >
>> >
>> > >       > Can Traffic Management Settings be configured for TCP
>> > >       protocols other than HTTP?
>> >
>> >
>> >
>> > >       > Would like to limit maximum upload and download sizes for
>> > >       other TCP protocols:  SMB, NFS, FTP, and RDP.
>> >
>> >
>> >
>> > >       > Is this possible?  If so, how?
>> >
>> >
>> >
>> > >       > Thank you.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > >       > _______________________________________________
>> >
>> > >       > squid-users mailing list
>> >
>> > >       > squid-users at lists.squid-cache.org
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> >
>> > >       > http://lists.squid-cache.org/listinfo/squid-users
>> >
>> >
>> >
>> > >     _______________________________________________
>> > >     squid-users mailing list
>> > >     squid-users at lists.squid-cache.org
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> <mailto:squid-users at lists.squid-cache.org>
>> <squid-users at lists.squid-cache.org>
>> > >     http://lists.squid-cache.org/listinfo/squid-users
>> >
>> >
>> >
>> >
>> >
>> >
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>>
>> iQEcBAEBCAAGBQJXMlFEAAoJENNXIZxhPexGO6AH/RsDrJKihobs93E9OLhT7uuB
>> 6KjX5eSfcNzYmTX1QsTn4SDf2l3HaItZ5jPuSFGSBMTuGo0RaHc0Y+YIcRO8CuOG
>> PQDBPXff2Vg16o06Ty78XLUAfWUr1q4uu6G5Vp8F2cLWSjk7thuFu9XoYe5Q2z1V
>> yN99aV/Kol+Om//eSPOf3hre3ONYRFn2lR+GJET9QNfogiRakpFOzeeGp3fXQgzA
>> S6n2MfhyhYRO3lDtjGcrWDoR5Tz8OdKlReuwHqtkuQi/OA95O9CpfwnEnORGLVN6
>> G4H0pG7MrXBbl5zRhspkr9BNvtunkFsSnUlcUhBtKj1RhsC7H9g7lvkE8QKphIU=
>> =kDA0
>> -----END PGP SIGNATURE-----
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160516/7453c891/attachment-0001.html>