From: Lopsch <lopsch@lopsch.com>
To: netfilter@lists.netfilter.org
Subject: Re: CONNMARK patch do not work in kernel 2.6.9
Date: Tue, 14 Dec 2004 02:41:58 +0100 [thread overview]
Message-ID: <41BE44E6.4010407@lopsch.com> (raw)
In-Reply-To: <1916839365.20041214012818@comtv.ru>
[-- Attachment #1: Type: text/plain, Size: 3790 bytes --]
Evgeniy Zaitsev schrieb:
> Hello, Lopsch.
>
> Sunday, December 5, 2004, 6:19:55 PM, you wrote:
>
>
>>>I try to use latest patch-o-matic to
>>>I have tried to use last patch-o-matic
>>>(patch-o-matic-ng-20040621.tar.bz2 also do not work)
>>>for addition of purpose CONNMARK in iptables on a kernel 2.6.9
>>>
>>>But the patch is not set, as does not find the necessary lines of a code in a file
>>>linux/net/ipv4/netfilter/ip_conntrack_standalone.c
>>>
>
> L> Try this:
>
> Thanks, Lopsch, patch are works. It appears, for its imposing it was
> necessary to take advantage switcg "-F 3", As with "-F 2 " don't
> passed any chunks.
>
> Unfortunately, I have faced the same problem, as with previous a patch (patch-o-matic-ng-20040621)
> on a kernel 2.6.7
>
> iptables -t mangle -A PREROUTING -i eth1 -j prert_services_ctv_spec_ctv
> iptables -t mangle -A prert_services_ctv_spec_ctv -s 10.0.0.0/8 -m mac --mac-source 00:90:27:A7:58:21 -m
> state --state NEW -j CONNMARK --set-mark 0x40
> iptables -t mangle -A prert_services_ctv_spec_ctv -m mark --mark 0x40 -j ACCEPT
> iptables -t mangle -A prert_services_ctv_spec_ctv -s 10.0.0.0/8 -m state --state NEW -j CONNMARK
> --set-mark 0x60
> iptables -t mangle -A prert_services_ctv_spec_ctv -m mark --mark 0x60 -j ACCEPT
>
> In this rules list a command
> iptables-t mangle-A prert_services_ctv_spec_ctv-m mark - mark 0x40-j ACCEPT
> does not work:
>
> # iptables -t mangle -nxvL prert_services_ctv_spec_ctv
> Chain prert_services_ctv_spec_ctv (1 references)
> pkts bytes target prot opt in out source destination
> 5 304 CONNMARK all -- * * 10.0.0.0/8 0.0.0.0/0 MAC
> 00:90:27:A7:58:21 state NEW CONNMARK set 0x40
> 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MARK match
> 0x40
> 116 6048 CONNMARK all -- * * 10.0.0.0/8 0.0.0.0/0 state NEW
> CONNMARK set 0x60
> 57464 48953156 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MARK match
> 0x60
>
>
> This commands used for "not simple routing":
>
> ----- router1 ---\
> LAN1 LAN1-router,NAT / mark 0x40 \
> 192.168.1.0/24 ---> 192.168.1.1(eth1) LAN2 10.0.0.0/8
> \ mark 0x60 /
> ----- router2 ---/
>
>
> LAN2, 10.0.0.0/24 it is possible to enter two different ways, through
> router1 with mac addr 00:90:27:A7:58:21 and through router2.
>
> Inside LAN1 are a servers which from LAN2 are visible under different
> IP-addresses (router1 and router2 addresses).
> Therefore it is necessary what the inquiry coming through router1 in
> LAN1, back came back as through router1. For router2 - it is similar.
>
> For this purpose I marking incoming connections (from LAN2) in a chain
> "prert_services_ctv_spec_ctv" (*mangle table) and when packets on this connection come back in LAN2,
> they depending on marks (I apply - restore-mark) on the same channel on whom they and came.
>
> But the matter is that a command
> iptables-t mangle-A prert_services_ctv_spec_ctv-m mark - mark 0x40-j ACCEPT
> does not work, therefore all entering connections are marked as 0x60
> and are sent through router2 :(
>
> I where that was mistaken in a spelling of rules?
> I can not understand in any way. Thought, switching to kernel 2.6.9 will rescue, appeared - has not
> rescued.
>
>
>
>
Sorry I can´t help, because I don´t understand what you´re trying to
explain and the topology of that network :(.
--
PGP-ID 0xF8EAF138
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 825 bytes --]
prev parent reply other threads:[~2004-12-14 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 10:24 CONNMARK patch do not work in kernel 2.6.9 Evgeniy Zaitsev
2004-12-05 15:19 ` Lopsch
2004-12-13 22:28 ` Re[2]: " Evgeniy Zaitsev
2004-12-14 1:41 ` Lopsch [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=41BE44E6.4010407@lopsch.com \
--to=lopsch@lopsch.com \
--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 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.