From: Konrad <kcem@tlen.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Problem with marking packets...
Date: Tue, 24 May 2005 22:11:03 +0000 [thread overview]
Message-ID: <4293A677.2050802@tlen.pl> (raw)
Hello everyone...
I have a little trouble and need some help :P
How can I check on which interface the packet is going (eth0, eth1; I
have two ISP and on eth3 little LAN), using to check it TC and IMQ? (HTB
script)
I tried to mark packets, but on chain POSTROUTING this does not work...
Maybe because packets fall on IMQ before signing.
I tried marking it on FORWARD but packets also didn't hit their class.
PREROUTING is working(!), but with this I can only queued download traffic.
Problem is very essential. I need to distinguish on which interface
packet is going.
Im routing packet using this:
ip route add default via 192.168.10.1 dev eth0 table neo
ip rule add fwmark 0x03 table neo
ip route add 80.53.133.24/29 dev $DEV_DSL table dsl
ip rule add fwmark 0x04 table dsl
And I'm marking traffic as I want.
IMQ is working in AB mode. I have src IP before nat, and dst after nat.
Upload traffic is going to IMQ1 here:
iptables -t mangle -A POSTROUTING -j IMQ --todev 1
Some ideas?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-05-24 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 22:11 Konrad [this message]
2005-05-26 8:39 ` [LARTC] Problem with marking packets Konrad
2005-05-26 10:18 ` Andy Furniss
2005-05-26 12:50 ` Konrad
2005-05-26 19:20 ` Andy Furniss
2005-05-26 23:19 ` Konrad
2005-05-30 15:29 ` Andy Furniss
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=4293A677.2050802@tlen.pl \
--to=kcem@tlen.pl \
--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.