From: Arindam Haldar <arindamhaldar@inbox.lv>
To: NETFILTER <netfilter@lists.netfilter.org>
Subject: iptables mangle & iproute
Date: Wed, 18 Dec 2002 08:41:28 +0530 [thread overview]
Message-ID: <3DFFE760.1020204@inbox.lv> (raw)
i all,
an extract of my rule tables...
40: from all to 203.x.x.64/25 lookup TABLEa
40: from all fwmark 40 lookup TABLEa
50: from 203.x.x.0/24 lookup TABLEb
iptables mangles are as follows..
root@ICG:root# iptables -nvL -t mangle
Chain PREROUTING (policy ACCEPT 7995K packets, 2646M bytes)
pkts bytes target prot opt in out source destination
85 6908 MARK all -- * * 0.0.0.0/0 203.x.x.64/25
MARK set 0x40
Chain INPUT (policy ACCEPT 526K packets, 252M bytes)
pkts bytes target prot opt in out source destination
0 0 MARK all -- * * 203.x.x.64/29 0.0.0.0/0
MARK set 0x40
im not able to find the problem for why i cant trace or ping to
203.x.x.64/25 network and vice-versa.
i want to add that all forwading rule are there.. it was working when i
didnt used _fwmark_ ..want to use fwmark for policy routing...
one last but not least things to ask is --> _marking_ based policy
routing a good solution that one without _marking_ ???
thanking in advance...
A.H
reply other threads:[~2002-12-18 3:11 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=3DFFE760.1020204@inbox.lv \
--to=arindamhaldar@inbox.lv \
--cc=netfilter@lists.netfilter.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