From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Where have my all my TC filters gone??
Date: Fri, 05 Dec 2003 03:25:25 +0000 [thread overview]
Message-ID: <marc-lartc-107059517623088@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107057513904348@msgid-missing>
Hi there Robert,
: I have snipped out part of a script to load balance and bandwidth shape
: upload traffic to a NIC (eth0/ETH_WAN) on a 2mbit/256kbit ADSL line.
: The balancing will be carried out for 3 users with 1+ PCs connected on
: another NIC. There are iptables instructions (not shown in the script)
: to mark packets based on PORT and TOS. These are snipped as the marking
: appears to work its just the TC FILTERs that just disappear :-(
They should be there.....the command you posted just doesn't ask the
kernel the question which would show your filters!
: Stef (or anyone else :-) can you please explain why:
:
: # tc filter show dev eth0
: #
Try "tc filter show dev eth0 parent 1:1" and "tc filter show dev eth0
parent 1:10". This should present you with your filters.
: shows no filters are in place on eth0 after running the script below???
If no handle in particular is specified in the "tc filter show dev $DEV"
command, then the default (root) handle "1:0" is displayed.
: Is this a problem with having a 2-level deep HTB class tree?? When my
: HTB tree is only 1 level deep the TC filters get fed back properely
: with the above command!!
:
: BTW I don't get any errors when running the script from a CLI.
[ snipped stuff ]
: tc filter add dev $ETH_WAN parent 1:1 protocol ip prio 1 u32 match ip src ${ROB_IP} flowid 1:10
: tc filter add dev $ETH_WAN parent 1:1 protocol ip prio 1 u32 match ip src ${DAVE_IP} flowid 1:20
: tc filter add dev $ETH_WAN parent 1:1 protocol ip prio 1 u32 match ip src ${MIKE_IP} flowid 1:30
Here you'll see that your script is attaching these filters to handle 1:1,
and below
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 1 handle 1 fw classid 1:11
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 2 handle 2 fw classid 1:12
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 3 handle 3 fw classid 1:13
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 4 handle 4 fw classid 1:14
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 5 handle 5 fw classid 1:15
: tc filter add dev $ETH_WAN parent 1:10 protocol ip prio 6 handle 6 fw classid 1:16
your script attaches these filters to 1:10! This means that you'll only
be able to see them if you explicitly list the filters attached to this
handle.
This doesn't really solve your problem, though....in order to solve your
problem, (I think) you should be able to alter the handle on all of your
"tc filter" statements to "1:0". Then try running your script again.
That should put you much closer to your goal.
Good luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-12-05 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 21:51 [LARTC] Where have my all my TC filters gone?? Robert Walker
2003-12-05 3:25 ` Martin A. Brown [this message]
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-107059517623088@msgid-missing \
--to=mabrown-lartc@securepipe.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.