Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: hanhbnetfilter <hanhbnetfilter@yahoo.com.cn>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Incomprehensive problem with tc filter & mangle
Date: Mon, 13 Jan 2003 06:47:59 +0000	[thread overview]
Message-ID: <marc-lartc-104244058902986@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104197594226744@msgid-missing>

iptables rules must set on right netcard
you shuld set it on eth2(eth0) not on eth1

_________________________________________________________
Do You Yahoo!? 
"洋节土节都要过,大礼小礼不放过"
http://cn.promo.yahoo.com/holiday/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-01-13  6:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 21:44 [LARTC] Incomprehensive problem with tc filter & mangle Ronan LAVIEC
2003-01-07 23:55 ` Victor Cassar
2003-01-08 10:50 ` Ronan LAVIEC
2003-01-08 18:32 ` Stef Coene
2003-01-08 18:57 ` Ronan LAVIEC
2003-01-08 19:07 ` Stef Coene
2003-01-13  6:47 ` hanhbnetfilter [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-104244058902986@msgid-missing \
    --to=hanhbnetfilter@yahoo.com.cn \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox