To: lartc@vger.kernel.org
Subject: [LARTC] Problems with CBQ.init + aliased IP's
Date: Tue, 21 May 2002 20:38:13 +0000 [thread overview]
Message-ID: <marc-lartc-102201356700612@msgid-missing> (raw)
Hello
I made a set of CBQ rules using the cbq.init script, but i got one aliased
interface eth1:0 that is the gateway for a machine in a subnet...
I put a rule for this machine in the eth1 but seems that CBQ isn't limiting
the traffic for it, and in the config files I can't put eth1:0 as the
interface...
note that there's a route to all traffic going to the especific IP to pass
for the eth1:0 interface.
sniffing the eth1:0 with tcpdump i can see packages going from the net to
the IP, and sniffing the eth0 i can see the packets coming. I manage to
limite the outgoing traffic putting the rule in eth0, but the traffic
incoming to the IP no, because it's exiting by a aliased interface.
There's a solution for it?
[]s
coredump
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-05-21 20:38 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=marc-lartc-102201356700612@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.