From: "bharat merja" <merja@blazenetonline.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Need guide for B/W control based on MAV address
Date: Tue, 17 Apr 2001 12:41:38 +0000 [thread overview]
Message-ID: <marc-lartc-98751063014308@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Dear All,
I have four thick ethernet segments centrally connected to Intel switch. All customers are using DHCP for IP confoguration so IP to MAC address mapping is dynamic. Some of the clients are using proxy at thier end so they are eating big pie of our Internet Bandwidth. I want to restrict those clients to specific limit by using their MAC address.
I am controling bandwidth to some IPS by their FIX IPs, but regarding this dynamic pool I am confused how to do so?
Please guide me how to control bandwidth on BASE of MAC address.
Thanking you in advance.
Regards
Bharat Merja.
[-- Attachment #2: Type: text/html, Size: 1316 bytes --]
next reply other threads:[~2001-04-17 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 12:41 bharat merja [this message]
2001-04-17 17:40 ` [LARTC] Need guide for B/W control based on MAV address Christian Worm Mortensen
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-98751063014308@msgid-missing \
--to=merja@blazenetonline.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox