From: David Watson <David.Watson@team17.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Routing based on fwmark
Date: Tue, 04 Mar 2003 18:27:29 +0000 [thread overview]
Message-ID: <marc-lartc-104680270328524@msgid-missing> (raw)
I'm having trouble routing on high fwmarks, I want to use a lot of
different marks for 2 routes so that I can QoS based on the marks
ip rule looks like this:
0: from all lookup local
32751: from all fwmark 31 lookup dslout
32752: from all fwmark 30 lookup dslout
32753: from all fwmark 29 lookup dslout
32754: from all fwmark 28 lookup dslout
32755: from all fwmark 27 lookup dslout
32756: from all fwmark 26 lookup dslout
32757: from all fwmark 25 lookup dslout
32758: from all fwmark 24 lookup dslout
32759: from all fwmark 21 lookup dslout
32760: from all fwmark 11 lookup dslout
32761: from all fwmark 10 lookup fibout
32762: from all fwmark 8 lookup dslout
32763: from all fwmark 7 lookup fibout
32764: from all fwmark 2 lookup dslout
32765: from all fwmark 1 lookup fibout
32766: from all lookup main
32767: from all lookup default
now when I mark say web traffic with 8 or 2 it goes to the dslout table,
but if I use 11 or 21 it doesn't. I guess I've a limited number of marks to
play with?
kernel 2.4.20, iptables 1.2.7.a with wrr and imq
Thanks
_____________________________________________________________
David Watson, Network Manager, Team17 Software Ltd.
Phone: +44-1924-267776 Fax: +44-1924-267658
_____________________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-03-04 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 18:27 David Watson [this message]
2003-03-04 18:58 ` [LARTC] Routing based on fwmark Martin A. Brown
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-104680270328524@msgid-missing \
--to=david.watson@team17.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.