All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] ip alias question
Date: Thu, 06 Mar 2003 01:37:23 +0000	[thread overview]
Message-ID: <marc-lartc-104691432214323@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104689471923894@msgid-missing>

AFAIK, tc works on physical device queues. Thus having virtual devices
over the same physical interface will not let the virtual devices be
freed of control. You must use src/dst options. Instead of attaching to
virtual devices, it might be better to do it using subnets whereby you
do not have to give too many rules for matching src/dst ips.

Mohan

-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of Gilles Dégottex
Sent: Thursday, March 06, 2003 12:05 AM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] ip alias question


Hi all

	Sorry if i didnt found the answer in HOWTO's, mailing lists
archives or any 
other place. and sorry if i write english like a spanish cow :P

	I'm currently using 'tc' to limit upload and stop breaking the
connection of 
my cable modem. my eth0 has an ip alias eth0:1 which should not be
limited by 
tc, but "tc qdisc add dev eth0" seems apply effect to eth0 AND eth0:1 :(
	Is there any smooth solution to leave eth0:1 in peace ? or do i
have to limit 
effect with "ip src" and "ip dst" ?

Regards,
Gilles Dégottex
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-03-06  1:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 18:34 [LARTC] ip alias question Gilles Dégottex
2003-03-06  1:37 ` S Mohan [this message]
2003-03-08 19:41 ` Gilles Dégottex

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-104691432214323@msgid-missing \
    --to=smohan@vsnl.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.