From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] traffic shaping with 2 class c's
Date: Mon, 08 Jan 2001 15:26:39 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416835@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416834@msgid-missing>
<PRE>On Mon, Jan 08, 2001 at 09:08:10AM -0600, Chris Glanzer wrote:
><i> Hello, I really appreciate this site. Finally, there is updated info on cbq
</I>><i> and people with knowledge to back it up - - Thanks
</I>><i>
</I>><i> Here is my situation,
</I>><i> I am at a college with a single 512k line for 450 machines. Our servers and
</I>><i> fac/staff are on C class x.x.166.x and all students are on C class x.x.167.x
</I>><i> . Currently, a few student machines are monopolizing our connection for
</I>><i> napster and make business related telnet painfully slow (all telnet is
</I>><i> pointed at the same server off campus.)
</I>
><i> 1.) I wanted to make sure that it was possible to have 2 C class addresses
</I>><i> behind IProute2.
</I>
Of course.
><i> 2.) Would it be possible to limit napster on a per-session basis and also
</I>><i> have a combined limit?
</I>
Not sure. I think napster *traffic* looks like http. Also, I'm not sure if
you can limit per tcp session.
><i> 3.) Currently, we are not supporting DCHP and I do not have the resources to
</I>><i> change the gateways on all machines. Would that be needed? The current
</I>><i> router/gateway is x.x.166.254, it would be possible for me to add an
</I>><i> additional IP address to it. This is probably my biggest concern, since I
</I>><i> want to maintain all my current, real IP's.
</I>
If your router is already Linux, I don't see any problem.
Regards,
bert hubert
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
next prev parent reply other threads:[~2001-01-08 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 15:08 [LARTC] traffic shaping with 2 class c's Chris
2001-01-08 15:26 ` bert [this message]
2001-01-08 15:40 ` alex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-98373940416835@msgid-missing \
--to=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.