From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: shemminger@linuxfoundation.org, netdev@vger.kernel.org
Subject: Re: Fwd: iproute2 / xtables / undefined symbol in m_ipt again
Date: Wed, 2 Jul 2008 21:58:00 +0300 [thread overview]
Message-ID: <200807022158.00343.denys@visp.net.lb> (raw)
In-Reply-To: <20080702111139.43ca320a@extreme>
I did test on vanilla iptables and git iproute2.
Only thing i change - corrected path to libraries in iproute2 sources.
How it can work correctly if iptables doesn't add param_act (which is inside xtables.o) to anything else than iptables/ip6tables/iptables-restore/iptables-multi binaries?
It is physically impossible. Possibly your iproute2 using old iptables library, since in new one path to libraries is changed.
The new iptables will show:
tablename: mangle hook: NF_IP_PRE_ROUTING
target: MARK xset 0xc8/0xffffffff index 0
old:
tablename: mangle hook: NF_IP_PRE_ROUTING
target: MARK set 0xcb index 0
Command:
$TC filter add dev $2 parent ffff: protocol ip prio 10 u32 \
match u32 0 0 flowid 1:1 \
action ipt -j MARK --set-mark ${id} \
action mirred egress redirect dev ifb0
On Wednesday 02 July 2008, Stephen Hemminger wrote:
>
> This needs more investigation. I think it is more of problem with your iptables
> library installation than iproute. It works fine for me build/run on Ubuntu Hardy.
>
--
------
Technical Manager
Virtual ISP S.A.L.
Lebanon
next parent reply other threads:[~2008-07-02 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807021308.20117.denys@visp.net.lb>
[not found] ` <20080702111139.43ca320a@extreme>
2008-07-02 18:58 ` Denys Fedoryshchenko [this message]
2008-07-02 19:10 ` Fwd: iproute2 / xtables / undefined symbol in m_ipt again Stephen Hemminger
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=200807022158.00343.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=shemminger@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).