From: Supratim Mitra <officeworks.supratim@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB traffic control over VLAN interface.
Date: Wed, 13 Jul 2005 10:39:08 +0000 [thread overview]
Message-ID: <5fea9f54050713032718bf2a84@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]
Hi All,
This is my first mail to the LARTC mailing list.I am having some problems
with the download bandwidth over VLAN.The setup i am having at my place is
somewhat below..
+-------------------+
| |
| FTP Server |
| |
+-------------------+
|
+---------------+ |
| | |
| eth1=|-------+
| My Box |
| eth0=|--------+
| | |
+---------------+ |
|
+----------+----------+-----------------------+
| | | |
vlans -> eth0.1 eth0.2 eth0.3 ................eth0.1001
I am doing some traffic control with my box.It <http://box.It> has got the
phsical interfaces eth0 and eth1.eth1 is connected the FTP server and on
eth0 VLANs are created.It <http://created.It> has the usual tc(HTB) and
iptables rules added for traffic control.
when i am downloading anything over physical interface eth0 without using
any VLAN i am getting the desired download bandwidth with TCP,UDP and
ICMP.The upload bandwidth using the VLAN is desired one.Even the download
bandwidth using the VLAN interfaces with UDP and ICMP is correct.
But the problem arises when i am downloading anything using the VLAN
interfaces with TCP.Its is showing around 180kbps for the alloted 256kbps
and around 350kbps for 512kbps.
Thanking in Advance!
regards,
Supratim
[-- Attachment #1.2: Type: text/html, Size: 4092 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-07-13 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5fea9f54050713032718bf2a84@mail.gmail.com \
--to=officeworks.supratim@gmail.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 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.